Skip to content

1.9.0

Latest
Latest

Choose a tag to compare

View all tags
@jleinenbach jleinenbach released this 11 Nov 21:02
1.9.0
a86bcd3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release ships everything merged into main since 1.8.0: one pull request (#244) that brings the work of the fork jleinenbach/GoogleFindMy-HA (fork release 1.15.37 and one later schema and documentation change) to this repository. The full history, one entry per fork release, is at https://github.com/jleinenbach/GoogleFindMy-HA/releases.

Why update

  • Device pictures: each tracker now shows Google's product image, as in the Find Hub app.
  • The "Trigger device refresh" action works on every button of the integration. Before, picking a statistics or token button failed with an error. The action also has a description in the action editor now.
  • Faster support when Google changes its data: at DEBUG level the integration names fields it does not know yet. Normal logging is unaffected.

Upgrading from 1.8.0

  • Update through HACS or Marketplace as usual, then restart Home Assistant.
  • Minimum Home Assistant version: 2025.9.1 (unchanged).
  • Going back to 1.8.0 needs no reverse migration (see below). Take a backup before any downgrade.

Breaking changes and migrations

  • Config entry and storage migrations: None.
  • Removed: the unused cloud battery_level placeholder. It was never filled from Google's device list and never appeared on an entity, so nothing you see changes. Battery levels still come from Bluetooth (unchanged).

Fixes

Ordered by effect for users.

  1. trigger_device_refresh no longer fails on statistics and token buttons. The action also has a description in the action editor now. (#244)

Enhancements

  1. Product image as entity picture. The main tracker shows the image Google provides for the device model. Only HTTPS addresses on Google's image host are accepted. Your browser loads the image directly from Google, without sign-in, so Google sees your IP address and the time of loading, as with any image hosted by a third party (see the README, section on the device picture). (#244)
  2. Unknown-field diagnostics at DEBUG. When Google adds fields to its responses, one log line per device names their path and wire type, and only again when the pattern changes. No identifiers, texts or key material are logged; below DEBUG nothing is examined. (#244)
  3. Fields observed in November 2026 are declared under neutral names. Their meaning is unknown and is not guessed. A table of all such fields is in docs/FMDN.md, section S8.5. A field on phones that may carry an identifier is redacted. Related report to Spot: leonboe1/Spot#1. (#244)

For contributors

  • AGENTS.md allows the unknown-field diagnostics at DEBUG and names its keys.
  • New tests for the diagnostics, the picture, the schema fields and the completeness of the S8.5 table.

Known open issues

Unchanged from 1.8.0:

  • #211 and #234, periodic ringing of some tags.
  • #224: the reported watch has no canonical ID and is still not offered.
  • #236: whether the IPv6 fallback fixes the reporter's case is not confirmed.

Pull requests in this release

#244.

Assets 3
Loading