🔑 Longer master tokens supported, clearer device-list errors
The integration accepts longer Google master tokens. If sign-in works and no devices appear, the log now points you to the reachability checks. Alarm and timer events also carry more detail for your automations.
⚠️ Before you update
- If you use Google Keep Sync, update it to 1.2.0 first. The integrations share a Google sign-in library. Google Keep Sync 1.2.0
- Requires Home Assistant 2026.11.0 or newer, unchanged from v1.17.0. On older versions, Settings > System > Repairs can now explain which version you need. Your saved settings are kept. Recovery steps
For a Marketplace install, install the Google Home update in Settings, then restart Home Assistant. Manual update instructions
✨ Highlights
🔑 Sign-in fixes
Master tokens no longer have to be exactly 223 characters long. Longer tokens can pass the format check, and Google still decides whether to accept them. Errors now explain what to copy and paste, including the required prefix and the 200-character minimum.
When Home Assistant asks you to sign in again, select Reconfigure on the Google Home card. You can switch between Browser sign-in and Master token on the same form, including after an error. Sign in to the same account to keep your devices, entity IDs and automations. Sign in again
🩺 Signed in, but no devices?
Sign-in and fetching Google's device list use different servers. If the request fails with UNAVAILABLE, the log now names googlehomefoyer-pa.googleapis.com and points to the existing checks in Settings > System > Repairs > System information (in the overflow menu), under Google Home.
Open that section to check both servers, even if the integration loaded without devices. If your DNS filter or firewall blocks the device-list host, allow it. Google may also be temporarily unavailable. An ok result confirms only basic HTTP reachability, so the device-list request can still fail. Troubleshooting
🔔 More useful alarm and timer events
- Timer events include
duration, the length the timer was set for. A notification can say "Pasta set for 0:10:00 is ringing", including when several timers are running. Notification example - Alarm events include
recurrence, the repeat days reported by the speaker. For example,[1, 2, 3, 4, 5]means Monday through Friday. Event attributes
🐛 A few fixes worth mentioning
- A malformed Do Not Disturb or alarm volume reply keeps that setting's previous value while alarm and timer sensors can still update.
- Unreadable saved Bluetooth tracking data no longer prevents startup. Trackers without usable saved state show
unknownuntil fresh scans establish presence.
The documentation follows the latest release. For master, use the unreleased documentation.
The integration uses glocaltokens 2.1.1 for Google sign-in and ghome-local-api for speaker requests.
Thanks to everyone who reported problems, suggested improvements or shared feedback. ❤️
If you find the integration useful, please star the project on GitHub.
📋 All changes
27 merged pull requests and one release-housekeeping commit since v1.17.0. Full comparison.
🚀 Features (2)
🐛 Bug Fixes (6)
🈵 Translations (1)
📄 Documentation (3)
🧱 Dependency Updates (9)
🔧 Internal improvements (6)
🧰 Maintenance (1)