I thought everything was fine but now having looked at the logs I realise that when I’m out and the heating is Off, when the scheduler changes the temperature, the heating gets turned back on! ie the hvac_mode goes back to heat.
Is there a simple way to stop that happening?
OK, noted. Thanks Tom.
So I’m using the custom:simple-thermostat card and the custom:scheduler-card card. These enable me to add/modify schedule entities which I’ve found are stored in .storage/scheduler.storage in JSON (?) format. Using the scheduler-card UI, I think I can add a condition “heating must be on” for the schedule to trigger. This should be ok but when I come home and my automation turns the heating back on, it will be at the last temperature it was told and not the temperature for the time I come home!
Having read the Github for the scheduler-component add on, I think I can do better than that by editing the scheduler.storage file to add stop times to my schedule entities and setting track_conditions to true. The way I read it is that then the schedule entity with a start/stop of, say, 10:00/12:00 will not fire if I’m away, but if I come home between those times it will then fire. Is that correct?
I’m guessing the scheduler-card has not been written to enable this extra complexity.
I will give it a try and see what happens.
I Just had a look. You have to pick one of the schedule entities to run, so that doesn’t work either.
I’m going to try editing the scheduler.storage file as mentioned earlier.
As an aside, When adding/editing a scheduled event in the scheduler-card, I only see the Time and Options tab on my laptop (Windows/Chrome), but not on my desktop (same) nor my phone (Android/companion app).
I don’t use it so I could be wrong but it looks to me like the action occurs when scheduled. i.e. set your temp on schedule, which turns the thermostat on.