Hey gang, I’ve got a chunk of free time lately, and I’ve been working on some of the backlog issues I’ve had with my HA instance. The one that is giving me trouble right now is my thermostat - I use Honeywell total connect (or whatever its called), and it works just fine when using the normal thermostat card or controls. However, I want it to be warmer in the day, and colder at night. So I had been using a scheduler entity from the HACS store. It always used to work, but lately I’ve been getting out of bed and realizing the temp is still set to the nighttime temp.
It’s not every day, and it seems to work 90% of the time, but I had always thought that the scheduler entities did a periodic check to see if the thing they controlled was at the proper state? Seems like if the scheduler ‘misses’ the switchover time, it’s just stuck at the night time temp all day unless I manually change it.
So this got me thinking… Is there a better, or more ‘approved’ way to do this sort of thing?
I use my thermostat to handle that, and override as needed from HA. The other thing I do, if it’s a cloud api, is make the change, wait a period of time that’s reasonable for the update to occur, and check the state. If state is not what I want it to be, set again, wait a random back off and check again. There’s a service you can call to update an entity, too.
Homeassistant, as far as I’ve been able to figure out, doesn’t do desired states natively. You can’t declare “from 19-21h I want it to be 17°C”. You have to build it yourself.