Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with sleep algorithm needs fixing

6446252
over 1 year ago

Mostly, I like the current sleep algorithm. It identifies phases plausibly, if with some misidentification. But last night it had a much more serious failure that needs rectification.

Last night, I got a few hour sleep before about 3:30, but woke up and thought of some ideas relevant to my work. So I got my Chromebook out and spent perhaps 30 minutes writing them down for latter reference. I then got several hours more sleep, eventually getting up after 10.

Garmin missed ALL of the sleep after 3:26. Presumably the algorithms simply don't allow for sleep that is broken up by a substantial period of activity, so counted 3:26 as the absolute end of my sleep.

I have no doubt that this can be fixed, to avoid missing logging several hours of sleep when it happens 

  • 0 over 1 year ago

    That feature failure has been going on for at least a couple of years.

    I sometimes wake up in the milddle of the night and can't go back to sleep, so I do 10-15 minutes on the treadmill or excerise bike, then I can go back to sleep. I just edit the sleep time in the morning and adjust the wake time. But it's not really that important that I capture those numbers every day. In the grand scheme of things it's a speck of sand on a beach.

    If it bothers you, report it to support. Of course you may not see anything happen in a reasonable time frame.