Motion triggers random Insteon events

[dex]

 

I have a simple pair of programs for motion in my garage.  This one turns the lights on with motion from any of three detectors...

Gar Motion Detected - [ID 001B][Parent 001A]

If
        '2 Main Level / Garage / Garage Sensors / Garage Motion 43' is switched On
     Or '2 Main Level / Garage / Garage Sensors / Garage Motion 47' is switched On
     Or '2 Main Level / Garage / Garage Sensors / Garage Motion 64' is switched On
 
Then
        Set '2 Main Level / Garage / Garage Overheads' On
 
Else
   - No Actions - (To add one, press 'Action')

And this one turns the lights off after a few minutes of no motion...

Gar Lights Auto Off - [ID 0004][Parent 001A]

If
        '2 Main Level / Garage / Garage Sensors / Garage Motion 43' Status is Off
    And '2 Main Level / Garage / Garage Sensors / Garage Motion 47' Status is Off
    And '2 Main Level / Garage / Garage Sensors / Garage Motion 64' Status is Off
 
Then
        Wait  3 minutes 
        Set '2 Main Level / Garage / Garage Overheads' Off
 
Else
   - No Actions - (To add one, press 'Action')

This behavior works perfectly as expected in the garage. 

However, sometimes, when motion is triggered, completely unrelated lights go on or off elsewhere in the house.  Using security cameras, I can correlate 100% of these lights/scenes going on/off immediately after motion in the garage.  Roughly 90% of the time there is no random event.  But 10% of the time there's garage motion, something goes on or off that has nothing to do with the garage

When it does happen, all of my Insteon wall modules will come on every time this happens.  Sometimes, there's also a dual-band dimmer switch, or two.  Sometimes an entire scene will go on or off (e.g. living room lights via 7 Insteon switches).  

I have deleted, factory-reset, and rebuilt from scratch the scenes and programs -- multiple times!  The specific devices that come on/off vary slightly after I do this, but the behavior persists.  If I disable the two programs above, the behavior disappears entirely.

This is a persistent, multiyear annoyance.  I had this issue when I was on ISY-994 (several years ago) and continue to have it on Polisy (past couple years).  I'm currently running IoX v.5.7.0 (2023-09-11).   Additional "about" info is attached as an image.

Any obscure bugs, behaviors, or hints any of you have would be appreciated.   Thanks!

 - Dex

 

 

 

[tazman]

Have you checked the link tables in the motion sensors? Maybe have the event viewer open on level 3 while you trigger the motion sensors?

[TJF1960]

If the motion sensors are Insteon, you may be experiencing the all on/ all off command that Insteon has since gotten rid of in new devices. There are many posts about it on this forum. Here is a link to UDI mention:  

INSTEON Random All On Events - Universal Devices, Inc. Wiki (universal-devices.com)

[dex]

On 11/12/2023 at 11:35 AM, tazman said:

Have you checked the link tables in the motion sensors? Maybe have the event viewer open on level 3 while you trigger the motion sensors?

 

Thank you, @tazman.  I have completely removed and re-added all implicated devices and the link tables are as pristine as they can get.  I even authored the programs as new to ensure there was no stray bits there.  

[dex]

On 11/12/2023 at 11:37 AM, TJF1960 said:

If the motion sensors are Insteon, you may be experiencing the all on/ all off command that Insteon has since gotten rid of in new devices. There are many posts about it on this forum. Here is a link to UDI mention:  

INSTEON Random All On Events - Universal Devices, Inc. Wiki (universal-devices.com)

 

Bits of this description are similar to what I’m experiencing, so I’ll give it a go to put some delays in the programs to create separation from the motion event and the first ‘set scene’ command.

Makes me also wonder about multiple motion sensors with overlapping ranges — could two of them be triggered (near) simultaneously create collisions that might exhibit this behavior in the system?