v1.7.8

⚠️ 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.8.

This release stabilizes the standalone command-line setup and makes the first
location after a fresh login reliable. It also removes several confusing or
misleading messages that used to appear during key setup, and adds an opt-in
debug switch to the bundled CLI. Nothing is removed for existing working
installs.

Highlights

Clearer key setup, no more misleading errors

• Setting up your Google credentials no longer shows the alarming, misleading
  "vault key retrieval failed" message, and no longer wrongly asks you to log in
  again while the owner key is still being retrieved. A missing owner key is no
  longer treated as fatal: it can be derived later at runtime, so first-time
  setup stays calm and predictable.

New --debug switch for the bundled CLI

• You can now run the command-line setup with python main.py --debug (or by
  setting the GOOGLEFINDMY_DEBUG environment variable) to get verbose, opt-in
  diagnostic logging when you need to troubleshoot a first-run problem. Normal
  runs stay quiet.

Reliable first locate after setup

• After a fresh login the integration now establishes a fresh push (FCM)
  session before it issues the very first location request, so the first
  locate succeeds instead of timing out while the new registration is still
  settling.

Transient network hiccups no longer look like lost credentials

• A temporary DNS or check-in failure is now classified as a transient error
  and retried, instead of being misread as an identity loss that would trigger
  an unnecessary re-authentication. Good key material is preserved across brief
  outages.

Cleaner shutdown and a hardened standalone first run

• Stopping the integration no longer surfaces a spurious "Unknown error in
  listener" traceback.
• The standalone CLI first run is hardened: it starts correctly from the
  integration folder, tears the browser down deterministically, and fixes the
  Windows WinError 6 and the session-leak issues that could appear on the very
  first run.

Use it as a GoogleFindMyTools replacement

You do not need a separate GoogleFindMyTools checkout. On a desktop system that
has a browser, run the bundled CLI directly:

python main.py

This performs the one-time Google sign-in in your browser, generates the account
keys, and writes the resulting secrets. You then import those secrets into the
Home Assistant integration; the config flow accepts them as long as the shared
key is present. In other words, this integration can fully replace the
GoogleFindMyTools workflow for obtaining and refreshing the credentials. Add
--debug if you want to see what the setup is doing.

Under the hood

• Every fixed behavior ships with regression tests: 2 new test files plus
  expanded coverage across 7 existing test files. Each contributing change was
  CI-green and reviewed before it was merged.
• The async-marker guard now actively covers the CLI entry-selection tests (its
  legacy allowlist shrank by one), so fallback-runner test execution stays
  correct even without pytest-asyncio installed.
• No breaking changes for existing installs: the config_entry schema version
  is unchanged, and diagnostics remain strictly redacted.

---

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

Full Changelog: v1.7.7...v1.7.8