Versa 3 won't connect to my Pixel 6

[kristabeakley]

I had this issue with my versa 2 and was told by Fitbit that it was a problem with my watch so I upgraded to the 3 and it's the same problem. 

The Fitbit app keeps saying i need to grant Nearby Permission to sync and set up...I have all permissions granted in the settings and my phone Nearby Permissions are on 

I'm not understanding what to do next and Fitbit support has not been helpful. 

Has anyone successfully resolved this issue before?

Moderator Edit: Clarified subject

[MarreFitbit · Accepted solution]

Hi there, @kristabeakley. Welcome to the Community Forums. Thanks for the details provided in your post about the issue with your Versa 3. I understand where your concern is coming from. 

For more information bout the message you're getting, I'd recommend taking a look at these two help articles Why is the Fitbit app prompting me to turn on location services? and What should I know about using the Fitbit app on my Android phone?

Hope that helps. 

[kristabeakley]

Thanks for the reply, but I'm sorry to say that it's not helpful. It's something to do with one of the updates that was rolled out through the beta program. When I opted out of the beta program and rolled back to a previous update, it worked just fine. Then I re-enrolled in the beta program. It updated my app, and it stopped working. I tried to give feedback to the beta program and was told I had to be a part of the beta program in order to do that, but when I'm part of the beta program, my Fitbit doesn't work. Very disappointing. I really hope they catch this glitch before the next roll out

[Pbmartucci]

Have you had any luck? Since getting my Pixel 6, my versa 3 doesn't sync correctly. My steps update in the app, etc, but it doesn't receive anything from my phone, such as text messages or calls. The app only updates when I manually sync:-( 

[Ashokabs]

I though the problem was with Android 13 beta. I was unable to even connect the watch and my Pixel 6 phone. Now with the Android 13 stable it is still not connecting. I have to use the laptop and back sync the phone through the tracker.

[Ashokabs]

None of these work. It is a waste of time.

[Nolefan32]

I have the same problem with my Versa 3. From what I've found, it has to do with Google Assistant. If you're running Android 13 and select Google Assistant as your voice assistant, your Fitbit will stop communicating with your phone via bluetooth. The workaround is don't select a voice assistant, or select Alexa since it doesn't seem to have that problem. If you're already stuck with the problem, best I can find is the only way to get Google Assistant off your Fitbit is a hard reset. This was a persistent problem throughout the beta trials of Android 13, and I had hoped it would have been resolved with the stable release, but alas it appears to persist. Frankly I'm afraid to try it again until someone says that there's either been a new release of Android 13 or the Fitbit app that's specifically resolved it.

[Ashokabs]

You are absolutely right. I used a second phone with Fitbit app to setup Alexa assistant and sure enough the phone paired and started syncing. Looks like this has been a problem for long and hence the pairing process often takes long or one has to repeat it several times. I wish this could be resolved considering that Google owns Fitbit!

[Ashokabs]

The problem is arising from the Google Assistant in the Fitbit app and Versa 3. This was identified by another contributor. I was able to set up Alexa using another phone and then my Pixel 6 immediately synced with the watch. It is working very smoothly.