Ecobee "Current Temperature" not updating through HomeKit Controller integration

Just paired my Ecobee Smart thermostat with the HomeKit controller integration.

The Smart sensor that comes with the thermostat updates temperature pretty frequently, however the “current temperature” entity of the thermostat is slow to update (hasn’t changed in over 1 hour). I know its inaccurate because the temperature displayed as part of the climate entity is different. (See below, for example the climate entity thinks the current temp is 20.4 C, while the “current temperature” sensor entity thinks it’s 21.2C and hasn’t changed in over an hour.

image

Is there a way to fix this?

2 Likes

I’m on homeassistant version 2021.7.4 and observing the same behavior. On the overview page I can click on the temperature sensor and see that it hasn’t updated once in the last half hour. It did appear that the cooling status mode is updating instantly as once the AC kicked on I do see that it displays “cooling” on the tile. Any suggestions on getting the temp updating more frequently would be appreciated. I"m currently reading them through the ecobee web API but I had hoped to transition to local control with more timely updates.

I do now see that when I click on the history tab of the main entity card I can see the temp moving - albeit in only whole number increments (i’m using F) This should allow me to see temperature with tenths resolution right?

UPDATE It appears restarting home assistant after the initial homekit device setup is allowing the values to track as expected.

2 Likes

Thanks @baku104788 for the Update. This was killin me. Looks like all I needed to do was restart :tada:

2 Likes

Thank you this helped me just now!

It stops working after a while even after a restart. Supposedly it was fixed in 2025.3, but it’s still happening in 2025.4.

2 Likes

Yeah this is happening to me too. Quite annoying. More reason that the homekit integration is far worse than the ecobee version that new people can’t use.

1 Like

Experiencing the same here. Anyone opened a bug report?

I’m seeing the same bug. I’ll post this on git.

Summary:
Ecobee is connected using Homekit integration.

Upon start, the Current Temperature entity is updated with the correct temperature. After that, it never updates… even days later its the same as the initial reading.

2 Likes

(2025.06) I am having the same problem as well. Interestingly, when this occurs, the ecobee IOS app is unable to control the fan (auto/on) and other thermostat functions. Previously when this happened, a HA restart took care of it. This time I also have to power cycle the ecobee.

1 Like

Restarting HA did not resolve this for me. Current Temperature hasn’t changed since it’s initial reading at installation two days ago.

2 Likes

UPDATE:
I posted a ticket on Github for this and the dev posted back saying that the Home Kit integration is unreliable and they’ve seen this problem. Its not likely getting fixed anytime soon, if at all.

@Ltek Mind posting a link to the GH issue?

Just set up a new Ecobee thermostat with the HomeKit integration and am seeing the same issue.

Disappointing to hear that the HK integration is considered unreliable. Would this have similar behavior with an Apple hub?

I believe this is the GitHub issue:

I see the post from @ltek but not the response from the dev.

I’ve setup an automation to reload my ecobee if the temperature and humidity are both unchanged for 30 minutes. If you are using the thermostat states for other automations it could lead to some unexpected behavior since it will go unavailable briefly during the reboot (i.e. if you are monitoring for a specific attribute like “fan on for x minutes”).

Yes, I’ve seen that issue occasionally. I moved over from NEST where this was a consistent issue (daily) and with ecobee / HomeKit I only see it every week. Could be around power fluctuations. I use a similar automation to reload it. For me it’s only on the current temperature sensor, the temperature in the climate entity continues to update.

The linked issue is short on data. We really need a diagnostic log when the problem is occurring and a debug log leading up to the problem.

In my case it is directly correlated to the ecobee going offline. Every time this happens I lose the thermostat’s sensor updates. As soon a I reload the HK integration for the ecobee the sensors begin to update again. If the ecobee remains up the sensors continue to update indefinitely (for weeks at a time now).

EDIT: If you are looking for a 100% repro, unplug the ecobee from the wall for a couple of minutes and then plug it back in. I have drywall and paint work going on at home and have done this several times, and each time the sensors stop reporting after plugging it back in while the climate entity’s states/attributes continue to update as normal.

The states (for temp and humidity) on the climate entity continue to update for me when the exposed sensors do not. I’ve created template sensors for those states and can use them reliably. The only downside is that the temperature is in full degrees instead of tenths.