Michaelco

I have 38 programs. No other programs run when I execute the 'Then' section of code of the ISY Query - I don't "get it".

Thanks, for the suggestion that I verify the "Trigger Reverse" - it is still de-selected. I forgot to say, the system has been running well, and the last programing changes I made was March 9th - and, in a different area. Up until yesterday, it has behaved as I would have expected. This morning, for whatever reason, the gate status changed state 14 seconds after the 3 am ISY Query was run. And, the outdoor lights turned on (as they should if the gate status went to 100%). I don't believe the "Status 'The Gate Status' is not off" is the reason the gate opened (or why the driveway lights came on yesterday). If the code was "Status 'The Gate Status' is On" I would expect the lights to come on (as they did). For me, the two mysteries are 1) Why the gate status changed state after the ISY Query this morning, 2) and why the Driveway lights came on after the ISY Query ran the day before. When I ran the ISY Query 'Then' code this morning (11:03 am), nothing else ran - e.g., looking at the log, or the program list in the console. The gate didn't open, nor did the driveway lights come on. Maybe more data points will come tonight :~{

I have had some of the outdoor lights coming on during the last two days. Both this morning and yesterday morning, at 3:00 am. This time period corresponds to the ISY Query, however, I only have three scenes I've set up, and any correlation to the ISY Query doesn't make sense. Furthermore, the entrance gate showed a status of opening right after the ISY Query ran - there should be no connection between the ISY Query and the entrance gate opening, so this event doesn't make sense. I've color coded three different events in the log entries (below) - I also attached the excerpt of the log because of format issues with the forum post. Any insights, or suggestions would be appreciated. I have changed the time the ISY Query fires off - from 3 AM to 8 AM, to reduce the risk of dear walking through the entrance - which is the primary reason we have enclosed the property. History for : Yesterday morning: Driveway lights came on at 3 am - they were the only lights that came on The only scene the driveway lights are associated with is "Scene OutDoor Path Light", which affects the following 4 sets of lights. 1) Driveway Lights 2) Entry Porch Lights 3) Garage Outside North 4) Garage Outside West So, if the "Scene OutDoor Path Light" triggered, I would have expected more than the 5 driveway lamp posts to turn on. This morning, was a different situation. 14 seconds after the ISY Query ran, the entrance gate status changed state. This triggered the "Scene OutDoor Path Light" on, and the set of lights embedded in the sidewalk (Paver Lights) to turn on as well. 5 minutes later, the GateIsOpenCloseIt program tries to close the gate without success - the GateIsOpenCloseIt program's objective is to ensure the gate is closed during the evening after 8 pm. I haven't seen any explanation/reason for the gate opening at 3 am, but upon opening, I would have expected the path lights to come as they did - and stay on until the gate status changed to closed. Quite baffling! I am using the "sense" side of the Insteon 2450 I/O module to monitor the gate closed limit switch, and the normally open contact of the same module to open/close the gate. ==================== Applicable portion of Logs ====================== Yesterday: Scene:ISY Status Query Tue 2015/04/21 03:00:00 AM Program Log Driveway Lights Status 100% Tue 2015/04/21 03:00:13 AM System Log Today: Scene:ISY Status Query Wed 2015/04/22 03:00:00 AM Program Log The Gate Status Status 100% Wed 2015/04/22 03:00:14 AM System Log Scene:Scene OutDoor Path Light On Wed 2015/04/22 03:00:15 AM Program Log Garage Outside West Status 100% Wed 2015/04/22 03:00:16 AM System Log Garage Outside North Status 100% Wed 2015/04/22 03:00:16 AM System Log Entry Porch Light Status 100% Wed 2015/04/22 03:00:16 AM System Log Driveway Lights Status 100% Wed 2015/04/22 03:00:16 AM System Log Sidewalk Paver Lights On Wed 2015/04/22 03:00:16 AM Program Log Sidewalk Paver Lights Status 100% Wed 2015/04/22 03:00:17 AM System Log Gate Open-Close Off 0 Wed 2015/04/22 03:05:15 AM Program Log ========================= End of logs ========================================= ========= Referenced Programs ============ TempPathLightsOn =========================================== If Status 'The Gate Status' is not Off Then Set Scene 'Scene OutDoor Path Light' On Run Program 'SidewalkLights Temp On' (If) $intAllPathLightsAreOn = 1 Else - No Actions - (To add one, press 'Action') =========================================== GateIsOpenCloseIt =========================================== If Status 'Gate Open Status' is On And $sBetween8PmAnd5Am is 1 Then Send Notification to 'TextMichael' content 'Closing Gate' Send Notification to 'TextJane' content 'Closing Gate' Wait 5 minutes Set 'Gate Open Control' Off Else - No Actions - (To add one, press 'Action') Wait 5 minutes to close gate - in case coming home between 8 pm and 5 am - want to allow enough time to get through the gate before this gate keeper program closes the gate automatically =========================================== ================== End of Referenced Programs ====================== UD Log.pdf

Thanks - makes sense, now that you provide the answer :~}

I'm finally getting around to incorporating one of the Insteon 2842 motion sensor I bought back in January, and getting odd results during setup. I went to link the sensor (via Liink Sensor menu item) with the ISY 994, and entered in the devices address, and a friendly name "Driveway Motion". The name was altered by the ISY to "Driveway Motion - Low Bat". The battery should be new, but replaced it to rule out a potential low battery problem. Deleted the device and added it back in via Link Sensor menu choice. Same thing happened - friendly name I gave it was altered as before. The sensor didn't appear to work at first, but seems to be doing fine now. Just want to ensure the "- Low Bat" addendum to the name I entered isn't indicating some issue. Normal, or questionable?

Thanks

So, if I had used "Status 'Gate Outside Safety Loop Sens' is On" instead, it would create a change of state on both the "driving over the sensor" and "driving off the sensor"? Would it be accurate to say the code after the Wait command would not execute, if the "driving off the sensor" occurred prior to the Wait period completing? Thanks for all of the responses - the subtleties are not always in the forefront of my mind...

Are you sure? ==== LeeG posted the following when I posted having problems with code not executing after the Wait command (back in early December) ===== When a Wait or Repeat statement is executed the If clause can run again when any of the trigger conditions change. For the statements after the Wait not to execute it means a trigger condition changed while inthe Wait causing the If to execute again with a False result causing the Else clause to execute. ======================================= I also got confirmation from UDI support that the ISY re-evaluates the conditional (the “IF”) of the program, and if it has changed during the Wait period, the “Then” code won’t continue executing from the line of code following the Wait. This seemed to be the case prior to a couple of weeks ago - not sure what changed, but the behavior is different.

I thought I understood the nuances of using the Wait command, but apparently I don't. I noticed a couple weeks ago, something that had been working correctly for well over a month no longer did. The program that no longer works correctly was to detect if a vehicle parked for more than 20 seconds in an area outside our gate. If so, a counter (intTotStoppedAtGate) would be incremented. Another program automatically opens the gate when my phone comes within range of my home, but only if the intTotStoppedAtGate is zero - The ISY will send a text notification to my phone letting me know of possible deliveries if intTotStoppedAtGate is greater than zero. The reason I want to inhibit the gate from automatically opening is companies like Fedex and UPS will leave the packages on the inside of the gate where the potential for damage could occur when the gate opens. Not sure how they get packages over the gate, but I’m sure they are gently placed on the driveway :~}. I’m using an Insteon I/O module (model 2450) to relay a signal to the ISY when the sensor (inductive loops) in the road detects a vehicle. In order to try to understand what’s going on, I simplified the way I was detecting the parked vehicle -so this is not the code that had been working for months, however I can’t see why the intTotStoppedAtGate counter is incremented when I am only driving over the sensors for a period of 3 seconds. My understanding, is the code following the Wait command won't execute if the condition ( Control 'Gate Outside Safety Loop Sens' is switched On) is no longer true when the Wait period is over. This baffles me as the Loop Sens is only on for 3 seconds, and the Wait period is set for 20 seconds. Any insights on this would be appreciated. ========= Here is the code I am using =========== If Control 'Gate Outside Safety Loop Sens' is switched On Then Wait 20 seconds $intTotStoppedAtGate += 1 Send Notification to 'TextMichael' content 'Someone At the Gate' Run Program 'FlashLight' (If) Else - No Actions - (To add one, press 'Action') ========================================== Here is the section of the log which shows the sensor detecting the car as I drove down the driveway. Yet, the intTotStoppedAtGate counter was incremented. Gate Outside Safety Loop Sens Status 100% Sat 2015/03/07 04:33:18 PM System Log Gate Outside Safety Loop Sens Status 0% Sat 2015/03/07 04:33:21 PM System Log

Not accessing the admin console via a browser - I'm using the ISY994 Administrative Console java app

There were a couple areas where I have needed to quit ISY to continue working. One area is when saving a newly created program, which is fairly repeatable. I'm not as clear on the sequence which requires a "Admin restart" for the second area - which is, creating a new variable. In both cases, I don't believe it's limited to creating a new program or variable, and most likely applies to editing an existing program or var. Sequence for first issue: Create "New Program", add Condition code (IF), and Action (THEN), edit New Program name, and Save without leaving the New Program text box. Get the Save Programs dialog, but the dialog doesn't release and stays visible (and empty - without thermometer). Have to quit the ISY to continue - there may be some kinder way to recover, but I haven't found it. Add "New variable", set Init, and Value, and edit the variable name. Save without leaving the variable Name text box. This will, at a minimum, fail to allow me to switch to Details tab without first changing focus to another field on the variable window. Sometimes, need to quit ISY Admin to continue.

Thanks for the reminder - thought this was a newbie related issue well suited for the forums. I think I know how the issue was created. The Admin console doesn't appear to work well when saving without first exiting a field which has been modified. It has been slowly "training" me to exit the fields I have been editing prior to saving, but I'm slow to train

I wrote the following, and it worked as I would have expected: ============= Test code ============== If Control 'Living Room Lamplink' is switched On Then $Int_TestVar7 += 1 Wait 15 seconds $Int_TestVar8 += 1 Else - No Actions - (To add one, press 'Action') =================================== I went back to my TempPathLightsOn program and changed the line of code (Wait command) - changed both the minute and second spinner values it to 0 minutes and 16 seconds respectively. Looks like the problem with the wait command was some sort of corruption, as executing the "Then" worked as I would have expected. I then changed back to 10 minutes and 15 seconds, and reran the "Then" section - worked fine. A bit frustrating to have this happen the first time using the Wait command, as I would not have expected a problem with a line of code created by selecting drop downs and spinners. Thanks for your confirmation on how the Wait should work - I should have created the little test program, when I first hit the problem

I'm looking for a relay contact closure (which is connected to the I/O Linc sensor input). I'm new to ISY and Insteon, but thought if I'm monitoring the sensor side of the I/O Linc module, I should look at the Status. Is this not the case? When I view the logs, I can see the Status does change when I drive over the safety loops, and the "Then" section of code in TempPathLightsOn executes. However, It appears the code after the "Wait 10 minutes and 15 seconds" fails to execute. The line of code ($Int_TestVar3 += 1) which precedes the Wait command executes, but a similar line of code ($Int_TestVar2 += 1) which is after the Wait command fails to change. When I look at the variables when I select the program tab in Admin I see the "last change" to $Int_TestVar2 was Nov 30th, which was the date when I created the var - the value hasn't been altered in the dozen times I've run my tests. I would have thought the code prior to the wait command would have executed, and after 10 minutes and 15 seconds specified by the Wait command, the ISY would continue with the next line of code - e.g., $Int_TempPathLightsOn = 1 I have little doubt I'm doing something that the ISY doesn't like, but have no idea what it is. I will play around with a new program that does little more than increment a var before a wait command and increments a second var after the wait command. And, view the "last changed" column to see if both increments occur.

That's consistent with what I would have thought. In further checking, I see the PrcsdSafetyLoops flag does change to 1, but is reset very quickly. In one test it reset 1 minute after it had been set, and in a second test it reset after 37 seconds. Needed to have my laptop with me in the car to see it, as the "action” was over by the time I got into the house, so missed seeing the var change state. Glad the wifi reached the end of the driveway. The interesting thing, to me, is int_PrcsdSafetyLoops is only set two places - it’s set to a 1 in the “Then” section of TempPathLightsOn and is reset to 0 in TempPathLightsOff. Running of TempPathLightsOff should have been delayed 10 minutes and 15 seconds by the " Wait 10 minutes and 15 seconds” line of code. Another interesting thing, is if TempPathLightsOff is executed (resetting the int_PrcsdSafetyLoops, why weren’t the other lines of code executed - like turning off the lights, and Int_TestVar4, etc.

I have a program that turns on path lighting, for a little over 10 minutes, if it is nighttime and a vehicle has driven onto the driveway. I am not currently using scenes, but will in the final. This is the first ISY program I've written which makes use of a Wait command, so I may be missing understanding on how it works. In general, what I'm trying to do is straight forward, but the programs for managing the path lighting are a bit more complex than the other programs I've written. I am using variable called int_PrcsdSafetyLoops which is to limit execution of the code that turns the lights on to one time - even if there are multiple triggers each time a vehicle drives down the driveway. I also have some sidewalk lights which are scheduled to come on each night for 4 hours (after sunset), which should ignore the command to turn off when someone drives down the driveway and it's still within the 4 hour scheduled time period. Reason for int_PrcsdSafetyLoops var: There actually are two safety loops, and right now I have taken both their contact outputs and wired them to the I/O Linc module. So, if I drive the car out of the driveway and back during my testing, I will get 4 closures of the I/O Linc. The goal is to trigger off the first contact closure and ignore the remaining 3. At some point, I may add direction info, so the lights only come on when we arrive at the property, but I may not worry about that issue. The wiring will be changed so it only takes input from the Outside Safety loop, but this will involve more time than I had between rain storms. Plus, I should be able to write code that only looks at the first occurrence - I'm guessing it's something simple, but for the life of me, I can't see why it won't ignore. The lights turn on fine, but the lights fail to turn off, and the flag int_PrcsdSafetyLoops never changes from the value 0. int_TestVar3 increments by a count of 4 each time I drive over the two loops going out the driveway, and back over the loops coming back on the property. int_TestVar also increments by a count of 4, which I believe happens when I drive past the loops - going from a contact closure state to an open state. Int_TestVar2, Int_TestVar4 and Int_TempPathLightsOn never changes, which could be confirmation the code after the WAIT command never executes. Any ideas on where I'm going astray? Is there a log that displays not only the events, but also lists variable change of state? Michale ================== main code pieces ============== Program TempPathLightsOn If $sIsDark is 1 And Status 'Gate Outside Safety Loop Sens' is On And $int_PrcsdSafetyLoops is 0 Then $int_PrcsdSafetyLoops = 1 Set 'Garage Outside West' On Set 'Garage Outside North' On Set 'Out Mod A' On $Int_TestVar3 += 1 Wait 10 minutes and 15 seconds $Int_TempPathLightsOn = 1 Run Program 'Temp Path Lights Off' (If) $Int_TestVar2 += 1 Else $int_TestVar += 1 Comments: Mod A controls the sidewalk lights. They can be turned on anytme (while dark), but they won't be turned off if the time is during their normal "On" time period (as controlled by sLightPathOnVar. Var int_PrcsdSafetyLoops is to protect against multiple triggers from the two safety loops. The "Then" section should only execute once when a vehicle drives accross the safety loops, turn on the desired lights, and turn the lights back off after the wait period has timed out. Then reset the vars. Program TempPathLightsOff If $Int_TempPathLightsOn is 1 Then Set 'Garage Outside West' Off Set 'Garage Outside North' Off Run Program 'Sidewalk Lights Temp Off' (If) $int_PrcsdSafetyLoops = 0 $Int_TempPathLightsOn = 0 $Int_TestVar4 += 1 Else - No Actions - (To add one, press 'Action') Comments: Mod A controls the sidewalk lights. They can be turned on anytme (while dark), but they won't be turned off if the time is during their normal "On" time period (as controlled by sLightPathOnVar)

I'm looking for Insteon devices to do two separate functions at an entrance gate. The first is to allow a switch closure function for a gate operator, which will get triggered either via mobile device manually, or when a geofence rule has been met Essentially looking to control contact to closure. I believe the Insteon's Micro Open/Close 2444-222 device would do the job, but want to confirm before buying (possibly the wrong device). The second area is to alert when a vehicle drives across the loops which are buried under the driveway. I have relay contacts which change state when the loop detector circuit is triggered - I could handle a module that worked off of either dry contact closure, or senses low voltage change of state. I believe the I/O Linc 2450 would do the job, however would rather have a micro module that could tuck inside the enclosure. Are there other choices that can be "wired in"? Are there any Insteon devices (or compatible) that can provide audible alert when vehicle is detected?