Google Assistant answers on the wrong device

[BroadsNet]

I have two Nest Mini's one in the kitchen and one in the bedroom. I have a Nest Hub in the lounge. When I bought these devices two years ago they worked perfectly.

The issue I have now is they answer on the wrong device.

I can stand in front of the Nest Hub in the lounge, but I can hear the Nest Mini in the bedroom answering. Conversely when sitting by the Nest Mini in the bedroom I can hear the Nest Hub in the lounge answering. Sometimes they all answer together, i.e setting a timer.

I have set the sensitivity according but this has no effect.

This is becoming really frustrating as it's obviously a firmware issue as they worked perfectly when I bought them 2 years ago.

[BasikBlack]

I have the same issue with my devices. I have a Google Hub 2nd Gen, Nest Audio speakers, nest minis, my PIXEL 6 PRO, a Pixel 6a, etc and in the beginning when I first got my PIXEL 6 PRO and the Hub, it would at least offer a text box that would pop up asking if it was answering on the correct device and if not you could choose which device you expected it to answer on. However, I have not seen this box pop up in months. It was useful in the beginning but for a very short time and now I'm having the same issues again. When I'm at home 99.9% of the time, my assistant on my PIXEL never even picks up the invocation and half of the time that's what I'm looking for. There's supposed to be a simple way to send results and screen data from the device that answered (in this case the hub or incorrect device) and have that sent to your phone. But again, that option pops up only a very small percentage of the time and if I just tell the assistant to do it, it has no idea what I'm talking about. In fact, I'm going to go a step further here and say that in the past three months I've noticed that my assistant on my various devices in my home 90% of the time, has no clue what I'm talking about and says it cannot complete the task. I'm seriously about to dub my Google hub useless because it won't do 90% of what I ask it to. I'm with ya and all ears for suggestions on this thread.

[GcHulda]

I've been having the same problem for a long time. I have multiple speakers and hubs and thought that the one closest to me should respond but it seems to be very random

[Dan_A]

Hi folks,

That certainly hasn't been easy for all of you ― let’s check this out and find the solution together. It would really help a lot if you could do a sequential reboot for all your devices. Unplug the power cord of your router followed by all your Nest speakers. Plug them back in starting with your router. Restarting your phone might also help. Once everything’s back up and running, mute your Nest speakers except for one and check if it responds to your command. Kindly check each device and tell me how it goes.

Best,

Dan

[BroadsNet]

Thanks for your suggestion Dan.

I tried this and when the other devices are muted each device worked perfectly.

[Princesss]

Hi BroadsNet,

Thanks for responding. Have you already tried to perform a complete reset to your devices?

Best,

Princess

[BroadsNet]

Yes, I tried this first as Dan suggested.

[Princesss]

Hi BroadsNet,

Thanks for trying the steps. Could you please provide the cast firmware version of your Google Nest speakers?

To check which firmware version you're on, follow these steps:

1. Open the Google Home app .
2. Touch and hold your device's tile.
3. Tap Settings Device information.
4. Under "Technical information," check for Cast firmware: "X.XXX.XXXXX." If the device is on Fuchsia, check for System firmware version: "X.XXXXXXXX.X.XXXXXXX"

Best,

Princess

[BroadsNet]

Hi Princess

Thank for getting back to me.

Both Nest Mini Speakers use the following -

System firmware version: 324896

Cast firmware: 1.56.324896

Regards

BroadsNet

[Princesss]

Hi BroadsNet,

Thanks for the additional info. Could you please uninstall and reinstall back the Google App from your phone and retrain your voice match? Let's see if these steps would work.

1. Make sure your mobile device or tablet is connected to the same Wi-Fi network or linked to the same account as your speaker or display.
2. Open the Google Home app .
3. At the top right, tap your account.
4. Verify that the Google Account shown is the one linked to your Nest speaker or display. To switch accounts, tap another account or Add another account.
5. Tap Assistant settings Voice match. You'll find a list of devices that are using Voice Match.

From here, you can:

• Retrain your voice model, if needed.
• Invite others to set up Voice Match on shared devices.
• Remove a shared device by tapping the X. This removes your Google Account (and Voice Match) from the device.
• Add new shared devices.

Let us know how it goes.

Best,
Princess

[BroadsNet]

Thanks Princess

I tried your suggestions but unfortunately it has not fixed the issue.

In the kitchen with the door closed the Nest Hub in the lounge still answers when I address the Nest Mini in the kitchen.

On occasions when I set a timer on the Nest Hub in the lounge all the devices in my house start a timer. Yet when I stand in front of the Nest Mini's the Nest Hub answers and the speakers announce - "Sorry, something went wrong. Please try again in a few seconds".

 Regards

BroadsNet 

[Muddi]

Hey BroadsNet,

Chiming in, please adjust your Nest Hub's sensitivity to "Hey Google." Follow these steps below or you can visit this link for more information about the feature.

1. Open the Google Home app.
2. At the bottom, tap Home.
3. Touch and hold your speaker or Smart Display.
4. At the top right, tap Device settings > Audio > “Hey Google” sensitivity.
5. Choose how sensitive you want Google Assistant to be when it responds to you.
   • To change this setting on another device, tap Adjust more devices.

Let me know how it goes.

Cheers,

Muddi

[BroadsNet]

Thanks for your suggestion Muddi. I already have the sensitivity set to 'Most sensitive'. It has no effect.

The issue only affects my Nest Mini's. I have no issue with a Lenovo Smart Clock.

Regards

BroadsNet 

[Princesss]

Hi BroadsNet,

We appreciate all your efforts. We'd be happy to take a look into this for you. Please fill out this form with all the needed information then let me know once done.

Best,

Princess

[Muddi]

Hi BroadsNet,

I'm just checking in if you had the chance to fill out the form?

Cheers,

Muddi

[BroadsNet]

Thanks Muddi

I've been a bit busy with the holidays but I will fill in the form.

Regards

BroadsNet

[Dan_A]

Hi BroadsNet,

Thanks for the heads-up and we understand, with the holidays and all. Take your time and enjoy. If in case, here's the form to fill out.

Cheers,

Dan

[Dan_A]

Hey there,

@BroadsNet, we got your form — thanks for filling it out. Our team will reach out to you via email anytime soon. Please continue the conversation there.

@BasikBlack, @GcHulda, have you had the chance to try the steps provided? If so, how was it?

Thanks,

Dan

[BasikBlack]

Yeah, my entire Google Home has been nightmare these past couple weeks with the updates and nothing has wanted to work properly, some things stopped working, some couldn't be added back. I ended up factory resetting most of Google devices just to get them properly set in the home app to be functional. 

I know all about the sensitivity setting and I do use it and did previously and it helped a little bit nothing majorly noticeable. 

That said, I've got have over a dozen devices in a condo about 1,000 SQ ft so there's going to be a little room for error. However, since factory resetting most of them and reading them to home, I am finally getting the alerts on my phone again asking me if this is the correct speaker and when answering I've noticed. So far it seems like they're setting back to a more accurate and functional home. 

I guess time will tell. But I'll also be moving in about a month so I'll get to set up the whole thing again soon enough 😆. 

[Dan_A]

Hi BasikBlack,

We're glad to hear that your Nest devices are slowly getting back its spunk and we appreciate you sharing it in the Community. Keep monitoring on the behavior, if it persists or, if you have other questions or concerns, you know where to find us. 

It looks like we can consider this one complete, so I will lock the thread in 24 hours and we wish you a Happy New Year!

Kind regards,

Dan