Closed poindextrose closed 1 year ago
ENOTFOUND is a DNS lookup error. Your machine for whatever reason isn't able to make DNS lookups, probably as some consequence of the outage. It isn't a plug-in issue, or a Homebridge issue.
Thanks for looking into this. I wish it was that simple. While DNS was unavailable for a short period of time when DNS came back on the homebridge-nest plugin was unable to reconnect to the API. Everything else on the system was functional and the ONLY thing I did to restore the plugin to working status was to restart the plugin from the homebridge UI. After restart it worked as expected.
I'll see if I can reproduce with a minimal example.
@poindextrose - the error you are getting is from the Linux network stack: getaddrinfo ENOTFOUND grpc-web.production.nest.com
It's likely that Linux's DNS cache remained stale for a little while after the network came back. It's possible that restarted the Homebridge process flushed it. Unfortunately, if you are getting ENOTFOUND errors from the network stack, it's completely beyond my influence.
My network went down due to power outage while homebridge continued to run on a laptop. After the network/power returned (40 minutes later), homebridge-nest was still unable to connect to Nest 9 hours later when I realized it wasn't connected. After I restarted the child bridge it immediately connected to Nest API.
Here are the logs when the network went down. It was doing it's normal things with "illegal value" as it always does then we lose network at 8:58:37 AM when we see the ENOTFOUND.
The log continues this repeat the same error message but then changes do reauthenticating at 6:30:49
...repeats until I restart the child bridge at 6:54:04PM
Config
Recently install home bridge and this plugin a few weeks ago on a new machine node -- version v12.22.9 npm homebridge --version 8.5.1