Overview
This spike explores how to bring Zepp (Amazfit) wearable data into the Data Hub common schema. The goal is to ingest workouts, sleep, and daily health metrics in a stable way that does not rely on fragile reverse engineering, and does not require giving credentials to third-party services.
Deliverables
| ID |
Title |
Effort |
Status |
Owner |
| 1 |
Zepp ingest options and recommended path |
M |
Complete |
Chatty |
| 2 |
Spike report |
S |
Complete |
Chatty |
Key Decisions
- Use supported APIs as the ingestion surface. Zepp does not appear to offer a clean, stable end-user cloud API like Strava. Prefer sync bridges into Strava and Google Fit or Health Connect.
- Canonical stores: Strava is the canonical workout store, Google Fit or Health Connect is the canonical daily health store (sleep, HR, steps).
- One-time Zepp backfill is acceptable, ongoing Zepp scraping is not. If we need deeper history, use a manual export or token capture workflow once, then stop.
Technical Notes
Data types we care about
- Workouts: rides, walks, runs, GPS, HR, pace/speed
- Daily health: steps, continuous HR, resting HR, sleep stages, HRV or stress if available
Ingestion paths (ranked)
- Zepp → Strava for workouts, then ingest via Strava API
- Zepp → Google Fit or Health Connect for sleep, HR, steps, then ingest via Google
- Optional one-time backfill: community exporter that uses the Huami GDPR export flow token to export workouts in open formats
- Zepp OS mini program: engineering-heavy option to stream sensor data forward going
Artefacts:
docs/spike-006/zepp-data-options.mdreports/spike-006-report.html
Outcomes
- Clear recommendation for Zepp ingestion aligned to Data Hub schema and safety goals.
- Concrete next actions identified for implementation and for verifying what Zepp currently syncs in your setup.
Open Issues
- Device specifics unknown. Need Amazfit model and confirmation of which sync bridges are enabled (Strava, Google Fit, Health Connect).
- Google Fit deprecation risk. Fit REST API is deprecated for new users. Health Connect is likely the longer-term path on Android.
- Backfill approach is fragile. Reverse engineered exporters may break. Treat as one-off only.