Got the same problem here.
Thermostat shows in Hassio.
Initialy it gets the right data.
But does not update at all.
I can change temp and it will trigger the nest thermostat.
But if I change the thermostat on its own, nothing happens in Hassio.
An update_entity does nothing, restarting the nest service does.
Removed and recreated all google links and stuff over 9 times now. Hope someone figures it out 
Has to be a problem with the integration or card since we are all getting it. Cannot be a setup issue as I tried it multiple times too. Will have to wait for an update or someone to come up with “hack” to force an update every 15 minutes or something.
Same problem with my Sensi Thermostat integration, thought it was just me. Only updates settings after a restart of HA.
Hello there! I am using eq3 BLE TRVs (through eq3btsmart) and I am getting the same behaviour for entities coming through a remote home assistant installation (using the ‘remote home-assistant’ integration). On the local one, they work fine. The remote ones only update their status if I manually reload the ‘remote home-assistant’ integration. As a workaround, how can we automatically reload integrations?
To all those who had this issue of HA Cards not updating – did you resolve it, if so how?
facing same issue with Tuya WIFI thermostat 
any luck to fix this ?
I have the same issue and no fix just an observation.
To the zwave communiity:
I have the Radio Thermostat Company of America (RTC) - CT101.
The cards are just fine and update but what is not refreshing correctly is zwave-js. I downloaded the zwave to MQTT and have way more control than the standard zwave-js. I am able to refresh the operating state sensor from the console now and I can get the card to change. So, the card is fine but how can I get zwave to refresh the sensor when it is triggered on and monitored until off?
Seems like a refresh thing in the thermostat or zwave module. But I am having the same issue as everyone else.
Same issue here. I just went through hell and back setting up SSL and external access (damn websockets) for this one integration that doesn’t seem to work. External access goes against all of my security best practices too! One-two punch and I’m out, sorry Nest, in with the EcoBee (for the second time now).
I see the same behavior with some Tuya zigbee radiator thermostats. Initially they all worked okay, now one or both fail to update for hours and hours. Oddly, the temperatures match i.e. with the Smartlife app, so I am not sure if this is an actual HA problem.
I would beg to differ that this isn’t a HA problem. The temps match but the status does not. Not too sure why. I have every one of my 50 other devices work as they should and show the correct current action/status of the device. The/my thermostat has never shown the current status correctly even after many add/removes I have done to get it to work as it should. Not a big deal but would like to see it work correctly. I never had this issue in Smartthings. It showed what was happening on the device. This is an HA issue and this should work better than it is.
Just to add to this… I switched over my radiator valves from a Tuya hub and Tuya integration to a Zigbee coordinator and ZHA and still get this exact same behavior.
Updated 2 or 3 times after pairing, and not since (2 hours). Even reloading ZHA doesn’t change it.
I think there may be a multitude of root causes for this symptom. I was similarly able to control my thermostat, but the state wasn’t updating in the lovelace UI.
I found error messages in my home-assistant.log indicating that the nest integration python script was trying to unpack celsius values from Google’s response. Changing my units from metric to imperial fixed the issue for me.
It occurred to me to try this because I recently changed from imperial to metric, and noticed a few days later that the thermostat view was broken. Note that you should change the units in configuration.yaml (after restart, those will always override the units you set from the UI).
for the history of this issue, likely folks in 2020 had pubsub misconfigured which is no longer possible to do.
what is this about Celsius and Fahrenheit errors? That sounds like a huge unexpected problem that needs to be fixed. What was logged?
Context: am nest integration maintainer
Sigh - I restarted the homeassistant and lost the logs. Is there some place where logs from previous runs are backed up?
I am unsure what is happening but even though this post is from 2020, it seems that this problem returned. I have noticed that the HA integration is not updating the set temperature unless you reload the integration. It does respond to the set temperature on the Nest itself, but just doesn’t report it back to HA. This happens every few days it seems and then after the reload it works again for a while.
I did notice the fact that if you rapidly change temperatures (noticed during testing), that it throws API errors about having too many API calls in a short time frame and I am wondering if that is why it fails to report the set temperature back to HA.
The API has rate limits, independent of any update problems.
I would say run the release 2025.2.x which is being released tomorrow and see if it resolves your issue (there seemed to be an issue where things were getting stuck, and the subscriber has been rewritten and that avoids it). Otherwise, file a github issue report and fill out the template with the requseted information if you think there is an issue.
ah that makes sense. Let’s hope that fixes the issues. Thx for the quick response!
I am glad you asked this question. I had the same issue start happing again a few months ago with my card not updating. What I did to fix it at least for now was to lower the reporting threshold to 0.5. Since doing that my card is now reporting and updating correctly.
I will move it back after this next update to see if it was fixed. I will report back and let you know if it fixed the issue. But try what I did above if the update does not help.
Z-Wave? My Nest thermostats have their own integration: Google Nest. I’ve never had a problem with them.
What did you mean by Z-Wave? Yes, there are numerous integrations and happy you are on Nest. This Is a card that isn’t updating no matter the integration.
