Charge 3 not tracking sleep

[Jopw]

Bought my Fitbit Charge 3 on Saturday. Tracked my sleep first night, hasn’t since for last 3 nights. Have to keep putting it on charger and restarting. Few hours later it appears on watch and phone. Can’t keep doing this! Any ideas?

Moderator edit: format

[EthyWest]

I’ve tried all this but it’s not working. Is Fitbit going to take more responsibility for this issue and actually offer an update that works. I’ve had this charge 3 for a week and it’s only tracked sleep once. I’m very disappointed in this product and would like a good and final resolution ASAP! 

[Lymmeln]

After the last Fitbit update with new firmware in Charge3 & Fitbit app it started to show som sleepdata but it is very inaccurate it swings between 30min to -8h in t weeks roll the Dice

[Grenol]

Good luck, don't hold your breath 

[paulwilj]

Save the frustration and ship it back now for refund. That is what I did 2
months ago. If everyone did this, money talks!

[Grenol]

Word!!!!

[Oceanpixie]

It’s so easy! Lol! 

[Oceanpixie]

It’s so easy! Just: step 1 of 39

[Oceanpixie]

Good for you! My charge 2 worked like a dream. Not waterproof but I can forfeit that. It is smashed and still worked like a dream!

[tangerinedogs]

My Charge 3 was very rarely tracking sleep. I tried everything suggested but nothing helped. 

It has now tracked regularly for the past month. Unfortunately, I can’t provide any helpful suggestions because I had given up even trying to get it to work.

Strangely, it started tracking in the first day of a family holiday to Tenerife. I can’t imagine there is a connection, and I’m not suggesting that as a solution (although it was a great holiday), but  the tracking did just kick in after months of frustration 

[Lymmeln]

I think you just spotted the normal erratic behaviour of Fitbit , let's hope it continue to work for you

😉

[WolfsongCA]

A suggestion from FitBit to log sleep manually is NOT an acceptable answer.  No one buys a FitBit to log their data manually.  FIX THIS MESS!  (I bought 5 at xmas for my 3 kids, son-in-law, and daughter-in-law.  2 have failed and had to be exchanged.  RIDICULOUS!)

[WolfsongCA]

How in hell do you mark an issue "solved" when there are 14 pages of comments indicating it is NOT solved--plus another thread with 33 pages that was closed, also claiming to be solved, while 33 pages of comments declare it most certainly is NOT.  Clearly this is a known problem with the Charge 3, and FitBit has no intention of standing behind its product.  If you can't make the Charge 3 work, then give us all the next level up tracker in exchange.  This is unacceptable.

[Lymmeln]

Yes, if Fitbit can't fix the FB3  they should give us the next level up tracker in exchange it is a shame that they not even comment/admit the problems, I got data between 0 to 9 hours and I recently read a article  about that Fitbit i s making a lot of money on their products... no wonder,  making erratic  products without replacement program and no comments from the Company wont make any one happy 

//L

[Plap17]

Just when I thought!  A week ago, I had two accurate nights of sleep data. So exciting (sarcastic). The last two nights, both: two separate logs split randomly in the middle of the night. The later half of the night being a corrupted read. I was able to go in and delete corrupted, and recover full read in first. Hope that makes sense. 

Agree this cannot possibly be marked 'solved'.

[SueMug]

Still only getting 2-3 hour readings

[Lymmeln]

I would like to know on what basis you can mark this Solved??!!   I can for sure tell you it isn't

It's as erratic it can be, ant right now it's just a plastic watch

[Opps]

Info to track sleep is rather stupid it offers no constructive solution. 

[Lymmeln]

Now I found another funny behaviour...I got on the spinning bike watt cycle, the watch displayed 171bpm and when I sync FB3 with Fitbit app I got 141bpm.. unbelievable pice of accuracy

After restarting the Fitbit app i got 166 bpm

[Lymmeln]

I restarted Fitbit app and got 166 BPM, do we see a sync problem......

[NickeyBaySide]

Syncing it was the fix thanks