Open heyepic opened 8 months ago
I have the same issue with Google home devices on different networks
it essentially boils down how zeroconf package works and whether or not it can detect the devices living on a different network. Is you home assistant instance on the same network as google home devices?
Main SSID network can communicate with new IoT VLAN as mDNS allows for it. Other Google Home integrations I have setup see the devices on the new VLAN but this add-on does not.
Ideally it works like the Google Cast integration where you can specify if mDNS fails:
it would be interesting to look through the code of how other integrations discover network devices and make use of that in this package as well.
having a configuration to manually add "known hosts" would be great, so any PRs are very welcomed :)
One two three, not it! But I agree, the code is out there to take it seems. :)
Thanks for the add-on, regardless. Have been using it for awhile - and hope to continue to do so.
Same problem like other said.
Logs: 2024-01-09 23:45:19.736 DEBUG (SyncWorker_1) [glocaltokens.client] Successfully initialized 3 Google Home devices 2024-01-09 23:45:19.747 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device xxy speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later. 2024-01-09 23:45:19.747 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device xxx speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later. 2024-01-09 23:45:19.747 DEBUG (MainThread) [custom_components.google_home] Failed to fetch timers/alarms information from device XXX speaker. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later. 2024-01-09 23:45:19.747 DEBUG (MainThread) [custom_components.google_home] Finished fetching sensor data in 3.220 seconds (success: True)
My Google Home Pods are in other vlans like homeassistant instance.
greetings
Describe the bug
I have about 15 Google Home devices. I recently took advantage of a feature on my Amplifi Alien router which creates a new SSID for IoT devices. I'm in the process of removing all devices from current WiFi and moving them to the new IoT SSID.
The problem is when the integration grabs all devices, it did not detect the new device I moved to a separate vlan. Any ideas as to how to make sure it sees these moved devices? The display in question is "Office Display" which is a Nest Gen 2 Hub. You'll see it in the logs below.
The IoT SSID Nest Hub is currently connected to the internet and I can see it in the Google Home app with it living on its new SSID.
Version of the integration
If you are unsure about the version check the github release here.
Logs