---
title: "Open Wearables 0.5.2: Polar Webhooks and HRV Score Integrity"
description: "Open Wearables 0.5.2 adds Polar webhook support, expands workout type mappings, new Garmin fields, and stricter HRV scoring."
canonical_url: "https://openwearables.io/blog/open-wearables-0-5-2-polar-webhooks-sport-type-expansion-hrv-score-integrity"
---

# Open Wearables 0.5.2: Polar Webhooks, Sport Type Expansion, and HRV Score Integrity

[All posts](https://openwearables.io/blog)

[Releases](https://openwearables.io/blog/category/releases)

Open Wearables Team · May 20, 2026 · 3 min read

Open Wearables 0.5.2 is out. This release focuses on a full Polar refactor with webhook support, expanded sport type coverage across providers, new Garmin fields, and a stricter HRV-CV scoring policy. Full release notes are on [GitHub](https://github.com/the-momentum/open-wearables/releases/tag/0.5.2). If you want to see Open Wearables running in your stack, [book a Discovery call](https://openwearables.io/).

## Key takeaways

- Polar now syncs sleep and timeseries data, with optional webhook support
- WorkoutType enum expanded: 70+ provider-specific mappings updated across Apple, Garmin, Suunto, and WHOOP
- Garmin now fetches allDayRespiration and moveIQActivities
- HRV-CV Resilience Score returns null instead of a fallback SDNN value when RMSSD data is missing
- New recovery summary endpoint added
- Two new contributors, bringing the total to 36

## Polar refactor and webhook support

The Polar integration has been reworked to synchronise sleep and timeseries data. By default, **Periodic Pull** remains the active sync method. Webhooks are opt-in: enable them in `Settings > Providers`. Once enabled, Polar pushes data to your Open Wearables instance rather than waiting for the next pull cycle.

A few things worth knowing before you enable webhooks. Your instance needs to be publicly reachable. Polar webhook delivery has the same retry behavior as other providers, so handle duplicate event delivery gracefully. The fix for duplicate `EventRecordDetail` inserts in this release (using savepoints to handle conflicts) covers exactly this kind of scenario.

If you are building a wellness or fitness app where Polar data timeliness matters, the webhook path is now viable. If you are running batch analytics, Periodic Pull is still the simpler option.

## Expanded sport type support

Before 0.5.2, a lot of provider-specific activity types ended up mapped to `WorkoutType.OTHER`. That made sense as a placeholder, but it became a problem when you needed to differentiate activities in your application logic or analytics pipeline.

This release expands the `WorkoutType` enum and adds explicit support for activities that were previously swallowed by `OTHER`. Over 70 provider-specific mappings have been updated across Apple, Garmin, Suunto, and WHOOP. New named types include cricket, lacrosse, racquetball, bowling, archery, fencing, fishing, wakeboarding, parkour, curling, and more.

This is a non-breaking expansion since new enum values are additive. Existing records mapped to `OTHER` will not be retroactively updated, but new syncs will use the correct types.

## New Garmin fields

Two fields have been added to Garmin-specific attributes: `allDayRespiration` and `moveIQActivities`.

`allDayRespiration` provides continuous respiration rate data across the day, not just during tracked workouts. `moveIQActivities` exposes Garmin automatic activity detection: walking, running, cycling, and swimming identified without requiring the user to manually start a workout.

## Strict RMSSD enforcement for HRV-CV Resilience Score

Previously, when overnight RMSSD data was missing for a user, the HRV-CV Resilience Score calculation would automatically fall back to SDNN. RMSSD and SDNN measure different aspects of heart rate variability. They are correlated but not equivalent, and using one as a silent substitute for the other produces scores that look valid but are computed on different underlying data.

0.5.2 disables the SDNN fallback pending further validation. Users without overnight RMSSD data will now receive a `null` score instead of a fallback value. A null score is honest. A score computed from a different metric without disclosure is not.

If your application currently displays HRV-CV scores, add handling for null values and consider surfacing a message to users explaining why the score is unavailable when RMSSD data is missing. The fallback may be re-enabled once the relationship between RMSSD and SDNN in this specific calculation has been validated more rigorously.

## Other fixes and changes

- New recovery summary endpoint
- Fix: commit each data type individually and rollback session on exception for Oura and Whoop
- Fix: cast to local date for summary endpoints
- Fix: validation for date parameters in OpenAPI specs
- Fix: skip invalid user rows during email validation
- Fix: handle duplicate EventRecordDetail inserts gracefully with savepoint
- Updated all Python and TypeScript dependencies

## Upgrading

```
docker compose pull && docker compose up -d
```

Full changelog: [github.com/the-momentum/open-wearables/releases/tag/0.5.2](https://github.com/the-momentum/open-wearables/releases/tag/0.5.2)

Docs: [docs.openwearables.io](https://docs.openwearables.io)

Questions or feedback: join the [Discord](https://discord.gg/openwearables) or open an issue on GitHub.

## 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)
