07-10-2017
20:13
- last edited on
07-14-2017
05:17
by
MarreFitbit
07-10-2017
20:13
- last edited on
07-14-2017
05:17
by
MarreFitbit
My Fitbit 1 just quit syncing. How do I get it to start syncing again?
Moderator edit: updated subject for clarity
07-11-2017 01:59
07-11-2017 01:59
I would try restarting your phone and then restarting your fitbit using this procedure:
https://help.fitbit.com/articles/en_US/Help_article/1186/
Give this a few tries as it doesn't always work. If it still won't sync after that then there are some more ideas to try in this help file:
07-11-2017 14:11 - edited 07-11-2017 14:16
07-11-2017 14:11 - edited 07-11-2017 14:16
My fitbit has stopped syncing and now won't do anything. Im gutted have loved using it. What can i do?
You can see my progress and how much i use on my data
Please you can help Rachel
07-11-2017 14:13
07-11-2017 14:13
Stopped working please help rachel
07-11-2017 14:15
07-11-2017 14:15
I gutted stopped syncing i use the one all the time. Please help. You can see on my data the amount i use it i miss it and am quit annoyed it has just stopped
Rachel turner
07-12-2017 00:06
07-12-2017 00:06
@Rachelturner Have you tried the multiple restarts and troubleshooting steps listed in my post above?
07-17-2017 23:36
07-17-2017 23:36
It appears we are having a return of the sync problem that visited us several months back.
It's not your Fitbit, folks, it's the software. My One has not sync'd for several days, now. Search the message boards and you will find a very, very, very long thread about this issue and that it is not YOUR problem, it's the website's problem, or more technically, the Fitbit Connect software's problem.
07-19-2017 22:42
07-19-2017 22:42
I wish I had known it was the website problem before i deleted my device from my account. Now I can't add it back in on either my phone or my computer. It still tracks my data on the device, but syncs to nothing. Sigh.
07-20-2017 05:04
07-20-2017 05:04
Since everybody, including me, stopped working at the same time, don't you think this might have been a software update issue?