Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New Voice Assistant Issue

2249581
11 months ago

I've run into a Voice Assistant Issue I haven't seen reported before. I'm using a Venu 2 Plus with a Pixel 7 Pro, and the Voice Assistant on the watch is usually able to connect when I trigger it, but about half the time Google Assistant won't activate. The watch shows the microphone icon like it's supposed to, but instead of Assistant appearing on my phone, the screen will just flash black for a second. The phone shows the little green microphone icon at the top of the screen, but I get no response from Assistant.

Has anyone else run into this? I've already tried rebooting the phone and watch, removing/re-pairing the watch, and even factory resetting the watch, but it doesn't make a difference.

I'm running Android 14 on the phone and 17.04 on the watch.

  • 0 7 months ago in reply to 2249581
    2249581 said:
    To make it work, you'll need to update the device name and MAC address in the "Garmin Connected" profile.

    Can you explain this more for us beginners? I can get to the Garmin Connected profile and can see a Name field that says Optional and and Address field with an address in it - but where do I find my data?

  • 0 7 months ago in reply to Al P

    Go into tasker 

    Tap on the Garmin connected profile

    In there tap on BT connected

    Delete address that's in there

    Tap search icon and find your watch, so it populates that field

    When back out, tap Heavy check mark️ at top right

    You should be five

  • 0 7 months ago in reply to Al P

    If you click the little magnifying glass next to Name or Address on the State Edit screen, you can choose the Garmin from the list of your paired devices. Either Name or Address will work - you don't have to use both.

  • 0 7 months ago in reply to 2249581

    What did you find worked best for the %msToWait variable?

  • 0 7 months ago in reply to 2249581

    LOL thanks. I was clicking the option to show available commands, I did not think to click the search icon. Open mouth

  • 0 7 months ago in reply to 6057581

    I have it set to 1500 right now. For me that seems to be the best balance between not waiting too long to retry and not retrying prematurely.

  • 0 7 months ago in reply to 2249581

    Kudos to you this works really well! Assistant still gets confused sometimes if you get new messages when replying to current messages, and I also noticed that sometime it leaves the assistant dialog live on your phone screen and then it will not take new commands when you try to invoke it again. But thise seem to be more Google Assistant issues than watch issues.

    Do you have a Tasker setup that reads your messages and prompts you for a reply from other BT devices? Something that could be used to receive and reply to messages in the car if you have BT but no Android Auto.

  • 0 7 months ago in reply to 2249581
    2249581 said:
    I have it set to 1500 right now. For me that seems to be the best balance between not waiting too long to retry and not retrying prematurely.

    Where did you set this? I see a Wait step (14) but it looks like the input goes from 0-59. Maybe you use 15?

  • 0 7 months ago in reply to Al P

    Glad it works for you too. There are definitely some imperfections and hiccups, but it's a big improvement over "works half the time if you're lucky". I don't have any other Tasker projects at the moment, but I bet someone has developed something like what you're describing.

  • 0 7 months ago in reply to Al P

    You don't have to update the task itself to change the wait time. Just change the %msToWait value in the VARS tab.