help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bluetooth refuses to connect-Versa

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

‎05-04-2018 15:24 - last edited on ‎11-02-2021 19:07 by Fitbit Moderator

‎05-04-2018 15:24 - last edited on ‎11-02-2021 19:07 by Fitbit Moderator

I received an update to the Android app last night.  Now Bluetooth consistently refuses to connect despite repeated reboots of both the phone and the watch as well as several re-pairings.  Strangely, the app says that syncs are succeeding even though the Android Bluetooth settings page shows that the watch never connects via Bluetooth.  Is it possible that this problem is related to the new app release?

 

I just discovered that turning on the Developer Bridge on both the phone and the watch causes the Bluetooth icon on my app to come on, and the app then receives data delivered by the phone.  However, Android's Bluetooth screen for the Versa (Classic) seems to indicate that there is still no connection.  In other words, the Connect button is still activated and seems to do nothing.

 

Moderator edit: added label

Moderator edit: updated subject for clarity

Best Answer
Labels:
0 Votes
3 REPLIES 3

‎05-04-2018 15:26

‎05-04-2018 15:26

P.S.: I'm running firmware version 32.32.4.19 and companion app version 2.71.

Best Answer
0 Votes

‎05-04-2018 15:42 - edited ‎05-04-2018 15:43

In response to arthurgleckler

‎05-04-2018 15:42 - edited ‎05-04-2018 15:43

The Fitbits use BLE, bluetooth low energy.  The traditional connection using the device in Android bluetooth isn't necessary.  Just make sure you have your phone's Bluetooth turned on, then use the Fitbit app to confirm connection with the tracker. 

 

I use the app's heart-rate tile for this, if you're seeing a pulse in it, the phone and Fitbit are BLE connected.  Starting a connected GPS activity will usually work then, too.

Best Answer
0 Votes

‎05-04-2018 15:47

In response to BamIAm

‎05-04-2018 15:47

Thank you very much.  I've tested now and the app is receiving updates consistently now.

 

Even though I was wrong about the Bluetooth connection status, there was something wrong because the app wasn't receiving updates and wasn't displaying its Bluetooth status icon, which is based on <peerSocket.readyState === peerSocket.OPEN>.  Once I reinstalled the app from Studio, everything started working again.

 

Thanks again.

Best Answer
0 Votes