Continuing the discussion from Hub Update 1.1.7:
Yea! This is an excellent add! Now how about a setSleep (or setNight). That would complete my thermostat needs. Thanks.
UPDATE: setAway worked perfectly today. Thank you for adding this!
I had several rules that set the thermostat in an away mode and I had to set the heating and cooling setpoint temps is each rule, with one thermostat per rule. With the new setAway command, the 'climate' Away is established in the thermostat and I just have to set the program mode with the setAway command to all thermostats in a single rule. Much easier.
@bravenel @mike.maxwell Can we get a setSleep (or setNight or setAsleep) too? I have two thermostats (and two HVAC units) and each has it's own unique heating and cooling times and temps. It would be far easier to set those climate paramters in the thermostats themselves, then just issue the setSleep command to each thermostat at the same time in the same RM rule. I can get around it, but it requires redundant RM setups (with the unique heating/cooling setpoint temps) for each thermostat.
In my case I program the thermostat 'Sleep' mode to turn at a midnight in the thermostats. But, if anyone is home (HOME mode) AND it is between (10:00 PM and 5:30 AM) AND there is no motion detected for 15 minutes then RM will trigger the thermostat's Sleep/Night mode. Right now I have to do that once for the upstairs thermostat (where everyone sleeps and it is more comfortable) and once for the downstairs thermostat (where the temps have a broader variance range). A setSleep would allow me to keep my climate parameters in the thermostats and have a single RM issue a command to all thermostats when the program mode (Home/Away/Sleep) should change.
Thanks ... and keep up the great work. I appreciate it!