The problem I’m having with this feature (turn off lights after x minutes of no motion) is that it doesn’t seem to be working properly – or at least not the same way – after my switch to hub v2.
I have several lights in hallways set to turn on with motion, and then turn off after 2-5 minutes of no motion. This all worked perfectly fine under the old hub/app.
Now, this use case is biting us all the time, because the new one doesn’t handle it right:
- Person walks into dark hallway. Motion is detected; light turns on.
- Person leaves hallway; motion sensor registers “motion stops”. A timer starts (presumably), let’s say this one is set to turn off after 2 minutes of no motion.
- Person re-enters hallway 90 seconds after the “motion stops” event. 30 seconds later, the light turns off, even though there is now motion detected in the hallway because someone is in it.
Lights turning off while there’s motion active has been driving us absolutely bananas since the hub v2 “upgrade”. I presume this is because there’s some logic error in the new Smart Lights app in which it doesn’t reset its timer/unschedule the lights off command if motion is detected again before the motion stop timer expires.
I have looked through several threads about the new buggy Smart Lights app but I haven’t seen a peep from Support. I’m not going to install a non-blessed SmartApp to “fix” this because then it has to execute in the cloud, which totally defeats the purpose of Hub v2. Given that lighting is probably one of the most commonly automated things, I imagine the scope of impact is significant. @Ben can you provide any insight?