Can anyone help me understand why this is hanging. The Rule is pretty simpleā¦I think. Basically, if motion is active turn the lights on, and if itās after dark, turn two lights on. If motion is inactive, turn the lights off. And if itās after dark, turn the two lights off.
Whatās actually happening is that it turns the lights on and they hang on until I either see it and turn it off, or it is re-triggered with another Motion event.
I had it only set to motion active with a wait for event (motion inactive), but that failed more than it worked. This way pictured works about 75% of the time.
The rule looks like it should work. Have you seen a log of a time when you had to turn it off? Did it indicate that it had sent the command to close the light(s)? I wouldnāt be surprised if the issue is with the command not getting to the light for some reason. (Signal interference?)
I have a set of Hue Lights in my living room that will occasionally not turn off. Hubitat thinks that they are off, but the are notā¦ So I tried to reproduce how I fix the problem. I setup an Illuminance sensor next to them and have the hub check to see if the light value is higher than it should. When that happens, it sends an on command and then an off command. That has worked very well, but did require some tweaking to ensure it could work properly.
Iāve been watching the logs and it looks like the motion is inconsistent on changing to inactive. There is a zigbee powered device in the light fixture of the laundry room, so I should have a repeater within a few feet of the Motion. It only flashes when it activates and waits two minutes to reset. I checked the device status and it showed active on the hub. However when I walked into the room, it flashed. Iām guessing itās a device reporting issue?
The problem Iām having is that it really doesnāt log when it doesnāt work so Iām not seeing whatās happening. I just come in and itās been on for an hour.
That would explain the problem; the second half of your Rule actions (that turn the light off) will not happen if this event does not occur.
Is this a smart bulb? 
Many Zigbee smart bulbs are notoriously bad repeaters and could be causing problems with the rest of your network, like these sensors. Keeping the bulbs on their own network (Hue Bridge, second Hubitat, etc.) is an often recommended solution.
For a workaround in the meantime, if you went back to using "Wait for event: motion inactive" instead of writing the Rule this way, then you could add a timeout and at least the lights would turn off at some point (though that would also happen even if motion were truly active for that long, so you'll probably want to make the timeout pretty long).
1 Like
Is your motion sensor event log showing it going active and inactive? You should be able to see each time the device goes active and inactive and then go look at hub logs and look at that the inactive times to see what happened.
1 Like
