v1.7.3

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

This is a small, focused release. It makes the map's "Min Accuracy" slider
actually work and hardens how low-quality location points are handled, so the
map only shows points you can trust.

Highlights

The map "Min Accuracy" slider now actually filters points

• Previously the slider was a label only and had no effect on what was
  drawn. It now filters location points by their accuracy radius: points whose
  reported accuracy is worse (larger radius) than the slider value are hidden,
  so you can suppress vague, low-quality fixes and keep the map readable.
  (The filter is off by default, so nothing changes until you move the
  slider.)
• Invalid or missing accuracy values are no longer treated as "perfect".
  Legacy or malformed history points with a missing, zero, negative or
  not-a-number accuracy used to slip through any positive slider setting as if
  they were best-possible. They are now normalized to a conservative fallback
  before filtering, so a 10 m setting no longer lets unknown-quality points
  through.

Under the hood

• Internal robustness and test hardening around the map view's accuracy
  handling (a stub-tolerant resolver that keeps the targeted map-view tests
  reliable), and a small contributor-only documentation anchor that keeps the
  version string in manifest.json and const.py in sync. These do not
  change behavior.

---

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

Full Changelog: v1.7.2...v1.7.3