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

Multiple sleep periods

Seems to be a lot of evidence that Garmin does not want to implement this feature for some reason. For example, they recently added REM functionality, but it still measures only one sleep period per day. I find this especially mystifying in the context of a company with aviation pretensions, since pilots often have to sleep on erratic schedules. Also internationally questionable when you consider any country with a traditional siesta or daytime nap. In my own case, I think the broken sleep patterns are mostly a function of aging, but I've also noticed that there seems to be a lot of that going around.

To recap, the device should measure several sleep periods per day. My single largest annoyance with the device, and my dissatisfaction is growing over time.
  • Why the belated notification about this comment? For what it is worth, much to my surprise, I'm still using the Garmin device and the sleep data is still weird and, I am convinced, inaccurate.

  • Why the belated notification about this comment?

    I suspect someone upvoted or "liked" your post.

  • I'm a bimodal sleeper who also uses daytime naps when my schedule allows. I know of many of my sporting colleagues who sleep similarly. For us, single iterations of 'Bed' and 'Wake' times are neither use nor ornament.

    The continuing omission of multiple sleep periods makes a mockery of Garmin's performance management software suite, and damages the company's reputation. For that reason alone, Garmin marketing needs to get a hold of this requirement and drive the techies to a solution.

    A simple short term option would be to allow manual input of secondary sleep periods rather than just a single start / end point.

  • I just noticed that my body battery calculation is always completely off when having more than one sleep period a day. The Fenix 6 appears to still omit "smaller" sleep periods entirely. I have filed a feature request, but this is a major oversight on Garmin's part and should indeed be considered an errror/bug and not just the lack of a feature.