v1.7.2

⚠️ A full restart of Home Assistant is required after updating.
Reloading the integration alone is not enough: this release changes how the
push (FCM) connection is tracked across reloads. After updating, restart Home
Assistant and confirm that manifest.json shows 1.7.2.

This release fixes a "stuck disconnected" connection status after changing
settings, makes the integration recover on its own from a stale encryption
key, adds a new diagnostic sensor, and further reduces log noise.

Highlights

Connection status no longer gets stuck after changing settings

• Fixes a case where changing any setting flipped the connection status to
  "Disconnected" and it never recovered until a full Home Assistant restart
  (reloading the integration did not help). The push connection was actually
  healthy the whole time; only the internal bookkeeping was out of sync after
  a reload. The status now heals by itself. (Resolves the "modifying settings
  causes disconnection" report.)

Self-healing from a stale encryption key

• A stale or invalid shared encryption key is now detected and turned into a
  proper re-authentication prompt instead of silently failing to decrypt
  locations forever. A single transient failure no longer triggers re-auth;
  only repeated, confirmed failures do.
• Pasted credentials are cleaned up automatically. Accidental whitespace in
  copy-pasted keys/secrets (including those received through cloud discovery)
  is trimmed, so a stray space no longer breaks decryption.

New diagnostic sensor

• Adds an "Encryption Key Status" diagnostic sensor so you can see at a
  glance whether the key is healthy, and the FCM connection status entity was
  renamed for clarity. The new sensor also recovers on its own once a
  background push proves the key is working again.

Quieter logs

• Less noise during normal operation: a server-initiated push close, the
  first network retry, and best-effort metadata lookups are now logged at
  INFO/DEBUG instead of WARNING.

Under the hood

Extensive test and coverage hardening across the FCM receiver lifecycle,
decryption, owner-key handling, config/discovery secret normalization and the
reload path, plus a crypto-misuse audit on the core primitive files. These are
internal safety nets that lock in the fixes above against regressions and do
not change behavior.

---

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

Full Changelog: v1.7.1...v1.7.2