Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Versa Won't Sync

Replies are disabled for this topic. Start a new one or visit our Help Center.

I've had my Versa for a while now, and as long as I keep up with syncing it, it usually isn't a problem.

 

For whatever reason I just didn't get around to syncing it this past week, and when I tried to sync it, it my phone couldn't find it. I tried turning off my phone's bluetooth and turning it back on, tried restarting my versa, tried restarting my phone, tried turning off my versa and then turning it back on, tried syncing my versa with other devices, everything came back with the same result.

 

Upon searching for a solution to the problem, I found a solution on these help forums that suggested that if I had already done everything that I had already tried, the next step was to remove my versa from my fitbit account and reconnect it, which I have now attempted. Unfortunately when I tried to add my versa back to my account, I've encountered a problem where my versa can't be discovered.

 

I assumed that the problem might be something that I could fix by factory resetting my Versa. I knew that it was going to cost me a week of stats, and was probably going to be a huge pain to reinstall updates and get rid of the Starbucks App again, but whatever. Unfortunately this did not solve my problem, so now I have a fitbit Versa that refuses to sync and doesn't even display the time anymore, so it isn't even functional as a watch.

 

To summarize:

Problem:

Versa is not discoverable.

 

Steps Taken:

  1. Cycled Bluetooth on phone
  2. Updated Fitbit App
  3. Cycled Bluetooth on phone again.
  4. Restarted Fitbit App
  5. Restarted Versa
  6. Restarted Phone
  7. Turned off Versa, waited 15 seconds, turned on Versa
  8. Attempted Sync of Versa with other devices
  9. Removed Versa from Fitbit Account and attempted to reconnect it
  10. Factory Reset Versa and attempted to set up Versa like the first time again
  11. Removed other paired devices from my phone's bluetooth profile.
  12. Tested discoverability of my phone itself with the bluetooth of my PC.
  13. Uninstalled the fitbit app and reinstalled the fitbit app.
  14. Attempted to pair my versa to my account through my phone again.
  15. Restarted my factory rest Versa with the two-button hold.
  16. After this it actually did try to be discoverable for a minute and asked me to punch in a 4 digit code, but then I was treated to a "Not Working/Try Again" page on my phone again, and my Versa became unresponsive.
  17. Pressed the "Try Again" button, prompted me to punch in a 4 digit code that was not displayed on my watchface.
  18. Cycled bluetooth again and rebooted the Versa for what feels like the millionth time.
  19. Force-quit the Fitbit App and restarted it fresh again.
  20. Finally got it to come up with "Found It!" again, punched in my numbers and got a "Sorry, this is taking longer than usual" message before it brought up that "Not Working/Try Again" page again.
  21. Decided to leave it for a little bit to see what would happen.
  22. After about 5 minutes when I realized that what it was doing was nothing, restarted the Versa and attempted again.
  23. Force-Stopped the fitbit app, and attempted again.
  24. Moved all of the offending devices so that they were now within 5 feet of my wireless router to give them the benefit of proximity to my wireless.
  25. Cycled the bluetooth on my phone and rebooted the Versa again.
  26. Got to the 4 digit code, at which point my Versa became unresponsive and my phone brought up the "Not working/Try again" screen.
  27. Became frustrated with the realization that a set up that had told me to set aside 30 minutes had now taken over 2 hours and left the watch and phone to think about what they had done.

Current State Of Things:

  • My Versa is fully charged and sitting in its cradle. It's screen displays the Fitbit Logo, and maybe it's doing something, it's impossible to tell.
  • My Phone is fully charged and plugged into the same power strip as my Versa. The app currently suggests that things aren't working and is asking if I'd like to try again.
  • The entire setup is a couple of feet away from my wireless router

Current Feelings:

When my Versa is working, I really, really like it. It's encouraged me to take extra walks and really get into more exercise. I also like the way that it looks like an actual watch instead of like most fitbits. I tend not to use a lot of its features because I turn off the bluetooth except to sync the watch in an attempt to save battery life, and I don't own bluetooth headphones to enjoy the Versa's music functions.

Unfortunately, when my Versa isn't working properly, it is always a huge and horrible hassle. Once every handful of months I end up having this experience where I look on the help-board for the "My Versa decided not to sync anymore" and go through a stupid amount of troubleshooting trying to fix the thing. I usually eventually get it working again, but every time I do I always wonder why it had to be so hard, or why it had to take so long.

I'll keep doing things, and when I eventually get it all sorted out, I'll come back on here with probably another 20 steps that I took to finally get there.

Best Answer
0 Votes
3 REPLIES 3

In the two hours since I posted my initial list of attempts I've continued to have a bunch of fun and exciting issues trying to connect to my fitbit so that it'll stop being a shiny black pebble that emits light and displays the Fitbit logo. The current cycle that I'm running through over and over again is as follows:

 

  1. From the "Not Working" page, I hit "Try again" which starts the discovery again.
  2. A Few seconds later it often displays the fun green circle with the checkmark and says "Found it!" and then sometimes jumps immediately back to step 1
  3. If it doesn't jump back, it sometimes asks me to "Enter the number on my Versa's display" which if my Versa displays the 4 numbers I punch them in.
  4. Most of the time it doesn't display numbers, and instead just displays the Fitbit logo, so I sit and wait in the hopes that it will show the numbers, but when it doesn't it eventually times out and jumps back to step 1.
  5. In the event that it displays the 4 numbers, I punch them in, and then it either apologizes for taking longer than normal and then jumps back to step 1, or it just immediately jumps back to step one.
  6. And then the cycle continues, over and over again for the past 2 hours.

Back at the beginning of this process the Versa did display numbers most of the time. Lately it seems to have decided that it is as exhausted with this process as I am and can't even be bothered.

Best Answer
0 Votes

I continued the cycle of attempting to sync my watch, and going to the "Not working/Try Again" window. After what totalled 9 hours (which I'm a bit dismayed to say is longer than the 30 minutes that the set-up initiation suggested it would take) I was able to reconnect my Versa with my account.

 

It continues to be argumentative about syncing, but now at least it functions as a watch again.

 

Final Thoughts:

There is no way that it should have been this much of a hassle to get it to sync in the first place. After I factory reset it, it should have been a quick and simple process to reconnect it with my account. As I said earlier, when the Versa works, I'm happy with it, but when it starts doing strange things I know that I'm in for a not great time trying to get the thing working agin.

Best Answer
0 Votes

Hoho! I thought I had solved my woes, and at least it was going to be a nice happy watch again, but things are not fixed after all.

 

Current State Of Things:

My Fitbit Versa is currently displaying the wrong time (Off by an hour). This seems like exactly the sort of thing that could be solved by syncing it, however it still doesn't do that (I was a little over-excited when I accepted the fact that it was a watch again as the solution to my problem). My Versa is currently not discoverable by my phone or my computer, so I guess that it is still suuuuuuper broken.

Best Answer
0 Votes