01-02-2024 02:41 PM
Folks:
Google Home app often isn't refreshed with current room temp. Say at 11:00 am I open my app. Says my home is 70 degrees. If I throw away the app from memory and reload it, now it reads 67. I've turned on background refresh to the app and it doesn't fix it.
Worse is lately my house will be getting cold. App will say home is 67 and the furnace should be heating to 70 but nothing is on. I'll go into the app, power off the furnace, power it back on and then suddenly the furnace turns on and heats to 70. It is like the app is going to sleep. Any advice?
01-03-2024 08:27 AM
I am having the same issue I think. Did it just start a few weeks ago?
My temp isn't updating and the heater just runs until I log in to check what the sensors read. I've had it say 82 on some sensors, but the nest thermostat itself says 67 on the temp ring, thus the heater continues to run. range set to 69-72. Once I change the scheduled temp manually and maybe swap the active sensor it will update (or refresh) and all of a sudden realize it's hot and the kick on the A/C. It's just a yoyo back and forth, with the app not actually updating on it's own.
I personally think it's a bug in a recent update that people haven't realized en mass just yet.
01-03-2024 09:27 AM - edited 01-03-2024 09:29 AM
There MUST be a bug because for over a year I've had NO issues and now this is constant. My furnace will be 4 or 6 degrees colder than the heat that is called for, and the only way I can tell Nest to call for heat is to go into the app, click the "flame" icon, then click "off". Wait a few seconds, then click "heat" and then the app calls for heat to the furnace.
This is clearly a big issue and I'm at the point of needing to go a different direction with a smart thermostat--or just go old school. I'm now to the point where everyone in my home is wearing 2 layers of clothing and hats because, "Dad is making the house too cold to be able comfortable." It's only 65 degrees but we forget it has been 65 for 4 hours, while nest shows 71 in the circle. Furnace, meanwhile, is quite.
01-03-2024 10:01 AM
Does any one know how we submit a potential bug request or escalate to Google?
01-03-2024 10:59 AM
I would venture to say that the energy lost because of this over the past 1-2 months FAR outweighs any energy saving I would have had for the whole year. Pretty much costing me money to have an "energy saving thermostat". If it isn't addressed soon I'll have no choice to to move away from this system as well. Surely we aren't the only ones...
01-09-2024 11:07 AM
still no info from any admins on this?
02-23-2024 09:57 AM
Hello folks,
I know it has been a while, but I wanted to ensure that everything was covered here.
@ssokc, I reviewed our conversation on your thread, and I'm glad to see that everything has been resolved with the help of our team. For any future questions or concerns, don't hesitate to reach out to us — we're always here.
@TKHanson1, the discrepancies in temperature readings and the delay in activating the furnace seem indeed troublesome. Here are some suggestions that might help:.
If the problem persists, tell us more about the steps you have taken so we can check for more options. Let us know if you need more help.
Best regards,
Mark
03-18-2024 04:43 AM
I’ve done all that and it’s not at my end, definitely an app or server issue especially with 3 Nest E thermostats! Check my post for App Lagging Behind Schedule. Still waiting for a response from that post. 🤔
03-18-2024 04:39 AM
I’m having a similar issue iOS, iPad AND iPhone! My schedule calls for heat with 3 Nest E thermostats, I open app and see heat is on but temperature is displaying nighttime temperature of 64* but all 3 thermostats are displaying schedule temperature of 68*, 68* and 66*. Something is wrong with this app or the server. The app is updating displaying in Heat mode though. The funny thing is if I manually put in Away Eco displays almost instantly. 🤔