Sleep data disappears
in progress
Arjan Juurlink
Sleep data dissapears after changing imports: i disabled utrahumans integration with garmin because i already receive garmin workouts through google fit (in ultrahuman it was shown twice). Since then todays Sleep Heart Rate Variability, Sleep Heart Rate and Heart Rate Dip were suddenly zero, so the recoveryscore cannot be calculated. I cannot see if sleep data comes from Fit/Google Nest or from ultrahuman ring, but it seems changing integration in garmin effected the sleep data in sonar (i know the data was there in sonar before i changed it). How can i get the data back?
Arjan Juurlink
Thx
Byron
Hi Arjan - we're taking a look into this. A couple questions:
- which device are you wearing to sleep to track your night time vitals? Is it Garmin, Ultrahuman, or both?
- If you go to the Profile tab, and tap on "control how your data is consolidated across data sources" > and then "sleep", is the data source for your sleep data enabled there currently?
Arjan Juurlink
Byron see email I've tested everything with correct lineage. sleep data corrects itself when i wait a couple of hours.
I have one question regarding the garmin import of Outdoor Running
Picture with 751 in the filename shows garmin connect screenprint. Other 2 are Sonar: Only import Outdoor running from Garmin. And the sonar activity screen with one correct import with 653Kcal en one wrong import with 827 Kcal.
All my other apps like Fit, Polar and Samsung show also the right result, and are excluded from the import in the manage data tab in my profile.
How this this happen?
Byron
Arjan Juurlink: Just to confirm: are you saying that the issue you reached out about originally for your sleep data has been resolved?
As for the Outdoor Running workout issue - we'll look into that today. I think I might know what the issue is, and it will be resolved by an update we're making shortly that gives you control over which devices contribute to your workout data on Sonar, but let us confirm.
Arjan Juurlink
Byron hi, the sleep data was a matter of patience, it recalculates after a couple of hours. I’m not sure how this happens after a while, and i’m still not sure what sonar uses as a source, but it adds up now, since i use the correct lineage. So yes the original problem seems not a sonar problem but a matter of lineage and patience. I still like to understand the source of the datapoints i pointed out however. You can close the bugreport, hope you can still clarify the source of the datapoints.
Glad that the upcoming release will solve the ghost data on outdoor running sessions, i’ll be patient!
Byron
Arjan Juurlink Actually the sleep data should be recalculated within 1-2 seconds maximum after you've made a change, so we are going to take a closer look at this for you and see if there's an unexpected edge case occurring that we haven't caught yet.
In terms of how sleep is calculated - it's a great question because there's a lot of complexity behind the scenes that needs to be handled. Here's how things work at a high level - if helpful to clarify further (or if you have any feedback on how things can be done better) - just let me know:
- Ignoring Disabled Sources
Any sleep data sources you’ve toggled off in Sonar are completely ignored. They won’t be used to calculate your sleep for the day.
- Prioritizing Detailed Sessions
If you have “Prioritize Detailed Sessions” enabled (this is Sonar’s default setting), we focus on sleep sessions that include detailed sleep stage data—like light, deep, and REM sleep. Simpler sessions that only track time asleep, such as those recorded by a phone, are deprioritized (i.e. they will only be considered if you have no sleep sessions with sleep stage data).
- Consolidating Data from Each Device
For devices with sleep stage data, we “stitch” together each device's sleep session data. This is because a sleep session often consists of hundreds of individual sleep samples, which we need to combine in order to arrive at your daily sleep totals.
- Determining What to Display
We either use the longest session, the average, or the sum of all the enabled device sleep sessions—depending on the “Consolidation Type” you’ve selected in your Sleep settings.
The sleep vitals that are shown to you (e.g. Sleep HRV, Sleep RR etc.) are then those that occurred during the sleep session that is being displayed to you.
Byron
Arjan Juurlink In terms of your workout data, we confirmed that this is something that will be resolved by an upcoming update, which will be providing you with more control over workout de-duplication and which workout data sources are displayed in Sonar.
Similar to sleep, there's quite a bit of complexity in showing the correct workouts for us to think through, but we're hoping to have this update out within the next 1-2 weeks.
Arjan Juurlink
Byron Great! Looking forward to it!
Arjan Juurlink
Byron then my conclusion is that the sleep data from NEST and ULTRAHUMAN should actually be calculated immediately. So sleep heart rate variability, sleep heart rate and heart rate dip should never actually be 0 (and that does happen sometimes, but that seems to be corrected after hours, but the data turned out to be missing for a few days). Thanks for taking a look at this.
Byron
Arjan Juurlink yes your sleep data should be re-calculated immediately, and the sleep vitals that occurred during the sleep sessions should not be zero either.
The fact that you're seeing a delay for a few hours is definitely a bug, so we'll look into what may be causing that.
Arjan Juurlink
Byroni’m using the mobile website on firefox on my android and laptop btw
Byron
in progress