Sync your Move
Syncing is how Move sends new data to your phone. The watch records continuously on-device and only transmits when you trigger a sync, so your trends update on your schedule.
How to sync
Open the HealthyPi Move app and tap the sync icon in the top-right corner. The transfer runs automatically over Bluetooth.
You can sync as often as you like — there’s no minimum interval. Keep your phone within a few metres of the watch until the indicator clears.
What syncs, and how often
| Metric | Recorded on device | Available after sync |
|---|---|---|
| Heart rate | Every minute, continuously | Day / week / month trends |
| Skin temperature | Every minute, continuously | Day / week / month trends |
| Activity (steps, calories) | Every minute, continuously | Day / week / month trends |
| SpO₂ | On-demand only (per measurement) | Per-measurement history |
| ECG | On-demand 30-second recordings | Stored as separate log files |
Continuous SpO₂ is power-hungry — it requires running the optical sensor and the MAX32664 algorithm hub at high duty cycle. Move opts for on-demand SpO₂ to preserve battery for round-the-clock heart-rate, temperature, and activity tracking.
What happens during sync
- The watch and app establish a BLE connection.
- The app pulls any new minute-by-minute samples since the last sync.
- ECG recordings since the last sync are transferred as separate log files (use Fetch Logs in the Devices tab to retrieve them).
- The app rebuilds the daily/weekly/monthly trend views with the new data.
The time-zone sync also runs in the same step — Move picks up your phone’s current time zone, so trends are bucketed correctly.
Exporting your data
Your synced data lives in the app’s local storage on your phone — nothing leaves the device unless you export it. Export options are evolving; current support:
- ECG recordings — accessible via Devices → Fetch Logs.
- CSV / JSON export of trends — in active development, surfaces in upcoming app releases.
For the full data-ownership story (where data lives, retention, deletion), see Data Ownership & Privacy.