10-12-2019 06:23
10-12-2019 06:23
My versa 2 will not sync since Oct 10th. I have reinstalled the app, restarted the tracker, unpaired all my devices from bluetooth and still getting the no device found error. What can i do next
10-13-2019 15:24
10-13-2019 15:24
Same problem. Android Google Pixel 3a phone. Sometimes it syncs but most of the time it says not found and restarting phone and Versa doesn't fix it.
10-13-2019 17:28
10-13-2019 17:28
Hello @Nikkigush and @JamesHumbers, welcome to the Community Forums!
First, I appreciate your effort and patience for troubleshooting this situation prior to posting, I totally understand how frustrating this matter can be for both of you but I'm here to help with this. That said, if you haven't already done so, I recommend you to check how the syncing procedure works here and see if there's a missing requirement on your Android mobile devices that are preventing the syncing procedure to be completed.
Also, please move forward to the troubleshooting steps that are specified on: Why won't my Fitbit device sync? and let me know how it goes.
Keep me posted, I'll be around if you need anything else.
10-14-2019 03:25
10-14-2019 03:25
I'm having the same issues with my Versa, it hasn't synced since 12th October and says device not found. All issues started after the latest firmware update. I have followed all the steps in the above troubleshooting, uninstalled the app, unpaired device, deleted the device from the app, now I can not re-pair it. I can't even wear the watch now because the time is out and running 20mins slow. I'd really appreciate some help. It seems like alot of people are having major issues since the last update.
10-15-2019 19:29
10-15-2019 19:29
Welcome aboard @Lei_sha, thanks for bringing this to my attention and troubleshooting your device prior to posting.
Let me share with you that our Fitbit devices use your mobile device information to display the time with the syncing process, therefore, by simply syncing your Versa it should display the correct time but since you're experiencing syncing difficulties this is the reason why the time is not showing as it should. So we can move forward with this, can you please let me know which Android mobile device are you using? Please make sure that's a compatible device with our products and services.
I'll be around.
11-09-2019 10:22
11-09-2019 10:22
I'm having a similar issue. I have an LG G6+. Just got my Versa 2 on Thursday. Connected fine. Then stopped syncing yesterday. Rebooted Versa 2, restarted phone, turned off/on bluetooth, logged out/in of fitbit app, uninstalled/reinstalled fitbit app, etc. Have gone thru this a few times. Sometimes it reconnects only to not sync hours later. I'm ready to send it back.
11-11-2019 08:44
11-11-2019 08:44
Same here, Huawei mate 20 pro.
Hugely frustrating; it's going back.
11-11-2019 23:34
11-11-2019 23:34
11-14-2019 03:47 - edited 11-14-2019 05:29
11-14-2019 03:47 - edited 11-14-2019 05:29
@Robm508- I haven't sent my watch back 🙂 in the end, I had some success by configuring the phone to exclude the fitbit app from memory management i.e. go into the power saving settings and stop the phone from shutting down the app.
Keeping the watch for now though I'm still a bit disappointed with it. A number of apps just don't work, and quite frankly, after shelling out for the watch, asking users to pay for a premium sub to get the data insights is taking the p*** for a watch that's marketed in the "fitness" sector.
11-14-2019 04:49
11-14-2019 04:49
Same issues here. It stopt synchronize since yesterday.
Got the Samsung S10.
11-14-2019 14:40
11-14-2019 14:40
I've found that clearing the data cache then syncing helps. But you shouldn't have to keep doing this. Poor response from Fitbit
12-05-2019 07:18
12-05-2019 07:18
I was able to override the issue. Had it happen to me about two days after initial setup. I have a versa 2, running android with october 1st security patch. First time no device was found, I went through unpairing, restart both devices fitbit removed device. No luck re pairing the device at that point. Reset factory settings on my versa, cleared all data from fitbit settings under app management. Reset network connections in phone. Finally was able to pair the two again.
FFWD to yesterday. I had the same issue of no device found. This time I went in and force stopped the fitbit app. Then I cleared the cache from the fitbit app under settings>apps>fitbit>storage> clear cache. Then back out to the fitbit app menu again, select battery> then allow background activity. Make sure that optimize battery usage is displaying "not optimized". Back out to the fitbit app menu one more time and select permissions> storage (enabled). Now I restarted the versa 2 ( 10 second depress on the side button) restarted my phone. Reopened the app, logged in, and was able to connect no problem. So far I've had no other issues. Will update if it happens again.
12-11-2019 07:31
12-11-2019 07:31
I have the Versa (not Versa 2) and have been having the same issue for the past few days. I sync using an iPhone 11.
I was able to temporarily get syncing to work by factory resetting the Versa and removing/re-adding the watch. But then, as others mentioned, I noticed something was up when my watch began displaying inaccurate times. The watch would also intermittently not be able to connect while I was trying to update the face display. And now it’s back to not being found at all.
It seems odd that so many are having the same issue around the time new firmware updates were pushed.
I have had the Versa less than a year (April).
12-15-2019 14:02
12-15-2019 14:02
Also having this issue bought my versa 2 on the 12th and have had the issue since the second day. Has anyone had any luck fixing it seriously considering returning it.
12-29-2019 19:34 - edited 12-29-2019 19:36
12-29-2019 19:34 - edited 12-29-2019 19:36
Any more updates? Looks like more and more people are having this issue and you (Fitbit) stopped responding.
12-29-2019 20:11
12-29-2019 20:11
12-29-2019 20:54
12-29-2019 20:54
That's highly disappointing. That's a terrible excuse from Fitbit. I had a Charge 2 that worked perfectly with my phone. I upgraded to a Versa 2 and now I'm having this issue. Same kind of phone. It's not the phone. It's not the app. It's the Fitbit. They are only using that as an excuse to not help, which is a bad public image for them. I thought they'd be more supportive with their devices instead of giving genetic / canned excuses to stop troubleshooting, helping, and updating their firmware. I'm seeing others that state their phone is on the approved list and are still having issues.
12-30-2019 00:55
12-30-2019 00:55
I contacted them twice and was on both occasions given a vague excuse of “it’s a known issue” even though I told them it happened randomly before updating firmware or iOS. I even asked if I could mail mine in for a replacement and they just stuck by their “we’re working on this known issue” reply. I even tweeted that I was throwing mine in the trash because it’s useless and got the same reply from their Twitter support. Thanks Fitbit.
12-30-2019 07:43
12-30-2019 07:43
12-30-2019 19:33
12-30-2019 19:33
Absolutely useless. I hate that they blame phones instead of actually helping and admitting there's an issue.