Start mobieusHealth. Join and track your health. Get started

Connecting a device

3 min read · 434 words · 1 revision · Updated Sep 6, 2026

Three device accounts connect to Loopa directly: Withings, Oura and iHealth. You sign in once at their end and Loopa pulls your readings on a schedule. Everything else reaches Loopa through Apple Health, which is covered on Hume Health and other devices.

Device sync is a Loopa Premium feature. Logging everything by hand, including activity, stays free.

Connecting one

Health › Settings › Devices, or Health › Sync on the web.

Pick the service and tap Connect.

You are taken to their sign-in page. Loopa never sees your password for it.

Approve the access they ask for, and you come back to Loopa connected.

Disconnect is on the same screen and takes effect immediately.

What each one brings in

Withings. Weight and body fat, blood pressure, pulse, blood oxygen, and body and skin temperature.

Oura. Sleep duration, resting heart rate, blood oxygen and steps. No weight and no blood pressure, because the ring does not measure them.

iHealth. Vitals, weight, body fat and steps.

Food is never imported. iHealth exposes it and Loopa deliberately does not write it into your diary: your food log is something you curated, and an import with no reliable way to recognize an entry it has already seen duplicates every meal on every overlapping sync.

Your own entries always win

A day is synced per day, per source, and re-running a sync overwrites that day's device readings rather than adding another copy. So the hourly sync and the Sync now button are both safe to press as often as you like.

A reading you entered by hand beats a device reading for the same thing. Loopa never overwrites what you typed.

When it needs reconnecting

Access tokens expire, and a service can revoke one when you change your password at their end. When that happens the connection shows needs reconnecting and stops trying.

That is deliberate rather than a failure to retry: once a service has said the token is invalid it says so every time, so retrying costs a request an hour and fixes nothing. Reconnect and the next run picks up normally.

What crosses, and what does not

Readings come in. Nothing goes out. Loopa does not write to your device account, does not post anything there, and does not share your Loopa record with them.

The sync status screen carries timestamps, counters and error messages only, never a reading.

Related

Contributors:
Last edited by mobieus · Community, account and privacy coverage: buddies, challenges, credits, appeals, devices and the legal documents
Created Sep 6, 2026
Was this article helpful?