--- title: "Open Wearables 0.6.1: Data coverage & observability" description: "Open Wearables 0.6.1 adds a Data Coverage tab, PULL_SYNC_LOOKBACK for periodic pull syncs, webhook observability improvements, and provider bug fixes." canonical_url: "https://openwearables.io/blog/open-wearables-0-6-1-data-coverage-observability" --- # Open Wearables 0.6.1: Data coverage & observability [All posts](https://openwearables.io/blog) [Releases](https://openwearables.io/blog/category/releases) Open Wearables Team · Jun 23, 2026 · 3 min read ## 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](https://github.com/the-momentum/open-wearables). ## 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](https://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](https://openwearables.io/blog/open-wearables-0-6-0-womens-health-fit-files) [Open Wearables 0.5.2: Polar Webhooks, Sport Type Expansion, and HRV Score Integrity](https://openwearables.io/blog/open-wearables-0-5-2-polar-webhooks-sport-type-expansion-hrv-score-integrity) [Open Wearables 0.5.1: Oura & Strava Webhooks and Live Sync Status](https://openwearables.io/blog/open-wearables-0-5-1-oura-strava-webhooks-live-sync-status) ## Keep reading Releases · Nov 3, 2026 · 11 min read ### Open Wearables 0.11.0: daily aggregates and faster summaries Open Wearables 0.11.0 moves day and session values into their own aggregate tables, adds day, week and month time series, computes missing workout statistics and cuts the heaviest summary from seconds to 25 ms. Contains breaking changes. Releases · Oct 26, 2026 · 11 min read ### Open Wearables 0.10.0: new dashboard, nutrition data and sync-aware webhooks Open Wearables 0.10.0 rebuilds the dashboard in SvelteKit, adds 42 nutrition series types with a meal event, tags every data webhook with the sync it came from and splits calories into total, active and basal energy. Contains breaking changes. Releases · Sep 23, 2026 · 13 min read ### Open Wearables 0.9.0: Google split into two providers, energy renamed, and a long list of API corrections Open Wearables 0.9.0 splits Google into google_health and health_connect, renames energy to active_energy, disables the Google Health API rollup that wrote duplicated rows, and fixes date bounds, filters and pagination across the API. Contains breaking changes. ## Run it in your own cloud Open Wearables is open source and self-hosted. Start from the repository, or bring us in to stand it up in your account. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book)