Can you check if Oura makes a difference in ´Sleep time´ or ´Bed time´?
Some consider Awake as Sleep Time, others don´t.
Tx. For the 26th Intervals got “sleepSecs”:20970 which is 5h46m. I will add some more logging to see exactly what Oura sent. Maybe there are some extra fields.
@MedTechCD See the screenshot below (for 26th July). The difference does not correspond to what it’s fill in intervals.icu.
@david Ok, thank you. If you need more information, do not hesitate. I can answer on intervals.icu chat too.
Edit: today there is still a difference (total sleep → intervals.icu = 7h54, Oura = 8h38, sleep score → 86 vs 95).
I added some logging and have looked at data for the 27th of July (oldest that comes back):
"summary_date": "2023-07-26",
"bedtime_end": "2023-07-27T08:07:38+02:00",
"bedtime_start": "2023-07-26T23:37:38+02:00",
"duration": 30600,
"total": 21810,
"awake": 8790,
"rem": 1770,
"deep": 4680,
"light": 15360,
"score": 64,
"score_total": 61,
Note that he summary_date is 2023-07-26 but Intervals.icu records this on the 27th because that was the day you work up on. Intervals.icu has:
The total field is used for sleep time (21801 = 6h3m). The score comes from “score” (64).
So it all appears to match?
The data from your logs match with the data inside intervals.icu (Wellness).
But it’s not match with the data from Oura.
Total sleep → 6h24 vs 6h03.
And I am wondering if the sleep score matching is not a coincidence?
From Oura: date / sleep time / sleep score
2023-07-28 / 8h38 / 95
2023-07-29 / 7h40 / 71
2023-07-30/ 7h46 / 78
It’s not match with values from intervals.icu.
It’s not seem to be an error from your side but rather Oura side.
Am I the only one to notice these differences?
I use Oura myself and it’s always been fine and haven’t had other reports of problems. Did you perhaps connect an Oura account for someone else in your household who happened to be logged in?
I am the only one in my household with an Oura ring and an Oura account.
I will try to contact Oura.
Just a thought: Time zones are set correctly?
@MedTechCD which time zones?
In intervals.icu, yes. I set my max HR and, for running, I prefer use Pace for zones.
In Oura, there are not any.
I mean the clock settings of your devices. Are your Mobile, PC, Oura all set in the correct time zone?
Like GMT + x. Discrepancies in between the used devices can result in very strange results.
From david’s logging above, the Oura results from the API come in wit a GMT +2 offset which is Central European time.
Yes, on my mobile and on my PC, the time zones are the same.
Actually, I’m from France so it’s GMT+2.
I spoke with Oura support for information:
The data collected from the Oura App is based on the previous algorithm. Oura has since transitioned to using a new algorithm as its primary method for data analysis and insights.
[…] This transition to a new algorithm is part of Oura’s continuous efforts to enhance accuracy and provide more refined insights to users. As a result, variations in data might occur between the old algorithm and the new one.
[…] While we don’t have a specific date for when the new algorithm will be fully implemented across all platforms, including the mobile and web apps, rest assured that our dedicated team is actively working to ensure a seamless transition.
According to this information, I wonder why I am the only one to notice this.
Wow. That’s annoying. I am using a Gen 2 and I just checked and my numbers match so maybe its that.
Well they had the „old“ and a „beta“ algorithm. But they claimed they swapped to the new beta as default
Edit: just checked my data (gen3) and intervals and the app match up to a minute (probably a rounding error of seconds)
Hey Pierre,
You are not the only one. I noticed the same problem today.
Have a 3rd Gen Ring but am getting different data (for sleep time, quality, readiness, score) from Oura to Intervals integration.
So must be the same issue that Oura is sending data based on the “old” algorithm.
1 Like
Hi @david,
The Oura ring is not always reliable. Sometimes, it considers an afternoon nap as a night of sleep. Therefore, it is not possible to correct the data on the Oura platform.
It is possible to correct the data from intervals.icu. However, the synchronization window will overwrite the modification. I have several questions: what is this synchronization window? Could it be customizable? How can I correct the data without it being overwritten in the next synchronization?
Thanks.
Intervals.icu goes back about a week for Oura. So currently it pulls data from 25 Feb. Probably easiest to just wait until that window has passed the bad data day and then edit it. Be careful not to disconnect and reconnect Oura. When that happens your complete history is updated.
Strange that you cannot edit the data in Oura.
1 Like
I’ve modified intervals.icu data that is one week old. 
Thanks @david
In oura, I can’t retroactively adjust the data on my end, and Oura support can’t do it either. 
Possible sleep period types. ‘deleted’ = deleted sleep by user. ‘sleep’ = user confirmed sleep / nap, min 15 minutes, max 3 hours, contributes to daily scores ‘late_nap’ = user confirmed sleep / nap, min 15 minutes, ended after sleep day change (6 pm), contributes to next days daily scores ‘long_sleep’ = sleep that is long enough (>3h) to automatically contribute to daily scores ‘rest’ = Falsely detected sleep / nap, rejected in confirm prompt by user
Not sure how the integration in intervals works but it should filter for ‘long_sleep’ to avoid picking up the naps.