graphs awake and sleep time simultaneously.

[john-is-my-name]

The image above is a typical sleep graph. Note that there four 'humps' where I was awake for a few minutes at night. I did a mouse-over for the widest one that was 8 minutes in duration. If you add up these humps, the total would be about 15 minutes.  Note that I am getting awake 'dots' of a minute in duration AT THE SAME TIME that I am in light sleep. As being awake and asleep are mutually exclusive states, I am surprised that the FitBit algorithm graphs awake and sleep time simultaneously.  The data would be meaningful if these dots of awake time cold be removed and the sleep time allocated to 'light sleep'. 

[Rich_Laue]

The little red dots are very short periods of time that Fitbit considered you being awake. A period of time so short that the break in the blue is unpercievable 

[john-is-my-name]

Hi Rich; I consider your analysis to be correct! Fitbit's compromise is to have the user being both asleep and awake at the same time.  My contention is that if there is continuity to my light sleep, FitBit's algorithm should consider this to be an anomality that is below a threshold of being considered awake and therefore allocate the time to my sleep time and not awake time.    FitBit already does this for REM and deep sleep. 

I find a useful measurement to add-up my 'humps' of awake time and divide this by my total  (intent to) sleep time.  The result gives by a percentage of how efficient my sleep time is.