Recently I decided to change a motion sensor scene to program control instead.  So I unlinked my 2842-222 MS from a scene with two 2466S switches and wrote a dead simple program, when MS sensor switched on, set scene on.

Since that change, the trigger seems sluggish, like I see the MS blink, but the lights may delay almost a second coming on.  I did have variability in the reaction speed of the direct linked scene, but the program version seems pretty consistently slow.

I attach a part of the event communication log I think is appropriate, with 31.84.0B the MS, and 1D 87 34 and 1D 89 B0 the switches.

What sort of delay is "normal" to be seen in a program like this?  Can anyone see anything instructive in the log?  Thanks in advance.

-Alan

PS: IoP version is 5.4.4.

ISY-Events-Log.v5.4.4__Sat 2022.06.18 11.10.47 AM.txt

Edited June 18, 20223 yr by webminster

The absolute fastest way for a light to react to motion captured by an Insteon motion sensor is to use a scene.  

A program will always be slower, as the ISY has to receive the motion event, then run the THEN stanza in the program to send a command to the lights.  With the scene, the ISY isn't involved other than being notified of the device status.

I've found that the delay you're experiencing is normal when using a program instead of a scene.

Thanks for the reply.  Appreciate the information, I expected a smidge extra delay because of the intermediate step, I'm just a little surprised it added a noticeable delay to the processing.

-Alan

Not knowing what you're looking to do, there is some programmatic flexibility with the scene. They can be modified by the "adjust scene" functionality if necessary.  Below is an example of where I adjust a scene for differing on-levels based on time (using the latest/greatest ISY firmware):

West Hall On-Level - [ID 00B7][Parent 000A]

If
        From    Sunset  +  1 hour 
        To      Sunrise (next day)
 
Then
        In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 25% in 0.5 seconds, 1 retry
        In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 25% in 0.5 seconds, 1 retry
        In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 25% in 0.5 seconds, 1 retry
 
Else
        In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 50% in 0.5 seconds, 1 retry
        In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 50% in 0.5 seconds, 1 retry
        In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 50% in 0.5 seconds, 1 retry
 

 

Edited June 18, 20223 yr by Bumbershoot

Are there ways to improve the speed/responsiveness of programs on the Polisy/IoP?  It's not just the MS program above (went back to direct links)... I've other programs that seem to also have oddly long delays, like a program to detect when I've turned off my kitchen cans and island lights, to automatically turn off undercabs (inconvenient switch)... sometimes take a couple of seconds to run.  Don't think there's a way I could do that with a scene.

On 6/18/2022 at 4:06 PM, webminster said:

Are there ways to improve the speed/responsiveness of programs on the Polisy/IoP?  It's not just the MS program above (went back to direct links)... I've other programs that seem to also have oddly long delays, like a program to detect when I've turned off my kitchen cans and island lights, to automatically turn off undercabs (inconvenient switch)... sometimes take a couple of seconds to run.  Don't think there's a way I could do that with a scene.

You might read through this thread: