-
Notifications
You must be signed in to change notification settings - Fork 100
Description
Hello,
I just change my email account because the other old one was hack.
However I was not able to connect this integration to my new account.
Context
Environment
Running Home Assistant OS on supervised install (SSH access available)
Python 3.12 environment inside Home Assistant SSH add-on
Tried both manual and Docker token generation methods
Goal
To generate a valid master_token for the ha-google-home integration in order to access Google Home devices and local APIs.
Steps attempted
- Docker method (daniklasz/ha-google-home-token)
docker run -it --rm daniklasz/ha-google-home-token
Error:
pull access denied for daniklasz/ha-google-home-token, repository does not exist or may require 'docker login'
→ Image no longer available on Docker Hub.
- Manual Python environment
Created a virtual environment and installed glocaltokens:
python3 -m venv gtoken
source gtoken/bin/activate
pip install glocaltokens
Then tried several versions:
pip install glocaltokens==0.10.1
Error:
ERROR: No matching distribution found for glocaltokens==0.10.1
Only versions up to 0.7.6 exist on PyPI.
- Import errors in all known glocaltokens classes
Tried multiple versions and imports:
from glocaltokens.client import GoogleHomeClient
from glocaltokens.client import Client
from glocaltokens.auth import GLocalAuthenticationTokens
All failed with variations of:
ImportError: cannot import name 'GoogleHomeClient' from 'glocaltokens.client'
NameError: name 'Client' is not defined
ModuleNotFoundError: No module named 'glocaltokens.auth'
So no valid entrypoint exists anymore matching the current documentation.
- Dependency build errors
Installing recent glocaltokens versions failed on Python 3.12 due to missing C++ build chain:
FileNotFoundError: [Errno 2] No such file or directory: 'c++'
and later:
Building wheel for grpcio (this may take a while) → fails silently or hangs.
- OAuth Playground attempt (for manual refresh token)
Tried generating a master token manually using OAuth 2.0 Playground
with scopes:
https://www.googleapis.com/auth/homegraph
https://www.googleapis.com/auth/clouddevices
Both fail with:
Erreur 400 : invalid_scope
Some requested scopes cannot be shown.
and later:
This site is no longer accessible.
Google no longer allows this website to access your account for your protection.
Any idea?
→ Confirmed Google has fully revoked both homegraph and clouddevices scopes for normal accounts.
Root cause (confirmed)
Since early 2024, Google removed support for the “master token” API endpoint used by glocaltokens and similar scripts.
OAuth scopes homegraph and clouddevices are now restricted to verified partners only.
“Less secure apps” access and “DisplayUnlockCaptcha” were fully deprecated mid-2024, making legacy authentication impossible.
Result: all community tools that rely on this token generation path are now broken.
Impact
Users can no longer set up ha-google-home integration.
Existing setups break after token expiry (cannot refresh).
Local access to Google Home devices (volume, timers, alarms, etc.) is effectively lost.