This has always been a big issue on my previous VA HR and I was hoping it would be better on the FR645M. However the last 2 nights the watch/GC failed to detect sleep start properly. I don’t understand how GC can think my sleep has started when there is still so much movement? If you look at the 2 graphs attached, wouldn’t it be more logical to detect sleep start 0.5 to 1 hour later? My sleep time setting is between 0:00 and 7:00. ciq.forums.garmin.com/.../1377460.jpgciq.forums.garmin.com/.../1377461.jpg
My issue is not HOW and IF to interpret the sleep data itself, but how Garmin detects sleep start. For some people it does seem to work, and not for others. But looking at it in a very simplistic way, if you look at movement and HR data, how can Garmin say sleep starts when there is still so much movement and a certain (higher) HR level?
Try editing the sleep start and end times for a few days on your data (three vertical dots in top right of your screenshot) to match your movement pattern and see if it gets better. After doing this, mine seemed to stop detecting getting up in the middle of the night as '3 hours sleep last night'.
Thanks for all the feedback on this. 2 days ago I corrected both the sleep times of the 2 nights I earlier posted here and the last 2 nights sleep start detection was correct. So, maybe you indeed have to ‘teach’ Garmin how to detect sleep start properly.
For me though it doesn't tell me anything other than I get 7 hours sleep which I know and what I aim for.
This highlights 2 things I dislike about Garmin sleep tracking: - it really only tells you how long you were lying down - The goal of 8 hours sleep / night is entirely arbitrary.
This could be solved by: - allowing users to set movement thresholds to count time in light sleep vs. awake and deep vs. light sleep. - allowing users to set their own sleep goals
