Connections / Data and dashboards

InfluxDB and Marrow Health

Automated

Every metric as a time series in InfluxDB, posted on a schedule.

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

Automated Free

Marrow posts CSV or JSON to a URL on a schedule, with the app closed. You need: Telegraf or the 30-line bridge from the recipe.

In Marrow, open Export and tap InfluxDB. Turn Automated on.
Run the Telegraf listener or the bridge from the recipe in front of InfluxDB.
Open the recipe
In Marrow: New Automation. Its page asks for:
- Address: The address of the bridge or Telegraf listener, not InfluxDB itself. It looks like https://<bridge>/.
- Headers: Add Authorization: Bearer and the secret the bridge expects.
- Data and Cadence: the kind of data, JSON or CSV, and how often it runs.
- Run: Tap Run now to send a first payload.

Marrow posts straight to InfluxDB and fails. InfluxDB's write API takes line protocol only, so Marrow's JSON gets a 400. Point Marrow at the bridge or the Telegraf listener from the recipe.
Server answered 502 from the bridge. InfluxDB refused the write. It answers 401 when the token is wrong or cannot write to the bucket, and 404 when the org or bucket name is wrong. InfluxDB 2 wants Authorization: Token and the API token.
Telegraf gets nothing. The listener defaults to port 8080 and the path /telegraf. The recipe sets port 8798 and /marrow, so the address in Marrow must match. It takes Basic auth: Authorization: Basic and the base64 of user:password.
Telegraf answers 204, yet no points. Telegraf answers success even when it parsed nothing. Check that the json_v2 block matches the payload, and run Telegraf with --debug to see what it read.

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.