Sleep recording bug
-
Hello, yesterday I went to sleep at about 22:30 and woke up around midnight and wasn’t able to start to sleep again for a couple of hours. My Race recorded the first part of my sleep (22:45 - 23:54) as a nap and added it as part of sleep time of the night before, resulting in an even shorter total sleep time for the last night. I think it’s pretty odd that that part of sleep/nap is added to the previous night, instead of the current one.
-
@Stefano-M64 I believe it does that since the <nap> was part of the same day so it has to combine them. couple of hours is long time to be considered one sleep imo so the watch worked good no?
-
@EzioAuditore said in Sleep recording bug:
@Stefano-M64 I believe it does that since the <nap> was part of the same day so it has to combine them. couple of hours is long time to be considered one sleep imo so the watch worked good no?
normally people sleep at night, starting in the late evening, so I believe it would be more logical in any case to add that nap to the following sleeping time, which is also temporally closer: only 2 hours with respect to the about 16 hours separating the nap from the previous sleep period. Moreover, in my Daily sleep target, I set Time in bed between 22:00 and 8:00: this should force everything happening in that period to be interpreted as the sleep time for that night. Otherwise, what’s the utility of the Time in bed setting?
Still wondering what makes the difference between nap and sleep in the Suunto’s algorithm … -
@Stefano-M64 It adds it to the day rather to the upcoming sleep I think. So later when you show metrics and tables by day (resources, recovery) are applicable to the same day not to the next day (If I make sense).
The same is done by Oura.
