Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nest Mini Device has gone missing #227

Open
TwoWheelDev opened this issue Apr 21, 2021 · 5 comments
Open

Nest Mini Device has gone missing #227

TwoWheelDev opened this issue Apr 21, 2021 · 5 comments
Labels
question Further information is requested

Comments

@TwoWheelDev
Copy link

Describe the bug

After installing the package from HACS, I could see our 3 google devices (2 nest mini speakers and a chromecast). When I went back to setup some automations today I noticed one of the nest speakers was unavailable (Bedroom speaker).

So far I have done the following:

  • Restarted Nest Mini
  • Confirmed the Nest Mini is connected to the network and shows in the Google Home app correctly.
  • Removed and re-added the integration to Home Assistant - at which point it only discovers two devices

As can be seen from the logs HA is unable to the IP address of the device

Version of the integration

If you are unsure about the version check the github release here.

1.4.3

Logs

2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.scanner] Got 2 devices. Iterating...
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.scanner] Appending new device: {name:Lounge speaker,ip:192.168.1.115,port:8009,model:Google Nest Mini}
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.scanner] Appending new device: {name:Bedroom TV,ip:192.168.1.121,port:8009,model:Chromecast}
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Iterating in 7 homegraph devices
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] 'TV' local_auth_token is not found in Homegraph, skipping
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] 'Bedside Light' local_auth_token is not found in Homegraph, skipping
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] 'Bedroom Light' local_auth_token is not found in Homegraph, skipping
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Looking for 'Bedroom TV' in local network
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Bedroom TV] Initializing new Device instance
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Bedroom TV] google_device is provided, using it's IP and PORT
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Bedroom TV] Set device_name to "Bedroom TV", local_auth_token to "r***********************************************************************************************************", IP to "192.168.1.121", PORT to "8009" and hardware to "Chromecast"
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Adding Bedroom TV to devices list
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Looking for 'Lounge speaker' in local network
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Lounge speaker] Initializing new Device instance
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Lounge speaker] google_device is provided, using it's IP and PORT
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Lounge speaker] Set device_name to "Lounge speaker", local_auth_token to "B***********************************************************************************************************", IP to "192.168.1.115", PORT to "8009" and hardware to "Google Nest Mini"
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Adding Lounge speaker to devices list
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Looking for 'Bedroom speaker' in local network
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Bedroom speaker] Initializing new Device instance
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Bedroom speaker] google_device is not provided, using manually provided IP and PORT
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] [Device - Bedroom speaker] Set device_name to "Bedroom speaker", local_auth_token to "x***********************************************************************************************************", IP to "None", PORT to "None" and hardware to "Google Nest Mini"
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Adding Bedroom speaker to devices list
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] 'Lounge Light' local_auth_token is not found in Homegraph, skipping
2021-04-21 21:03:36 DEBUG (SyncWorker_4) [glocaltokens.client] Successfully initialized 3 Google Home devices
2021-04-21 21:03:36 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Bedroom speaker. We could not determine it's IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2021-04-21 21:03:36 DEBUG (MainThread) [custom_components.google_home] Requesting endpoint setup/assistant/alarms for Google Home device Bedroom TV - https://192.168.1.121:8443/setup/assistant/alarms
2021-04-21 21:03:36 DEBUG (MainThread) [custom_components.google_home] Requesting endpoint setup/assistant/alarms for Google Home device Lounge speaker - https://192.168.1.115:8443/setup/assistant/alarms
@DurgNomis-drol
Copy link
Collaborator

DurgNomis-drol commented Apr 21, 2021

This is probably related to the same problem i have #202.

@KapJI
Copy link
Collaborator

KapJI commented Apr 21, 2021

It's a different issue. Here it's not timing out, it was not discovered by zeroconf.

In leikoilja/glocaltokens#69 I reduced zeroconf timeout to 2 seconds. Maybe it's too low? Can you modify it manually (find glocaltokens/const.py in installed module) and set it back to 20 seconds?

@TwoWheelDev
Copy link
Author

So after being somewhat busy with university, and not having time to look at this it seems to have resolved itself. The device that was missing has now been discovered... hopefully it doesn't disappear this time around!

@TwoWheelDev
Copy link
Author

Okay, my joy was short lived... I now have two devices showing as unavailable!
image
image

Annoyingly my old V1 chromecast, shows up fine...
image

@KapJI where would I find glocaltoken/const.py (not too familiar with the underlying structure of HA and where to edit stuff!)

@KapJI
Copy link
Collaborator

KapJI commented Apr 28, 2021

@DLintott Please show your logs to begin with.

glocaltoken/const.py is somewhere where python installs packages in your system. It's very hacky to modify it right there.
I think simpler way to do the same thing will be downgrading glocaltokens to 0.3.0. For this edit manifest.json in custom_components/google_home folder, reboot HA and make sure it pulls 0.3.0 and installs it (you can follow that in logs)

@ArnyminerZ ArnyminerZ added the question Further information is requested label Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants