Why does my Charge 6 not track my entire sleep even when I wear it all night? The total inaccurate.

[Ktankers]

I want to know why my sleep total on my charge 6 is not accurate even though I wear it all night. For example, last night I want to bed around 9 PM and went to sleep fairly quickly. I slept until around 12:30 PM when I got up to go to the bathroom. I went back to bed and fell asleep again fairly quickly. My Fitbit only registers the time from about 12:45 until I woke up around 6:30 AM. It does this frequently - at least 3 or 4 times a month so my data is inaccurate. I have worn a Charge Fitbit for years now and always wear it all of the time. I have never had this problem until the charge 5.  I bought a new Charge 6 a few months ago thinking that maybe my Charge 5 had a problem but the inaccurate sleep count also happens on the Charge 6.  I tried to find the chat support for the Charge 6 but all I get is a person for Aria.  Your service stinks since Google bought Fitbit.  If I can't get any help solving this problem, I will most likely not buy another Fitbit in the future even though I have bought them since they first came out. HOW DO I GET A PERSON TO HELP ME WITH THIS PROBLEM????

[Talahthas]

Welcome to the Fitbit community, @Ktankers!

Sad to hear that you're having issues tracking your sleep with your Charge 6.
To get more accurate results, I'd recommend checking if you've set up your sleep goal and your sleep schedule in your Fitbit app. To see how to do that, please have a closer look at 'How do I set or change my sleep goal in the Fitbit app?' and 'How do I set a sleep schedule in the Fitbit app?' following this link:

How do I track my sleep with my Fitbit device? 

You might also want to try if setting sleep sensitivity to sensitive will get better sleep tracking results for you.

[goldenrodfarm]

I can’t make any sense out the sleep tracking on my charge 6. For example last night I went to bed at 138am, got up briefly at 831, then slept until 10.  According to the charge 6 my sleep time didn’t start until 458 and ended at 831 with a total sleep time of 3 hours. It doesn’t allow you to add in the time from 138 to 458 where I was sleeping or the time after 832. According to Fitbit any time I get up ends the sleep. I tried sensitive mode one night and it is worse, I guess I don’t sleep at all under that mode.  They have changed something because I have had fitbits since 2014 and this problem just started with the charge 6, it has turned sleeping info into a total inaccurate useless thing on a Fitbit.  My sleep time is set from 12 to 9 and it really doesn’t seem to affect anything. How can Fitbit say I was awake from 138 to 458? Who the heck would stay in bed awake for hours?  Since I have gotten this charge 6 it seems to be failing on all the items I would use it for, steps are all messed up too. Sometimes it shows no steps at all for hours when I have been doing things during that time. One day I had 0 steps for 3 hours while I ran errands, I walked across the WM parking lot, walked all the way to the end of the store to pickup cat food, back to the cashier and back to the car, no shopping cart involved. Then walked into TSC, loaded 8 50 lb bags of grain on my grain cart, checked out, loaded them in my car and took the cart back, 0 steps occurred. Went in the grocery store to pick up just a couple things, walk from the parking lot, picked up a hand held carrier in my right hand, walked around the huge store for 25 minutes, checked out and carried my bag, in the right hand to the car, and amazingly enough this whole 3 hours Fitbit did not record one step. I am about ready to toss it, steps are way out of sync, I counted 1000 steps, and Fitbit said it was 357. And it sends only partial information to Fitbit. I have restarted to apps, deleted the connection and restored, and redownloaded the apps, but there are days when it says I only have 289 steps in MFP but 4600 in Fitbit. Or just on Sunday my steps were 6100, but only 4000 in Fitbit and there seems to be no way to correct it. Maybe I have a lemon, or maybe google is ruining them.