search

chrisjshull / homebridge-nest

Nest plugin for HomeBridge
699 stars 112 forks source link

Nest Account Problem - Could be a wider issue... #571

Closed jamie-2bit closed 1 year ago

jamie-2bit commented 1 year ago

After years of runing the Nest thermostat using a Nest account (not Google), I'm getting these errors, along with timeouts using the nest app and the browser web app. Could be a server-side issue but thought I'd raise it here too.

[10/13/2022, 8:04:40 PM] [Nest Thermostat] Nest API call to subscribe to device settings updates returned an error: ENOTFOUND [10/13/2022, 8:04:40 PM] [Nest Thermostat] Retrying in 10 seconds.

I've made sure the Access Token is correct and updated, still having issues. Based in Australia (in case it's localised)

St3faan commented 1 year ago

I have the same issue, but with a google token login. I've refreshed the tokens, but no luck getting it to work again.

[10/13/2022, 4:13:58 PM] [Nest] initing thermostat "Living Room Thermostat" [10/13/2022, 4:13:58 PM] [Nest] initing home_away_sensor "Home Occupied" [10/13/2022, 4:13:58 PM] [Nest] initing protect "Attic": [10/13/2022, 4:13:58 PM] [Nest] initing protect "Living Room": [10/13/2022, 4:14:04 PM] [Nest] Nest API call to subscribe to device settings updates returned an error: ENOTFOUND [10/13/2022, 4:14:04 PM] [Nest] Retrying in 10 seconds.

mbierman commented 1 year ago

I use a nest account and things look o.k. to me so far.

pespinel commented 1 year ago

Same issue here with a Google refresh token:

[13/10/2022, 20:33:23] [Nest] Nest API call to subscribe to device settings updates returned an error: ENOTFOUND
adriancable commented 1 year ago

ENOTFOUND is a DNS lookup error. Feels like a Nest service issue. Backed up by @jamie-2bit's finding this also happens with the Nest app. Will leave open for now and please reach out in a couple of days if it still happens.

jamie-2bit commented 1 year ago

Update: Switching my iPhone to celular data (not wifi) allows me to log into the nest app. I'll try switching off PiHole and changing local network DNS and see if that works. I'll report back here.

jamie-2bit commented 1 year ago

Switching off PiHole doesn't make a differance. PiHole DNS Logs seem ok..

2022-10-14 08:04:34 | A | czfe93-front01-iad01.transport.home.nest.com | Nest-Thermostat.local | OK (answered by one.one.one.one#53) | CNAME (7.4ms)

2022-10-14 08:04:32 | A | czfe61-front01-iad01.transport.home.nest.com | Nest-Thermostat.local | OK (answered by one.one.one.one#53) | CNAME (8.0ms)

2022-10-14 08:04:30 | A | czfe07-front01-iad01.transport.home.nest.com | Nest-Thermostat.local | OK (answered by one.one.one.one#53) | CNAME (7.1ms)

2022-10-14 08:04:30 | AAAA | czfe89-front01-iad01.transport.home.nest.com | localhost.localdomain | OK (cache) | CNAME (0.2ms)

adriancable commented 1 year ago

Try turning on Personal Hotspot on your iPhone, connect your Homebridge machine to that, then reboot your Homebridge machine (Linux maintains a DNS cache) and see if it works.

jamie-2bit commented 1 year ago

I think I've found the issue. I've switched my local network from using the CloudFlare DNS servers (1.1.1.1) to the Google DNS servers (8.8.8.8) and all Nest related problems have resolved themselves.

St3faan commented 1 year ago

Hi all,

I switched to the cookie method, as the google token method does not work anymore.

Furthermore, I also noticed issues with the nest app. After changing my network DNS server from 1.1.1.1 to google's 8.8.8.8, this issue was solved. Disabling PiHole did not resolve the issue.

However, changing the DNS servers did not solve the "[Nest] Nest API call to subscribe to device settings updates returned an error: ENOTFOUND" error.

Anyone else with the same issue?

ingvaldlorentzen commented 1 year ago

I'm also experiencing this. Running Pi-hole with Cloudflare DNS. Switched over to Google account a couple months back, with refresh token in the config.

jamie-2bit commented 1 year ago

Hi all,

I switched to the cookie method, as the google token method does not work anymore.

Furthermore, I also noticed issues with the nest app. After changing my network DNS server from 1.1.1.1 to google's 8.8.8.8, this issue was solved. Disabling PiHole did not resolve the issue.

However, changing the DNS servers did not solve the "[Nest] Nest API call to subscribe to device settings updates returned an error: ENOTFOUND" error.

Anyone else with the same issue?

@St3faan I’m almost 100% sure this issue is a DNS problem with Cloudflare. I’d double check that all Nest devices and apps are using the Google 8.8.8.8 DNS, ie flush cache and restart devices.

jamie-2bit commented 1 year ago

I'm also experiencing this. Running Pi-hole with Cloudflare DNS. Switched over to Google account a couple months back, with refresh token in the config.

@ingvaldlorentzen Did switching your DNS servers in PiHole from Cloudflare to Google fix your issue?

ingvaldlorentzen commented 1 year ago

Tested it now, and that does seem to solve the issue. Weird..

jamie-2bit commented 1 year ago

It seems that one of the causes of this issue is using a Cloudflare DNS server and the solution is to switch over to a Google DNS server. It could just be a temporary problem with Cloudflare, only time will tell. I'll close off this issue & thanks everyone for your help in solving it.