Naps being detected as sleep

DirtJezus said:

Shouldn’t all sleep OUTSIDE of the sleep schedule be tracked as a nap ?

It should do that, but it doesn't.
Just like the backlight "no timeout" actually means 5 minutes.

DirtJezus said:

naps register as sleep and overwrite my sleep data.

From what I see Nap time is added to total sleep time but does not affect the overnight sleep score. A nap is a short sleep anyway so I can't see why that shouldn't happen.

The watch detecting any sleep when active whether nap or real sleep is a different matter. 

DirtJezus said:

Naps get detected sometimes, and other times my naps register as sleep and overwrite my sleep data.

If the nap is recorded as being longer than 3 hours, including wake periods, then it will replace your night of sleep. Some ways to defeat this:

- turn off the wrist HR during longer periods of computer work or TV watching (using battery saver for example to make it visible because of the watch face),

- turn on "move IQ" so that you get alerts when you didn't move enough.

PS: Right now, I am testing another related trick. To avoid having the watch start my sleep while I watch TV in the evening, I have left the evening report turned on, but I have moved the start of my sleep mode schedule so that the evening report shows up about when I typically go to bed. To help with the scheduling, the evening report shows up 1h55mn before the start of the sleep schedule. Initial testing shows that no sleep will be starting before the evening report, unless the "nap" is longer than 3 hours. It matches previous comments by Garmin that sleep detection is heightened a couple of hours before the start of the sleep schedule.

I think the 3 hours also includes the total of multiple naps. thanks for the tips - but I’m not really interested workarounds to get my watch to behave the way it’s supposed to. The sleep detection algorithm should start with a nice big IF statement flagging sleep as a nap if detected outside the set sleep schedule - no matter how long a nap. 

 No - the nap wasn’t added to the total. My overnight sleep was REPLACED with the nap - which was outside of the set sleep schedule. 

DirtJezus said:

I think the 3 hours also includes the total of multiple naps

When the watch thinks you fell asleep, it starts analyzing your sleep phases just like during the night. If you move a bit, it might see it as an “awake period” and then continue recording further sleep, or it might end the sleep. The total sleep duration is the “nap” duration. If this duration is greater than 3 hours, then it replaces your previous night.

i don’t like this behavior neither but I can see how it might be useful for people with a variable sleep schedule.

It looks like the sleep algorithm does its thing on its own in the background and “drops” its results. It seems the algorithm is unaware of the UI/UX interactions since you can manipulate the watch, including resetting it, while it still sees you asleep.

Maybe as the Firstbeat integration continues to unfold we’ll see tighter integration and control.

I just wish there was some way to turn off automatic sleep detection during the day.  At the very least there should be a way to delete the fake naps it erroneously detects. 

What did you actually see? A change in Sleep Duration? A change in Sleep Duration and Sleep Score?  Naps less than 3 hours are added to the sleep duration without impacting the sleep score. A single nap in excess of 3 hours is likely to result in the last sleep metrics, both score and duration, being overwritten. 

1270461 said:

there should be a way to delete the fake naps it erroneously detects. 

That might only be necessary when naps longer than three hours are detected in error that overwrite previous sleep. Any falsely detected naps that are less than three hours are most like to be as a result of very low levels of activity that are essentially rest anyway and would positively affect Body Battery etc. Having that nap time added to overnight sleep time is not really of any consequence. 

The main problem that needs to be addressed as I see it is the false detection of naps in excess of three hours that replace sleep score and sleep duration. 

Multiple (false) naps totaling around 5 hours did not erase my night's sleep.

I've had mine register a nap while I was driving, and I don't know too many people who feel recharged after a long drive.