belias

I have a few Insteon Micro Dimmers set up with toggle switches on the input. I would like to create a program that detects the switch position. In other words... If [light output] is ON, AND [light switch] is OFF THEN WAIT 15 minutes Set [light output] to OFF This way the light only automatically shuts off if it was turned on by a program or scene request, but won't automatically turn off if the switch was turned on. Is this possible? Thanks, Brian

OK - I'll email support and ask. Thank you!

I have a few older ISY 99i units that I would like to use as basic automation controllers (through the network module). They're great, reliable and easy to program... Is there any way to do this without connecting a PLM? Thanks.

I checked out the thread on the new leak sensors, and it looks like the major change is that the new version does not update the node status when the sensor goes from wet to dry. The issue (if I understand it correctly) is that this creates the situation where everything can look fine in the program (Status = 1; no emails) even though the sensor could be stuck in a Wet condition (and unable to report a new leak). I took a look at the programs, and came up with the following thoughts on a modification. I don't have the new version of the leak sensors, so it will be up to someone else to test and report back. Open for suggestions on how to streamline this as well... "Change Log" 1. If a heartbeat signal is received and the sensor is reporting "wet", the status will remain at 9 (causing future emails to be sent) 2. If a heartbeat signal is missed and the sensor is reporting "wet", the status will change to 2 (heartbeat missed; causing future emails) 3. This preserves the functionality of the Variable Control 3 program (regardless of wet / dry) to ensure that Variable Control 2 is running correctly 4. The modified program should work with old and/or new sensors Program Modifications (untested) 1. Variable Control 2 is split into 2 separate programs: Variable Control 2a If ( Control 'Leak Sensors / Kitchen Sink-Heartbeat' is switched On Or Control 'Leak Sensors / Kitchen Sink-Heartbeat' is switched Off ) And Status 'Leak Sensors / Kitchen Sink-Wet' is not On Then $sLeakKitchenSink = 1 Wait 25 hours $sLeakKitchenSink = 2 Else - No Actions - (To add one, press 'Action') Variable Control 2b If ( Control 'Leak Sensors / Kitchen Sink-Heartbeat' is switched On Or Control 'Leak Sensors / Kitchen Sink-Heartbeat' is switched Off ) And Status 'Leak Sensors / Kitchen Sink-Wet' is On Then Wait 25 hours $sLeakKitchenSink = 2 Else - No Actions - (To add one, press 'Action') 2. Modify Variable Control 3 If ( $sLeakKitchenSink is 1 And Time is Last Run Time for 'KitchenSink - Variable Control 2a' + 26 hours ) Or ( $sLeakKitchenSink is 9 And Time is Last Run Time for 'KitchenSink - Variable Control 2b' + 26 hours ) Then Wait 5 seconds $sLeakKitchenSink = 3 Else - No Actions - (To add one, press 'Action') That's it...please report back any findings and I will update the original post if it works properly. Thanks. - Brian

Hi All. Glad the programs are working well, and apologies for my delay in getting back to this thread. I have updated the original program post to include the 5 second wait in the Variable Control 3 program. Thanks everyone for the feedback on this. - Brian

EricK, et al., This has been bugging me for a while (why the VC 3 program would run and set the $Leak variable to 3). I think I figured it out, and have a proposed solution. Here's the scenario for how it happens: 1. Leak sensor goes offline for 25 hours 2. The VC2 program sets $Leak = 2 and then stops running 3. Sometime later, a heartbeat signal is received 4. The VC2 program now runs and sets $Leak = 1 5. ** Here's the problem: In this instant, the $Leak variable = 1, BUT the "last run time" of VC2 hasn't been updated, so all the conditions of VC3 are met and it runs, setting the variable to 3 6. So now, the $Leak variable is stuck in 3 So, here's my proposed fix: Add a 5 second wait at the top of all VC3 programs: Then Wait 5 seconds $sLeakKitchenSink = 3 This should allow enough time for the "Last Run Time" to be updated, once the leak sensor comes back online and the VC3 program won't run. If this works, please let me know and I'll update the original post. Thanks, - Brian

Hi EricK, Sorry for my delayed response as well, but it looks like you're getting some good suggestions. If the VC2 program shows as "Running Then" in the status, I'm not sure why would get a notification email. If it continues to happen after the ISY restart, check the value of the variable itself (something like sLeakLaundry) - it should be either 1 (normal) or 2 (heartbeat missed). If it's 3 then at least we know why the email alert is being triggered...

Yup - that's exactly what I've done as well. Any time the "All Off" is pressed, the ISY waits 3 sec. and runs a program to turn that button (scene) off...

Hello, I have an 8-button KPL (latest revision from SH, just installed). Button A is the local load; Buttons B to G are various scenes; and Button H is the "Room Off" button. What I'm trying to accomplish is: pushing Button H should cause all room devices and KPL buttons to turn off. This should happen immediately on button push with no delay or KPL button flashing. So far, I've been able to get close, but not perfect (at least not without a program). Here's what I have so far: Case A - Set Button H as the controller of a scene with all room devices and all KPL buttons (A to G) as responders - Set device levels to 100% (under the main scene and under the Button H controller) - Set Button H as non-toggle OFF ---> This works, however when Button H is pressed it flashes for a few seconds on the KPL before the KPL buttons are shut off. This is a bit confusing to the user. Case B - Set Button H as the controller of a scene with all room devices and all KPL buttons (A to G) as responders - Set device levels to 0% (under the main scene and under the Button H controller) - Set Button H as non-toggle OFF ---> This results in all devices and KPL buttons turning off immediately when Button H is pressed; EXCEPT for Button H, which turns on and remains on. This is strange because it is definitely set as Non-Toggle OFF. Also, the ISY believes Button H is OFF until I query the KPL (local load), at which point is recognizes it's actually on. Pressing Button H again has no effect - it remains on until I issue an off command to the scene containing it. Any help would be greatly appreciated - even if it's just explaining WHY Case B is happening. Thanks! - Brian

f.demello: You are correct that the Leak Startup program should show an "On" under the Run At Startup column. If right-clicking and selecting "Enable Run at Startup" isn't changing the status, then perhaps someone else with a bit more ISY knowledge could chime in - this works on my unit. Also, the "normal" status of the programs is that each "Variable Control 2" program should be in a "Running Then" status (which it appears yours are). If this occurs again, please be sure to get the status of the individual leak sensor (On / Off), as well as the current state of the leak sensor variables. If all is working correctly, you should get one email per device that activates. The program should only "reset" 10 seconds after receiving an "Off" signal from the leak sensor. Hope this helps. - Brian

Hi Frank, See image below... Use the "Add And (..)" button, then use the "Move Line Up" button to move them into position. The parenthesis cause the program to be evaluated as: one from group 1 must be true AND one from group 2 must be true. Without the parenthesis, I'm not sure how to get the same result. Hope this helps. - Brian

Sure - hopefully this helps. It's in the "Schedule" section but a little hidden...

Thanks for the positive feedback...glad people are finding this useful. jzsjr: If you only see 2 nodes (wet and dry) for your leak sensors, you may have to update your ISY Firmware and remove/re-install the leak sensors. As of Firmware 4.0.1 (viewtopic.php?f=25&t=10770) the leak sensors should add with 3 nodes: dry, wet, and heartbeat. Then the programs should make more sense... LeeG: Thank you - I didn't realize heartbeat messages could be either on or off... - Brian

Sure - hope it's useful. Thanks. - Brian

I have 6 leak sensors that I have spent the past few months integrating in with the ISY. It took a while to get them to perform as I wanted, and I figured this might be helpful to others trying to figure out the same thing. Here goes... 1. Functionality 1a - A notification is sent twice a day for any problem with a leak sensor (i.e. missed heartbeat) at 9:00am and 6:00pm. This avoids the inevitable single email that I ignore and the problem goes uncorrected for weeks... 1b - A notification is sent immediately when a leak sensor is activated (and also again twice daily as above). This email is not sent repeatedly even if the sensor is "fluttering" at first activation, which it commonly does. 1c - The email notification shows the status of EVERY leak sensor (heartbeat received as expected, heartbeat missed, sensor activation, etc.) 1d - If the program monitoring heartbeat signals somehow fails or is shut down, a problem notification is sent. 1e - All functionality should survive an ISY reboot without user intervention. 2. Setup - First Leak Sensor 2a - Add the leak sensor device to the ISY, for this example we'll call it Kitchen Sink 2b - Create a state variable called sLeakKitchenSink; set Init = 1 and Value = 1 2c - Create a program called KitchenSink - Variable Control 1: If Status 'Leak Sensors / Kitchen Sink-Wet' is On Then $sLeakKitchenSink = 9 Else Wait 10 seconds $sLeakKitchenSink = 1 2d - Create a program called KitchenSink - Variable Control 2: If Control 'Leak Sensors / Kitchen Sink-Heartbeat' is switched On Or Control 'Leak Sensors / Kitchen Sink-Heartbeat' is switched Off Then $sLeakKitchenSink = 1 Wait 25 hours $sLeakKitchenSink = 2 Else - No Actions - (To add one, press 'Action') 2e - Create a program called KitchenSink - Variable Control 3: If $sLeakKitchenSink is 1 And Time is Last Run Time for 'KitchenSink - Variable Control 2' + 26 hours Then Wait 5 seconds $sLeakKitchenSink = 3 Else - No Actions - (To add one, press 'Action') Note: For ease of explanation, assume a second leak sensor named "Storage Room" has also been added using the steps above. 3. Setup - Core Components These only have to be set-up once, regardless of the number of leak sensors. 3a - Create an integer variable called iStartUp; set Init = 0 and Value = 1. 3b - Create a custom notification called "Leak Sensor Activation". This is the content I use: A water leak has been detected at the location below with a status value of "9": Kitchen Sink: (((Use "add variable" to add your sLeakKitchenSink variable here))) Storage Room: (((Use "add variable" to add your sLeakStorageRoom variable here))) ---Status Key--- 1 = Heartbeat OK (normal status) 2 = Heartbeat missed 3 = Heartbeat check program not running 9 = Leak detected ----------------- 3c - Create a custom notification called "Leak Sensor Problem". This is the content I use: A problem has been detected with a leak sensor. Details below: Kitchen Sink: (((Use "add variable" to add your sLeakKitchenSink variable here))) Storage Room: (((Use "add variable" to add your sLeakStorageRoom variable here))) ---Status Key--- 1 = Heartbeat OK (normal status) 2 = Heartbeat missed 3 = Heartbeat check program not running 9 = Leak detected ---------------- Note 1: It may take up to 36 hours for a "heartbeat missed" signal to clear. Note 2: Status Code 3 indicates the "Variable Control 2" program is not running for some reason. 3d - Create a program called Leak Startup and ENABLE RUN AT START-UP If $iStartUp is 0 Then Run Program 'KitchenSink - Variable Control 2' (Then Path) Run Program 'StorageRoom - Variable Control 2' (Then Path) Wait 5 seconds $iStartUp = 1 Else - No Actions - (To add one, press 'Action') ** Set to run at start-up ** 3e - Create a program called Leak Sensor Activation If $sLeakKitchenSink is 9 Or $sLeakStorageRoom is 9 Then Send Notification to 'Brian' content 'Leak Sensor Activation' Else - No Actions - (To add one, press 'Action') 3f - Create a program called Leak Sensor Problem If ( Time is 9:00:00AM Or Time is 6:00:00PM ) And ( $sLeakKitchenSink is not 1 Or $sLeakStorageRoom is not 1 ) Then Send Notification to 'Brian' content 'Leak Sensor Problem' Else - No Actions - (To add one, press 'Action') 3g - Test leak sensor in "wet" mode and ensure a notification is sent 4. Brief Explanation 4a - The 10 second wait in Variable Control 1 serves to stop multiple emails from being generated if the sensor "flutters" when it first activates. 4b - The Variable Control 2 program should always be in a "Running Then" state, looking for the heartbeat signal. If it's missed then it changes the variable to status = 2 which triggers a notification email. 4c - The Variable Control 3 program serves as a "watch-dog" for Variable Control 2. If it's stopped (manually, ISY issue, etc.), then it changes the variable to status = 3 which triggers a notification email. 4d - The iStartUp variable is initialized to 0 on start-up and this triggers the "Leak Startup" program to run. Without this program, the potential exists for a "dead" leak sensor to go undetected after the ISY starts up. 5. Procedure for Adding a New Leak Sensor 5a - Add device 5b - Add state variable (sLeakSensorName) 5c - Add programs: Variable Control 1, Variable Control 2, Variable Control 3 5d - Modify Leak Startup program 5e - Modify Leak Sensor Activation program and Leak Sensor Activation notification 5f - Modify Leak Sensor Problem program and Leak Sensor Problem notification 5g - Test leak sensor in "wet" mode and ensure notification is sent Edit 11/26/2013: Variable Control 2 program now allows either an Off or On signal for the heartbeat. Thanks LeeG.Edit 12/15/2014: Added Wait 5 seconds to top of Variable Control 3 program.