08-27-2019 07:06
08-27-2019 07:06
My Versa has a mind of its own - it syncs fine some of the time but not others. It seems to not want to sync first thing in the morning when I need my sleep stats. I have reinstalled software, reset Versa, completely charged watch, took the phone off charger and put it on charger. It will worked and then decide to be Finicky again. What to do? Expensive watch to not be able to get stats!
08-28-2019 05:36
08-28-2019 05:36
@MarIanns welcome to our Fitbit Community! I'm happy to assist you with your Fitbit Versa since it's experiencing syncing issues. By the way, thank you for troubleshooting this issue before contacting our forums.
Please try the troubleshooting steps that are listed in this help article. This article contains steps that you already tried but you can skip them and proceed with the rest.
Keep me posted on the outcome! 😀
08-28-2019 09:06
08-28-2019 09:06
08-28-2019 14:18
08-28-2019 14:18
i have same problem with iphone 6s. so you are not only one. probably latest fitbit update broke.
08-28-2019 14:37
08-28-2019 14:37
Have you restarted your phone? Unpaired and re-paired bluetooth?
08-28-2019 15:13
08-28-2019 15:13
Having the exact came issue with an Android phone so not just you 😔. 'Device not found for 2 days now`. Works perfectly fine with the app on my ipad though but that's not as convenient as it is not always with me
08-28-2019 21:15
08-28-2019 21:15
08-28-2019 21:18
08-28-2019 21:18
mostly before i go to run i restart fitbit versa, then iphone 6s and after that mostly fitbit find iphone connection. this is standard thing and sometimes it takes 10 min before versa find iphone gps signal.
08-28-2019 21:18
08-28-2019 21:18
08-29-2019 00:26
08-29-2019 00:26
Really getting fed up with this sort of response to a wide ranging issue.
08-29-2019 00:29
08-29-2019 00:29
Same here, @urmoluts. Worked fine and then...no bueno. So I fired up my old Galaxy S5...and it works just fine. Of course, I had to flip a gajllion switches in the settings to get things the way they should be. Fitbit devs failed somewhere along the line.