3rd Gen Thermostat will not wake

[KenF]

I’ve owned my nest 3rd generation learning thermostat since 2019. This issue started in November 2022. I search forums and found a couple similar issues with locked threads but no solution.

My display doesn’t come on when I approach or touch it. The battery is fully charged and power within specs. I hear clicking and I can push and change settings like temperature and see it reflected in the phone app. After making changes and continuing to turn the dial and push in it may eventually respond. It will always start working if I hold in for 10 seconds and restart. This is not a power or battery issue and I’ve not found an answer in forums or other online resources.

I called an hvac pro, they came out and tested the wiring, line voltage, etc and stated everything is good to the thermostat.

[aatienza]

Hey KenF,

I’m sorry to hear you’re having trouble with this. No worries, we'll check this out. Is the thermostat's display seated properly? Are all the wires of your thermostat seated firmly in its terminals (with no loose or exposed wires)? Could you check if you're able to control your thermostat in the Google Home app? If so, send us a screenshot of your power reading.

Thanks,

Archie

[KenF]

I ended up reaching out through the support form found in another post and they had me do a full reset and the thermostat display has been waking and responding for the past 13 hours.

Unfortunately, the full reset meant starting over with everything including seasonal savings but otherwise the thermostat display is responding.

I mentioned in the original post this is not a power issue, I did all of the basic troubleshooting and even had a hvac pro come out and test everything with equipment. But to answer specifically all wires are fully seated and the power has read consistently as follows the entire time I’ve had this issue. Also, I have never received low power alerts and I could control the thermostat through the app and google home.

Battery: 3.931V, Voc and Vin: 32.71V, Lin: 200mA

It has been 13 hours since I received the support message and completed the full reset. If the thermostat continues to respond today, I consider this resolved.

Thank you for responding and assisting.

[Jhonleanmel]

Hey KenF,

Awesome — glad to hear that your issue is fixed. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.

Best,
Mel

[Jhonleanmel]

Hey there,

Checking back in should you still have some questions here. Let us know by replying to this thread.

Best,
Mel

[Jhonleanmel]

Hi everyone,

Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.

Thanks,
Mel

[KenF]

I am still having issues with the thermostat and have been working directly with the nest support team around solution options. I will post if a solution is found. 

[EmersonB]

Hello everyone,

@KenF thanks for getting back to us. Sounds like a plan. I'll keep this thread open but please be advised that as Community Specialists, we occasionally do a bit of housekeeping to keep the conversations in our community fresh and relevant. This includes locking threads after a period of inactivity.

I appreciate your help, Mel and Archie.

Best,
Emerson

[Markjosephp]

Hi there,

Thanks for assisting, Emerson.

@KenF, I wanted to follow up and see if you are still in need of any help. Please let me know if you are still having any trouble from here, as I would be happy to take a closer look and assist you further.

Regards,

Mark

[KenF]

The thermostat is being replaced with a new one, so I no longer need assistance. IT t seems it is a defective thermostat. Thank you.  

[Markjosephp]

Hi KenF,

Sounds great! I'm glad to know that it was sorted out and will be replaced. So I'll lock this thread in 24 hours, and if you have any other concerns or questions, please start a new post. 

Thanks,

Mark