05-27-2020
14:30
- last edited on
05-28-2020
09:25
by
JuanJoFitbit
05-27-2020
14:30
- last edited on
05-28-2020
09:25
by
JuanJoFitbit
I tried to Sync a few times today and it never worked. I tried under Sync now as well as in Today by holding and pulling page down as always.
I switched the bluetooth on and off a few times, then unpaired but now it won't let me pair/sync again
Thanks
Moderator edit: updated subject for clarity
05-28-2020 09:23
05-28-2020 09:23
Hi @LoreleiNeith, it's great to see you in our Fitbit Community! I'd like to follow up and help you with your Fitbit device since it's not connecting with your phone. By the way, thank you for troubleshooting this issue before contacting our forums.
Please let me know what is the model of your Fitbit device. Also, let me know if you get any error message when you try to re-pair your Fitbit device.
In the meantime, restart your Fitbit device as described in this help article. After this, try setting up your device from scratch and see if the issue gets fixed.
Keep me posted!
05-31-2020 12:35
05-31-2020 12:35
Hi Juan,
Thank you for taking time to answer my query.
There had been another response to my message from one of the community gurus, in which different steps to take and try had been listed. I followed those and the sync started to work again.
I still wanted to thank you for your response though
Antonella
05-31-2020 16:19
05-31-2020 16:19
Hi,
Can you share the steps you took to resolve the issue?
Thanks
05-31-2020 22:24
05-31-2020 22:24
Hi there,
Here they are
If none of those ideas work for you then it’s probably best to contact customer support via: contact.fitbit.com
06-02-2020 08:27
06-02-2020 08:27
Hi @LoreleiNeith, that's great news! I'm glad to hear that you managed to get the issue resolved. Thank you for posting the update here and thank you for sharing the steps you followed. Don't hesitate to get back if more assistance is needed.
@andi3b, thank you for joining us in this thread! I would like to follow up and would like to know if the issue was fixed after following the steps that @LoreleiNeith shared.
See you guys later! 😀