-
Notifications
You must be signed in to change notification settings - Fork 77
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
Google WIFI router causing error - local_auth_token must follow the correct format #348
Comments
The device discovery feature is linked to your Google account, so that might be the issue why it adds the device from different homes, however, I find it strange that it's working at all, since all the requests are made locally, so if the Home Assistant installation is on one network, and the device on another, that should not work. For your question on Google WiFi, that's totally a bug, it shouldn't be recognized as a device. |
@jazzyisj and @CallumCVM i looked at the code implementation for client in
|
The integration is working exactly as expected. Concern 1 was the error raised by the google wifi. They do not appear to be causing an issue, I believe just reclassifying the log message as debug would probably be adequate. Concern 2 is fact that the integration is grabbing devices for a google home other than the intended one associated with HA. The underlying issue probably lies on the google end of things. There likely isn't a way to limit which "home" to fetch the devices from when dealing with multiple homes any more than there is a way to prevent HA entities from being added to a second home in the Google Home app. Not a big deal, any unwanted devices can always be disabled within HA. |
Done. Thanks! |
Describe the bug
Errors when Google WIFI on network. Interesting to note that this Google WIFI router is actual set up on a second home in the Googe Home app. It is not in my primary home. We should be able to limit this integration to a specific home.
Version of the integration
Logs
The text was updated successfully, but these errors were encountered: