RM help for motion light

I cannot find any example of a simple Motion activated light that turns on with motion and then turns off after a delay. Plus also use a switch to control this same light at anytime.

I do not want to use Motion Lighting. I tried that already and the light to on takes several seconds to happen. I need it to work so if I walk into a room, within 1 second the light turns on.

I have no idea if I need to define a rule or use a triggered rule or what. Anybody have an example of this basic lighting using RM?

Thank you Eric. I'll try your setup.

I created a thread asking why there was a discrepancy between automations in RM and ML as RM just seemed faster to me and was told they should be the same speed or ML should actually be slightly faster.

What I discovered on my own was that they were right. What was causing my slow automation was actually my sengled bulbs. For some reason if the bulbs were turned off with their level being below 20% then it takes longer to turn back on. The ramp up rate from off to on is way slower.

Both lights triggered by same sensor but bulb on the left is set to a higher level when it was last on.

I say all this to say...I've set the minimum level for my lights to 25% at nights and have had no further issue with lights seeming to take forever to come on. I use ML to turn them on with motion and I use RM to turn them off if they were on and motion is inactive. That way if they're turned on by any means other than motion, they will still turn off after a set delay.


ML turns on with motion


RM sets levels depending on mode


RM turns lights off if they're on and there's no motion

2 Likes

If you still want to do it in RM I'd suggest define a trigger and set that trigger to be when motion starts.

1 Like

Thanks for the info. I've set up motion lights now and came to the conclusion that they work better using RM instead of the ML. Still not as fast as it should be, but I think it is an issue with my controllers. I am using Gen 1 Fibaros (not Zwave+) and the HE drivers available could be better. I get a lot of parsing messages mixed in with the regular light execution entries. They work, but the delay is 3-7 sec. Sometimes even longer. My vera setup before was less than a second. And I am only dealing with 10 lights here.
I will keep playing with it all as time goes on and post if I come up with a solution.

That's a masssssiiive delay! The delay in the video I posted was enough to drive me up the wall as it had me reaching for the light switch every time and that's not even a 1 second difference so I can't imagine what 3-7 secs would feel like! I really hope this can get resolved for you!

Tell me something...does turning the lights on and off usinjng the device page take 3-7 seconds as well? I'm wondering where the issue is, if it's with the motion sensors, lights or both :thinking:

I don't have any "smart" bulbs but I see the same thing with the lights in my hall. There are two fixtures wired to one dimmer. Both fixtures have two sockets. I think one bulb in each is a Phillips and one bulb is a Cree - both "dumb" bulbs. When the rules kick in the bulbs come on with a significant delay between the Phillips bulbs and the Cree bulbs. I will, at some point, move bulbs around and replace a few to get more consistency but it's surprising how differently the bulbs react to ramp up (and presumably ramp down, although I have not noticed it).

The dalay is the same using a dashboard, direct device page or switch.
Yep, driving me nuts

Is this the same delay we are dealing with on the elk m1 driver? Or is this unrelated.

I think the same.
If I use the dashboard to turn on/off lights there is no delay.
Only through automation.