07-23-2024 03:39 PM
I recently had to reset and add my thermostat back to my Nest app due to a thunderstorm frying my modem. Troubleshooting that led to factory resetting my router, thanks Xfinity, which then my thermostat couldn't connect to the WiFi because changes.
Anyway, after all of that my thermostat was acting differently. Before I could tell that it was accurately, in my mind, sensing the temperature and reacting accordingly (cooling in this season). Now it will let the entire house get up to the desired temperature (74 F) and turn on my A/C. I know for a fact that the thermostat is in a warmer part of the house so I was confused why it takes so long now. The thermostat and the Nest app read the same but when I pulled up the web client the temperature it showed was 77 F. Oddly enough when I looked there the temperature updated on the thermostat and Nest app.
I guess my question / concern is why the wide difference in temperatures? And why is my thermostat not reflecting that until I bring up the web client? There's a 0.5 C rounding or something that I read but this is a good 3 F difference, which is about the same I suppose. Am I being too overly concerned or is the difference between the app / thermostat vs the web client something I need to fix?
07-27-2024 03:22 PM
Hi MinimumForce,
Thanks for posting in the community! I apologize for the inconvenience you're experiencing with the Nest Learning thermostat's target temperature not matching between the web and app. Help's here!
To better assist you, please provide the following information:
In the meantime, you can try clearing your computer's cache and restarting both your computer, WiFi router, and Nest thermsotat device to refresh the connection. For reference, you can check out the following article: Restart or reset a Nest thermostat.
Please keep me posted.
Best regards,
Jenniffer