v1.7.4

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

This is a small, focused release. It brings back the accuracy circles on the
map and stops a misleading re-authentication prompt that appeared when a single
device (for example an old phone that has been switched off for days) could not
report its location, even though all your other devices were working fine.

Highlights

Accuracy circles are back on the map

• The map again shows the GPS accuracy circle for a location. In recent
  builds the circle had stopped appearing. It now shows up when you select
  (click) a device on the map, and switches to the device you pick next, so you
  can see how precise each fix is without the map getting cluttered.

No more false re-authentication prompt for a single offline device

• A single device that cannot be located no longer triggers a bogus "please
  re-authenticate" prompt. Previously, if one device (such as a phone that
  had been powered off for several days) failed to decrypt its own location
  while the rest of your devices kept working, the integration wrongly asked you
  to generate a new secrets.json. Re-authenticating did not help, because the
  keys were fine, only that one device was unreachable. This single-device case
  is now logged as a warning and no longer asks for re-authentication.
• Genuine, account-wide key problems still prompt for re-authentication as
  before, so this change suppresses only the misleading single-device case,
  not real credential failures.

Under the hood

• After a Home Assistant restart, location points restored from history that
  carry a missing or invalid accuracy value are now correctly flagged as
  "estimated", so the map no longer draws a solid, trustworthy-looking circle
  for a fabricated fallback radius. This hardens the accuracy handling above
  against older/stale history rows.
• Additional test and robustness hardening around the decryption/re-auth
  decision and the map's accuracy handling, plus a contributor-only guard that
  keeps the version string in sync across manifest.json, const.py and
  pyproject.toml. These do not change behavior.

---

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

Full Changelog: v1.7.3...v1.7.4