I have a scene called Garage Lights that has a 2477S On-Off switch as a controller/responder, and a Motion Sensor II as a controller/responder. I don't really think the MS II is acting like a responder at all, at least the way I have it configured. Here's the problem: If the motion sensor detects motion, it issues an On command for the lights, then waits for no motion detected within a timeout value, and then issues an Off command if the timeout is reached. All that is good and expected. However, if the lights are turned off by the 2744S while the MS II is still waiting to issue its Off command, the MS never issues another On command if motion is subsequently detected, thinking the lights are already on. Is there any way to configure the MS II so that it always issues an On command if it detects motion, even it it thinks the lights are already on? Can it be done if it's powered by a USB cable?

A motion sensor can only be a controller. It cannot respond to commands. It's sounds more like a configuration issue. I would shorten your timeout proud so it sends the on command more often.  your other option would be to send only on commands and let the isy handle timeouts via programs

Edited March 23, 20196 yr by lilyoyo1

Hey, thanks for replying. What I did initially was to configure the MS II to issue on commands only, and I had a "timer-off" program that was normally disabled, but was enabled and run by virtue of the lights coming on (from either switch or MS II). After it timed out (10 minutes), it issued a scene off command, and then disabled itself. A second program was triggered by the MS II's On commands to (1) wait 5 seconds, (2) disable the time-off program, then (3) re-enable it, to get a fresh timer going. Seems like it should have worked, but it proved unreliable for some reason. I'll go back and give it another try. Thanks again...Jack

13 hours ago, JacktheRipper said:

Hey, thanks for replying. What I did initially was to configure the MS II to issue on commands only, and I had a "timer-off" program that was normally disabled, but was enabled and run by virtue of the lights coming on (from either switch or MS II). After it timed out (10 minutes), it issued a scene off command, and then disabled itself. A second program was triggered by the MS II's On commands to (1) wait 5 seconds, (2) disable the time-off program, then (3) re-enable it, to get a fresh timer going. Seems like it should have worked, but it proved unreliable for some reason. I'll go back and give it another try. Thanks again...Jack

You're welcome. I would simplify that alot more than what you have it. I would also shorten the timeout. 10 minutes is a really long time. 

Personally I would do 1-3 minutes max (assuming good coverage). I would then write a program that says if status 2477s is on and ms2 is not switched on, then wait 5 minutes and turn off light. 

As long as the motion sensor is triggered, the wait will never be fulfilled keeping the lights on. The 3 minutes also allows you to manually turn off the lights when leaving the room and lessens the chance of motion catching you and simply turning them back on.