cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Nest not turning heat on. 3rd Gen nest runninbg firmware version

Tenna1dt
Community Member

3rd Gen nest running firmware version 6.2-22 will not turn furnace on.  Set at 69, house is 59.  Running fine some days, but randomly works, then doesn't. Factory reset (as recommended by Nest Support) didn't work.  Getting standard "2+ hours" message.  Seems like quite a few customers are experiencing same issue but the concern has yet to be resolved.  Should I replace with an Ecobee? 

6 REPLIES 6

jennytulipani
Community Member

I am experiencing a the same problem.  In the northeast where I live this is a real issue. 

Ryan_G
Community Specialist
Community Specialist

Hi everyone,

 

Thank you for reaching out and we're sorry for the delay.

Let's try the following for us to further isolate the issue:

  • Restart your Nest thermostat.
  • Remove the thermostat from the base. Check all the wires are properly inserted.
  • Check your HVAC filters and drip pans for clogs.
  • After a restart, go to settings > equipment > select the right heat type and source based on your HVAC system.

Let us know how it goes by replying to this thread.

 

Regards,

Ryan

jimmac
Community Member

did you receive a positive fix to your recommendations since I have the same issue

Ryan_G
Community Specialist
Community Specialist

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


 

Surreal2020
Community Member

I have a similar issue. When I use the Gen3, no heat (blower turns on, shows orange/heating on the display). Swap back the Gen2, everything works fine. 

jimmac
Community Member

I have exactly the same issue!!!!!!