10-11-2018
08:25
- last edited on
10-12-2018
09:59
by
LanuzaFitbit
10-11-2018
08:25
- last edited on
10-12-2018
09:59
by
LanuzaFitbit
Been unable to synch since adding it 4 days ago
Moderator edit: Clarified subject
Answered! Go to the Best Answer.
01-24-2019 10:37
01-24-2019 10:37
Hello everyone!
I apologize for the delay in my response.
@Saint7 Glad to read that it seems to be working for you now!
@Cd19793, Thanks for sharing that information!
For everyone, let's try to restart the connection from scratch:
@KentuckyCat, It is important to mention that the Kindle Fire is not a supported device and thus we cannot guarantee that it will work correctly. My suggestion would be for you to try going through the steps in this help article with the Windows 10 device.
Feel free to reach out with any further questions.
01-24-2019 11:54
01-24-2019 11:54
Is this still an on going issue? My device has not successfully synchronized since Jan 12th. I've updated the app to current. Unable to participate with my office challenge group and missed out on a huge week of stats in last weeks challenge bumping me out of the running.
Most importantly though I'd like my device to work as it should. When can we expect a fix?
Thank you.
01-24-2019 11:55
01-24-2019 11:55
Just seeing this post. Will try and get back to the group.
01-24-2019 12:32
01-24-2019 12:32
Have tried this many times. Not working. When I called Fitbit they said they were aware of the situation and will fix it immediately. A month ago. They said the next firmware update will fix it.
When I enter the 4 digit number to pair, it says connecting... and the Fitbit icon appears on the charge3. Then the icon goes away and the battery returns on the face of the device Then Connecting... forever on the app on the phone.
01-24-2019 12:40
01-24-2019 12:40
Will we lose our data on the device if we do this?
01-24-2019 16:28
01-24-2019 16:28
I told bluetooth to forget the device and rebooted my phone (Pixel 2) then went into the app to added a new device. I received the prompt to replace my fitbit charge 3. I continue and the bluetooth search never finds my charge 3 which is plugged into the power cord with my phone right next to it.
This is super frustrating. If there are this many people having this issue we need more details please.
If it's a firmware update that's going to fix the device how are we going to be able to get the firmware updated if our phones cannot find the device.
Is there a way to get this escalated to a high priority? Please advise.
01-24-2019 16:33
01-24-2019 16:33
01-24-2019 17:06
01-24-2019 17:06
I believe the "solved" needs to be removed from this posting.
01-24-2019 17:20
01-24-2019 17:20
I just installed the Fitbit app for apple on an ipad and logged in to the fitbit app. It pulled over my charge 3 information. It was able to successfully sync all of my data back from Jan 12th. I didn't even have to pair the Charge 3 with my ipad for it to do that (as long as I manually sync) So the Charge 3 itself seems to be fine. This seems to be an Android / Android App issue?
01-24-2019 17:38
01-24-2019 17:38
I tried syncing on my iPhone - no luck. I got to the same point. I entered the 4 digit code and then it never connected. I also tried syncing using my computer - same thing.
01-24-2019 18:15
01-24-2019 18:15
@mabbit wrote:I tried syncing on my iPhone - no luck. I got to the same point. I entered the 4 digit code and then it never connected. I also tried syncing using my computer - same thing.
If your phone is on the same home network as your computer try to disable WiFi on the phone and use wireless data. This will change your IP address to what your carrier gives you, and the Fitbit cloud server cloudflare.net may let it pass instead of blocking.
01-25-2019 10:53
01-25-2019 10:53
Hello @ClimbGuy, @mabbit, @Saint7 and @SunsetRunner.
As it has been mentioned by @SunsetRunner, be sure to try using a different internet connection to try and run the setup process.
Please know that we’re aware of it and are working to identify a resolution as quickly as possible.
We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track.
Please let us know if there's anything we can do to assist you in the meantime.
01-25-2019 11:01
01-25-2019 11:01
My Charge2 just arrived! Set it up in about 2 minutes...NO ISSUES!! Yay! It synced to my Kindle without having to do anything. I know I was told a Kindle is not an approved device but I have used my old Charge with my Kindle for years and now the Charge 2 has no problems with it.
Fitbit needs to fix the C3 issues and quit telling us to jump through hoops on our end to fix what is an obvious issue on their end. All these syncing issues have made all of us lose confidence in what was a great product.
01-25-2019 11:23
01-25-2019 11:23
01-25-2019 12:53
01-25-2019 12:53
I also cannot get my android (Samsung Galaxy 😎 to Bluetooth pair with my charge 3, after having deleted the pairing in Bluetooth settings as part of my troubleshooting/recovery efforts. if I uninstall and reinstall Fitbit, Fitbit prompts me to pair, but nothing ever happens. notifications and other benefits of pairing are lost.
on the syncing front, my charge 3 seems to be succeeding a bit more often now, usually the second or third try after successfully syncing my charge 2.
01-25-2019 13:13
01-25-2019 13:13
I should add that I am afraid to try removing the charge 3 from my profile and then re-add it with setup procedure, for fear that the setup will fail and I will be worse off than I am now.
01-25-2019 13:19
01-25-2019 13:19
That's my problem. I removed the device and now I can't add it back on. It gets stuck in the pairing process. I would hold off on that if I were you
01-25-2019 13:21
01-25-2019 13:21
I tried using cellular data instead of Wi-Fi and it didn't make a difference. It still got stuck after I entered the 4 digit code.
01-25-2019 19:23
01-25-2019 19:23
Cellular, wifi at home, wifi at work. Makes no difference for me. Still won't pair back up.
01-27-2019 16:51
01-27-2019 16:51
@CinDB Thank you. I am glad I saved your post before it is deleted by a moderator.