Oura data sync problems

[hildaer]

Hi, I just found the correct place to file a problem .

From the Oura data sync there are a few minor bugs:

** The "Resting Rate" and "avg. Hr" values are switched

** if you open the Oura app but then continue to sleep there will be multiple readiness score computation, this leads to duplicated rows (with different values) in the data for the same day, the values associated with the first one are kept in the curves.
I think it should be the last one that should be used and that it should just replace the values of the precedent computation, not add a row.

Thanks

[mipapo]

We only store the sleep data from Oura yet and there is everything correct. We use the readings from the sleep entry. The sleep resting heart rate of the sleep has no influence on the general resting HR of the day.

[hildaer]

No, sorry michael but not everything is correct.

As you need more detail:

** the first image shows the multiple row problem.

** the second and third shows the switch between Oura's rest HR values and average HR value (Oura reports the lowest in the night as RHR).

[mipapo]

The switched Resting Heart rate and average hr on the big table is a display issue which will be fixed. If you look at https://runalyze.com/health/sleep/add there is the correct view. (Has been fixed now)

Duplicate entires are currently not handled for Oura - I will take a look at it. The bad thing about Oura is that we don't get notifications about new or updated data so we never can guarantee a "good sync" here

[hildaer]

Thanks Michael.

[hildaer]

An additional comment for the multiple rows for the same day, one fix would be to simply to check at syncing if an entry for the day is already available. If it is, you only need to remove the previous row and replace it with the current values.

[mipapo]

An additional comment for the multiple rows for the same day, one fix would be to simply to check at syncing if an entry for the day is already available. If it is, you only need to remove the previous row and replace it with the current values.

That's clear - Is also on our list. Currently we are working on a bigger internal update and can't put the fix in between.

[hildaer]

Thanks Micheal, that is great.
Sorry for the disturbance, have a great day.
-- Xavier

[mipapo]

A fix will go live with a bigger deploy tomorrow (bigger internal deploy - no new features)

[mipapo]

Fix is live, but I wasn't able to test it (will be able to do it with my own oura hopefully in the end of november)