the-momentum/open-wearables

Whoop sends daily aggregates, for example daily strain score (even if there are no workouts), and certain things like sleep sessions are associated with cycles. We will need to add the /v2/cycle endpoint support to app/services/providers/whoop/data_247.py module. It is very similar to other endpoint returning data, so most of that is just connecting the endpoint and copying some code (or preferably separating a part of the code and making it reusable).

Context When we calculate an OW sleep score (provider=internal), it's derived from a specific provider's sleep record (Garmin, Whoop, Oura, ...). On the dashboard a user can see multiple "OW" badges for the same night - but there's no way to tell which underlying source each one came from. Proposed fix Frontend: Display the source provider next to "OW" badges (e.g. OW · Garmin 92, OW · Whoop 94) so users can tell which sleep record drove each calculation. Backend: The data is in the DB - health_score.sleep_record_id → event_record.data_source_id → provider - but HealthScoreResponse (backend/app/schemas/model_crud/activities/health_score.py) only exposes provider and data_source_id. To avoid an extra lookup against /users/{user_id}/data-sources, add a source_provider: ProviderName | None field; for internal scores resolve it from the linked data source, for others it equals provider.

Provider Komoot — popular outdoor navigation and route planning app for hiking, cycling, and mountain biking with 35M+ users. Website: https://www.komoot.com API: Partner-only (B2B), not publicly accessible OAuth2 example: https://github.com/komoot/komoot-oauth2-connect-example Apply for access: https://www.komoot.de/b2b/connect#profileconnect API details Detail Value Auth OAuth2 (partner credentials required) Access B2B partnership application required Auth URL https://auth-api.main.komoot.net/ API URL https://external-api.komoot.de/v007/ Endpoints User tours (routes), tour details with GPS tracks Webhooks Unknown Data available Tours/Activities: hiking, cycling, mountain biking with full GPS tracks Route details: distance, duration, elevation, surface type Planned routes: user-created routes (not just recorded activities) Important limitation Komoot does not offer a public API. Integration requires B2B partnership approval. Existing partners include Garmin,

Parse and save granular sleep stages from Ultrahuman sleep_graph Ultrahuman API returns timestamped sleep stage transitions in sleep_graph.data, but data_247.py only extracts aggregated durations (deep/light/REM/awake minutes). The sleep_stages JSONB column in sleep_details exists and has a GIN index, but is empty for all 83 records in the database. API payload { "type": "sleep", "object": { "sleep_graph": { "data": [ {"startTime": 1711234567, "endTime": 1711234867, "type": "awake"}, {"startTime": 1711234867, "endTime": 1711236067, "type": "light_sleep"}, {"startTime": 1711236067, "endTime": 1711237267, "type": "deep_sleep"}, {"startTime": 1711237267, "endTime": 1711238467, "type": "rem_sleep"} ] } } } What needs to happen Parse sleep_graph.data in data_247.py and save to sleep_details.sleep_stages JSONB column Normalize the schema (e.g. convert unix timestamps to ISO 8601, map stage names to our standard enum) Add integration

Add resting heart rate (night_rhr) parsing for Ultrahuman Ultrahuman API returns night_rhr (Resting HR - Sleep Time Average) in the daily metrics response, but data_247.py doesn't process it. API payload { "type": "night_rhr", "object": { "day_start_timestamp": 1705276800, "title": "Resting HR", "values": [ {"value": 52, "timestamp": 1705290000}, {"value": 50, "timestamp": 1705293600}, {"value": 51, "timestamp": 1705297200} ], "subtitle": "Sleep Time Average", "avg": 51 } } What needs to happen Map night_rhr to SeriesType.resting_heart_rate (id=2, unit=bpm) Add "night_rhr" to the processed types in load_and_save_all (similar to how vo2_max was added) Decide whether to save the avg as a single daily value or each values[] entry as time series samples Add integration test Related Fixture already has night_rhr data in tests/providers/conftest.py:417