When Oura logs both a main overnight sleep (type: long_sleep) and a nap (type: sleep) on the same calendar day, Intervals.icu stores the nap duration in sleepSecs rather than the overnight duration.
The sleepScore and avgSleepingHR appear correct (they come from the main sleep), but sleepSecs is wrong.
Matches between Intervals sleepSecs and Oura nap duration on my profile:
9/9 anomalous days confirmed as nap duration. The match is exact to the second in every case.
Expected behaviour: sleepSecs should reflect the longest session (type: long_sleep) when multiple sessions exist, or the sum of all the sessions of the day
Device: Oura Ring (v2 API), synced to Intervals.icu.
Notably, all the original 8 dates reported (2025-10-29, 2025-11-01, 2026-01-06, etc.) now show the correct summed value — so the historical data was backfilled. But something has
regressed in the last ~4 weeks: every day since 24 April that had a nap is wrong again, while days without naps (e.g. 2026-05-15, -16, -18) are fine.
hi david,
Actually this is still happening on my account: 29 of 71 days since 1 Sep. On those days sleepSecs is short (9–55 min), while the sleep score, HRV and sleeping HR are the full night’s. The Oura app shows a single sleep for these nights, with no nap or second entry:
2026-11-09: in bed 21:12, up 05:14 in Oura; Intervals has 2850 s (0:47)
2026-11-03: in bed 22:06, up 05:52 in Oura; Intervals has 540 s (0:09)
Other days: 2026-11-02 (2580 s), 2026-10-30 (3300 s).
Can you see which sleep period the sync is taking for these days? Could sleepSecs use the long_sleep period, as the score and heart rate already do?
