Local iPhone Bluetooth presence and estimated rooms for Home Assistant. Install with HACS, enroll with Presence Pair, and keep presence data in your home.
Pairing creates a private Bluetooth identity using a short-lived QR invitation. Presence tracking later resolves advertisements locally without reconnecting to the phone. A receiver that hears advertisements cannot necessarily create bonds or export identity keys.
| Component | Implemented support | Verification status |
|---|---|---|
| Initial app pairing | Windows receiver, BLE central and peripheral roles; iOS 17+ Presence Pair | One physical iPhone/Windows setup recorded successful app 219 enrollment on October 7, 2026: protected exchange, HA commit, phone receipt and fresh reception. Recovery-patched live versions were used; Windows enrollment files match 0.2.1. The exact 0.2.1 full matrix remains pending, not multi-device certification. |
| Windows passive tracking | MQTT Windows observer | Live deployment verified; coverage depends on antenna and phone advertisements |
| Native HA Bluetooth tracking | Shared HA Bluetooth cache, including non-connectable scanners and supported proxies | Native API and timestamp behavior covered by local tests; per-installation runtime verification required |
| HA host | HA OS, Container or other supported HA installation with MQTT | Live deployments observed on HA 2026.8.3 and 2026.9.4; not every HA release or installation mode has been physically tested |
| Linux/BlueZ initial pairing | Experimental in-process or remote receiver, BlueZ key storage read-only | Behavioral tests only; physical Linux/iPhone and ARM certification pending |
| ESPHome/Shelly/Sonoff initial pairing | Not implemented by Presence Bridge | Passive HA-compatible radio support does not imply enrollment support |
| Android/Apple Watch enrollment via app | Not implemented by the iPhone app | Do not describe as universally compatible |
The Windows receiver’s configured user must remain signed in for initial pairing; the desktop may be locked and no server-side PIN dialog is required. The passive Windows observer runs as a service task. No desktop/workstation outside the configured receiver is required by the public pairing flow.
binary_sensor on means a recent matching advertisement, not proof that its
owner is carrying the phone.device_tracker reports home when detected and unknown when not detected.
Missing radio coverage must not establish a person’s absence by itself.Local unit tests cannot certify every radio/driver combination. Before claiming support for another hardware setup, verify the public HA panel and installer on a clean supported Windows machine, then test fresh pairing, a valid saved bond, one-sided stale bonds, cancellation, timeout, user decline, HA/MQTT restarts, removal and a second phone. Confirm protected GATT ACK, HA persistence and phone receipt for each successful enrollment. No test may unpair unrelated devices.
The current development recovery is bounded to one repair per attempt, even if the peer’s address rotates. It requires the current verified QR claim and an old bond: weak protection, protected-write rejection or bounded persistent post-verification connection failures can trigger recovery. Pre-claim radio timeouts never authorize unpairing. See the state matrix. These recovery changes are included in the 0.2.0 preview; older 0.1.36 archives do not contain them.
Version 0.2.1 adds an explicit, administrator-confirmed repair for an exactly identified saved Windows bond that cannot be opened. An unverified radio timeout does not silently delete it. Verified removal persists iPhone preparation across HA restarts; app 219 or later asks the owner to forget the old iOS bond if present. Ordinary retries preserve valid bonds. See the acceptance checklist.
The installation matrix distinguishes HA hosting from enrollment. The integration does not install a Windows receiver or manage the host’s radio driver. MQTT is required for remote receivers, but not for local Linux enrollment. The local mode requires system D-Bus and readable BlueZ bond storage; HA OS does not automatically expose that storage to Core. Linux is headless and does not require a logged-in graphical user. See Linux setup.
Exercise screen lock/app background, away/return and at least two independent receivers before using room estimates for consequential automations. Keep the current working pairing when running software-only tests. The private physical clean-room harness deliberately removes only the selected phone before a fresh attempt; this is not a policy to reset working bonds on every normal QR scan.
Presence Pair 1.0.0 (build 220) is Apple-approved and publicly listed in the Italian App Store, verified November 4, 2026. That approval is separate from receiver compatibility: a full GitHub release does not certify additional hardware. Linux remains experimental and the full hardware matrix is not certified. Repeat the public-app test on each supported setup; successful unit tests or App Store approval cannot replace physical results.
References: HA Bluetooth APIs, Private BLE Device.