I’ve recently been diving into the world of smart lighting automation, and I must say, it’s been a fascinating journey!
I’ve set up a system where my exterior lights are controlled by motion and contact sensors, turning on to 95% brightness when triggered. It’s been working like a charm, but I’ve hit a bit of a snag that I’m hoping the community can help me with.
Here’s the deal: I want to add an override feature where if I press any of the Caseta dimmer buttons, the lights will stay on at 100% brightness until I manually turn them off. It’s a simple idea, but figuring out how to implement it in the Rule Machine has been a bit of a puzzle. I’ve seen similar functionality in the motion-based lighting app, where pressing the button triggers an override, but translating that into a rule has been tricky.
Let me walk you through what I’ve tried so far. I’ve set up a rule that monitors the motion and contact sensors, turning the lights on after detecting movement or an open contact. The lights then turn off after 5 minutes of no activity. But adding that manual override has been the sticking point. I’ve experimented with different logic flows, but nothing seems to quite hit the mark.
I’m curious if anyone else has tackled a similar challenge. Maybe there’s a clever way to use state variables or conditional triggers to make this happen. Any tips or tricks would be greatly appreciated! I’m excited to crack this one and take my smart lighting setup to the next level. ![]()
![]()