Min. Sleep HR too high?
-
I’ve noticed for sometime that the “Minimum Sleep HR” reported by Suunto isn’t the actual lowest HR from the overnight data. Here’s an example from last night’s sleep. This is two images stitched together to show the issue. At the top, notice the overall range is 45-73bpm, then below the graph it says Average HR is 53bpm and Min. sleep HR is 48bpm. I’m not sure why it claims 48 when it clearly has 45 as the low point of the range. The bottom part of this screenshot is what it shows when I select the lowest point in the timeline, showing me yes, I did get to 45bpm.
This is pretty consistent every day, where the reported min. sleep HR is a few points higher than the lowest actual point on the graph. One thing I noticed is that Suunto doesn’t write all its data to Apple Health, and reviewing last night’s data, 48 is the lowest it sent to the Health system, as shown here:
Note the Apple Watch recorded several samples at 42-47 lower than the overall “min sleep HR” Suunto claims, so I do believe my HR dip was closer to 42 than to 478. This would be fine if the two devices were simply getting samples at different times, with one capturing a low point the other miss, but looking at the Suunto HR graph, it did get the lower points, but doesn’t send all samples to Apple Health and also not apparently noticing its own samples?
Do I misunderstand what “min. Sleep HR” is supposed to mean? If I have, then perhaps the descriptions of the data is wrong. From my vantage, it seems this is simply a bug in noting the actual lowest point.
-
@raven said in Min. Sleep HR too high?:
I’ve noticed for sometime that the “Minimum Sleep HR” reported by Suunto isn’t the actual lowest HR from the overnight data
Yep, I’d noticed that myself for a while now
-
@raven This has been discussed before and, if I recall, the reason for the discrepancy is that the minimum sleep HR is actually the lowest average HR over a given time period (I think 10 minutes? not sure, though). This can obviously differ from the absolute lowest specific HR reading.
Vertical Ti / S9PP Ti / S9P Ti
-
@duffman19 said in Min. Sleep HR too high?:
@raven This has been discussed before and, if I recall, the reason for the discrepancy is that the minimum sleep HR is actually the lowest average HR over a given time period (I think 10 minutes? not sure, though). This can obviously differ from the absolute lowest specific HR reading.
Appreciate the context. Given that info, I still feel there’s an issue here. As one can see from what I presented, I think it’s easy to think there’s a conflict between “Min Sleep HR” and the lowest point of the graph. It may be there needs to be a different label, something like “low sleep trend” that indicates the value isn’t the lowest recorded, but whatever it’s meant to represent. As it is, it just looks like the system is “lying” to me when it tells me my low sleep HR was X but it’s always actually X-2, or X-4, etc.
-
@duffman19 it is not a time frame thing as the app presents it in 10 minute frames anyway:
-
@2b2bff I wish there was a way to see all the samples that were taken. With Apple Health one can dig and find it as I showed above, which typically people aren’t going to look there all the time, but on occasion it’s nice to be able to inspect all the samples. But Suunto doesn’t write all its samples to Apple Health, so can’t be used to check that. The observation you have, that selecting a point on the HR graph shows a number in a ten minute range, suggests that’s an average of all the samples taken in that time? Or is it something else?
Regardless, your own screenshot also shows this issue, that Suunto is saying “min. HR sleep” is one value, but one can find lower numbers looking at the overall range and selecting points. If this is common with all Suunto devices and on both Android/iOS then it seems by design? I would like for there to not be a discrepancy.
