One source you choose
An owner-operated GoogleFindMy-HA installation can expose one selected device_tracker through Home Assistant. Alternatively, your relay can read one explicit normalized coordinate report file that you prepare.
Bring a selected Home Assistant tag report onto your FamilyAtlas Items map, with its real measurement age.
Software for configured deployments, off by default. FamilyAtlas remains in early access. No retail tag model or live source account has been verified for this relay.
An owner-operated GoogleFindMy-HA installation can expose one selected device_tracker through Home Assistant. Alternatively, your relay can read one explicit normalized coordinate report file that you prepare.
The Items list, details and map use the source measurement time. Refreshing the relay cannot make an old location look new. Network reports never say Live, Nearby or Out of range.
Parents see their family’s items. A child sees only items assigned to them. The tag report is not proof that the person carrying it is there.
Only the latest report is kept, with the family’s 7/30-day retention choice. No network-item history, Bluetooth scan/ring, GPS heartbeat, battery or pet safe-area alerts. Direct Apple Find My or Google Find Hub pairing is unsupported. Apple accounts, beacon keys, OpenTagViewer ZIPs, OpenHaystack and FindMyFlipper imports are not implemented. A generic coordinate file is not automatic Apple-network access. Upstream integration availability and delayed/withheld locations can prevent reports.
The server receives only an opaque stream/generation and allowlisted measurement coordinates, time and accuracy through a signed request. Home Assistant credentials and external entity/device IDs stay in private local files. Unknown accuracy is labelled approximate; no invented precise radius. Tracker Safety remains a separate personal, local check without a cloud relay.
Read about unwanted tracking checks
Home Assistant REST API · GoogleFindMy-HA · Source review / Kaynak incelemesi