Charge 6 not tracking sleep

[Ms_Emzie]

My main reason for buying and using my Fitbit was the sleep tracker and I’ve been very content with it so far — until yesterday morning when I noticed suddenly hadn’t tracked my sleep. I thought it was a glitch at first, but now this morning it has again failed to track any sleep at all during the night.

I haven’t changed any settings or done anything else different than usual, neither on the device nor in the iOS app.

What is wrong and how do I fix it?

Moderator edit: edited title to clarity.

[CrisVillaFitbit]

Hello and welcome to the community, @Ms_Emzie!

Thanks for letting me know about this situation in regards to your sleep tracking using your Charge 6.

I recommend you to check this article, in the part 'Why don't I see sleep stages today?' for you to have some tips and be able to double check everything is ok to track your sleep.

Let me know how it goes once you've done it.

[Edword]

Do you mean the sleep data is not showing in the watch or the app. Mine often does not show in the watch but it still shows in the app. I got mine on 12 of may and mostly it does not show in the watch but does on the app. If its not fully showing on the app you could turn the sensitively up in setting. It could also be the seniors need wiped if suncrème or something gets under it

[CrisVillaFitbit]

Hello and welcome back to the community, @Edword.

Thanks for the insight and for the suggested solution. I also recommend you to check the article I attached in my previous comment, you can try it out too for this situation to improve.

[PatNYC]

I have had Fitbit for the past 12 years. Always very happy about the logs. With the new app i have 3 main problems:

1. Sleep is detected as fragmented  even though sleep occurred in one session

2. Inaccurate detection of sleep stages

3. Unable to edit and combine the perceived fragments, which in reality reflect short awake periods (which qere previoisly accurately assessed).

What is fitbit doing to fix the issue?

[RiekoC · Accepted solution]

Hello @PatNYC 

Every now & then, my sleep log isn't correctly tracked in the Fitbit app. Like you, it will sometimes break my sleep into 2 sessions. When this happens, I take note of my sleep start & wake times. Then delete one of the sleep logs and edit the remaining log with the correct sleep start or end time. It would take some time for the app to update my sleep stages and score, around an hour or so. 

However, when this happened yesterday, my sleep stages didn't update and I only had basic sleep info. I had to delete the edited sleep log, then enter my sleep manually into the app. After I did this, my sleep stage graph appeared along with the rest of the sleep data.

Here are the steps to edit the sleep log when you have more than 1 sleep session

• Tap on the Sleep duration tile on the Today page of the Fitbit app
• Tap on the 3 dots in the upper right of the sleep page
• Tap on Delete sleep
• On the next page, select one of the sleep logs to delete. Confirm deletion
• Tap on the 3 dots in the upper right of the sleep page
• Tap on Edit sleep
• Tap on Edit. Update the sleep start or end time. Tap Save in the upper right

If the sleep stage graph doesn't appear after an hour or so,

• Delete the sleep log using the instructions above
• Tap on the "+ Log sleep" icon in the bottom right of the Sleep page
• Enter your sleep start & wake time. Tap Save in the upper right

[PatNYC]

Thank you so much !!! It worked

[RiekoC]

You're welcome @PatNYC . Glad the steps helped you.

Please let us know if there's any other assistance that we can provide.

[Paulinks]

This does not always work. Sometimes after I delete one of the sleep logs, usually the shorter one, then go back and edit the remaining log, I am told that it can't be edited because data has already been recorded for that period. I have also tried deleting both logs and manually entering the sleep session. Sometimes that works, sometimes not. THIS NEVER HAPPENED WITH THE OLD APP.

[katgogo]

That did NOT work for me either on brand new Charge 6! Sleep info is the primary function I bought this when my Charge 5 broke and always reported sleep data on it. So, what now???

[RiekoC]

Hello @katgogo 

Since your Charge 6 has a faulty band clip, you should return the device for a replacement if you are still within the return window. You don't want to lose your Charge 6 because the strap won't stay connected.

[Paulinks]

As of October 22, 2024, this STILL does not work. Google needs to pay attention.

[KATWILL63]

That does not work because when you try to log it, it says it’s already logged after an update. This happens about once a month. It’s frustrating even if you try to hand log it in. It says it’s it cannot be logged because it’s already logged and it’s not showing It’s not like the old Fitbit app where you could go in and fix it now it’s Google where you can’t do squat

[KATWILL63]

The problem is always blamed on the tracker or the phone. It was because of an update that the sleep was not tracked once again I’m trying to manually log it and it says it cannot log it because it’s already logged, which is not again the tracker is charged and cleaned and well taken care of and always updated and my phone’s always updated

[RiekoC]

Hello @KATWILL63 

Although I'm not sure that this will work, you can try clearing the cache for the Fitbit app on your phone/tablet. Then, force stop the app and re-open. That might clear out whatever is causing the app to indicate that you already have a sleep log.

If that doesn't work, you can try clearing the storage for the Fitbit app your phone/tablet. Then, force stop the app and re-open. You'll need to log back into the app after you do this.

Please let us know if this worked for you.

[Paulinks]

Sounds good. I'll try to remember this next time it happens. Thank you.

[KATWILL63]

Did all that took out the app reinstalled the app sign back in took out the Bluetooth three started my phone restarted the watch whenever it updates sometimes it pulls this it’s upsetting but maybe I have to get something else if it keeps happening in this frequently thanks for the tips