I will get screencaps of the switch, sensor and app state during this limbo when I'm home later today.
1 Like
I'm running in to the same issue that @Ryan780 described -- in the following sequence:
- Walk in to a room & trigger motion sensor
- Motion Lighting turns on the lights
- Manually switch off the lights
- Allow motion sensor to reset
- Walk back in to the room (before the Delay Off timer for Motion Lighting)
- Motion sensor reports active again, but the lights don't come back on
I checked the application state as you'd suggested, @bravenel , and indeed "on" is set to True when the lights are off. The switch detail page correctly shows the state as "off", and the events page confirms that a physical off had occurred.
Pure speculation: for some reason, Motion Lighting isn't subscribed to the "off" event of the switch once it's already been turned on?
Please show the app setup page. Turn on logging in the app, capture the sequence that fails for you.
Thanks!
Setup page:
Logs:
[Motion sensor]
dev:188 2019-05-25 05:28:17.370 pm info Office - NYCE Ceiling Motion Sensor is active
dev:188 2019-05-25 05:28:13.524 pm info Office - NYCE Ceiling Motion Sensor is inactive
dev:188 2019-05-25 05:27:51.436 pm info Office - NYCE Ceiling Motion Sensor is active
[Zigbee dimmer]
dev:788 2019-05-25 05:27:59.504 pm info Office - Cans was set to 0% [physical]
dev:788 2019-05-25 05:27:51.729 pm info Office - Cans was set to 73% [digital]
[Motion lighting]
app:803 2019-05-25 05:29:02.829 pm info Motion active Office - NYCE Ceiling Motion Sensor
app:803 2019-05-25 05:29:01.720 pm info Delaying off for 2 minutes
app:803 2019-05-25 05:29:01.685 pm info Motion inactive Office - NYCE Ceiling Motion Sensor
app:803 2019-05-25 05:28:51.650 pm info Motion active Office - NYCE Ceiling Motion Sensor
app:803 2019-05-25 05:28:50.866 pm info Delaying off for 2 minutes
app:803 2019-05-25 05:28:50.834 pm info Motion inactive Office - NYCE Ceiling Motion Sensor
app:803 2019-05-25 05:28:17.425 pm info Motion active Office - NYCE Ceiling Motion Sensor
app:803 2019-05-25 05:28:13.606 pm info Delaying off for 2 minutes
app:803 2019-05-25 05:28:13.571 pm info Motion inactive Office - NYCE Ceiling Motion Sensor
app:803 2019-05-25 05:27:51.555 pm info Setting dimmers [Office - Cans] to 73
app:803 2019-05-25 05:27:51.523 pm info Motion active Office - NYCE Ceiling Motion Sensor
Happy to merge those in to a single time ordered list if that's a better view, too.
Are you on the latest build?
We added an option called "Don't turn on if turned off manually". I'm pretty sure we did that because of the opposite situation to what you're describing. And, because without that they would always turn on when motion becomes active.
Moreover, whenever the lights are not turned on from motion active, it will tell you why in the logs.
Instead of copy/paste, it's better to just show a screenshot of logs.
Yep, I'm on the latest build. I don't see anything in the logs describing why it's not turning on -- guessing because it's not registering the physical off event and state.
To get around what you're saying above -- I think it would be nice to have a configurable "hold down timer". So for example, suppose you set the hold down timer to 5 minutes -- after a physical turn off, any motion events would be ignored for 5 minutes. But after that hold down timer expires, subsequent motion events would turn on the load.
This would do it, although it doesn't have to be physical off. See what happens if you turn the lights off from the web ui of the hub. I bet they come back on with motion.
What kind of device is this? There are issues with some devices not reporting off from the switch. This can sometimes be overcome with polling.
Check out Z-Wave Poller, if this device uses Generic Z-Wave Dimmer.
I tried the test you described - turning the dimmer off from the web ui. That didn't change the result -- when the motion sensor becomes active again, the lights do not turn on.
(Device is a Leviton DL6HD-1BZ Lumina RF using the Generic Zigbee Dimmer driver)
I notice that your device didn't report off. It reports 0%. Look at the device events (Events from the device page). See if there are any off events.
Motion Lighting is looking for an off event.
Thanks! I think there are two issues:
- My light is indeed behaving in a weird way. It is not reporting off. (Appears to be an issue with the dimmer firmware or the device handler)
- Motion lighting does not respond to an Off, even when present. I first fixed the device handler to send an off, and second, tried this with entirely virtual devices. You can see from the logging below (ignore the Office NYCE alerts which snuck in) that Motion Lighting doesn't log anything after an Off from the virtual dimmer:
Try enabling override.
Scratch that, I think it's working..
I believe I had the same problem. Finally figured out what to do to get past it.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
