-
Notifications
You must be signed in to change notification settings - Fork 74
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
Can't find Google Home device on separate vlan #774
Comments
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? |
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: 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
The text was updated successfully, but these errors were encountered: