rleidy

I never experienced an ALL ON for all devices, but I did find my garage door opening unexpectedly. I did switch to the GoControl Z-wave controller and have not had any problem since.

Nothing in particular, I was just curious about this exception case. My understanding was that a conditional that checks the status of a device actually only compares against the status that's currently cached by the ISY - no device interaction. Techman's test indicates that a status check for is/is not responding actually hits the device. I just wondered if that was the only exception case.

Does anyone know if there are other conditionals that are active in this way? (As opposed to the passive comparison against the cached status in the ISY?)

The GFCI is at the breaker. I'm actively looking for the source of the trip, but meanwhile I want to know if/when it trips. The breaker feeds an outdoor circuit with UF cable that was installed "creatively" by the previous home owner. I've already eliminated the section of cable that was at least part of the problem, but until I get a heavy rain, I won't have confidence that it was the source of the entire problem. I've got a pond waterfall pump on the circuit and that's the main source of aeration for the pond and It should be running 24/7. I want to know if/when it stops so I can switch over to a temporary extension cord for the pump while I continue my troubleshooting of the circuit fault.

Bingo! Thanks!

I understand the concept of if/then/else. I better, since I've been a software developer for 30 years. What I'm trying to understand is under what circumstance will a program will trigger with a condition of "status device is not responding". It seems to me that a command must first be sent to the device (whether a query or ON or OFF, etc.) in order for the ISY to detect that the device is not responding and consequently update its cached status value for the device, and then trigger the program. In my scenario, the device should be ON constantly. I won't be turning it ON and OFF, so if the GFCI trips, my expectation is that the ISY won't know about it until the 3am query, and then the program would be triggered. If I want to know about the tripped circuit sooner, wouldn't I need to periodically issue my own query? This is currently a mental exercise, because I won't get a chance to install the device until this evening. I'm just trying to get a handle on what I'll need to do ahead of time. I guess I'll figure it out once I have the device installed.

I'm not sure how to do it without 2 programs. One to periodically query the device, and the other to check the status for "not responding" and send a notification. Am I missing something? Or does the check for "not responding" perform an implicit query?

Oh, okay, that's easy, thanks. I never noticed the "responding" status value. So, I would create one program to periodically query the device and then call a 2nd program to check the results of the query? Does the device Query operation complete before returning?

I'm troubleshooting an outdoor circuit that is on a GFCI circuit breaker that trips on occasion. I would like to know when the circuit trips. If I have an Insteon device on the circuit, is there a good way to detect when the ISY can no longer communicate with it?

You won't be able to wire it without a rewire to bring neutral into the box.

You can set time range programs to "run at startup" so that if power returns during the range the devices will be set to the desired state.

It might also be an intermittent communication issue. I don't have a very rigorous mesh myself, and I've seen sometimes commands never make it to the destination device.

I relocated the PLM back to its original location in the electrical room and connected it to the ISY through Cat6 wiring and patch cords, and everything seems to be working. I won't know for a few days if that will solve the intermittency that I was seeing, but it doesn't seem to be any worse.

It sounds like there's room to hope it will work. I'll give it a shot. Thanks, all.

A little history: I had my ISY and PLM co-located in my electrical room, with the PLM plugged-in to an outlet right off the main panel and a short Cat6 cable between the ISY and PLM. Due to real-or-perceived issues with the IOlinc controlling the garage door opener, I decided to switch to a Z-Wave controller for the GDO. I had to move the ISY/PLM to the center of the house to get the closer to the garage, and with a couple Z-Wave outlets in between, the ISY is able to control the GDO about 80% of the time (not great, but getting there). However, I'm now having issues with Insteon devices with the PLM at its new location. There's an even greater lag than normal in program execution triggered by motion sensors, and sometimes KBL LED's are getting out-of-sync. So, my thought is that I move the PLM back to the electrical room and use the Cat6 though the structured wiring panel to connect it to the ISY. Is this likely to work at all or cause me any new issues? I'm guessing there's probably 50ft of Cat6 cable between the two, and it would have taken me less time to hook it up than to write this post, but I wanted to make sure I wouldn't harm anything before I tried it. Thanks!

If the main issue is that lights are not turning off due to the program being interrupted during a WAIT, can you not simply move the guts of the Then clause into a separate program that's disabled, and then call that program's Then path from the triggered program? This will provide the timer reset functionality and since the sub-program has no trigger, it will always run to completion.

Having just purchased an ISY earlier this year, I am still a newbie at ISY programming. I've found that regardless of one's programming experience with more transitional languages, the ISY environment and programming can sometimes throw you for a loop. Yesterday, I ran into an issue that took some head-scratching to figure out what was going on. But, once I recognized the cause, it was an "Oh. duh." moment. I share that issue below, and hope that other more experienced ISY programmers will jump in and share their own bite-sized tidbits of wisdom on ISY programming problems/solutions/workarounds/etc. Here's my Gotcha: I have a program to turn on some outside lights when there's motion within a range of hours when it's dark. After 10 minutes, it turns them off. It seemed simple enough, but yesterday I discovered that all of the lights were sill on in the middle of the day. I'm sure the experts will spot the problem immediately. It took me a little longer. Driveway Motion - [ID 000F][Parent 0010] If From Sunset To Sunrise + 30 minutes (next day) And Control 'Outside / Front Door Motion Sensor-Sens' is switched On Then Run Program 'Christmas Lights' (Then Path) Wait 2 seconds Set 'Entryway KPL.1' On Wait 2 seconds Set 'Outside / Lightpost' On Wait 10 minutes Set 'Outside / Lightpost' Off Wait 1 minute Set 'Entryway KPL.1' Off Wait 1 minute Run Program 'Christmas Lights' (If) Else - No Actions - (To add one, press 'Action') The thing that bit me was that I didn't account for all reentrancy paths. In my case, I left for work that day less than 10 minutes prior to 'Sunrise + 30 minutes', triggering the program by my motion, and all the lights came on. While the program was in the 'Wait 10 minutes', the time went past 'Sunrise + 30 minutes' causing the program to run again, aborting the running program, and the program took the Else path, leaving all the lights ON. My takeaway was that I need to consider all reentrancy paths in programs that can be interrupted (due to Wait, Repeat..) To fix this, I believe all I need to do is place the contents of the Then block into a separate program (disabled) and simply call its 'Then' path from this program. The separate program will only be reentered with continued motion that resets the 10 minutes ON timer, which is what I want. Regarding the separate 'Christmas Lights' program: The Christmas lights are ON for a wider time range, so that's in a separate program. Calling the 'then' path forces them ON. Later, calling the 'If' allows them to stay On or go OFF according to that program's time range. Anyone else have some programming gotcha's to share?

I had the backup issue, too. This link had info that fixed it for me: http://forum.universal-devices.com/topic/11762-cannot-backup-isy/?do=findComment&comment=127682

I just ordered the Z-Wave daughterboard from UD today. Do you have any recommendations for a Z-Wave garage door controller with door status? Then I could re-purpose the iolinc for something else. Any thoughts on the GoControl/Linear GD00Z-4?

Possible ELK in my future.

Thanks for your diagnosis, LeeG. If the relay had been activated, what event or events should I see in the log? I decided that I wanted to have the sensor still attached but have the relay disconnected. When I went to unscrew the N/O and COM wires, I found that the COM wire was loose and partially out of the connector. It wasn't close to the N/O wire, so I don't think that they were making contact with each other and causing the opener to activate (but that would explain the behavior I'm seeing if they did). And I can't see that a loose COM could cause the iolinc to misbehave. But, it shouldn't have been loose, so I went ahead and tightened it down and left the relay connected. I'll keep it connected until I get another phantom open. I hope it's not a neighbor's garage remote activating mine - I know that's a long shot, but this weekend I'll recode the transmitters. I've attached the saved device links table for the iolinc in case that's helpful. I also did a compare with the PLM table, and the were identical. The last 4 rows were identical/ignore. (What's that mean?) Thanks for the help.

36.88.5E is a motion sensor, and it is a controller for a hall light. That hall light is the load on a KPL. On that KPL, one of the non-load buttons controls the iolinc for the garage door opener via a program. That program is: Open Garage Door - [ID 001F][Parent 001E] If Control 'Back Hall KPL.1 / Back Hall KPL.A' is switched On Or Control 'Entryway KPL.1 / Entryway KPL.A' is switched On Or Control 'Kitchen / Kitchen KPL.1 / Kitchen KPL.H' is switched On Then Set 'Garage / Opener-Relay' On Else - No Actions - (To add one, press 'Action') Originally, I was using a scene that consisted of the iolinc as a responder and the 3 KPL buttons as controllers. When I started experiencing the phantom opening, I deleted the scene and created the equivalent program to see if the problem persisted, which it did. The iolinc relay is not a member of any other scene or program. The buttons on each of the KPLs are set to non-toggle ON and their LED state is controlled by this program: Garage Door Status - [ID 0013][Parent 0012] If Status 'Garage / Opener-Sensor' is On Then Set Scene 'Garage / Scene - KPL Garage Door' Off Else Set Scene 'Garage / Scene - KPL Garage Door' On The scene 'Garage / Scene - KPL Garage Door' is just the 3 buttons on the KPLs all being responders. Here is a full 30 seconds of events before the garage door opened. Tue 12/08/2015 06:31:02 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 CB 11 01 LTONRR (01) Tue 12/08/2015 06:31:02 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:02 PM : [D2D EVENT ] Event [36 88 5E 1] [DON] [1] uom=0 prec=-1 Tue 12/08/2015 06:31:02 PM : [ 36 88 5E 1] DON 1 Tue 12/08/2015 06:31:02 PM : [D2D-CMP 001A] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:02 PM : [D2D-CMP 0016] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:02 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 CB 11 01 LTONRR (01) Tue 12/08/2015 06:31:02 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:02 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:02 PM : [INST-SRX ] 02 50 36.88.5E 38.FF.8F 41 11 01 LTONRR (01) Tue 12/08/2015 06:31:02 PM : [Std-Cleanup ] 36.88.5E-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 12/08/2015 06:31:02 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:03 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:03 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:03 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:03 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:03 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:03 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:14 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 CB 11 01 LTONRR (01) Tue 12/08/2015 06:31:14 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:14 PM : [D2D EVENT ] Event [36 88 5E 1] [DON] [1] uom=0 prec=-1 Tue 12/08/2015 06:31:14 PM : [ 36 88 5E 1] DON 1 Tue 12/08/2015 06:31:14 PM : [D2D-CMP 001A] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:14 PM : [D2D-CMP 0016] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:15 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 CB 11 01 LTONRR (01) Tue 12/08/2015 06:31:15 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:15 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:15 PM : [INST-SRX ] 02 50 36.88.5E 38.FF.8F 46 11 01 LTONRR (01) Tue 12/08/2015 06:31:15 PM : [Std-Cleanup ] 36.88.5E-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Tue 12/08/2015 06:31:15 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:16 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:16 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:16 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:17 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 C7 06 00 (00) Tue 12/08/2015 06:31:17 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=1 Tue 12/08/2015 06:31:17 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:19 PM : [INST-SRX ] 02 50 34.88.C7 00.00.01 CF 11 00 LTONRR (00) Tue 12/08/2015 06:31:19 PM : [Std-Group ] 34.88.C7-->Group=1, Max Hops=3, Hops Left=3 Tue 12/08/2015 06:31:19 PM : [D2D EVENT ] Event [34 88 C7 1] [DON] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:19 PM : [ 34 88 C7 1] DON 0 Tue 12/08/2015 06:31:19 PM : [D2D EVENT ] Event [34 88 C7 1] [ST] [255] uom=0 prec=-1 Tue 12/08/2015 06:31:19 PM : [ 34 88 C7 1] ST 255 Tue 12/08/2015 06:31:19 PM : [D2D-CMP 0020] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:19 PM : [D2D-CMP 0013] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:19 PM : [D2D-CMP 000D] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:19 PM : [D2D-CMP 000A] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Tue 12/08/2015 06:31:19 PM : [INST-SRX ] 02 50 34.88.C7 38.FF.8F 45 11 01 LTONRR (01) Tue 12/08/2015 06:31:19 PM : [Std-Cleanup ] 34.88.C7-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 12/08/2015 06:31:19 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:19 PM : [INST-SRX ] 02 50 34.88.C7 11.01.01 CF 06 00 (00) Tue 12/08/2015 06:31:19 PM : [Std-Group ] 34.88.C7-->11.01.01, Max Hops=3, Hops Left=3 Tue 12/08/2015 06:31:19 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:20 PM : [INST-TX-I1 ] 02 62 00 00 13 CF 13 00 Tue 12/08/2015 06:31:20 PM : [INST-ACK ] 02 62 00.00.13 CF 13 00 06 LTOFFRR(00) Tue 12/08/2015 06:31:20 PM : [D2D EVENT ] Event [34 D7 9B 3] [ST] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:20 PM : [ 34 D7 9B 3] ST 0 Tue 12/08/2015 06:31:20 PM : [D2D EVENT ] Event [3B 89 E1 8] [ST] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:20 PM : [ 3B 89 E1 8] ST 0 Tue 12/08/2015 06:31:20 PM : [D2D EVENT ] Event [34 D9 2D 3] [ST] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:20 PM : [ 34 D9 2D 3] ST 0 Tue 12/08/2015 06:31:28 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 C7 11 01 LTONRR (01) Tue 12/08/2015 06:31:28 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=1 Tue 12/08/2015 06:31:28 PM : [D2D EVENT ] Event [36 88 5E 1] [DON] [1] uom=0 prec=-1 Tue 12/08/2015 06:31:28 PM : [ 36 88 5E 1] DON 1 Tue 12/08/2015 06:31:28 PM : [D2D-CMP 001A] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:28 PM : [D2D-CMP 0016] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:28 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 C7 11 01 LTONRR (01) Tue 12/08/2015 06:31:28 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=1 Tue 12/08/2015 06:31:28 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:29 PM : [INST-SRX ] 02 50 36.88.5E 38.FF.8F 41 11 01 LTONRR (01) Tue 12/08/2015 06:31:29 PM : [Std-Cleanup ] 36.88.5E-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 12/08/2015 06:31:29 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:29 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:29 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:29 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:29 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:29 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:29 PM : [INST-INFO ] Previous message ignored.

I have an iolinc controlling the garage door opener, and I've been experiencing an issue recently where it opens unexpectedly. I created a notification to email me when the door opened so I could identify just when it occurs, and I had the event viewer open so I could capture the traffic. Can someone make any sense of what is causing this? The snippet from the event viewer should bracket the event, but I can post more if necessary. The notification indicated that the garage door opened at 6:31:30pm. It happened again later in the evening, so I should have a log of that as well. I unplugged the iolinc until I can figure out what's going on. The iolinc address is 34.88.C7. It looks like that address first occurs at 6:31:19 PM Thanks for any help you can offer. Tue 12/08/2015 06:31:15 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 CB 11 01 LTONRR (01) Tue 12/08/2015 06:31:15 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:15 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:15 PM : [INST-SRX ] 02 50 36.88.5E 38.FF.8F 46 11 01 LTONRR (01) Tue 12/08/2015 06:31:15 PM : [Std-Cleanup ] 36.88.5E-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Tue 12/08/2015 06:31:15 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:16 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:16 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:16 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:17 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 C7 06 00 (00) Tue 12/08/2015 06:31:17 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=1 Tue 12/08/2015 06:31:17 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:19 PM : [INST-SRX ] 02 50 34.88.C7 00.00.01 CF 11 00 LTONRR (00) Tue 12/08/2015 06:31:19 PM : [Std-Group ] 34.88.C7-->Group=1, Max Hops=3, Hops Left=3 Tue 12/08/2015 06:31:19 PM : [D2D EVENT ] Event [34 88 C7 1] [DON] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:19 PM : [ 34 88 C7 1] DON 0 Tue 12/08/2015 06:31:19 PM : [D2D EVENT ] Event [34 88 C7 1] [ST] [255] uom=0 prec=-1 Tue 12/08/2015 06:31:19 PM : [ 34 88 C7 1] ST 255 Tue 12/08/2015 06:31:19 PM : [D2D-CMP 0020] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:19 PM : [D2D-CMP 0013] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:19 PM : [D2D-CMP 000D] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:19 PM : [D2D-CMP 000A] STS [34 88 C7 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Tue 12/08/2015 06:31:19 PM : [INST-SRX ] 02 50 34.88.C7 38.FF.8F 45 11 01 LTONRR (01) Tue 12/08/2015 06:31:19 PM : [Std-Cleanup ] 34.88.C7-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 12/08/2015 06:31:19 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:19 PM : [INST-SRX ] 02 50 34.88.C7 11.01.01 CF 06 00 (00) Tue 12/08/2015 06:31:19 PM : [Std-Group ] 34.88.C7-->11.01.01, Max Hops=3, Hops Left=3 Tue 12/08/2015 06:31:19 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:20 PM : [INST-TX-I1 ] 02 62 00 00 13 CF 13 00 Tue 12/08/2015 06:31:20 PM : [INST-ACK ] 02 62 00.00.13 CF 13 00 06 LTOFFRR(00) Tue 12/08/2015 06:31:20 PM : [D2D EVENT ] Event [34 D7 9B 3] [ST] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:20 PM : [ 34 D7 9B 3] ST 0 Tue 12/08/2015 06:31:20 PM : [D2D EVENT ] Event [3B 89 E1 8] [ST] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:20 PM : [ 3B 89 E1 8] ST 0 Tue 12/08/2015 06:31:20 PM : [D2D EVENT ] Event [34 D9 2D 3] [ST] [0] uom=0 prec=-1 Tue 12/08/2015 06:31:20 PM : [ 34 D9 2D 3] ST 0 Tue 12/08/2015 06:31:28 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 C7 11 01 LTONRR (01) Tue 12/08/2015 06:31:28 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=1 Tue 12/08/2015 06:31:28 PM : [D2D EVENT ] Event [36 88 5E 1] [DON] [1] uom=0 prec=-1 Tue 12/08/2015 06:31:28 PM : [ 36 88 5E 1] DON 1 Tue 12/08/2015 06:31:28 PM : [D2D-CMP 001A] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:28 PM : [D2D-CMP 0016] CTL [36 88 5E 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 12/08/2015 06:31:28 PM : [INST-SRX ] 02 50 36.88.5E 00.00.01 C7 11 01 LTONRR (01) Tue 12/08/2015 06:31:28 PM : [Std-Group ] 36.88.5E-->Group=1, Max Hops=3, Hops Left=1 Tue 12/08/2015 06:31:28 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:29 PM : [INST-SRX ] 02 50 36.88.5E 38.FF.8F 41 11 01 LTONRR (01) Tue 12/08/2015 06:31:29 PM : [Std-Cleanup ] 36.88.5E-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 12/08/2015 06:31:29 PM : [INST-DUP ] Previous message ignored. Tue 12/08/2015 06:31:29 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:29 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:29 PM : [INST-INFO ] Previous message ignored. Tue 12/08/2015 06:31:29 PM : [INST-SRX ] 02 50 36.88.5E 11.02.01 CB 06 00 (00) Tue 12/08/2015 06:31:29 PM : [Std-Group ] 36.88.5E-->11.02.01, Max Hops=3, Hops Left=2 Tue 12/08/2015 06:31:29 PM : [INST-INFO ] Previous message ignored.

I'm using a scene to control the LEDs in the 3 KPLs, but I control that scene with a program (instead of using the iolinc as controller) so that I can reverse the sense of ON/OFF reported by the iolinc. (With my sensor, ON means that the garage door is closed. I know I can reverse that with an option, but my understanding is that the 3am query can mess you up.) Anyway, the program that controls the LEDs simply sets the scene to ON or OFF. The program runs when expected, but what I noticed was that *sometimes* the button LEDs were not all synchronized. So far, it's just been that one was ON when all the others were OFF. And, not the same KPL each time. For instance, all but LEDs are ON, garage goes down, program runs, scene is set OFF, most button LEDs go off, one stays on. Randomly. I'm just wondering if anyone else sees this behavior.

Not to hijack the thread, but I have a related question. I've got 3 KPLs with a non-toggle button on each that is used to reflect the state of the garage door. I have a monitor program that watches for a status change of the garage door sensor and then sets a scene on or off. The scene just has the 3 KPL buttons as responders. What I've seen on occasion is that sometimes not all buttons get set to the correct state (e.g., button is lit, but the garage door is down). I'd like to have confidence that the button state is correct - what is the best way to handle this? Should each button be placed in its own scene and have the monitor program set each scene on/off? Or, have multiple "set scene on" or "set scene off" statements for the same cumulative scene to make sure the message is received? If anyone has had this issue, what is the most effective way to deal with it?