Google nest eco mode Problem

[mchen]

My nest thermostat switches into eco mode in the middle of the night when we are sleeping. I have checked my settings and my phone location settings. The home and away assist says it has not been reading my phone do I rechecked  location settings and are all set as per the instructions. Why is this happening? I need help. It is freezing us out when we sleep. 

[DP1]

Do you have google home speakers in your house?    I occasionally wake up around 3-4 am to find my thermostat set to 50 degrees.  The only pattern I see is whenever this happens one of my Google home speakers are offline and unable to reconnect to wifi.  I have no idea why it's offline since nothing else disconnected from wifi.   It's always a different speaker and it never reconnects until I unplug and plug back in.

[mchen]

No I do not have google speakers.  I am not sure what is happening or why. I am about to disable eco mode to spot this if I cannot figure out what is happening  I hate to do that for  savings and eco purposes. Thanks for trying to help. 

[DP1]

I disabled just about every feature and set eco mode to 70-76 and it's still happening. 

[mchen]

wow. I wish a real person would offer some help. I think I am beginning to hate this thermostat. 

[Markjosephp]

Hi folks,

Thanks for helping here, @DP1

@mchen, I'm sorry for any inconvenience caused by the unintentional activation of the Eco mode. Let's sort this out.

Phones contribute location data by reporting geofence crossings, which trigger Home/Away status changes. I'd suggest disabling the Home/Away Assist. Then, restart your thermostat to refresh.
 

Please let me know if that helps, or if the issue still persists.

Best regards,

Mark

[Markjosephp]

Hi mchen,

I'm checking back in — how's it going? Still need our help? Let us know so we can assist you right away.

Thanks,

Mark

[Markjosephp]

Hello mchen,

I'm checking in to make sure that you've seen my response. If you have any further questions or concerns, please let us know before we lock this thread in 24 hours.

Thanks,

Mark