Awkward sleep metrics

[altcmd]

@el2thek I know but just my point that sleep has been assumed without detecting a heart rate, but resources has continued its normal trend - an anomaly in the code, I feel.

[el2thek]

@altcmd Sleep tracking also works without tracking your heart rate. I think you’ll get better results having your sleep times a bit too early, than too late.

Alternatively, wear your watch a little longer before taking it off. The 20 steps you described could also have been going to the toilet and back to bed.

[altcmd]

@el2thek Got it. Thanks!

[freeheeler]

@altcmd
mine is set from 22:30 - 8:00 and my actual bedtime varies between 21:00 to 0:00 and 5:00 to 9:00. the watch gets my sleep really well, unless I watch TV and sit lazy there it happens that the watch starts tracking even before I go to bed. On the other hand, after an exhausting day I go to sleep earlier, the watch tracks, too and that’s what I expect.
On the other side, in the morning, once I’m up the watch recognizes but I am always active then.
I don’t remember that it has ever added more hours e.g. when I got up at 6 but layed lazy down for 1 more hour.

long story short: I suggest you play with the sleep limits and maybe find the setup that fits you best

[altcmd]

@freeheeler Thanks! Will do!

[mikekoski490]

@altcmd Mine is OK generally but I would prefer if there was an option to choose ‘Stop sleep tracking?’, so you can lie in bed with a coffee and not have that tracked as sleep. COROS had that option. I also noticed last night a 1 beat difference between Min. HR values on the same nights SA results and am still getting the odd gap in the sleep HR graph (?).

[isazi]

@mikekoski490 if I’m not wrong the 1bpm difference between watch and SA is rounding. Been there for a while I think.

[Brad_Olwin]

@altcmd mine is set from 22:30 to 6:30 and I typically wake 5:30 to 6:00 with no detection issues. For me Suunto does not recognize a short awake period during the night but does effectively detect sleep and morning wake times.

[altcmd]

@isazi Any thoughts on why I am seeing a 12 bpm difference?

[mikekoski490]

@isazi Thanks. Im not fussed by it, just thought Suunto would simply put ‘value of X = value of Y’ lol. I have had as much as a 4 beat difference too, BUT again its about trends not a single night, and I find Suunto to be more accurate reflection of how I felt my sleep was (Garmin was ALWAYS wrong).

[isazi]

@altcmd is daily or sleep the lowest?

[altcmd]

@isazi sleep is lower, naturally.

[altcmd]

@mikekoski490 thanks for the input.

[isazi]

If more people are seeing this, post in the Android or iOS app screenshots, and I will forward them to Suunto. And also write the app version you use.

[altcmd]

@isazi 2bpm off today. iOS 2.18

[Spree]

I’ve noticed this as well.

I think that if sleep tracking is activated, and you track at least a bit of sleep, then taking off the watch - so no movement - around the sleep time (imemdiately before or immediately after) will result in additional time “sleeping” being counted.

I guess it might be an unintende consequence of wanting to continue counting when you wake up in the middle of the night to go to the bathroom, or to a crying child.

[Likarnik]

@freeheeler For me it works quite good too regarding when I go to sleep and when I wake up, but I have S9P if algorithm is different. I always open SA to sync before setting alarm and put my phone in airplane mode. This way even if I am reading or watching something before bed, it does not count as sleep time, at least for me. Otherwise it did. Maybe my info is useful for someone.

[Brad_Olwin]

@altcmd In the last two photos you show, when did the 58 minimum occur? If not during sleep they may be different as the minimum in the first screenshot is specific for sleep. I checked mine and I am occasionally of by 1 bpm. As @isazi stated that is a rounding error. The watch does not read HR directly but calculates from IBI I believe.

[The_77]

@mikekoski490 you can manually stop sleep tracking by going to an activity and loading into a run/whatever, that triggers the end of sleep register. Workaround but it functions fine.

[mikekoski490]

@The_77 Perfect. Thanks for the tip!