Time To Fall Asleep totally wrong
closed
J
Jonathan
The estimated sleep latency is way too high for me. I think this is because I like to read a bit in bed before going to sleep. The Apple Watch then creates a shorter "in-bed segment" for the reading time and a longer for the time I actually spent trying to sleep. Apple Health (and also Bevel) filter this out correctly when visualising the sleep, but Bevel does not account for this when calculating sleep latency.
Grey
closed
Grey
under review
Grey
Thanks for the feedback, Jonathan. Unfortunately, there is no way to tell which in-bed segment is when you're trying to fall asleep. The best we can do is to use the time from the first in-bed segment to the first asleep segment.
I understand this is inaccurate for some users and am contemplating removing this feature completely. That said, it is useful to see when it does work. I'll leave this ticket open to see what others think.
Dylan
Grey is there a way to cross reference that with time asleep to find the closest one to when sleep time is?
Grey
Dylan: That's a possible improvement but you're still going to run into the same issue since the in-bed segment could be 10 minutes long or an hour long.
J
Jonathan
Grey Ah I think I understand the problem... an algorithm change that works for me reading in bed would give wrong data to the person lying there and trying to sleep 🤔
It also explains why the metric in Apple Health "time in bed" tends to be bonkers. If you ask me I think I would indeed remove it. Or you ask in some setup if people tend to spend time in bed before actually trying to sleep and adjust the algorithm accordingly in this case, somewhat in line of what Dylan suggested.
Grey
Jonathan: That makes sense. We have a new feature coming soon that will solve this issue. I'll close out this ticket for now.