Life Dashboard Companion for iPhone is an open-source app that reads 28 Apple Health types and sends them to Home Assistant, an MQTT broker or your own webhook. It sends the same payload as the Android app, so both phones can share one server.
App Store: coming · TestFlight: coming
Steps, sleep stages, heart rate, HRV, weight, blood pressure, glucose, VO2 max, workouts, nutrition and cycle tracking. Each starts off.
Each record names the app or device that wrote it. Daily totals count a walk recorded by iPhone and Watch once.
Backfill 30, 90 or 365 days. A record you delete in Apple Health is reported to your server at the next sync.
The Android app's keys, units and signing, so one Home Assistant or one receiver takes both phones.
An interval or fixed times, with quiet hours. iOS picks the moment; a Shortcuts automation gives you an exact time.
See the last sync on your home screen, and sync from there, from Control Center on iOS 18, or with Siri.
The Life Dashboard integration pairs with one QR code and keeps every day in long-term statistics. Over MQTT, Home Assistant Discovery sets the sensors up without YAML, from the first sync on.
Any server that accepts a JSON POST can receive the data: n8n, Node-RED, the Grafana stack or a script. Every record carries a uuid to deduplicate on and a source that names the app or device that wrote it.
HealthKit wakes the app when an enabled type has new data, and iOS runs background tasks when it sees fit. A fixed time means “not before”. For an exact minute, a Shortcuts automation runs Sync Health Data.
Apple Health, with the same payload
From source, on a Mac with Xcode: about an hour the first time. Your settings stay when you run a newer version.
An iPhone on iOS 17 or newer. To build it today: a Mac with Xcode 26 (macOS 26.2 for the newest Xcode, or Xcode 26.3 on macOS 15.6) and an Apple Account; about an hour the first time. With a free account the app stops opening after 7 days until you run it from Xcode again; a paid developer account signs it for a year. The Life Dashboard integration needs Home Assistant 2026.3 or newer with HACS. Want to skip the build? The public TestFlight beta is next.
Sends to the Home Assistant integration, the Grafana stack, an MQTT broker or any webhook.
About an hour the first time, if you've never used Xcode. You need a Mac with Xcode 26 (the newest Xcode needs macOS 26.2; on macOS 15.6, Xcode 26.3 works) and an Apple Account. Then: 1. Clone the repository and open the project in Xcode. 2. Pick your own team for the app and the widget. 3. Give both your own bundle identifiers. 4. Replace the app group in three places (the two targets' capabilities and one line in SharedSyncStatus.swift). 5. Run it on your iPhone and allow Developer Mode once. The setup guide shows each screen. With a free Apple Account you run it from Xcode again every 7 days; a paid developer account signs it for a year.
Yes. The app reads what the Watch writes to Apple Health, and total calories arrive only on days with resting energy, which usually takes a Watch. HRV is SDNN, the measure Apple Health stores, so it isn't the same number as RMSSD from an Android watch.
No. Apple's Screen Time API shows usage only inside a report extension that runs in a sandbox with no network access, so no iOS app can send it anywhere. Screen time per app is in the Android app.
No. The app asks Apple Health for read access only. Writing scale and blood pressure readings from Home Assistant into Health Connect is an Android feature.
Keep the companion app for presence and notifications. Its Apple Health sensors show today's total or the newest reading, and their history starts the day you switch them on. This app sends every record of 28 types, backfills up to a year, and also sends to MQTT or a webhook.
Yes. Each phone gets its own device in the integration, and on MQTT the iPhone uses its own base topic. A settings backup moves between the two apps too.
Yes, with two things to know today. The app keeps one signing secret, and pairing with Home Assistant sets it, so give a second receiver the same secret. And a payload counts as delivered once one destination takes it, so a destination that's down at that moment misses it. The app can send to several webhooks and to MQTT at once.
Today you build it from source with Xcode on a Mac. A public TestFlight beta is next. Until then you build it with Xcode and install it on your own iPhone. To update, pull the repository and run it again; your settings stay. Watch the releases on GitHub to hear when the beta opens.
Not yet: building the app needs Xcode, which runs only on a Mac. The public TestFlight beta is the next step and needs no Mac. Until then, an Android phone or the Android app on a tablet is the way in.
The app stops opening until you run it from Xcode again. Your settings and the data already sent stay; payloads that couldn't be sent wait on the iPhone. A paid developer account signs it for a year.
The JSON payload, signatures, retries and receivers for n8n and Node-RED.
Read the guide APIWhy neither has one, and how to get the data onto your server anyway.
Read the guide MCPThe stack's read-only MCP server lets a local model or Claude read your history. Works in Europe too.
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