10-23-2023 06:34 AM - edited 10-26-2023 06:58 AM
Hello everybody,
any updates from Google about the issue of wrong outside temperature? Years have passed, you can find many discussions closed (why?):
https://www.googlenestcommunity.com/t5/Nest-Thermostats/Wrong-outside-temperature/m-p/20404
Changing the zip code to something near you fix the problem but this is not the solution: if you do that, the feature "Home/Away" will stop working (probably because it tries to match the address with mobile, but since you have changed the zip code for fixing the wrong outside temperature, the system will recognize you always "away")
Thank you.
10-24-2023 01:50 PM
I'm starting debugging the issue by myself, at least on what I can do and with the tool at my disposal.
The main issue for the wrong outside temperature in the Thermostat 3rd generation is that still using weather.nest.com (and not weather.com as supposed) for grabbing the outside weather.
You can see the packets captured with tcpdump and ntopng.
Said that, this machine have some ports open to the world:
PORT STATE SERVICE
80/tcp open http
135/tcp filtered msrpc
139/tcp filtered netbios-ssn
443/tcp open https
445/tcp filtered microsoft-ds
As you can see the http (80) and the https (443) are open but if you try to reach http://weather.nest.com or https://weather.nest.com you will get an error 404
So, how can the thermostat getting the right weather if the service is not running? (or blocked, or something else?)
This is true for Nest thermostat with 5.9.5-2 software version
@David_K @CoolingWizard @Patrick_Caezza @jenelyn_O : could someone of you please help in passing this message to Google?
Thanks in advance.
10-25-2023 01:08 PM
Another interesting thing: home.nest.com uses https://home.nest.com/api/0.1/weather/forecast/<zipcode>,<countrycode>
to obtain the data. So in my case the complete url it's: https://home.nest.com/api/0.3/weather/forecast/10010,IT
Running
curl -q -s https://home.nest.com/api/0.1/weather/forecast/10010,IT |grep current_temperature
I get
"current_temperature":6.1,
and this is the same temperature (wrong) shown on the thermostat. If I try to change the zip code to a city close to mine, it works fine.
Now the questions is: who is in charge of managing the API of nest.com? They should be managed from Google as the company has been acquired from big G. Am I right?
10-25-2023 01:25 PM
Appreciate you sharing those details. I've asked a specialist to review this topic and advise on next steps. Just so you know, it may take a short while for them to do that.
10-25-2023 11:51 PM - edited 10-26-2023 03:08 AM
Thank you very much @David_K !
I would also sharing this: the thermostat and the app are reading the weather data from different sources:
Thermostat is reading the weather information from weather.nest.com
App (home.nest.com) is reading the weather information from https://home.nest.com/api/0.1/weather/forecast/<zipcode>,<countrycode>
Google home app: not yet tested
Sometime this cause a little discrepancy from the temperature you see on the app and the one you see on the thermostat. (from 0.5 to 1 degrees when I tested it)
It should be nice if Google could use an unique weather source, basically the same for device and app.
Thanks again.
11-21-2023 03:50 PM
Hello everyone,
@fabreg, thanks for bringing this up here at Google Nest Community. I appreciate you posting and updating us on your efforts to address your concern, and we wanted to look deeper into this. Please answer the following:
Thanks for looking into this, @David_K.
Keep us posted.
Best,
Renz
11-22-2023 03:03 AM - edited 11-22-2023 03:19 AM
Hello @RenzJ
Running the commands once again:
~$ curl -q -s https://home.nest.com/api/0.1/weather/forecast/10010,IT |grep current_temperature
"current_temperature":7.2, (wrong)
~$ curl -q -s https://home.nest.com/api/0.1/weather/forecast/10015,IT |grep current_temperature
"current_temperature":14.4, (correct)
It seems a problem of the data exposed by the API (hosted at home.nest.com)
Thanks!