Open Wearables 0.6.1: Data Coverage & Observability

Open Wearables is an open-source platform for wearable health data. It handles ingestion from multiple wearable providers, normalizes data into a unified format, and computes health scores that power downstream AI and coaching features. It is self-hosted, MIT licensed, and has no per-user fees.

Version 0.6.1 adds a Data Coverage tab to the admin panel, ships observability and logging improvements, and introduces pull sync lookback as a safeguard for periodic pull syncs. The release also includes provider-specific bug fixes across multiple integrations.

What data does this provider actually support?

When building on top of multiple wearable integrations, a common question is what data Open Wearables actually supports for a given provider. The new Data Coverage tab in the admin panel answers this directly. It shows which data types each connected provider supports, with always-up-to-date information. Everything is available in one place, giving you a full overview of data coverage per provider across Open Wearables.

The tab shows Open Wearables capabilities, not synchronized data status. It reflects what the integration supports for a given provider, not whether a specific user has synced that data.

Pull sync lookback

Open Wearables supports two sync modes: webhooks, which deliver data in real time as events are recorded, and periodic pull syncs, which fetch data on a schedule. Webhooks are the recommended approach.

A data gap in pull sync coverage can occur when users haven't opened their wearables app recently, causing the live sync window to expire. Pull sync lookback is a safeguard against this. When set, it extends the start of the sync window backwards by the specified duration.

The variable accepts human-readable duration strings: 2d (2 days), 3h (3 hours), 15m (15 minutes). Disabled by default.

Observability and logging

Version 0.6.1 adds several improvements to make production sync issues easier to diagnose.

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 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.

Upgrading

docker compose pull
docker compose up -d


No breaking changes. Database migrations run automatically on startup.

From Wearable Data to Health Intelligence

If your team has the data flowing and is now figuring out what to do with it, that is the starting point for Signal. Momentum's delivery framework for wearable health intelligence: Blueprint maps your use case, Foundation connects the data sources and deploys the intelligence layer, Intelligence lands coaching, insights, or dashboards inside your app. We bring the integrations, the data layer, and the intelligence. Your team ships the experience.