Sleep stage reporting errors since June 24, 2025

[MBO49]

Hello Fitbit Community,

Like many of you, I have found my awake time reporting to be 1-2 hours longer than previously, ever since about June 24th 2025.

To get around this apparent change in the algorithm, I just delete the sleep session and then manually log it back in, using the correct start and stop times.

For those time-points, I either use the times that had been automatically  recorded, or my own known time-points, if more accurate.

The result (so far), is that my recorded & reported sleep durations are much closer (if not spot on) to what they had been prior to the presumed algorithm update in the 3rd week of June 2025 that now merges restless time into awake time, greatly exaggerating awake time.

Hope this helps.

[TomLee1]

I’ve noticed the same thing recently — the sleep algorithm seems to be merging restless minutes into awake time, which definitely makes the reports feel less accurate. Your workaround of manually re-logging the sessions is smart, and I’ve also seen some users mention that turning the device off/on before bedtime sometimes helps reset the detection a bit. Hopefully Fitbit will fine-tune this in an upcoming update so we don’t have to do so much manual correction. By the way, if you ever need help clearing out space at home, you might find a reliable Junk Removal Service really useful.

[kemberly1]

Yes, I’ve been running into the same issue — since late June my awake time looks inflated by at least an hour or two compared to before. It really does feel like the algorithm is classifying restless time as fully awake. For now, I’m also doing what you suggested: either deleting and re-logging the session manually or relying on my own known sleep/wake times. It’s not ideal, but at least it makes the data more realistic. Some people in the community have suggested rebooting the device before bed, which sometimes seems to help with cleaner tracking  click here  Fingers crossed Fitbit rolls out a fix soon, because the previous reports were definitely more accurate.

[Kim-J]

I’ve also been seeing the sleep time discrepancy. Today I tried deleting and manually adding my sleep using the same times that my Fitbit had used and lo and behold I miraculously gained almost 90 minutes of asleep time.

I’ve also noticed that in an increasing number of cases my Fitbit is incorrectly choosing my start and end sleep times, e.g., it says my sleep ended at 2 am when it ended at 6 am. I think this is also related to the algorithm change, as it has decided that restless = awake. I have been manually correcting the start/end times when my Fitbit gets it wrong.

[MBO49]

Hi Kim-J & Fitbit friends,

Here’s a new curiosity:  I manually logged my sleep from 11:45 PM on Sept 23, 2025 to 7:45 AN on Sept 24, 2025.

8 hours of elapsed time in bed, of which the sleep stages timelines showed 7 hours & 30 min of sleep, the other 30 min being divided between awake and restless, which is about right for me, prior to June 24, 2025, that is…

But oddly, the sleep hours dial icon with the moon inside the circular dial shows 0 minutes of sleep.

And when I go back to the Edit or Delete Sleep screen, it shows -1 hour 40 minutes.

That’s minus 1:40 of sleep, presumably an algorithmic glitch triggered by my sleep starting on 1 date and ending on another date.

i tried re-deleting & re-entering the correct dates & times, but still the same results.

Nothing to be done at this point, but just a disconnect within the Fitbit sleep program displays.

Sleep well, everyone, despite this ongoing sleep-capture issue.

Best,

Mark

PS:  another oddity is that this message was rejected because it contains the following characters typed in symbols:  twenty-three dash twenty-five, as part of the dates mentioned above (which I then had to spell out).

Here is Fitbit’s advisory message (with the offending characters written out, to prevent another rejection:

The message body contains “twenty-three hyphen twenty-five”, which is not permitted in this community. Please remove this content before sending your post.

Strange to me that a data-driven app would block digital representations of dates…?!

[pierrecasper]

I’ve been seeing the same issue lately — my awake time has increased noticeably since around late June. It really does seem like the algorithm started counting restless moments as fully awake periods. Rebooting the device before sleep and syncing it right after waking up helped a bit for me.

While looking into this, I also started reorganizing my sleep setup and overall bedroom environment  this site had some helpful inspiration on optimizing window and door setups for better insulation and light control. Small adjustments there actually made my sleep tracking data a bit more consistent. Hopefully Fitbit patches the algorithm soon!

[pierrecasper]

While looking into this, I also started reorganizing my sleep setup and overall bedroom environment  this site had some helpful inspiration on optimizing window and door setups for better insulation and light control. Small adjustments there actually made my sleep tracking data a bit more consistent. Hopefully Fitbit patches the algorithm soon!