Versa 3 Repeatedly loses Bluetooth connection

[SunsetRunner]

3May2023 - it gets worse, but I'm not sure that it's FitBit or the garbage Android update:

a715wvlu4ewb6.

I have Google Assistant enabled in FitBit Versa 3.  To activate it, I just swipe left and press the little "Assistant" icon (blue, red yellow, green dots).

Most of the time, this would put the Assistant into listen mode and all would work fine.  Sure, the odd time, it would disconnect from Bluetooth or just not work, but rarely.

But now, immediately after this Android update, the FitBit app and the FitBit lose BT connection completely.  The ONLY want to force it to reconnect is by running the app, which is ridiculous.

I also notice in the Bluetooth app, where you see each device listed, the FitBit is NOT there!  However, after running the app and doing a sync, THEN it appears, but not in the 'paired devices" list.  Only in the "Available devices" list.  And when it does, there's nothing that I can do to get into its settings to assure that it doesn't go to sleep.

However, to totally contradict that, I just tested right now as I'm preparing this post and THIS TIME, even after syncing the Versa 3, which does work, nothing is listed now in the Bluetooth app AND now the Assistant still doesn't work.

I am hoping that the FitBit devs will revamp the app and how the watches connect to bluetooth or have an option to stop the app or fitbit from going to sleep and to keep BT awake.

I really like having the Assistant a swipe away when driving so that I don't have to mess with the phone.  It's really handy.

Now, that's gone!

Moderator edit: clarified subject.

[amorep]

i am having the same problem with my versa 3

[Guy_]

Hi @SunsetRunner , @amorep - unless you reconfigured the button, long press should also action Google Assistant.

Currently there is a general problem with it disconnecting.

Normally it only disconnects when you logout and when you login you have to connect again.

If Google Assistant is not working click profile photo and device photo in the Fitbit App and click voice Assistant and connect it again.

The only manageable Bluetooth entry is Versa 3 controls the rest is taken care of by the Fitbit App when you open it. You can try logout of the Fitbit App which may refresh the BT setup.

[amorep]

I have had my versa 3 for a couple of years and never had this disconnect with bluetooth before. I do not use a google platform as I use Mac and safari but have never had this problem. I think it is time I look into the Apple Watch since Fitbit is looking to go with google in the future. I have had Fitbit for at years and am disillusioned with the issues of late. I do not like the fact it disconnects constantly now.

[Jerv]

And when that doesn't work? 

Going into the app to reconnect Google Assistant is not only the opposite of why I chose the Versa 3 (the ability to use Assistant without taking my phone out of my pocket), but is also a very temporary solution that needs to be done multiple times a day. 

I've tried every solution I've seen in these forums; restarting, relogging, reinstalling, re-pairing, checking battery optimizations... pretty much everything except replacing the hardware. 

[Guy_]

Hi @Jerv - currently you can't do anything to fix it.

Something changed with Google itself.

Maybe Fitbit App 3.82 version available shortly has a fix.

[SunsetRunner]

That's exactly what I'm saying!

Is that after this forced Android update, now, to get the Assistant to work at all, we have to go into the FitBit app to "reconnect" it.

The app is NOT keeping the connection alive!

Obviously, it's not product if we have to now do that just to use the assistant.

Before this stupid update, the Versa 3 would stay connected to the phone and just pressing the Assistant Icon would active the Assistant immediately.

When one is driving, we can't be messing with the app to get it to connect again.

As a technician, it's obvious that when there's an Android update that breaks apps (and that can happen to any app at any time) as long as the update doesn't introduce a "bug", then the App devs need to work around the "changes" to keep things working.

As a side note, after the updated Android version happened, there were lots of complaints.  To my surprise, a week or few after this update, another update was pushed.  I had HOPED that this returned how BT to how it worked before.

So at this point, it's between FitBit and (in this case) Samsung (who pushed the Android updates) to figure out the problem and fix it.

It's not fair to customers to have features just broken like this and for the 2 companies to just ignore it.

Again, I'm a tech who has been in the industry for decades.  I know how this works.

[SunsetRunner]

Yeah.  Everyone will have the problem (or notice it) if they use the assistant.

Let's see if the Android Devs and the FitBit app devs take action or just ignore it.

If they do nothing or worse, TRY TO PUSH IT BACK TO THE CUSTOMERS, then I'm done with FitBit and I'll go to another brand that actually addresses issues as they arise.

[Guy_]

Hi @SunsetRunner - as mentioned earlier the problem doesn't seem to come from an Android update or a Fitbit App update but something that Google did with the Assistant independently.

I tested on an old version of the Fitbit App and a non updated Android phone and it also disconnects but didn't use to.

Fitbit may have found a solution in the Fitbit App version 3.82 but it has not been confirmed.

Note. The Google Assistant was working fine initially when it was released on the Sense/Versa 3 but part way through 2021 Google changed something and Google Assistant routines stopped working. So it is not the first time a modification has been sprung on Fitbit.

[SunsetRunner]

While part of that may be true, as a tech who has worked in the industry for decades and is very aware of what some updates can do, I can tell you 

CLEARLY

that literally, up to the day of the Android update, the Assistant worked fine.  But IMMEDIATELY after the update, the Assistant stopped working with this disconnecting thing.

I am aware that Google makes changes that can impact different apps and devices. VERY AWARE.

Interestingly, you say that in 2021 Google changes "something" and routines stopped working.  I find that interesting since the Assistant on my Versa 3 was working just fine until this latest Android update. PLEASE NOTE: the Android update DID make changes to how BlueTooth functions and I have a strong suspicion that what they did is allow BT to go to sleep, thereby losing connections.  Most devices can "wake up BT" when needed.  Sadly, in settings, they've removed an option in the BT protocols to make it stay awake.

And I do believe that they've done it again.  But one more time, Assistant was working right up to the very day of the Android update and now, it consistently does not working, unless I FORCE a reconnect... which, I've NEVER had to do before.

Please do widen your knowledge on this and please don't just stick to the items that you list.

There is more and there are those of us out here who can prove the issue.

Again, as a tech, I've worked decades in the computer field at "Corporate Levels" and have dealt with very poor, too early release updates on systems.  Not just Android.

At any rate, in 2019, Google acquired FitBit, so their Devs should be on the ball to address these issues.

After all, we all paid for the products (this is my 3rd fitbit) and if Google/FitBit is going to side-step and ignore this issue... AND/OR take YEARS to fix it, then I for want have no problem going to another brand.

And, I won't lose any $$ because I did buy the extended warranty from Best Buy which, due to the failure, allows me to return it for full credit!

When I do that, I make sure to let everyone know what's going on!

[Guy_]

Thanks @SunsetRunner - there may be 2 different issues here,

There is a recent general problem where GA gets randomly disconnected [which it wasn't doing before, but seemingly unrelated to any updates] and is different to Bluetooth getting disconnected which is the one you may have after an update.

For the Fitbit app to work properly, it and it's associated services must be enabled to run in background. An Android update may have introduced changes in that area via battery saving settings.

Hopefully you will find the phone setting causing the Bluetooth disconnect and Fitbit will find a resolution to the GA disconnect. If you can't wait hopefully Best Buy will agree to a full refund for these software issues, as opposed to a hardware fault.

You are right, there should be better communication within Google to eliminate the GA problems before they start.

[SunsetRunner]

That you, Guy_ for understanding what I was saying.

You are correct there.  There are 2 or more issues.  The BT issue, however, I know to be a major problem caused by that Android update, because, as I forgot to mention too, is that even syncing the app now is problematic.  It will work, but it complains once or twice that "it's taking a long time".  But it's almost like it doesn't "see" BT on the first run, but somehow, BT finally "wakes up" and it syncs.

The more I search around, the more I'm finding that people are having this and other BT related issues now.

Oh well.