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

Devices not showing up after logging into integration #735

Closed
theotherguy2175 opened this issue Jun 26, 2023 · 5 comments
Closed

Devices not showing up after logging into integration #735

theotherguy2175 opened this issue Jun 26, 2023 · 5 comments

Comments

@theotherguy2175
Copy link

Describe the bug

In the past this integration has worked great. Now all my devices show their entities as unavailable. So I removed and reinstalled the integration from HACS. I was able to get logged in using an app password and master token. But all the integrations shows is 1 entity that is: "Google Home (master Token)

Version of the integration

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

1.10

Logs

There are no logs that show up regarding this integration
@leikoilja
Copy link
Owner

@theotherguy2175 check the README section on how to enable logging and please provide detailed logs so we get a better understanding what's happening on your setup

@theotherguy2175
Copy link
Author

The only logs I was able to find were similar to issue #202 s logs. But after a reboot of the devices it still doesn't show up.

@leikoilja
Copy link
Owner

please enable debug log levels (following README) and paste here the output from the integration. it will help to see what steps the integration does and where might be the possible issue. Otherwise, it's impossible to guess what's happening on your setup

@theotherguy2175
Copy link
Author

I was able to get this from downloading the full logs:

ms, be sure to disable it if you experience issues with Home Assistant
2023-07-02 19:27:07.945 WARNING (Thread-LeaseMaintainer) [google.cloud.pubsub_v1.subscriber._protocol.leaser] Dropping 1 items because they were leased too long.
2023-07-02 21:11:45.493 ERROR (MainThread) [homeassistant.components.hassio.handler] /addons/core_google_assistant/changelog return code 500
2023-07-02 21:11:45.495 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch changelog for core_google_assistant:
2023-07-05 10:31:49.988 DEBUG (MainThread) [custom_components.google_home] Unloading entry...
2023-07-05 10:31:49.992 DEBUG (MainThread) [custom_components.google_home] Coordinator update interval is: 0:03:00
2023-07-05 10:31:52.254 DEBUG (SyncWorker_5) [glocaltokens.scanner] Creating zeroconf service browser for _googlecast._tcp.local.
2023-07-05 10:31:54.278 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Living Room speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device FamilyRoom TV. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Master Bedroom TV. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Living Room TV. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Kitchen display. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Garage speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Family Room Speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Master Bedroom speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device Laundry Speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
2023-07-05 10:31:54.279 DEBUG (MainThread) [custom_components.google_home] Finished fetching sensor data in 4.286 seconds (success: True)

@leikoilja
Copy link
Owner

as you see the error log says "We could not determine its IP address, the device is either offline or is not compatible Google Home device.".
there might be many issues why auto-discovery may not work, but none of them are related to this integration, but on how your network is setup. Perhaps you are using multiple subnetworks, but regardless zeroconf is unable to discover your devices on the local network

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants