11.25: Watch records sleep during watching TV in seated position, without showing it in the glances

I am trying to break down the various issues related to sleep.

Here is one that irritates me quite a bit: the watch records (fake) sleep without showing it anywhere. This is strange, because if you wake up during the night, you can see the watch is showing "sleeping" in various widgets (like stress and sleep) even if you are walking around. It also can show it during a fake nap during the day, like yesterday.

Last night, I started to watch TV around 9pm as usual. I had set my sleep period from 1am to 8am. After the movie, I took a picture of the glances. As you can see, the watch was apparently not recording sleep: the sleep glance is still reporting the fake nap detected that day with a zero score

 :

As expected, in the morning the watch reported I started to sleep at 9pm! One would rationalize that I was indeed awake, but the night experience shows that the watch does show "sleeping" when you are awake, going to the bathroom, for example, or if you activate the glances in the morning instead of browsing the morning report. Vice versa, the watch does show "sleeping" when you are actually awake when it detects a fake nap. So the real wakefulness doesn't seem to decide on whether the watch displays "sleeping".

This time I was able to correct the sleeping time and have it synced back to the watch

  • Why did you open a second thread??

    @Admin: could you close one of the two? Thanks

  • 2 different issues, 2 different threads. One issue is that fake naps replace your night of sleep and screw up your score. The other issue (this one) is that the watch doesn't show you when it is recording sleep, or sometimes, etc.

    So the situation is:

    - wakefulness detection doesn't work for certain/many users and destroy their sleep metrics, a cornestone of training readiness

    - there is no user visibility or control to sleep detection. The watch starts tracking sleep whenever it wants, hides it and you cannot reliably edit/correct the situation after the fact.

    This is a design flaw. The firstbeat algorithm is doing what it wants with no user control or validation, and the watch UI doesn't provide the hooks to get this under control.

    I am not even talking about flawed sleep phase detection, which has been documented elsewhere on the web.