Future Consideration Motion and Lights - "Off Means Off"
I currently have a Group with six (soon to be eight) KL135 bulbs and two ES20M switches.
The two switches are wired for power, but are not wired to a load, as I don't want them actually removing power from the KL135 bulbs or attempting to Dim them like standard bulbs.
After a lot of struggling through the app UI to figure out how to get motion sensing from the Switches to turn on the Lights using a combination of Smart Control and Smart Actions, I'm finding that on-with-Motion always works, and by that I mean ALWAYS - even after I've explicitly turned the lights Off.
The use case:
- When I have turned the lights On, I want them to stay On as long as the room is occupied (Motion recently sensed at the Switch).
- After some period of time without occupancy/Motion at the Switch, the lights should turn themselves Off.
- If the room becomes occuped again, the lights should turn themselves On again.
- There are times when I want to be in the room, but do NOT want the lights On, so I turn the lights Off (using either the Switch Power button, the app, or voice control). This might be to meditate or take a nap, for example.
What I expect:
- The lights remain Off until I explicitly turn them On again, after which they resume using Motion to dictate their state.
- After some period of time, apparently dictated by the Manual Off Buffer, if the sensor on the Switch detects any Motion, the lights turn themselves On again, disturbing my rest.
If the Manual Off Buffer feature is indeed what is breaking this use case, recommend adding an option beyond 5-60 seconds (like "Never" or an infinity symbol), that will keep the light Off indefinitely until either the user explicitly turns the Switch On again, or the next Scheduled event that sets some other state.