Key takeaways
- A new Data Coverage tab in the admin panel shows which data types each connected provider supports, with always-up-to-date information.
- PULL_SYNC_LOOKBACK adds safeguard functionality for periodic pull syncs using human-readable duration strings.
- Webhook logs are now linked to users and traces, including failed delivery attempts.
- Sync metadata now distinguishes between inserted and updated records.
- Provider-specific fixes across multiple integrations, with nine contributors including three first-time contributors.
Introduction
Version 0.6.1 is released. The release adds a Data Coverage tab to the admin panel and ships observability and logging improvements. It also introduces PULL_SYNC_LOOKBACK as a safeguard for periodic pull syncs, and provider-specific bug fixes.
Data Coverage tab
A new admin panel tab displays supported data for each connected provider, with always-up-to-date information. Everything is available in one place, giving you a full overview of which data types Open Wearables covers for each provider.
The tab shows Open Wearables capabilities, not synchronized data status.
Lookback for pull syncs
Although we recommend using webhooks, PULL_SYNC_LOOKBACK is available as a safeguard against data gaps if you need to use periodic pull syncs for any reason. When set, it extends the start of the sync window backwards by the specified duration. This addresses situations where data gaps occur because users haven't opened their wearables app recently.
The variable accepts human-readable duration strings: 2d (2 days), 3h (3 hours), 15m (15 minutes). Disabled by default.
Observability and logging
Webhook logs are now linked to users and traces, including failed delivery attempts.
Sync metadata now distinguishes inserted from updated records, subdividing items into inserted and updated categories.
The application version is now included in Sentry logs.
A new "skipped" sync status is added for syncs that complete with no new data to process.
Provider-specific fixes
Suunto: sleep sync statistics are now reported correctly. A webhook edge case in workout handling has been resolved.
Garmin: body composition and blood pressure data arriving via webhook now persists correctly. Previously these records were received but not stored.
Polar: training load fields now correctly accept float values. A validation error caused Polar's float data to be rejected on ingestion.
Whoop: UTC-aware datetime construction has been fixed.
Fitbit: date string-to-datetime conversion has been fixed.
Webhook delivery: non-retriable webhook responses no longer retry indefinitely.
Other changes
Docker Hub image publishing has been added to the CI/CD workflow. Official images are now published automatically on each release.
An ORM object downgrade issue that caused a "this session is in committed state" error has been fixed.
Upgrading
docker compose pull
docker compose up -d
No breaking changes. Database migrations run automatically on startup.
Community
Nine contributors participated in this release, including three making their first contributions. Full source code, contribution guidelines, and issue tracking are at github.com/the-momentum/open-wearables.
Open Wearables
Open Wearables is an open-source platform that connects your application to wearable and health data providers through a single API. One normalized data model, multi-provider support in a single self-hosted deployment, no per-user fees, MIT licensed, and health intelligence built in: normalized recovery, sleep, activity and biometric data ready for your product layer.
We offer custom deployment and integration support through Momentum. If your team needs help getting to production faster, we can set up and configure Open Wearables as part of a managed engagement. Let's talk.
Book a demo to see how Open Wearables fits your use case.
Frequently asked questions
What does the Data Coverage tab show?
It shows which data types each connected provider supports within Open Wearables, with real-time updates. It reflects integration capability, not whether a specific user has synced that data.
Does the lookback variable affect all providers?
It applies to providers using periodic pull.
Will the Garmin body composition fix surface historical records retroactively?
No. The fix addresses persistence going forward.
What does the "skipped" sync status mean?
A sync that completed with no new data to process.
How do I contribute?
The GitHub repository at github.com/the-momentum/open-wearables contains contribution guidelines. Three new contributors joined with this release.
See related articles
Open Wearables 0.6.0: Women's Health & FIT Files
Open Wearables 0.5.2: Polar Webhooks, Sport Type Expansion, and HRV Score Integrity
Open Wearables 0.5.1: Oura & Strava Webhooks and Live Sync Status