v1.7.1
Reloading the integration alone is not enough: several fixes touch how the
push (FCM) connection and background tasks are set up at startup. After the
update, restart Home Assistant and confirm that manifest.json shows
1.7.1.
This release focuses on connection reliability, the Play/Stop Sound buttons,
and far less log noise. It also adds a heads-up when a restart is needed.
Highlights
Push connection is much more resilient
The integration now recovers on its own from situations that previously left
device updates silently stuck:
- Corrupt push credentials are detected and repaired automatically. A
bad/garbled key used to crash the listener with anIncorrect padding
error and stop all updates. The credential is now validated and a clean
re-registration is triggered instead. - Repeated decryption failures now force a fresh registration instead of
looping forever. - A wedged push supervisor restart now heals itself, and registration
errors are split into distinct classes so the right recovery runs. - New guided repair: if push stays stuck, the integration now offers a
one-click "fix" (re-authentication) directly in Home Assistant instead of
failing quietly.
Play Sound / Stop Sound (ring) reliability
- Stop Sound can now always cancel an active ring, even when the device's
server status is read in a different order than expected. - The Play Sound cancel key is kept in every case, so the button no longer
ends up in an inconsistent state.
Map & sensors
- The "last seen" sensor no longer creates a stray extra marker on the map.
Stability
- A rare SSL/network teardown race in the Spot path is now handled cleanly
instead of surfacing as an unexpected error. - Re-authentication is started correctly when triggered from a synchronous
callback (no more await-on-non-coroutine glitch).
Quieter logs
- Routine polling timeouts are no longer logged as warnings. Nested poll
timeouts are staggered and idle/connected states are logged at INFO, so the
log is far less noisy during normal operation.
Setup
- Fixed a missing dependency:
grpclibis now a main dependency, so fresh
installs have everything they need. - You now get a notification when a restart is required after an update,
with troubleshooting notes for the post-upgrade setup URL.
Under the hood
Large test and coverage hardening across the crypto, key-backup, auth and FCM
paths (regression locks for base64 padding, CBC alignment, Scrypt parameters,
owner-key and token-cache handling), plus pinned registration headers. These
are internal safety nets and do not change behavior, but they lock in the
fixes above against regressions.
Reminder: restart Home Assistant after updating, then verify the version
is 1.7.1 under Settings → Devices & Services → Google Find My.
Full Changelog: V1.7...v1.7.1