Google assistant keeps disconnecting

[lfgalvao]

Google assistant started disconnecting again from my Sense. This happened to me for a few weeks last year, but it was solved by fitbit. Now it's happening again. I reconnect, and after a couple of hours the watch says I have to reconnect Bluetooth again. Anyone else having the same issue? 

[gaume]

It work for me too (versa 3)

[Wadjei]

I'm interested to see how you get on..

Fingers crossed!

[KN78]

Mines working too, for now. I wonder if the new samsung update helped it?

[quitob1]

It's possible some Samsung updates and other software updates I recently
did this morning also helped.

Although twice today now I had to reactivate Google assistant in the Fitbit
app and order for it to work again. At least that reactivates because it
didn't before.

[lfgalvao]

I was able to reconnected mine, finally, last night, but this morning it lost the connection again. Going to stick with Alexa, I think.

[gaume]

On my side this morning I had to reconnect Google Assistant manually and
the connection went through normally and continues to work until now. I
have the impression that I will have to do this every morning... It is not
yet completely corrected on my side but there is a big improvement.

[KN78]

Mine is still disconnecting several times throughout the day, but is easy to reconnect at least. Still not good enough as if i need to pick up my phone to reconnect it i might as well just set reminders from my phone.

[rcat72]

That's exactly what mine is doing. A step forward of sorts - but still an
absolute pain. Mine is set up to manage sockets for lights, it's
so.convinient to have something on me to do that, rather than finding the
phone

[EstuardoFitbit]

Hey everyone, thanks a lot for all your updates!

I can see some of you have already got the Google Assistant back to work. With that in mind, I would like to know if you guys have updated the app to the latest version. 4.30 is the latest one and it is available for Android and iOS. 

If you haven't, please do so and try to set up the assistant once again. 

Let me know if the assistant works again! 

[Swimfan02066]

Success on a Google Pixel - yay! Even more than once in a row. Thanks,
all, for the persistence. Seems like a small thing, but when you come to
rely on it, suddenly is very important!

[EstuardoFitbit]

@Swimfan02066 Thanks a lot for the confirmation. 

I'm glad to read this great news, I'll be around to hear any feedback you can have! 

[quitob1]

Hi @EstuardoFitbit - Thanks for chiming in and letting us know which version to use.

Yep - per my post yesterday I'm also on v4.30 and as of this moment my GA (Google Assistant) works.  However, in the past 24 hours my Sense kept dropping bluetooth or disconnecting from GA.  I've had to reactivate GA probably about 6-8 times, so it's not quite stable yet.

Please thank your devs and product teams for their hard work and persistance.  They are getting closer to a reliable and stable fix!

[EstuardoFitbit]

@quitob1 Thanks a lot for the report and your kindly words!

We would keep working hard to get the issue fully resolved as soon as possible and any additional details can be useful for us!

[KN78]

I have the most up to date fitbit app. While my google assistant will now
connect it disconnects many many times throughout the day.

So i dont consider that as working properly.

Its pretty useless if we have to constantly reconnect.

We are basically back to when the problem originated and it kept
disconnecting multiple times a day.

We still need a permanent fix please.

[NoSloppy]

That is correct. Apparently things may have gotten worse, but they never just reverted the update back to before the problem, or applied any kind of fix to my knowledge. The problem has always been that Google Assistant becomes disconnected.

Where can we see a change log of version 4.3.0? 

What was done specifically to address this issue which I can only assume somebody thought might fix it, which is weird because r&d should be able to tell if it's fixed or not as they're releasing the update. 

It's just weird.

[EstuardoFitbit]

Hey there @KN78 @NoSloppy, welcome back to the Community!

Thank you so much for taking the time to share your feedback! I completely understand that this isn't the solution we were all hoping for. Please know that we're still fully committed to resolving this issue.

It might take a bit more time than we'd like, but we're working hard to get it just right. Your patience and understanding mean the world to us. Thank you again for your feedback and for being part of our community!

[67Healey]

Dear Moderators - @EstuardoFitbit @LizzyFitbit @AndreaFitbit & everyone else on this thread..
I'd just like to remind everyone that the exact same problem happened last year. At least last year's fix didn't take going on 4 months.:-(
https://community.fitbit.com/t5/Sense/Google-Assistant-won-t-stay-connected-to-my-Sense/m-p/5404741#...
I have really tried to avoid this thread, as previous recent examples of trying to get things fixed (constant logon with new Samsung phones) took like 8 months of complaining on the forums before being resolved.
And, unfortunately, I'm also convinced that Fitbit support is powerless to help - I called in 2 months ago about this specific issue , only to be run through all the known steps to resolve that I told the rep I had already done. He then told me to reinstall the Fitbit app (for a second time on the same call!!) to get the newest version of the app - duh - the app was already up to date & I had just reinstalled the same version - so a third time wasn't going to fix anything. He then came back on the phone & said that "it was a known issue" & it would be fixed in the next app update. Uh, WRONG again.
I then called in a second time, 3 weeks after the first call. This time the support rep said that she was "escalating my issue" & I would hear back within two days. Well, that was a month & a half ago, so you decide....
The Sense just had a firmware update (for me) yesterday (44.128.6.17) - and after this I was actually able to have the GA connect to my Sense. Unfortunately, just like everyone else on this thread, the joy was short lived, and I haven't spent the time to track how long it takes to disconnect again & become unusable again unless you manually connect. What an absolute pain.
Fitbit app version 4.30. 
Android 14 / One UI 6.1
Samsung S24 Ultra. 
PLEASE ESCALATE THIS ISSUE!! So it doesn't take the same amount of time that the Samsung logon issue took! Thank you.

[trawg]

As with the above posters, mine is now back to reconnecting correctly, but it will drop the connection at some point randomly later the day.

The fact that this started working without a Fitbit software update (I've been on v4.30 for several weeks) reinforces my suspicion that this is not a Fitbit issue per se but a Google Assistant issue.

Without knowing anything about how it's all glued together I suspect Assistant has some sort of new aggressive connectivity polling thing which is timing out the device connectivity a bit more actively than it used to.

It sure would be nice if there was a shortcut way to get to the Assistant reconnection screen. Having to load the app, click the device in top left, click the device again, click Voice Assistant, then Google Assistant, then Reconnect several times a day - after over a month of trying it repeatedly only to end in failure - is starting to get a bit wearying.

[DCSERKITS]

Many discussion feeds on this topic are locked leading me to wonder if Fitbit has given up on voice assistant (GA) on the Sense 1. I've tried every suggestion. Reboot both the phone and watch, shut off battery saver, put both apps in "never sleep " mode. One suggestion wanted me to add, then update, at least 5 new apps then update them. I am now resetting GA in Fitbit every few hours. Is there a resolution on your roadmap or just angering users? Can you interface to Samsungs voice assistant instead?

[quitob1]

Surprisingly for the past day I have not had to reactivate my Google assistant. It's still working every time I push the button on my watch and seems stable so far! I wonder if the engineers did something new recently... 

If so, well done team and thank you!