Charge 6 - sleep data inaccurate

[ElRey61]

Has anyone run into the issue in the last week or so with sleep data incorrectly recording you being awake for long stretches during the night when you are asleep? These are uninterrupted stretches of 20 to 60 minutes once or twice a night when Fitbit is recording I am awake and I am asleep. I'm on version 20001.214.24 for Fitbit Charge 6. I may have installed this software version in the last 2 weeks? Also, I have restarted the Fitbit 6 during this time but that doesn't correct the problem. Thanks! 

Moderator edit - updated subject for clarity

[MonicaBarreto]

I do have that problem, as well as the opposite. I was hooked up to a cpap and another recording device and I didn’t sleep that night yet Fitbit said I did. I was still but definitely not sleeping. And I also have the issue where it says I was awake for two hours and I wasn’t. Sucks. Data no longer accurate. 

[TheVinny]

Yes two threads on the Sense 2 board regarding same exact issue. Not only have the current sleep times been affected, but even all of my previous history was changed. About 35 minutes less across every year since 2016. It seems almost crystal clear that the default setting for all sleep times now is the 'Sensitive' setting. Even though I have the 'Normal' sleep setting box checked. I experimented one time last year and tried sensitive setting. It basically counts all rolling over and/or movements as awake time under sensitive setting. Problem is, I am almost never awake during any of that. So when I saw the difference I was kind of floored and went back to normal setting. But before doing that I checked my monthly and even yearly average and both were changed dramatically right in front of my eyes just because I guess it applies the sensitive setting on older sleep times if you click on those averages while in 'Sensitive Mode'. Fortunately when I switched back to normal all of my averages all went back to normal. It takes away about 35 minutes a night for an 8 hour sleep time when counting all movements as awake time. 

So my guess is right now everything is under sensitive mode no matter what we choose and hopefully if they fix it it will all get back to normal times both now and correct the times since this happened near the end of June. 

[ElRey61]

Interesting. Yesterday I contacted customer service and they suggested I change my sleep setting to sensitive for last night to see what happened. It appears my sleep was recorded accurately. I didn't have an issue with it changing my prior data. 

[Psashman]

Yes I’ve had same sleep tracking issue, my sleep score was in the mid 80s and 90, now I get 50s and 60s and sometimes nothing.

Spoken to the help desk and I’ve we’ve tried different things, resetting , set sleep time, set sleep to sensitive.

Nothing worked, frustrating 

[JDSmillie]

I just spent an hour on a chat with help desk, they suggested the above and wearing higher on my wrist, which is illogical since the problem is changed readings since late June. 

Google Gemini tells me Google rolled "restless" into awake, but something they did in the process changed the readings, because I've never had restless and awake times much over an hour, now I'm getting 2-3 hours awake, and light sleep, hardly any REM or deep

[Earther]

That's interesting (and amusing) that Gemini knew and could tell you that, and it does sound like the problem. If you're willing, I hope you'll send that Gemini answer to Google tech support.

Gemini is great -- much better than the AIs that get more publicity (which is good, because I don't want it ruined by people wanting to make selfies and memes and write fake novels to entertain themselves and their social media friends). It is not always right, but, in my experience of asking it quite complex questions about health, nutrients affected by dietary restrictions, plants, pet injury and decline, it has been exceptionally helpful. 

[Psashman]

Hi,
I’m also getting about 3 hours of awake which I didn’t get before.
I’ve now put my sleep settings back to normal.

Fitbit told me that if the sleep setting change and watch reset don’t work (and they haven’t), to reset back to factory settings, I’m reluctant to do this as I’ll lose all my history.

I don’t think Fitbit help desk can help, they’re grasping at straws.

Sent from my iPhone

[TheVinny]

I have three different Sense 2 watches and all three show the exact same issue. I tried each one. It's not the watches. Since the app changed all of my older sleep times (back to 2016) as well as current sleep times starting around the end of June, the problem is with how the Fitbit app interprets the data. Clearly using sensitive mode algorithms to interpret what the watches record during sleep.  Basically turning any movements now into awake/restless time. That's what sensitive mode does. Problem is my app is still on normal mode. And I usually do not wake up at all during all those times that I am now credited with being awake. It should be a simple fix. But has been happening now for almost a full month. 

[TheVinny]

That has not helped. You can find out immediately too.

1- Take a screenshot of last night's sleep times and graphs.

2- Then completely delete last night's sleep data.  

3- Then switch sleep mode on your app to sensitive.

4- And lastly add back in your exact sleep times as previously recorded and see how it matches up with the first version that you deleted. 

If anything works you can see it right away. I tried it weeks ago and not one single minute changed. 

[TheVinny]

Interesting that the last two days I cannot delete my sleep at all. It either won't delete at all and just resets to original screen which is useless, OR, will delete (and is gone) but when I go to add a new sleep session back in, it pops back in just like it was before deleting. Definitely Fitbit having some major glitches going on with the Sleep App. I have an iPhone 14 Pro and Fitbit Sense 2.

[Earther]

You won't lose your history, because it's stored on their servers (aka "in the cloud). You might have to re-do any settings you customized, but maybe not even that.

[Earther]

The people who are programming the app apparently have no awareness that everyone is "restless" at some points during sleep but they sleep through that. They might be having bad dreams or maybe really good dreams, but they're still asleep even though they seem restless.

Also, nearly all older people have to get up to go pee during the night, which we do only half awake and go right back to sleep when we're back in bed.

Maybe that's not why, but whoever approved the software update that "rolled 'restless' into "awake" -- combined them into one thing -- made a mistake. It's fixable. We just need to get them to understand the negative effect it's having on "users" (us) and to FIX IT.