topic Re: Nest Temperatur Sensor won't switch from C to F in Nest Thermostats

Nest Temperatur Sensor won't switch from C to F

ausdfra — Sun, 01 Feb 2026 18:38:20 GMT

I have a home with multiple Nest learning thermostats (gen3 and gen4) and temperature sensors (gen1 and gen2). Some of the sensors display correctly in F, all the thermostats display in F and some of the sensors display in C. There is no setting on the sensors to allow me to change the display option. How can I correct this? See attached photo from Google Home (android) app.

https://photos.app.goo.gl/DFGhSi9hGVbXn7Ry5

Re: Nest Temperatur Sensor won't switch from C to F

BrianGS — Thu, 05 Feb 2026 04:00:48 GMT

Hi @ausdfra,

Thank you for posting in the community. I’m sorry to hear that some of your Nest Temperature Sensors are reporting in Celsius while your Nest Learning Thermostats and other sensors are correctly displaying in Fahrenheit. I understand how important it is to have all your devices consistent with your preferred temperature units. I appreciate you sharing the photo showing how this appears in the Google Home app. I'm happy to help you with this. Since you mentioned all your thermostats are already set to Fahrenheit on the Google Home app, could you please double-check the settings directly on the thermostats' displays?

Press the ring on your thermostat to bring up the menu.

Turn the ring to find the Settings (gear icon) and press to select it.

Turn the ring to find the Units option (ºF/ºC).

Press the ring to select it, then choose Fahrenheit.

Please keep in mind that Nest Temperature Sensors use Fahrenheit or Celsius based on the settings of the specific thermostat they are linked to.

Please let us know if you have any other questions!

Best regards,

Brian.

Re: Nest Temperatur Sensor won't switch from C to F

InTheWoods — Mon, 16 Feb 2026 21:21:52 GMT

I had the same problem with mine. My 4th generation thermostat showed degree's F and the sensor (on the app) showed degree's C. Changing settings on the thermostat or on the app yielded no results. Finally just closed the app and re-opened it and the problem went away. Should have tried the easiest solution first I guess!