Versa 2 and iOS Bluetooth Pairing Failures

[MrMarv]

New Versa 2 as of yesterday.

Versa 2 (70.7.14), iPhone 8 running iOS 13.3 and FitBit app 3.13 (919).

There is no Information Icon next to Versa 2 in the phone's bluetooth settings screen.

The Versa 2 entry in bluetooth settings disappears if I close the FitBit app.

Regularly being prompted to pair the device.

Cannot access "Settings...Versa 2...Notifications" and cannot enable All-day Sync, even though, by looking at the Web Dashboard, the sync is indeed occurring every 20 minutes. When I attempt to perform with of those two actions I am presented with the "Bluetooth Pairing Required" prompt.

This is quite different from my experiences with my Charge 3 and Alta HR before it, as well as many other paired devices on my phone.

I have four other devices paired but not turned on at the current time - they all have an entry and Information Icon in Bluetooth settings.

I have, in four distinct tests (the first three numerous times):

1. turned off bluetooth and turned it back on
2. removed the app from memory aka forced restart of the app
3. re-booted my phone
4. even deleted and reinstalled the Fitbit app

still being regularly prompted to pair the device.

<<edit>> I have just restarted the Versa 2. Issue continues.

Your thoughts, please.

[MrMarv]

Correction - once again my Versa 2 no longer is listed as a Bluetooth device when the FitBit app is not in memory. 

All other issues remain.

[MrMarv]

All five (or is it six) issues previously reported continue under release 3.20.1 (Build 953).

For me, it has been 92 days since I first reported this pairing failure issue. 

Additionally, not previously reported is the fact my heart rate is routinely not being displayed in the app until I take the app out of memory and restart it. This has caused me to back off my exercise routine because the last thing I want is for my ICD to engage its defibrillater while I am running on the treadmill. Yes, in other posts in the past I have mentioned that I ran enough in the Marine Corps to last me a lifetime, but hey, I'm allowed to change my mind. And I am jogging at a 12 minute-mile pace, not the 6 to 7 minute-mile pace for three miles I routinely tested at when serving.

Because I have an LVEF of 25% (1/3 of desired and 1/2 of minimal) it is pretty easy for me to come near, and potentially over, my max heart rate when jogging at 4 - 5 mph on the treadmill. My device kicks in its ventricular fibrillation logic approximately 15 bpm over my defined max heart rate.

Yes, my Versa 2 displays my heart rate, but the vibration level on the treadmill at 5 mph is just too much for a clean read of the number, whereas my phone on the treadmill's dashboard can be easily read.

While others may not have gone to the extent I did with regards to providing visuals and other diagnostic information, hundreds of users have been reporting either Bluetooth connectivity issues or other issues that appear to have been caused by those connectivity issues for at least twice as long as I have experienced since my Charge 3 "white screened" on me to be replaced by the Versa 2.

The post on February 6th by @KateFitbit, which is pinned to the top of this page, addressed issues I have reported, but apparently only for those users whose devices are cleanly paired. Without a clean pair those steps do not help.

@LizzyFitbit initialed a support team ticket on my behalf on February 7th - 85 days ago.

[MrMarv]

Additional lost functionality - 

Music control of songs playing on my phone.

For me, this would be beneficial while walking the neighborhood or doing chores around the house, like gardening - something I am doing a little more of since retirement.

I cannot determine if the connection loss is inhibiting the voice cues I can receive when using the walk applet in the FitBit app on my phone versus starting the walk on my Versa 2 Walk Exercise applet.

The lack of music control is not important while on the treadmill, as I have a Samsung music bar about five feet to the rear of the treadmill and the phone is resting on the treadmill's dashboard.

[MrMarv]

Day one-hundred twenty-one

iOS version 13.5

FitBit app version 3.22

Versa 2 firmware version 70.8.x

Versa 2 connects but does not pair - and for those not aware of it, there is a huge difference between connecting and pairing.

Continue to have a minimum of 10 pairing requests per day in addition to one or two pairing requests each time I have to take the app out of memory to force a sync.

Occasionally receive "Device Not Found" message for up to five seconds before getting the "Connected" message then the pairing request.

Dynamic heart rate display in the app is crippled - along with all of the other information points on the Today screen. After years of being able to have all that information available at a glance - - - especially heart rate - - - it is missed.

Cannot turn on “Share System Notifications” on as there is no “Information” icon next to Versa 2 in iOS Bluetooth settings.

As such, I cannot receive text notifications as I cannot enable them.

Nor can I receive email notifications.

Nor can I receive Calendar notifications.

Nor can I receive call notifications.

Nor can I enable All-day sync.

Music control of my phone’s music library from my Versa 2 is inoperative as I cannot connect to my phone.

Connected GPS is crippled. While it is somewhat accurate when the FitBit app stays in the foreground, it continually disconnects when not. Heaven forbid I would want to change to another music playlist on my phone in the middle of a walk.

One of my routine walks in the neighborhood:

First, this morning and yesterday evening walk the same exact route:

The last time I was able to get a clean representation of the same route - NINE days ago and I take this route once or twice each day, opting for a longer route the other two or three times:

@LizzyFitbit passed this issue on to Customer Support on February 7th of this year - 113 days ago.

Customer Support keeps dreaming up things to try, but to no avail. I can only think they are working from scripts and checklists and not actually talking to the development team. I have told them they are grasping at straws and have asked me to do the same thing over and over. After the last time I told them to flag my Support Ticket as no-contact until a confirmed fix is in place as their emails are getting irritating.

[MrMarv]

This evening - same route - FitBit app removed from memory, place back in, GPS assist walk initiated on Versa 2 and the app was kept in the foreground for well over 15 minutes.

Over a half of a mile, but the map shows less than 300 feet.

Eight functions, six of which I have grown to value over the years, just gone.

And this has been going on for how long? And I'm not just talking about my four months - it has been nearly 8 months for some.

[gorhamguy]

I’m still in the same boat as well!

[MrMarv]

Two-mile-plus walk to the local Rite Aid and back.

The FitBit app kept in the foreground the whole trip with the exception of about 10 seconds in the store for the purpose of showing an employee a product image.

The only time my device lost the Assisted GPS link was that 10 seconds and E-V-E-R-Y time I placed my phone in a screen lock status, which I prefer to do when it resides in my pocket.

The "Connecting..." status line was displayed each time I locked the screen within 5 - 15 seconds and went away to be replaced by the dynamically updated mileage within 5 seconds of unlocking the phone (FitBit app still in the foreground, of course).

This N-E-V-E-R happened with my Charge 3 in the 15 months I used it - of course my Charge 3 was paired and not just connected like my Versa 3.

[Scow]

My air plugs da will not be discovered by my Versace 2

[MrMarv]

@LizzyFitbit @KateFitbit 

Day 185.

So while others having the same issue as I have had their devices replaced by FitBit, apparently I don't rate that because I'm a little too much of a gentleman to really speak my mind and was willing to wait until the Development team came through,

I have now taken my Alta HR out of retirement until such time as I can determine if what I really want to do with my Versa 2. It's a shame my Charge 3 white-screened after 15 months otherwise I would have never had to get the Ionic that was DOA or the Versa 2 that doesn't play well with others.

[MrMarv]

@LizzyFitbit @KateFitbit 

After 200 days of pretty much being jerked around by Customer Support (why do I get the impression they were counting warranty days?) I fixed it myself.

I returned it to the retailer - at least Best Buy believes in Customer Service; though FitBit will pay in the end.

[MrMarv]

Okay - 

I marked my previous post as best answer, because for my particular situation it was indeed the fix for something that FitBit wasn't able to fix and wouldn't own up to there being a hardware issue.

Someone removed the best answer flag.

Twenty-two hours of continued operation as expected with the replacement that Best Buy provided me with.