If you're tracking Google FindHub (Find My Device network) BLE tags, or building your own ESP32/Zephyr trackers registered on that network, and forwarding their locations into Traccar: Traccar's own bridge for this, google-find-hub-sync, is a thin microservice that hasn't been touched since July 2025 and has a real bug in it. Google can rotate an account's E2EE owner keys, and the old code always requests owner_key_version=-1 instead of retrying with the version a tracker actually needs, so it fails with cryptography.exceptions.InvalidTag or "Failed to decrypt identity key encrypted with owner key version X" once that happens.
There's a fix, leonboe1/GoogleFindMyTools#114, but it's an open PR, not merged anywhere yet (another user already confirmed it fixed the same error for them).
I maintain GoogleFindMyToolsWebUi, which already has that fix, plus a web UI, per-device scheduling to Traccar (OsmAnd protocol preset built in) or other destinations, and BLE/ESP32/Zephyr custom tracker registration/flashing from the browser via browser to serial. Posting this here in case it helps anyone tracking these devices, and for whoever maintains google-find-hub-sync in case it's worth linking to or merging fixes from.
If you're tracking Google FindHub (Find My Device network) BLE tags, or building your own ESP32/Zephyr trackers registered on that network, and forwarding their locations into Traccar: Traccar's own bridge for this,
google-find-hub-sync, is a thin microservice that hasn't been touched since July 2025 and has a real bug in it. Google can rotate an account's E2EE owner keys, and the old code always requestsowner_key_version=-1instead of retrying with the version a tracker actually needs, so it fails withcryptography.exceptions.InvalidTagor "Failed to decrypt identity key encrypted with owner key version X" once that happens.There's a fix, leonboe1/GoogleFindMyTools#114, but it's an open PR, not merged anywhere yet (another user already confirmed it fixed the same error for them).
I maintain GoogleFindMyToolsWebUi, which already has that fix, plus a web UI, per-device scheduling to Traccar (OsmAnd protocol preset built in) or other destinations, and BLE/ESP32/Zephyr custom tracker registration/flashing from the browser via browser to serial. Posting this here in case it helps anyone tracking these devices, and for whoever maintains
google-find-hub-syncin case it's worth linking to or merging fixes from.