|
Post by jaronbrass on Apr 26, 2013 5:17:01 GMT -5
Curious question... I have 10 occupancy sensors controlling various 8S-DV switches and a few 6D dimmers. They're located in bathrooms, closets, laundry room, etc. and are simply there for convenience (and because I love playing with this system!)
I've created an Alternate Timeclock mode with 24 separate events, triggered either by a keypad button press or from my Roomie iOS app when I leave the house (time varies each day). Each event (on the hour) will put the sensors into Vacancy mode because my dog keeps tripping them and turning lights on in rooms where the door is open.
So here's the question - and the answer is probably obvious... when I return the system to Normal mode, the sensors' behavior doesn't change. They remain in Vacancy mode from what I have tested. Do I need to add 24 additional events to the Normal timeclock to put them back into Occupancy mode?
If the Lutron guys reading this would consider adding a global timeclock mode that only toggles the behavior of these sensors, that would be awesome!
Basically, when I leave, I push a button and they go to Vacancy. When I'm home, I push the same button and they go back to Occupancy mode.
|
|
Bailey
Full Member
San Diego Lutron Representative
Posts: 172
|
Post by Bailey on Apr 26, 2013 8:07:28 GMT -5
You would have to change the sensors back. The Vacancy mode for the sensors was turned "on" and therefore must be turned "off". You could create a single time lock event to turn on vacancy at some time where you are never up, say 3:00 AM and then another event to turn them "off", back to occupancy. Then use the integration protocol to activate that time clock event when the Roomie app detects you are no longer at that location. When you return, have it activate for the "off" event. Should be a bit easier than 48 events.
|
|
|
Post by jaronbrass on Apr 26, 2013 15:08:59 GMT -5
Thanks for the suggestion. I've been thinking about trying something like that.
Putting the system back into "Normal" should do just that - i.e. as things were before the timeclock change. Hopeful for a future release addressing this.
|
|