Life Dashboard Companion is an open-source Android app that sends Health Connect data and screen time per app to Home Assistant, MQTT or your own webhook, with no cloud and no account. It reads what Samsung Health, Google Health, Garmin Connect, Oura, Withings and others write to Health Connect.
Google Play: coming, as a paid listing of the same app · Obtainium · F‑Droid: coming
Steps, sleep stages, heart rate, HRV, weight, blood pressure, glucose, workouts, nutrition and cycle tracking, each with its own switch.
Each record goes out with a stable ID and the app that wrote it. Daily totals count a walk once.
Backfill 30, 90 or 365 days. In Home Assistant each day lands on its own date in long-term statistics.
Foreground minutes for every app, with a day boundary you choose and a filter that keeps the apps you pick out of what's sent.
The Life Dashboard integration, MQTT with Home Assistant Discovery, or any webhook that accepts a JSON POST. Several at once works too.
Scale and blood pressure readings from Home Assistant go into Health Connect, where Samsung Health and Google Health read weight.
The Life Dashboard integration pairs with one QR code and keeps every day in long-term statistics. MQTT with Home Assistant Discovery suits a setup that already runs a broker and only needs current values.
Point the app at n8n, Node-RED, the Grafana stack or a short script. A webhook also gets what no sensor holds: single meals, cycle tracking entries and workout details.
The app reads foreground time per app from Android's usage statistics, the same numbers Digital Wellbeing uses. Screen time has its own schedule and webhooks, and works without Health Connect on Android 8.0 or newer.
Health Connect and screen time per app
Open it on your phone and allow installs from your browser once. Each new release is on GitHub, or Obtainium updates it for you.
Health data needs Android 9 or newer with Health Connect, which is built into Android 14 and later and comes from Google Play on Android 9 through 13. Screen time works on Android 8.0 and newer. The Life Dashboard integration needs Home Assistant 2026.3 or newer with HACS. MQTT needs a broker, and a webhook needs a server that accepts a JSON POST.
Sends to the Home Assistant integration, the Grafana stack, an MQTT broker or any webhook.
25 of the 33 through the integration, 24 over MQTT. The other eight (nutrition, mindfulness, sexual activity and five cycle tracking types) are events rather than values, so they get no sensor; the integration counts mindfulness minutes per day. Workouts get a last workout sensor and the minutes of today and yesterday in the integration. A webhook of your own gets those records in full.
Yes, with two things to know today. Each tab 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. Health Connect and Screen Time can each send to several webhooks and to MQTT at once. Giving every destination its own secret and delivery is planned.
Each sync writes its payload to the phone first and deletes it only once a webhook has accepted it. The outbox holds up to 700 Health Connect payloads, about a week of syncs at the 15-minute interval, and the next sync that gets through delivers them first.
Yes. Each tab has its own Sync Schedule: every 15 minutes or longer, or a list of times, on the days you pick, with quiet hours. A Quick Settings tile, Tasker and MacroDroid can start a sync too.
No. Readings come back in the integration's signed response to the webhook call the app already makes, so Receive needs the Life Dashboard integration. Smart scale to Samsung Health walks through the setup.
Auth headers, signing secrets and MQTT passwords are encrypted with AES-256-GCM, with a key the Android Keystore holds. Android's own backup leaves them out, along with the webhook logs.
Between syncs the app does nothing: no service keeps running and no connection stays open. Each sync is a short job that Android starts on your schedule. On Samsung, Xiaomi and similar phones, set the app's battery usage to Unrestricted, or Android stops the scheduled syncs; the setup guide has the paths per brand.
Health Connect read permissions for the types you switch on, write permissions only for the Receive types you switch on, usage access for screen time, the camera only while you scan a pairing code, internet access, and notifications for failed syncs and backfill progress. Data goes only to the addresses you enter. The privacy policy lists every permission and every field.
Yes. Every build has the same package name and is signed with the same key, so one installs over the other and your settings stay.
Samsung Health, Garmin, Fitbit, Oura and Withings data as sensors, with a year of history.
Read the guide WebhooksThe JSON payload, signatures, retries and receivers for n8n and Node-RED.
Read the guide Screen timeMinutes per app as sensors, limits you set yourself, and several phones.
Read the guide Smart scaleWeight, body fat and blood pressure from Home Assistant into Health Connect.
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 ExportGalaxy Watch data as JSON in your own database, n8n flow or script.
Read the guide APIWhy neither has one, and how to get the data onto your server anyway.
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