Skip to content

v1.7.5

Choose a tag to compare

@jleinenbach jleinenbach released this 25 Jun 11:23
759a8cc

⚠️ A full restart of Home Assistant is required after updating.
Reloading the integration alone is not enough: a version update changes the
integration's Python code, which Home Assistant only picks up on a full
restart. After updating, restart Home Assistant and confirm that
manifest.json shows 1.7.5.

This release is all about a calmer, more trustworthy integration. It makes the
logs quiet again for normal setups, stops false "please re-authenticate"
prompts when the problem is only temporary, and catches an incomplete
secrets.json at import time instead of leaving you with a silently broken
install. Nothing is removed for existing working installs.

Highlights

Much quieter logs for normal multi-device setups

  • Phones and Bluetooth accessories (such as earbuds) no longer flood your
    log.
    These devices legitimately have no trackable location of their own,
    but earlier builds emitted a WARNING about them on every poll. Those
    expected cases are now logged at DEBUG/INFO.
  • A real "device dropped" warning is now reserved for something worth your
    attention
    , namely a device that was visible disappearing, or a genuine
    tracker going missing. Even then, the aggregate warning fires at most once
    per poll
    instead of repeating on every internal pass.

No more false re-authentication prompts for temporary problems

  • Temporary network or transport hiccups no longer masquerade as a broken
    login.
    Previously a transient failure could be misread as a permanent
    "stale key" and ask you to re-authenticate, which never helped because your
    keys were fine. These cases are now retried quietly.
  • A recoverable owner key is repaired automatically from your shared key
    using the existing refresh path, instead of bothering you.
  • A genuine, account-wide key problem still prompts for re-authentication as
    before
    , so only the misleading cases are suppressed, not real credential
    failures.

Incomplete credential bundles are caught up front

  • Importing a secrets.json that is missing the shared_key is now rejected
    immediately
    with a clear keys_missing message and guidance, instead of
    being accepted into a state that can never decrypt locations. The README now
    explains the shared-key second-login step and a bundled helper that fetches
    both keys in a single run.

Setup scripts keep working when Chrome moves ahead

  • The standalone authentication scripts no longer abort with
    only supports Chrome version 150
    when the Chrome-for-Testing stable
    channel runs ahead of your installed Chrome. The detected Chrome version is
    now always honored, and you can override it explicitly with the new
    --chrome-path / --chrome-version flags or the
    GOOGLEFINDMY_CHROME_PATH / GOOGLEFINDMY_CHROME_VERSION environment
    variables (the environment variables also apply to the Home Assistant
    runtime, which has no command line of its own).

Better diagnostics for support requests

  • The diagnostics download now carries per-device signal (Home Assistant
    core version, a coarse accuracy bucket, drop counters and auth/decryption
    telemetry), so a support request is actionable instead of relying on global
    counters only. Diagnostics stay redacted: only coarse buckets and counts are
    exposed, never tokens, emails or raw locations.

Under the hood

  • The obsolete, already-inert token input field on the re-authentication
    screen was removed in all languages; the corrected shared-key-aware flow
    replaces it. No user action required.
  • Server-side error messages from Google's backend are now captured and
    logged
    (they used to be dropped), turning previously silent decryption and
    empty-response failures into actionable log lines.
  • Per-device diagnostics now read the correct accuracy field, so the accuracy
    signal is no longer reported as empty during normal operation.
  • Lazy imports for the heavy cryptography/protobuf modules keep startup
    consistent with the documented import-deferral policy.
  • Every fix in this release ships with a dedicated regression test (18 new test
    files); the full suite is green in CI. The config_entry schema version is
    unchanged (2), and there are no breaking changes for existing installs.

Reminder: restart Home Assistant after updating, then verify the version is
1.7.5 under Settings -> Devices & Services -> Google Find My.

Full Changelog: v1.7.4...v1.7.5