Sleep phases recorded properly ?

Same for me, since a couple of week, deep sleep is no longer spread throughout the night. Deep sleep si now a "big block" at the beginning of the night.... an even starts at a time where I a m not sleeping.

==> see pix attached: First one on November 12th ad the other one on December 17th. 

On December 17th data, first slot of deep sleep from 11.04pm to 11.27... I was not sleeping... just reading..

Does anyone have an explanation ? 

Thanks 

Hi, after the fix a couple of weeks ago Sleep info seems to work fine on my watch.

No explanation, but the same problem.

I am coming from Fitbit (still wearing it) and noticed a big difference between the two, especially for deep-sleep and times awake. I first thought one of the two watches was off, or the fact that Fitbit measures over-detailled was the problem. I am wearing my Fenix for almost two months now and I have no deep sleep or a short block just in the beginning off the night. For me that feels not right.

Same here. Deep Sleep Only on beginning or not at all.

Or when im drunk i have 1-2 hours: D

For me it got much better after one of the updates and after some time of using it. 

Now it looks accurate most of the nights.  Considering that you should be having this deep phase dive somewhere in the first 1/3 of your sleep and its normal to have it for 1 hour max during each night 

1

It appears that missing deep sleep might be age related. Older folk (especially males - and I'm definitely in that category) have less slow wave sleep (SWS) than younger folk. For someone around 20y that's about 18% of the night, for us older folk it could be ~3%. I understand that Garmin is working on the algorithm to ensure it picks up the limited SWS sleep that older folks do get that is currently being missed and hence reported as Deep Sleep ---.

If REM sleep is lost it might be due to the absence of sufficient HRV data so you need to ensure the watch is being worn correctly even when sleeping. I tend to loosen mine off a notch or two so knowing this I might just try leaving it a bit tighter.

And then there are the back end server issues too...