Compatible phones and devices
An honest list: what works today, what is likely, and what Albert Life never promises.
Last updated: 16 June 2026
Albert Life is not compatible with every smartphone and every watch in the world. Each device must share signals in a verifiable way — and we always say what is missing.
This page is the public source for families, App Store / Google Play listings, and caregivers. If a model is not listed as tested, it may work partially only if it writes data to Apple Health (iPhone) or Health Connect (Android).
Golden rule
Never promise 100%. Missing or stale data → YELLOW state (“we don’t know right now”), not a fake emergency. Albert Life is not a medical device and does not replace a phone call or an in-person check.
Status legend
Smartphones — minimum requirements
The older person needs a smartphone with the Albert Life Elder app. The caregiver uses the Family app and/or the web dashboard.
| Role / system | Minimum requirement | Notes |
|---|---|---|
Elder phone — iOSTested | iPhone, iOS 13 or later | Primary path today. HealthKit for steps and heart rate (when shared). SOS and base presence without a wearable. |
Elder phone — AndroidTested | Android 8.0+ (API 26) | App installable with SOS/base presence. Health Connect health integration rolling out (see wearables). |
Caregiver phone — iOS / AndroidTested | As above + data/Wi‑Fi connection | Push notifications when configured. Web dashboard at albertlife.app. |
Elder without smartphoneNot supported | — | Albert Life alone is not enough. Human contact, home sensors (pilot), or future dedicated devices needed. |
Tablet only (no phone)Limited | — | Not the recommended path: SOS, presence, and wearables go through the elder’s phone. |
Wearables — data paths
Albert Life reads signals that reach the elder’s phone. We do not magically connect every brand: a supported data path is required (Health, Health Connect, or a future integration).
| Data path | Coverage | Honest limits |
|---|---|---|
Apple wearable → Apple Health → iPhoneTested | High (iOS) | Best path today. Steps and heart rate when shared to Health. Not continuous real time — OS sync (minutes–hours). Native fall only if Health exposes it. |
Wear OS / Samsung → Health Connect → AndroidRolling out | Medium–high | Many models may work when Health Connect is active and Albert has permissions. Android rollout in progress — do not promise iOS parity in store until closed. |
Fitbit / Garmin app → vendor cloudLimited | Medium | Frequent delays (5–60+ min). Dedicated cloud integration future; today only if data reaches Health Connect / Health. |
Budget bands / generic BLELimited | Variable | Some do not expose heart rate or steps to system health apps. No guarantee without per-model verification. |
Beghelli / Vivago / closed medical pendantsNot supported | — | Separate project and protocols. Not in this consumer matrix. |
Albert on-wrist companion appRolling out | — | On-wrist SOS and complications — post v1 launch. In v1 the wearable works through the phone. |
Works without a watch?
Yes — with clear limits. A watch enriches signals; it is not required.
✓
- SOS button on the phone (hold) and optional shake if enabled
- System presence and calm alerts if the app sees no activity for many hours
- Caregiver dashboard: green / yellow / red with a readable reason
- Safe Check and family contact
!
- No continuous heart rate without a wearable or Health source
- Less precise movement than wrist — phone charging or off → YELLOW
- Automatic fall detection only if a sensor or wearable reports it — not from phone alone in v1
Home sensors — compatible types
LimitedAlbert Life understands the home through discrete events (room presence, door, bathroom, SOS) — never continuous video surveillance. Consumer integration via Home Assistant / Matter is in pilot: buying compatible hardware makes sense if you prepare setup with us; it is not yet plug‑and‑play on every store install.
How data reaches Albert Life
Target path: sensor → hub (Home Assistant, Aqara/Matter, HomeKit future) → `home_bridge` → room presence dashboard. Every event carries confidence, timestamp, and explicit limits. Offline → YELLOW, never fake “ all OK ”.
Room map and “At home” card visible in Digital Home demo/pilot. General consumer release on roadmap (STEP-INDOOR-PRESENCE-01).
Sensor types supported by the Albert Life model
| Sensor type | Where to install | Signal for the family | Compatibility / notes |
|---|---|---|---|
Room presence (mmWave radar)Limited | Living room, bedroom, hallway | Person presence / approximate room | Best indoor signal: presence even when still. E.g. Aqara FP2, Matter/Zigbee equivalents. Does not identify who — approximate room only. |
PIR motionLikely | Hallways, kitchen, entry | Movement / passage detected | Detects movement, not seated presence. Useful budget complement; less precise than radar. |
Door contact sensorLimited | Front door (priority) | Left home / returned | Left home / returned. E.g. Aqara, Sonoff, Shelly via HA. Internal doors optional. |
Bathroom presenceLimited | Bathroom | Bathroom time / night presence | Prolonged bathroom time, night presence. Bathroom radar or dedicated PIR. Prudent threshold (e.g. 25 min) — not diagnosis. |
Physical SOS buttonLimited | Bathroom, bedside, entry | Immediate SOS to family | Emergency without smartphone. Zigbee/Matter (e.g. Aqara Wireless Switch). Requires hub and setup. |
Bed / chair sensorLimited | Bedroom (optional) | In bed / out of bed | In bed / out of bed. Pressure pad or low radar. More invasive install — only if truly needed. |
Water / leak sensorLikely | Under bathroom/kitchen sink | Water leak / flooding | Home safety (leak), not person presence. Useful but separate from daily wellbeing. |
Kitchen motionLikely | Kitchen | Kitchen / meal activity | No meal activity (digital_home meal windows). PIR or light presence. |
BLE room beaconLimited | Care home / large-home pilot | Approximate zone change | Approximate zone change via RSSI. Facility path (`facility_room_sensors`); secondary vs radar for family homes. |
Wi‑Fi sensing (router)Not supported | Whole home | Wi‑Fi presence (not active consumer) | Schema in repo but release-blocked — requires DPIA (T‑017). Not recommended family purchase today. |
Always‑on cameraNot supported | — | Not used for daily presence | Not daily Albert Life presence (P7). Video only separate opt‑in EMG flows, never default surveillance. |
Closed medical pendant (Beghelli/Vivago…)Not supported | — | Not in consumer matrix | Separate protocols and project. Not in this consumer matrix. |
Hubs and protocols (bridge to Albert Life)
| Hub / protocol | Typical protocol | Compatibility / notes |
|---|---|---|
Home Assistant (e.g. Green)Limited | REST / WebSocket → HA adapter | Priority path in code (`ClientBackedHomeAssistantAdapter`). Requires pilot and dev flags today. |
Aqara Hub M3 / Zigbee‑Matter hubLikely | Zigbee / Matter | Aqara sensors (FP2, door, SOS) → hub → Home Assistant recommended bridge to Albert. |
Matter / Thread border routerLikely | Matter over Thread | Certified Matter sensors; Albert integration via HA broker in MVP. |
Apple HomeKit / HomePodRolling out | HomeKit | Planned in architecture (`homeKit` enum); consumer UI “Coming soon” today. |
Closed vendor cloud without APINot supported | — | Proprietary apps without HA/Matter export are not an Albert Life path. |
Recommended setup (elder apartment)
- 1 hub (Home Assistant Green or Aqara Hub M3 + HA)
- 1 front door sensor
- 1–2 room radar presence (living room + bedroom)
- 1 bathroom presence or motion
- 1 physical SOS button (bathroom or bedside)
- Optional: kitchen motion, water leak sensor
Not recommended as an Albert package today
- Cameras in every room to “ know where they are ”
- Consumer Wi‑Fi sensing without legal review
- Mix of 15 brands without a common hub
- Sensors claiming certified fall/medical without multi‑signal evidence
Product examples (category, not Albert certification)
Presence: Aqara FP2 or equivalent Matter radar · Door/SOS/water: Aqara, Sonoff, Shelly via Home Assistant · Hub: Home Assistant Green, Aqara Hub M3. Verify Matter/Zigbee compatibility and pilot plan before bulk purchase.
Configurations validated today
A short list of what we tested or ran end‑to‑end in real/pilot environments. Other models may work partially.
| Configuration | Data path | Typical metrics |
|---|---|---|
| Elder iPhone (iOS 13+) | Albert Life Elder app | SOS, presence, Safe Check |
| iPhone + Apple wearable via Health | Apple Health → HealthKit | Steps, heart rate (when shared), movement |
| Caregiver iPhone + web dashboard | Family app + albertlife.app | Status, timeline, devices, alerts |
| Elder Android (API 26+) | Albert Life Elder app | SOS, base presence — wearable health rolling out |
Copy for App Store & Google Play
Ready-to-paste — follows rule B‑7: no “Apple Watch” in marketing until the companion ships.
Requirements
Elder phone: iPhone iOS 13+ or Android 8+. Caregiver phone: iOS 13+ or Android 8+. Internet connection. Albert Life is not a medical device.
Wearable (optional)
Optional wearable data via Apple Health (iOS) or Health Connect (Android) when the device shares steps and heart rate. Not all wearables share all metrics. Delays depend on the phone OS and vendor apps — real time not guaranteed.
Does not diagnose, does not call emergency services for you, does not work if the person’s phone is off or away from them. Technology can be wrong — use as extra help, never sole certainty.