Problem with google nest thermostat "urgent" alert in 2-zone system

[JAntP]

All of a sudden I seem to be getting bogus alerts that there may be something wrong with my heater because my downstairs thermostat is registering temperature declines during periods that my upstairs zone heater is on.  This seems to be a logic failure where Google is not distinguishing between zones.  At night when my downstairs thermostat turns way down, but my upstairs thermostat stays higher to keep us comfortable while sleeping, it is normal for the upstairs unit to be on while the temperature falls downstairs.

Thanks!

[Ryan_G]

Hey JAntP

Thanks for reaching out and we're sorry for the delay.

There could be multiple factors on why you're getting this alert from your thermostat. Check the temperature schedules. Try to restart your Nest Thermostat and pull it off the base for a couple of minutes. Check the surrounding of your thermostat placement as there might be some interference that possibly causes this alert to happen.

Let us know how it goes.

Regards,

Ryan

[Ryan_G]

Hey JAntP,

I just wanted to follow up and see if anyone is still in need of help? Please let me know, as I would be happy to answer any questions you may have.

Best regards,

Ryan

[JAntP]

I just responded to your question, but accidentally attached it as a response to my initial post.  Please see my following 2 responses, which are responding to your inquiry.

Thanks for following up.

[Ryan_G]

Hi JAntP,

Thanks for providing the details.

Few questions to further isolate the issue:

• Which Nest Thermostat are you using for your 2 zone system?

• Have you tried checking for the available updates? What's the current firmware update being installed?

• Does clearing or deleting the temperature schedule help?

Let me know by replying to this thread.

Regards,

Ryan

[JAntP]

I have 2 nest (not the learning) thermostats, one downstairs and one upstairs.  From my Google Home app, it looks like the thermostats are running software versions 1.1-9, although I have been assuming that the bug is coming from Google's servers, from whatever service is analyzing the data my thermostats is sending them.

I have not attempted to clear and reset the the temperature scheduled, as the schedule is somewhat complex to replicate and the issue hasn't caused any practical issue issued for me.  It's just annoying because Google's sending me false warnings and I'm now just ignoring them, which is a shame because I'm not getting the benefit of that monitoring. 

[Ryan_G]

Hi JAntP,

Thanks for your reply and we'll take this as feedback to improve our product and services.

If you have any other concerns, please don't hesitate to get back to us through this thread.

Regards,

Ryan

[JAntP]

Yes, there's a bug in Google's software and it reports false alarms.  It reports that my heater was on when it wasn't and thinks there's a problem because the temperature falls.  

Looking more closely at the timing of the reports, the issue seems to crop up right before a scheduled reduction in thermostat temperature setting occurs and the warning reports that my heater was on for several hours alongside temperature reductions which are false.  I wonder if it is because the heater is going on 5-10 min before the scheduled temperature reduction happens.  So for example -- I'll have a scheduled temperature reduction at 7:30am, when the thermostat is cut from 73 to 63 and the temperature isn't supposed to go back up to 73 again until 3:30 in the afternoon.  But I'll get a warning saying my heater was on from from 7:23am until 11:30am and the temperature was falling, so there might be something wrong with my heater.  This is not true as the thermostat reset down to 63 at 7:30 and the heater wasn't on at all between 7:30am and 11:30am.  

The code that is analyzing data has a bug.

[JAntP]

Just to substantiate my post above.  The email will say the heater was on from X time to Y time, but Google Home will show in the reported heater run times that the heater wasn't on at all for almost that entire period. So in my preceding example, the Google Home data I access in my app clearly shows that my heater didn't run at all between 7:30am and 11:30am, as should be the case since the scheduled temperature reduction occurred at 7:30am.  Everything's exactly right.  Just I'm getting an erroneous urgent warning message via that my heater was on during that period.  

[Ryan_G]

Hey folks,

Thanks for visiting the Google Nest Community. 

Since this thread hasn't had activity in a while, we're going to close it to keep content fresh.

If you have additional questions, feel free to submit another post and provide as many details as possible so that others can lend a hand. 

Hope this helps!

Kind regards,

Ryan