Home Assistant and Marrow Health

Automated

Steps, sleep, weight and calories as Home Assistant sensors, updated on a schedule, for dashboards and automations at home.

Open in Marrow works on an iPhone with Marrow 1.4.2 or later.

Automated (Webhook trigger) Free

Marrow posts CSV or JSON to a URL on a schedule, with the app closed. You need: Your Home Assistant, reachable over HTTPS.

In Marrow, open Export and tap Home Assistant. Turn Automated on.
Add the webhook trigger and sensors from the recipe to configuration.yaml.
Open the recipe
In Marrow: New Automation. Its page asks for:
- Address: Your Home Assistant address, then /api/webhook/ and the webhook id from the recipe. It must be reachable over HTTPS. No header needed. It looks like https://<your-ha>/api/webhook/<id>.
- Data and Cadence: the kind of data, JSON or CSV, and how often it runs.
- Run: Restart Home Assistant after editing configuration.yaml, then Run now.

Delivered, yet the sensors do not change. Home Assistant answers 200 even for a webhook id it does not know, so Marrow shows delivered. Check that the id at the end of the address matches webhook_id in configuration.yaml exactly.
Received remote request for local webhook. This warning in the Home Assistant log means local_only is on, its default. A request from the internet, a Nabu Casa cloud webhook included, then does nothing. Set local_only: false, as in the recipe.
Server answered 405. The webhook takes POST and PUT by default. If allowed_methods is set, it must include POST.
Edits to configuration.yaml do nothing. Restart Home Assistant after editing it. Changes to template entities can also be reloaded with the template reload action.
No HTTPS address. Marrow needs one. A Nabu Casa cloud webhook gives one, or put your own domain with a certificate in front of Home Assistant.
The values are empty. Pick JSON in Marrow. Home Assistant hands the body to trigger.json only when it is JSON.

Test with Run now. The line under Run now says what happened. Any 2xx answer counts as delivered. Anything else shows as Server answered and the status code, or the network error.
Check the Activity log. In the automation, More options, Activity log lists its last 30 runs with the result of each.
Runs come late. iOS picks the moment for background runs, and a phone that stays locked sends when it is next unlocked. Since last run catches up on the next run that succeeds.
A receiver on your home network. Marrow needs Local Network access to reach it (Settings, Privacy and Security, Local Network). Tap Run now once with Marrow open, so iOS can ask: in the background it refuses without asking.
It will not switch on. Each automation that is on counts as a connection. Free keeps 1 connection on at a time. Marrow Pro keeps up to 10: AIs, servers and automations together.

More fixes in the guides: Automated.