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.

Humidity reading 10 pts higher than what it should be

nestseattle
Community Member

Same as this earlier thread https://www.googlenestcommunity.com/t5/Nest-Thermostats/Nest-Humidity-Reading-Incorrect/m-p/211522/p... which has been locked which numerous people have called out. This seems to be an issue with the firmware update which has changed the sensor to give a reading which is 10 pts higher than what it should be. For example, if other humidity sensors in home state the humidity is 53%, then Nest thermostat says it is 63%.  I have done the suggestions of resetting, removing and putting back on, replacing the unit entirely etc. already. 

3 REPLIES 3

Markjosephp
Community Specialist
Community Specialist

Hello nestseattle,

 

I'm sorry for the late reply. It appears that you've exhausted all the possible steps on your end. Let's sort this out.

 

  • What type of Nest thermostat do you have?
  • When was the thermostat installed?
  • When did the issue start?
  • Do you have other active Nest thermostats?
    • Do they show the same issue?
  • Is your thermostat installed near any heat source, such as air vents that direct warm air, appliances (that include large televisions), electrical outlets, or other potential heat sources?

 

Going over the steps here might help:

 

  • Go to Settings > Technical Info > Network.
    • Get the signal strength value.
  • Turn on Sunblock under Nest Sense.
  • Apply a duct seal compound to the location where the thermostat is installed to close the penetration on the wall and serve as an insulator.
  • Disconnect your thermostat from your Wi-Fi network within 24 hours.

 

Please let us know how it goes.

 

Best regards,

Mark

Hi there,

 

I'm checking back in. Were you able to do the steps above? I'd be glad to hear from you — I'd like to make sure everything is working.

Best regards,

Mark

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