You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently deep sleep in the beginning after that permanent light sleep. There are probably more different detections by the band
maybe need to look at HR measuring if this is crucial for detecting sleep stages so we have reliable data Improvements to Heartrate #2
every 2nd HR is missing? why is there an extra sample just for the hr?
Targets:
fix deep and light sleep detection since this is actually out of line
try to detect REM sleep aka light sleep with some activity or higher HR (little below base HR) + some activity at the end which will then fall off into light sleep (where is the ideal time for waking up before getting back to deep sleep)
Light Sleep 1 -> Light Sleep 2 -> Deep Sleep 3 -> Deep Sleep 4 -> Deep Sleep 3 -> Light Sleep 2 -> Light Sleep 1 -> REM
Light Sleep (1)
Light Sleep (2)
Deep Sleep (3)
Light Sleep (2)
Light Sleep (1)
REM (0 / 1)
Light Sleep (1)
Light Sleep (2)
back to Deep Sleep (3)
repeat at 4.
REM State could be falsely detected with being awake, REM is actually in the light sleep detection but should not be interrupted. You will move around a bit in the end of the REM stage which could be used as indicator for a smart alarm.
Walking
1
16 - light walking
17 - bit flip with 1
26 -> rare
Running
50 -> rare
66 - > rare
82 -> start/end
98 ???
Sleeping
96-127
0110 0000 - 0111 1111
28 -> wake up ???
105 -> wake up ???
106 -> fall asleep ???
108 -> wake up ?? 112 -> sleep, raw_intensity =0 - after 10 minutes start sleep state
121 -> sleep, raw_intensity > 20 - start deep sleep ? 96 + 80 after - state changed after deep sleep? - some activity is starting here - after some sleep - activity detected - maybe state change into light sleep
122 -> sleep, raw_intensity =<20 - after 121 and some more activity - very often just intensity of 20 - maybe state change into deep sleep
123 -> fall asleep - deep sleep in gb after that after 10 minutes of 112
124 -> wake up - stop tracking in gb - first steps after sleep state
80 - ~~could be REM while sleeping (activity) - hmm no REM no activity at all ~~ - alternative for 112 while sleeping - 111 = 112 - 80 = 101 - probably bit flipping there ???
Immobile/Siting
80 ???
89 - after 121 state changed some activity - after that 80 and no activity - could be REM / REM Ending - Another bit flip
90 - sit down
96 - standing up
91 -> rare - start sleep state in GB
99 -> rare ???
0111 0100 - wake up
0111 0000 - fall sleep
definitely must use values bitwise
definitely no native tracking of light and deep sleep
The text was updated successfully, but these errors were encountered:
Dikay900
changed the title
Improvements to sleep detecting needed
Improvements to sleep detection
Jul 27, 2018
Targets:
Light Sleep 1 -> Light Sleep 2 -> Deep Sleep 3 -> Deep Sleep 4 -> Deep Sleep 3 -> Light Sleep 2 -> Light Sleep 1 -> REM
REM State could be falsely detected with being awake, REM is actually in the light sleep detection but should not be interrupted. You will move around a bit in the end of the REM stage which could be used as indicator for a smart alarm.
Walking
1
16 - light walking
17 - bit flip with 1
26 -> rare
Running
50 -> rare
66 - > rare
82 -> start/end
98 ???
Sleeping
96-127
0110 0000 - 0111 1111
28 -> wake up ???
105 -> wake up ???
106 -> fall asleep ???
108 -> wake up ??
112 -> sleep, raw_intensity =0 - after 10 minutes start sleep state
121 -> sleep, raw_intensity > 20 -
start deep sleep ? 96 + 80 after - state changed after deep sleep? - some activity is starting here - after some sleep - activity detected - maybe state change into light sleep122 -> sleep, raw_intensity =<20 - after 121 and some more activity - very often just intensity of 20 -
maybe state change into deep sleep123 -> fall asleep -
deep sleep in gb after that after 10 minutes of 112124 -> wake up - stop tracking in gb - first steps after sleep state
80 - ~~could be REM while sleeping (activity) - hmm no REM no activity at all ~~ - alternative for 112 while sleeping - 111 = 112 - 80 = 101 - probably bit flipping there ???
Immobile/Siting
80 ???
89 - after 121 state changed some activity - after that 80 and no activity - could be REM / REM Ending - Another bit flip
90 - sit down
96 - standing up
91 -> rare - start sleep state in GB
99 -> rare ???
0111 0100 - wake up
0111 0000 - fall sleep
definitely must use values bitwise
definitely no native tracking of light and deep sleep
The text was updated successfully, but these errors were encountered: