04-20-2023 10:46 - edited 05-01-2023 08:16
04-20-2023 10:46 - edited 05-01-2023 08:16
Good afternoon My problem is for some reason with no changes made to the phone or the app My sense regularly loses connection with the Google Assistant.
I can connect it within the app and it will do my reminders I can ask it questions but after a short time no more than 30 minutes The function will no longer be available. The watch will give the status that something went wrong and it may work if you try again.
Obviously it doesn't work.
I have reset the phone, reset the app , reset the watch. All permissions are as they should be and Bluetooth is functioning just fine. I'm not sure what's going on and what is causing the issue.
I continue to get other notifications messages and calendar events with no issue it's only trying to use the Google Assistant on the sense where I have this issue.
Please advise as this is a key function for me.
Moderator Edit: Clarified subject
05-16-2023 07:44
05-17-2023 05:10
05-17-2023 05:10
I came here to see if anyone had the same issue with their original Sense. Looks like I'm not alone. I just updated the app in my phone. It connected to Google Assistant more quickly than previous daily reconnections. The app update was from May 5 accordging to Google Play. Hoping that this is the update. If not, will keep an eye out.
05-17-2023 05:20
05-17-2023 05:20
Something is working in the correct direction. I did find my Fitbit made the connection itself last night. I will hold off voting for a couple of days so I can see how it operates. So far, good.
05-17-2023 05:29
05-17-2023 05:29
No 3.82 update available for me yet. Still on 3.81. Sigh. @Fitbit push me the update!
05-17-2023 05:39
05-17-2023 05:39
Hey,
I'm having the same issue on my fitbit versa 3. I'll connect to Google assistant and it'll work two or three times then stop woth the same "sorry something went wrong" message.
Did you happen to find a solution yet?
-Emily
05-17-2023 10:20
05-17-2023 10:20
Was hopeful after seeing the latest Fitbit app update to 3.82 available this morning. Updated the app, restarted both the phone and Sense but unfortunately the same problem persists. Seems whenever the watch gets out of Bluetooth range, Google Assistant isn't able to reconnect when back in range of the phone and a manual re-connection through the app is needed. Which is peculiar since all other Bluetooth functions such as sync and text message notifications work just fine on the watch once back in range of Bluetooth.
05-17-2023 17:37
05-17-2023 17:37
I had no problems until I did the latest update to the firmware on my sense. I guess that there is a bug in the last update that broke it.
05-18-2023 13:41 - edited 05-19-2023 05:22
05-18-2023 13:41 - edited 05-19-2023 05:22
I have 3.82 now running for 12 hours and haven't seen any issues with the connection since it was installed. Keeping fingers crossed.
UPDATE may 19: Still running fine and haven't seen any disconnects yet.
05-19-2023 05:52
05-19-2023 05:52
can you try to leave the phone far away so it's loose the bluetooth conecction to see if reconnect after
05-19-2023 05:57
05-19-2023 05:57
05-19-2023
06:14
- last edited on
08-03-2024
08:49
by
MarreFitbit
05-19-2023
06:14
- last edited on
08-03-2024
08:49
by
MarreFitbit
@knittymarie- do you have version 3.82 of the Fitbit App installed? If not it may still lose the connection.
In any case the watch Google Assistant won't ever work if the phone is too far away but it should pick up again once it is in range if working normally.
As @juliancan has asked @Jvdzande, we are waiting confirmation that 3.82 actually fixes the problem, which is still not available in my area and maybe not yours yet.
Author | ch, passion for improvement.
05-19-2023 06:43 - edited 05-19-2023 06:45
05-19-2023 06:43 - edited 05-19-2023 06:45
Ok, had some time now to do some real testing and this is what I saw after I made the distance big enough between the phone and Sense to make it fail first:
So guess there are still some issues?
05-19-2023 07:06
05-19-2023 07:06
Still waiting for the latest version the 3.81 does still disconnect.
05-21-2023 04:05
05-21-2023 04:05
Had my first regular disconnect today, and made it working again by going into the android fit it app, tapped left top on my account, tapped on the Sense watch, tapped on assistant, and GA showed disconnected. Just tap it and select to connect again. After that it works again, so it seems to be that the app loses the connection to GA after the watch is disconnected?
05-21-2023 06:02
05-21-2023 06:02
I was fighting with this myself for months. I heard the 3.82 update would resolve it, but I still don't have access to it. That said, it's been staying connected for the last few days... Knock on wood. I wonder if Google figured it out on their end and it doesn't require an update.
05-21-2023 17:44 - edited 05-22-2023 18:58
05-21-2023 17:44 - edited 05-22-2023 18:58
Hi everyone, and welcome to our new members.
Thanks for keeping me posted and your efforts while working on this matter. As mentioned before, our team is currently working to resolve it and hope to have a fix soon. Be sure to keep the Fitbit app up-to-date to ensure you receive the quickest resolution.
I appreciate your patience and the time taken to share your feedback. Rest assured I'll keep updating this thread once I have more details to share.
05-22-2023 07:47
05-22-2023 07:47
I've noticed a pattern having had the device about a month - anything your phone's assistant couldn't do without being unlocked then it won't allow the Sense to do - unless the phone is (or has been within a couple of minutes) unlocked.
E.g. if I asked my phone to turn on/off lights - it says I need to unlock the device first.
The same therefore seems to be true of the Sense - it just doesn't have the ability to tell you that.
Does anyone else find this? Or find it solves the issue for them? This might also vary on your phones security settings, work profile controls, etc.
05-24-2023 03:20
05-24-2023 03:20
I'm running Ver 3.82 (38251031) on my Pixel 4 and the Google Assistant on my Sense only stays connected for a minute or two after re-enabling it. Then its back to Bluetooth error message or the "Something went wrong...." message.
05-26-2023 09:11
05-26-2023 09:11
I've updated to 3.82 yesterday and I've been constantly connected do GA ever since. Never lost the connection even after being away from the phone. Fingers crossed. I have a versa 3 btw.
05-26-2023 17:30
05-26-2023 17:30
Updated to 3.82 yesterday. Been connected since. This may be the solution. Let us see how it goes for a few more days.