A focused follow-up to v1.2.7 that fixes how the integration connects to the auth add-on in both Docker standalone and Home Assistant OS environments.
Full changelog: v1.2.7...v1.2.8
🐛 Fixed
Docker standalone: cookie endpoint no longer requires a key by default (#125)
v1.2.7 / add-on 1.7.0 made /api/cookies always require an API key.
This unintentionally broke existing standalone deployments: the auth container and the Home Assistant integration do not share a volume, so the auto-generated key stored in ./data/api_key never reached the integration. As a result, every cookie fetch returned 403 ("cookies not available").
The API key is now enforced only when it can be used without manual configuration:
API_KEYis explicitly configured.- The add-on is running under Supervisor (HA OS / Supervised), where the key is shared through
/share/familylink/api_key.
In standalone deployments without API_KEY, the endpoint remains accessible (matching the pre-1.7.0 behavior) and logs a warning.
Thanks to @cdn4lf for the report.
HA OS: add-on discovery via Supervisor (#123)
On Home Assistant OS, add-on containers run in isolated Docker networks and are not reachable through localhost:8099.
The integration now queries the Supervisor /addons endpoint to resolve the add-on's Docker DNS hostname (with _ automatically converted to -) and uses that hostname for cookie retrieval.
Discovery order is now:
- Custom URL
- Supervisor-resolved hostname
localhost- Encrypted-file fallback
This change does not affect standalone or Docker Compose deployments.
Thanks to @ibrahimnajjar84 for the contribution.
Clearer authentication error on 403
When the auth server rejects a request because of a missing API key, the integration now returns an actionable error message pointing to:
?api_key=<key>./data/api_key
instead of the generic "cookies not available" error.
📦 Companion add-on
The Google Family Link Auth add-on has been updated to v1.7.1.
This release includes the standalone API key behavior adjustment described above (#125).
Be sure to update the add-on from the add-on store after upgrading the integration.
⬆️ Upgrade
Update the integration through HACS, then restart Home Assistant.
For standalone users affected by the v1.2.7 regression, upgrading to v1.2.8 together with Google Family Link Auth v1.7.1 restores support for the existing:
http://<host>:8099
configuration without requiring an API key.
If you prefer to keep the endpoint protected, configure:
API_KEY=<your-key>
on the auth container and use:
http://<host>:8099?api_key=<key>
as the integration URL.