09-01-2025
02:15
- last edited
Monday
by
MarioSFitbit
09-01-2025
02:15
- last edited
Monday
by
MarioSFitbit
Has anyone else noticed the "Time Asleep" element of the total sleep score is making no sense these days?
Last night my Charge 6 recorded 7 hours and 46 minutes of sleep, and gave me a Time Asleep score of 32 out of 50. Total Sleep Score was 76, Poor.
The night before, the same Fitbit Charge 6 recorded only 2 hours and 55 minutes of sleep and gave me a "Time Asleep score of 38 out of 50. Total Sleep Score was 81, Good!
Leaving aside the queston of whether my Fitbit is accurately recording my sleep this scoring is wild. What is going on?
Btw I'm quite sure that lately my Fitbit is NOT accurately recoding when I am asleep - I would definitely notice if I had stayed awake all night until 4.30 am as Fitbit suggested on the night it recorded only 2 hours and 55 minutes of sleep.
Charge 6, System: 66.20001.214.24, syncing with Samsung Galaxy S10e, Android 12
Moderator edit - updated subject for clarity
yesterday
yesterday
Hello @curiousmind1
I've seen other users reporting a similar issue with their Fitbits not correctly tracking their start sleep time. I'm not sure if this is related to the recent change in the Fitbit sleep algorithm.
For now, please submit this issue using the Feedback option in the Fitbit app:
The feedback reports are received by the team for review.
Rieko | N California USA MBG PE