Fix sleep reporting due to long awake times

[mikeulator]

I'm posting this hear because I contacted support and they wanted to do a bunch of non-related "troubleshooting" that wasn't helpful.  Hoping this gets picked up by a mod or someone who can enter it as a bug or feature request.

I use a Pixel Watch 3 to track my sleep.  Whenever I wake up in the middle of the night and am awake for a long time (not sure how long triggers it, but it's an hour or more) it often screws up the sleep reporting for the night.  This is highly annoying and not helpful for sleep tracking.  Sometimes it puts it in "other sleep", sometimes it keeps it all in one, and sometimes - like last night - it records it for the previous day!  I'm assuming because I technically woke up before midnight it puts it as part of yesterdays sleep but this is inaccurate.  I don't care about the "technical" day... for the vast majority of people their night's sleep spans two "technical" days but is still considered one sleep session/day.  So last night I fell asleep 8:55pm and woke up at 11:33pm... but was wide awake and didn't fall back asleep until 2:40AM and slept until 7:45AM.  The 8:55 to 11:33 is showing up for yesterday.  This is not helpful or accurate.  When you look sleep data from the graphs or other points of view, it looks like the night of 11/26 to 11/27 I got over 9 hours of sleep but I didn't.  It should all be counted as "last night" and if I had slept straight through it would all have counted for "today" and that's exactly how it should be even if it's broken up.

I can see this solved a few different ways.

1. Let us edit these separate sleep chunks and say what day it's attributed to.
2. Let us set the awake duration that makes the app break it up into a separate session.
3.  Let us set our "sleep day", where instead of midnight to midnight we set it from 8pm to 7:59pm, for example, and anything that falls into that time gets counted in one day.
4 Alternatively to 4, let us set our "sleep window" and that anything that falls within those hours gets counted as one session.  I think this is my preferred as it would allow naps to fall under "other" sleep.

[RiekoC]

Hello @mikeulator 

You are able to edit your sleep log, especially when it is broken up into 2 or more separate logs. This help page (<-- click) has the instructions. 

Regarding your other suggestions, you can submit those as feature requests in the Product Feedback forum (<-- click). You might want to check to see if there's already a feature request that matches or is similar to yours. I understand that the developers monitor the Product Feedback forum to see what features are being requested for potential future implementation. 

[mikeulator]

Thank you for the reply, I will definitely repost this to the Feedback Forum.  The editing of the sleep isn't a good alternative.  The only way to make it fit what I want is to extend the end time past midnight (I'm assuming) but then it's altering the end time for reporting and there will be a gap in the data.  That seems like more of a hack than a fix.

[mikeulator]

Now that I looked, that forum appears to be useless.  This was first started in 2015:  https://community.fitbit.com/t5/Product-Feedback/Merge-multiple-sleep-fragments-into-one-sleep-log-a...

And it still hasn't been implemented... and if I posted mine it would likely get moved to that thread as a duplicate.

[Rich_Laue]

It use to be that if you where awake for more than 10 minutes, your sleep was split. In response to the feedback forum, swank periods less than an hour are supposed to now merge. I can't find it joysticks to merge with longer periods of awake. Maybe the developers think the same. 

[mikeulator]

It doesn't necessarily need to merge into one continuous reporting block but it should report on the correct day.