Repository navigation
Firmware: Google Find Hub (FMDN) support for nRF5x tags #3
Description
Goal: nRF5x firmware advertises Google Find My Device Network frames (Eddystone service UUID 0xFEAA, frame type 0x40/0x41, rotating EID) so tags are locatable via Android Find Hub, alongside existing Apple OpenHaystack mode.
Phase 1:
- Build-time mode: APPLE (default, unchanged) | GOOGLE_FMDN | DUAL.
- FMDN advert from a precomputed EID table (mirrors public_key[] rotation).
- tools/fmdn_keys.py: EID generation from Ephemeral Identity Key per FMDN spec (AES-ECB-256 + SECP160R1), tested against spec vectors.
- Docs: provisioning limits (account-key registration needed; GoogleFindMyTools-style flow).
Acceptance: EID unit tests vs published vectors; nrf52832 GOOGLE_FMDN build succeeds; existing tests green; live: Android scan sees FEAA frame from flashed tag.
Activity
Advertise FMDN normal mode and bound the EID clock (#3)
Check the FMDN K=10 guard without the nRF SDK (#3)
Firmware: Google Find Hub (FMDN) advertising for nRF5x (#3) (#4)
dzianisv commentedon Oct 2, 2026
Code merged via #4. Open for live acceptance: flash nrf52832 GOOGLE_FMDN build, confirm Android BLE scan sees FEAA frame 0x40 with rotating EID. Blocked on hardware (no adb device, no nrfjprog on build host).