Morning everyone! I wanted to share a little story about my recent experience with Motion Lighting (ML) in my kitchen. At first, everything seemed to be working smoothly, but I noticed something odd—ML wasn’t turning off the lights consistently. The logs showed that it was being overridden, even though no one had manually adjusted anything. It turned out that ML itself was causing the override when it detected the lights were already on after a period of inactivity.
This was a bit confusing at first, but I decided to dig deeper. I reviewed the logs and noticed that ML was setting an override because it detected the lights were already on when it tried to turn them off. This happened when I left the room and the sensor became inactive, then came back in. ML’s logic was a bit counterintuitive in this case.
After some research and experimentation, I found a workaround by setting up a rule that turns off the lights after 15 minutes of inactivity. This seems to have resolved the issue for now. I’m still curious if there’s a more elegant solution, but at least the lights are behaving as expected again.
I’d love to hear if anyone else has encountered similar issues or has suggestions for improving ML’s behavior. It’s been a valuable learning experience, and I’m grateful for the community’s support in helping me troubleshoot this. Happy automating everyone! 