Assistance tracking down random triggered event

@jim_,

Your log was extremely useful. Just prior to your garage door event it recorded the following:

• Sat 02/28/2026 10:57:49 : [INST-SRX ] 02 50 54.68.42 00.00.01 CF 11 01 LTONRR (01) - Motion sensor trigger

• Sat 02/28/2026 10:57:49 : [Std-Group ] 54.68.42-->Group=1, Max Hops=3, Hops Left=3

• Sat 02/28/2026 10:57:49 : [D2D EVENT ] Event [54 68 42 1] [DON] [1] uom=0 prec=-1

• Sat 02/28/2026 10:57:49 : [54 68 42 1 ] DON 1

• Sat 02/28/2026 10:57:49 : [D2D-CMP 005D] CTL [54 68 42 1] [DON] op=is --> true - Program 005D trigger

• Sat 02/28/2026 10:57:49 : [ZWAVE-CTL-EVENT ] Basic Set from 23.0 unmapped (ignored)

• Sat 02/28/2026 10:57:50 : [INST-TX-I1 ] 02 62 00 00 21 CF 11 00 - Command from ISY to PLM to turn on group 21

• Sat 02/28/2026 10:57:50 : [INST-ACK ] 02 62 CF.11.00 CF 11 00 06 LTONRR (00) Corrupted acknowledge from PLM to ISY - Execute On for group 00 (all devices)

Your PLM should have echoed back the EXACT TX command that the ISY sent with an "06" added to the end. Instead it returned a corrupted command that I believe may have executed an group 0 on (all linked devices On). I'll try testing in the morning to verify.

@kclenden appears to be the 1st to have noticed this in the event logs. His post is here https://forum.universal-devices.com/topic/45721-lights-switch-on-at-random-times/page/4/#findComment-399260.

I'll confess that I do not understand why the PLM corrupted the command. It's interesting to note that the event viewer shows your motion sensor sending 1 On command to group 01 (02 50 54.68.42 00.00.01 CF 11 01). Motion sensors normally send 2. As said previously, delays in programs are normally used to prevent collisions. Your program 005d may have caused a collision at the PLM while the motion sensor was sending it's second ON communication.

The other approach is your devices themselves. We had discussed that Smartlabs has been removing the all-on code from devices. Unfortunately that has NOT been done for IOLincs, they are still susceptible. If you can forward your model/revisions/date code for your LampLinc we can probably figure out if it is still susceptible.

Try executing the All-on command from with ISY My Lighting window (hold onto your hat). Devices that turn on are susceptible (you have to verify this visually - the ISY will ASSUME all devices have turned on). If your LampLinc and IOLinc are the only offenders, replace them and get on with your life. I would highly suggest replacing the IOLinc regardless - I would post my opinion of these devices but the forum doesn't allow that type of language.

Edited 6 hours ago6 hr by IndyMike