Google WIFI router causing error - local_auth_token must follow the correct format
See original GitHub issueDescribe 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
v1.8.1
Logs
2021-09-21 01:34:27 DEBUG (SyncWorker_1) [glocaltokens.client] Looking for 'Google Wifi router' (id=8CCC28E85744C2B7DFE6E90A013B81A7) in local network
2021-09-21 01:34:27 DEBUG (SyncWorker_1) [glocaltokens.client] [Device - Google Wifi router(id=3c5639b1-7041-4fce-ad73-fe0d36da264f)] Initializing new Device instance
2021-09-21 01:34:27 ERROR (SyncWorker_1) [glocaltokens.client] [Device - Google Wifi router(id=3c5639b1-7041-4fce-ad73-fe0d36da264f)] local_auth_token must follow the correct format
2021-09-21 01:34:27 WARNING (SyncWorker_1) [glocaltokens.client] Google Wifi router device initialization failed because of missing local_auth_token, skipping.
2021-09-21 01:34:27 DEBUG (SyncWorker_1) [glocaltokens.client] Looking for 'Google Wifi router' (id=23D62ACE28B68134828189049C8D143D) in local network
2021-09-21 01:34:27 DEBUG (SyncWorker_1) [glocaltokens.client] [Device - Google Wifi router(id=4508cfb0-000d-4f0e-9ba5-9776b98d16f6)] Initializing new Device instance
2021-09-21 01:34:27 ERROR (SyncWorker_1) [glocaltokens.client] [Device - Google Wifi router(id=4508cfb0-000d-4f0e-9ba5-9776b98d16f6)] local_auth_token must follow the correct format
2021-09-21 01:34:27 DEBUG (SyncWorker_1) [glocaltokens.client] Looking for 'Google Wifi router' (id=6E382A9A0EAF47591124C1D261FADF64) in local network
2021-09-21 01:34:27 DEBUG (SyncWorker_1) [glocaltokens.client] [Device - Google Wifi router(id=b3b5870c-f0cb-4165-8c53-7b8926ed2983)] Initializing new Device instance
2021-09-21 01:34:27 ERROR (SyncWorker_1) [glocaltokens.client] [Device - Google Wifi router(id=b3b5870c-f0cb-4165-8c53-7b8926ed2983)] local_auth_token must follow the correct format
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
local_auth_token must follow the correct format · Issue #35 · djtimca ...
Just started noticing these errors in my logs: 2021-05-09 23:05:10 ERROR ... [Device - Nest Wifi router] local_auth_token must follow the correct for......
Read more >Fix your Google Nest Wifi or Google Wifi network
Follow these troubleshooting steps to fix: Google Nest Wifi router or point or Google Wifi point shows offline in mesh test; Can't connect...
Read more >Stay Connected with Google Wi-Fi Systems
Provide your home with Wi-Fi that you can count on with Google Wi-Fi systems. Get connected with home mesh Wi-Fi that works with...
Read more >Google WiFi system, 3-Pack - Router Replacement for Whole ...
A new type of connected system for seamless WiFi coverage throughout your home, helping eliminate dead zones and buffering; Replaces your current router, ......
Read more >How to Fix a Google Home That Won't Connect to Wi-Fi
That's because Google Home and Nest Wi-Fi malfunctions could be caused by a changed internet password, a low-speed internet connection, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jazzyisj and @CallumCVM i looked at the code implementation for client in
glocaltokens
and the logic seems right:error
and skip passing that device to theha-google-home
integration. Therefore, the integration should still be working for you and be correctly initialized for all other google home devices you have in your networks except the WiFi routers, those should just be skipped. Is that right or is the entire integration not working for you? p.s. perhaps we should revisit theglocaltokens
and not log “invalid token format” for devices like WiFi routers aserror
, but rather log asdebug
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.