The Life Dashboard integration is an open-source Home Assistant integration, installed through HACS, for the Life Dashboard Companion apps on Android and iPhone. One QR code pairs a phone, and every day lands in long-term statistics. No broker and no YAML.
Day totals for steps, distance and calories, and the latest heart rate, sleep, weight and blood pressure, each with its source app.
Every day lands on its own date, so a backfill from the phone fills a year of the Statistics graph card.
One code per phone holds a webhook URL and a signing secret. The phone never gets a Home Assistant login or token.
HMAC-SHA256 on every payload, checked in constant time before parsing. There's no switch to turn signing off.
The apps re-send on purpose. A repeat leaves sensors, day totals and sessions as they were; a correction replaces the old figure.
Map a scale or blood pressure entity, and the Android app writes each new reading into Health Connect.
Sensors appear the first time their type arrives, so you only get what you sync. A sensor holds the latest value; long-term statistics hold the past, each value on the date it happened.
Add the integration once per phone, and it shows a QR code with a webhook URL and a secret it generated: 64 hex characters. A payload without a valid HMAC-SHA256 signature gets a 401 and is logged without its contents. How to add Health Connect to Home Assistant walks through the pairing.
examples/dashboard.yaml is a view for one phone in three sections. Paste it into a new dashboard's raw configuration editor and put in your phone's name.
Keep the companion app for presence, notifications and device sensors. The two run side by side; this is what the integration adds for health data.
| Feature | Home Assistant companion app | Life Dashboard |
|---|---|---|
| Health Connect | 26 sensors | 33 types; 25 become sensors, and a webhook gets every record |
| History | From the day you enable a sensor, with today's value filed at sync time | A backfill of up to a year, every value filed on the date it happened |
| Screen time | Last used app | Minutes per app, with a day boundary you choose |
| Into Health Connect | No | Scale and blood pressure readings from Home Assistant |
| Other destinations | Home Assistant | Also MQTT, any webhook and the Grafana stack |
From the companion app's sensor documentation and its code, as of release 2026.8.4. The companion app and Health Connect goes row by row.
Sensors, statistics and a year of history
As a custom repository for now; the default HACS list is pending. Restart Home Assistant after the download.
Home Assistant 2026.3 or newer with HACS, where you add the integration as a custom repository of type Integration until it's in the default list. On each phone, Life Dashboard Companion for Android or for iPhone. Screen time, the sensors per app and Receive need the Android app; the sensors per app need integration 0.9.0 or newer.
Pairs with Life Dashboard Companion for Android and for iPhone.
Pick one; running both gives you two devices with the same numbers. MQTT Discovery creates the same sensors and suits a setup that already has a broker and only wants current values. Only the integration has backfilled history, a screen time sensor per app and readings back to the phone.
Yes. Add the integration once per phone, Android and iPhone alike. Each gets its own webhook ID, secret, device and statistics, and the entity IDs follow the name you give it, such as sensor.owen_s_pixel_steps_today.
Eight of the 33 Health Connect types are events: meals, mindfulness sessions, sexual activity and the five cycle tracking types. Workouts get a last workout sensor and the minutes of today and yesterday, and mindfulness counts as minutes per day in the statistics. For the raw records, add a second webhook in the app that points at your own backend.
Yes, on Android. Configure maps one entity per type: weight, body fat, lean body mass, bone mass, body water mass, height and blood pressure. The app writes each new value into Health Connect; Smart scale to Samsung Health has the setup.
No. The phone pushes a signed payload on its own schedule, and nothing in Home Assistant polls. A payload that fails while Home Assistant restarts waits in the app's outbox and goes out with the next sync.
Yes, a model you choose, through ha-mcp, a community MCP server for Home Assistant with a history tool that reads long-term statistics. Home Assistant's built-in MCP server only offers current states. With a local model nothing leaves your network; with a cloud model, your questions and the results go to its provider. Health Connect data over MCP has the setup, and the stack's own MCP server if you'd rather keep the data in Postgres.
Deleting the entry removes the device and its sensors, deletes its cloudhook if it had one, and deletes the phone's files in .storage. Its long-term statistics stay in the recorder, as they do for any integration you remove.
Samsung Health, Garmin, Fitbit, Oura and Withings data as sensors, with a year of history.
Read the guide FitbitThrough Health Connect, with no Fitbit Web API and no Google Cloud project.
Read the guide GarminSteps, sleep and heart rate from Garmin Connect, with no Garmin login in Home Assistant.
Read the guide Screen timeMinutes per app as sensors, limits you set yourself, and several phones.
Read the guideBoth apps send the same payload, so an Android phone and an iPhone can share one Home Assistant or one stack.
Life Dashboard