I didn't update to 2.4.3.X because I didn't see in the release notes anything relevant to the features I use.
The only mention to HomeKit is this one:
which BTW, is very unclear to me.
Anyway, I'm updating it now just in case.
Just to conclude this case, the unexpected temperature changes seem to be coming from the thermostat itself (or Ecobee Cloud).
It thinks it knows better than me what temperature I want 
This happens despite having schedule and all "smart" features disabled.
eco+: Disabled indefinitely
Hold Action: Until I change it
Smart Recovery Heat Mode: Disabled
Smart Recovery Cool Mode: Disabled
Smart Home/Away: Disabled
Follow Me: Disabled
I did some research and found a lot of people with the same problem.
"Solution": On my automation, after setting the set point and turning heat on, I've added 1 minute delay and an action to set the set point again.
3 Likes
How did you disable the schedule? AFAICT, this cannot be done directly. Here's what I did a long time ago, and after doing that have not experienced the mystery temperature changes you described ....
1 Like
Is it always 2 degrees difference? Might want to check the settings on your thermostat and adjust the minimum degrees difference between cooling and heating. If you set the heating at 23.5 while cooling is 23.5 AND you have the minimum 2 degrees difference, then the thermostat will adjust the set temperature accordingly (2 degrees difference, or whatever your minimum is).
2 Likes
My understanding is that if you have Hold Action: Until I change it, it ignores the schedule. Anyway, I'll apply your recommended schedule.
No, it varies between 0.5 and 2 degrees (ºC).
For changes made at the thermostat or via the ecobee API. I don’t know how changes made via HomeKit fit in.
1 Like
It still could be the same setting. Depending on how far apart the two temperatures are set to. I encountered this issue before, and it took me a lot of time to narrow it down.
3 Likes
