Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Charge 3 won’t sync

Replies are disabled for this topic. Start a new one or visit our Help Center.

I have had 3 Charge 3 trackers and the latest one has done the same as the first two. After a few months the synchronising stops. Nothing will make it reconnect. 

Best Answer
0 Votes
15 REPLIES 15

Welcome to the Fitbit Community, @Mep123. I'm sorry to hear your Charge 3 stopped syncing and that nothing will make it reconnect.

 

Could you please confirm that you have followed the steps of help article: Why won't my Fitbit device sync? Please provide more information about what happens with your device when you try to sync it. 

 

Keep on visiting the forums. 

Best Answer
The time on my Fitbit goes wrong.
The steps don’t synchronise. I complete a soft reboot and there is no change.
Then I do a total reboot and lose details. When I try to reload the device, my Bluetooth connection doesn’t recognise it. I have to set up a new device in the Fitbit app. Then the devise synchronises once And then have to do it all again. This is very inconvenient. Last time I had a problem I had to send it away and when it came back it was fine for a few months. Now back to the original problem.

Sent from my iPad
Best Answer
0 Votes

I am having the exact issue. I'm only on device 2 though.. Not 3.

Best Answer
Not good eh?

Sent from my iPad
Best Answer
0 Votes
Nope.. I'm working with fitbit now. Hopefully they can find a solution!
Best Answer
0 Votes

Hi, I can confirm that I have done everything in the article. It did manage to sync once and the data appeared on my app but now it wont do it again. The time is wrong again and I dont want to have to go through the reset every day.

 

 

Best Answer

Agree. I can't get my 3 to sync. I've done everything requested in this forum so far and it's not working. 

What do I need to do?

 

 

Moderator edit: format. 

Best Answer

Same here. Doing my nut in!

New version 4 about now, so ours will keep falling until us Charge 3er's buy an upgrade!

Best Answer
0 Votes

I have the same problem.  I'm thinking if I have to buy a new one again I'm buying a galaxy watch.

Best Answer
I have to agree. I love Fitbit but that’s 3 I’ve had that have failed in months

Sent from my iPad
Best Answer
0 Votes
I gave up on the 3 and have a 4 that will not sync also.
Best Answer
0 Votes

It's an ongoing issue since the last update. Is Fitbit working on a fix? Is there a time when we can expect this to be fixed or are we better off switching to Garmin? 

 

Best Answer

I too have tried everything listed and it won't sync. And now I can't even pair it at all either. I'm on android OS

Best Answer

I have a Fitbit Charge 101. I had last used it in 2015 due to some family and health issues. I'm now ready to get back to making me healthier and am sad to find out I cannot sync this fitbit. It knew me when I installed the app again. I use Win10 and no bluetooth. It won't reset to the correct time even though I have the correct timezone set. I can't even get it to do a reset using the hold the button on the wrist device. I've followed everything in the manual and on youtube, wikihow, etc. I even removed the device from my account and reinstalled the app for Win10 three times. Now it won't add the device to my Fitbit account. The firewall is open to Fitbit. If anyone has any suggestions, I'm happy to try them. As for now, I guess I'll just do without my Fitbit. I can't even email support, they only use Twitter. I do plan to try the Chat or the phone on Monday. But I'm not hopeful they can help unless I can go back to the 2015 software.

Best Answer
0 Votes

Hello Andrea, there is clearly a significant problem with the fitbit software. You (as a company) refuse to use the Android/iPhone pairing systems for bluetooth devices. That alone is a warning sign.

 

Having to turn off the app isn't a solution. It's a sign the software isn't good enough. Having to stop Bluetooth is also unacceptable. What if other devices are using it? Then the last option is to restart the tracker - which doesn't solve the problem.

 

There's a glaring bug. Add some debugging to your code and fix the underlying problem.

Best Answer