Inaccurate sleep on Charge 6

[Copland]

Did something change with the sleep tracking on the Charge 6 on or about 23 June 2025.  While I used to have sleep scores consistently above 80 with 8 hours sleep, since that date my scores are between 66 and 74 and it shows sleep times between 6 or 7 hours every day (I would occasionally get these sort of sleep scores previously but only if i had a bad nights sleep).  Personally, I have not noticed any change in my actual sleep patterns.  I have reinstalled my app and restarted my Fitbit and Bluetooth.  I have not changed the way I sleep or how I wear the Fitbit. Is there a setting I need to change?  Or was there an update that changed the way sleep scores are calculated. Thx

Moderator edit: edited title to clarity.

[PghPatti]

👍
Sent from my iPhone

[Copland]

I spoke to Fitbit Support again regarding the inaccurate sleep issues on the charge 6 – they could not help but the Fitbit Customer Care Team advised by email afterwards…..Thanks for letting us know about this issue. We’re aware of it and are working to identify a resolution as quickly as possible.

Could our community leaders @StephanieFitbit  @CrisVillaFitbit  or @JuanFitbit confirm this and perhaps elaborate further.

[Ben735]

@Copland (Base Runner)  Thank you for staying on this.  I hope FitBit fixes it.   

[Earther]

Thanks very much for your persistence and telling us that they actually know about it and are working on it. Yay!

Moderator Edit: Formatting.

[Lorraine_2017]

Same here... i do not like the new scores. Please Fitbit go back. When you look at your score, it is really depressing.  

[Matt3055]

These changes are terrible. Said I was awake for three hours the other night. I don't believe they are working on fixing anything. Everything Google touches gets ruined. If they really cared about their fitbit users, they would return the sleep algorithm to its previous, more accurate version. If they are trying to push fitbit users to go to Google products, I  can guarantee i won't be one of them. 

[Earther]

re: "Everything Google touches gets ruined."

I disagree. Gemini, their AI (not just the browser-mode option) outranks all others in recent tests with results published in the NY Times or Washington Post. Anthropic's Claude is the contender, not ChatGPT. Their security and spam filtering are excellent, their routers are good and even attractive designs. They constantly innovate, and you can actually reach a real person for tech support in the rare instances that you need help.

I've had Fitbits since the Flex (2013). Google has definitely improved it since they bought Fitbit (which was in decline).

I intensely dislike their push to move everyone to watches, but that's no different from the push to move everyone to apps rather than web access using a real computer. I tried a watch, another brand, and do not like them at all. So, like others here, I hope they'll at least continue to update and support their two best-selling Fitbit models: Inspire (best-ever model) and Charge. I'll bet they'll announce a Charge 7 by October 2025, latest. If that doesn't happen, then....

[Gaye]

It’s ridiculous what they’ve done!  I was wondering what happened because I know my sleep is the same as it’s always been.  Now I am consistently in the “poor” range but I know that is not true.  Why do they “fix” something that is not broken???  It was fine before.  Some engineer needed something to do at work so they let them screw up a program that was working fine.  🤬

--------

Last night, it said I slept 5 hours and 58 minutes - sleep score 66!!!  Said I was awake for 3 hr and 34 minutes - rem sleep was 42 minutes and deep sleep was 48 minutes.  No way!   But I know for a fact that this is bogus and not correct.  🫤

--------

Moderator edit - updated subject for clarity

[Matt3055]

Absolutely correct.

[raleighfit]

same here

[adrenalinjunkie]

I have the opposite problem to the op.  My weekly report says I regularly sleep over 7 hrs when in fact is is usually around 6 hours or less (I can't remember the last time I actually slept for 7 hours!).  Every evening when I sync my watch before sleeping I delete the sleeps it thinks I've had, when I've been watching tv, or I've been on the internet, or at the cinema.  In the mornings it has often added them back in again, so I delete them again, and/or edit my sleep start and end times, but the weekly report seems to still count all the deleted sleeps - it's the only way it could ever get to over 7 hours.

I will try changing the sleep sensitivity setting to normal, but certainly deleting or editing sleep does not seem to work.

[bookbrowser56]

I've noticed this on my Charge 5. I used to get anywhere between 65 and 85 as a sleep score. SAME Charge 5 NOW reporting 3-4 hours per night, since their unannounced tweek. 

---

Cris, just FYI, my Sleep setting is 'Normal' and my recoded sleep times are wildly inaccurate  .. these days.

[Matt3055]

The other night it showed me "awake" for 3 hours!

[raleighfit]

My sleep is doing much better. I restart my Charge 6 every night and get my
watch snug 2 inches up from my wrist

*Bob Metz*

[Gomers]

You just need to look at the sleep duration on the weekly email to know
it’s a load of rubbish. The app says I get 7 hours sleep most nights, in
the email it is always over 9 hours 🤷‍:female_sign:

[Copland]

It's hard to tell what is happening until the community leaders make some sort of comment - I mean is Fitbit happy with the changes the way they are or are they trying to fix it in the background without acknowledging there is any problem. Or do they just hope it will go away certainly StefanieFitbit and Fitbit seem to be putting their resources and expertise into the ASK COACH feature - can't wait for that!

[raleighfit]

I am getting a lot of wake time that I don't recall being awake. There is a fine line between Being Awake and Being in a Light Sleep.

[fkarm]

When I search the community for sleep issues, I see comments going back years, with the same problem with the same outcome. It’s a shame that no one takes pride in their merchandise anymore.  I too have tried all of the stated fixes to no avail. A big BOO👎