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: 

Google Assistant Cuts Off - Versa 3

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

‎05-31-2022 05:42 - last edited on ‎12-18-2022 18:00 by Fitbit Moderator

‎05-31-2022 05:42 - last edited on ‎12-18-2022 18:00 by Fitbit Moderator

Hi, 

 

I'm experiencing a problem with Google Assistant cutting off on my Versa 3. If I ask it a question it connects successfully to my phone and starts to provide an answer but then cuts off and displays "something went wrong, but it might work if you try again". If providing an explanation it gets a few words in and then goes silent and displays that message. I've tried logging out and back in to the app, uninstalling the app and installing it again, rebooting my phone and rebooting the watch but nothing seems to resolve the issue. I have two questions:

 

> Is there anything else I can try to resolve the problem?

> The only remaining thing I can think of is a hard reset of the watch but will this cause me to lose all of my data? 

 

Thanks for your help.

Best Answer
Labels:
0 Votes
1 REPLY 1

‎05-31-2022 11:25

‎05-31-2022 11:25

Update: after completing a hard reset the problem persists, if there's any other way to rectify please let me know

Best Answer
0 Votes