02-22-2019
04:08
- last edited on
09-08-2020
17:14
by
MatthewFitbit
02-22-2019
04:08
- last edited on
09-08-2020
17:14
by
MatthewFitbit
It's basically what the title says. Since I woke up this morning, I can't sync my sleep or workout to the app. Everything else is syncing. I have restarted my Charge 2 and I have disconnected my Charge 2 from Bluetooth and turned Bluetooth on and off. No success. It also does not sync to my Weight Watchers account.
Also, when I went to restart my Charge 2 in the charger, the button was non responsive and took numerous attempts from my husband and myself to restart.
Any ideas?
02-23-2019 12:05
02-23-2019 12:05
Hey @Poodlepants, I hope you are doin' fine! Thanks for trying a couple of tips prior posting. Besides them, I'd like you to take a look at the troubleshooting in this help article: Why won't my Fitbit device sync?
In order to fix the syncing issues between Weight Watchers and your Fitbit account, I suggest you to unlink and link again both apps.
About restarting your Fitbit, please make sure that the Charge 2 is well plugged into the charging cable, that the contacts align and you hear the noise while plugging it, so you won't have difficulties to press the side button.
Let me know how it goes!
05-21-2020 11:55
05-21-2020 11:55
I'm also having this same problem. I did all the trouble shooting that I can find and I'm not sure how to fix it. It hasn't recording sleep or workouts since 5/7. I honestly didn't notice because all I really use it for is to track my steps but I'm part of a flu study and they sent me an email reminder that I haven't synced my sleep or workouts. Any advice to get it to sync is appreciated!!
03-26-2021 21:37
03-26-2021 21:37
Have you figured it out yet? Mine is doing the same thing but sleep still seems to be working. I am just not getting the exercise part to sync and I use that a lot. Steps show up but without the exercise part I can't see how many calories I burned during the exercise or my heart rates.
01-02-2022 03:49
01-02-2022 03:49
Hi there, just wondering did you resolve this? Currently experiencing the same issue with my Charge 5.