Google Mini and my Samsung phone both answer when I say "Hey/Okay Google"

[Rdianco]

Disclaimer: This thread was migrated from our previous version of the Google Nest Community. You can continue to receive updates on your thread issue here or simply ask, browse or more in the new Google Nest Community.

Original poster: Mason W 

I've read the other posts about being on the same account. I am. My phone and mini used to work in harmony, and now they both trigger and I get two simultaneous or slightly delayed responses. Especially annoying with timers. 

My only solution would be turn the phones assistant off, but then I can't send my shopping list over, amongst various things.

[Rdianco]

Hello Mason W,

Thank you for your message. No worries, let's look into this issue to have your Google Nest Mini and Samsung phone respond at their respective times. I would be more than happy to help.

Your best solution to this issue would be adjusting your "Hey Google" sensitivity so that both devices aren't responding at the same time. Here are the steps: 

Set Google Assistant’s “Hey Google” sensitivity
IMPORTANT: When you adjust the “Hey Google” sensitivity for a device, it applies to anyone who uses that device.

1. Make sure the mobile device is connected to the same Wi-Fi or linked to the same account as the Google Nest or Home device.
2. Open the Google Home app .
3.  Tap the device card of the preferred speaker or display.
4. At the top right, tap Settings   Audio  “Hey Google” sensitivity.
5. Use the slider to raise or lower the device's sensitivity to make it more or less responsive to "Hey Google".

With adjusting and customizing the sensitivity for each device, you can shape which device responds.

Please feel free to reach out with any other questions or concerns you may have. Thanks!

- From Frances (Community Specialist)

[MissyLee5]

This issue has been happening to me too for a few months now. Every single time I use the phrase my phone will respond first, shortly followed by my Google home mini. Both will complete the command, which is incredibly frustrating, especially when it comes to my nighttime routine which includes playing relaxation sounds. Unless I tap away from the Google screen on my phone, both my phone and the mini will respond & play relaxation sounds. Both devices are on the same network, up to date, and nothing has changed other than this issue. It began one day and never stopped. I've tried unplugging the speakers as well. I don't want to adjust my sensitivity on my phone, because half the time when I'm away from home my phone doesn't respond already. At home, it always responds along with the minis without fail. When will this issue be fixed? 

[Jeff]

Hey, all.

Sometimes when you have multiple devices with Assistant, you can run into some confusing situations. I'm sorry that you've  been seeing Assistant respond differently than you'd like, but I have some information that should help you sort it out.

This article shows you how to handle the Assistant response between your phone and your devices on a home network: https://bit.ly/31tyDI9

If you run through the steps suggested there and still have issues, please let me know and we can look at other steps to take.

Thanks!

[MissyLee5]

Jeff, I have already done all of these steps multiple times. The devices are connected to my account, but everyone else has the same problem when trying to use the assistant. The phone answers first (no matter if you are closer to the speaker than your phone or not), then the Google home answers about 10-15 seconds later. So everything is doubled. My nighttime routine will play relaxation sounds on both my phone & Google mini, I'll have 2 timers/alarms 10-15 seconds apart, etc. There are many others who are having this issue as you can see by doing a simple Google search. It has been going on for months now. There must be a known issue, if there isn't a fix currently then Google needs to issue an update to correct this problem. It is extremely obnoxious & makes it very difficult to use the assistant when both the phone & speaker are talking over each other. 

[Gurr]

I am having the same issue. Just started about 2 days ago. Trying to find a solution. Actually started when I made my pixel 6 update for January. 

[MissyLee5]

Anything else I can try? As I stated above, I've already done these steps and nothing has changed. 

[Jake]

Hey all,

Sorry for the late reply. I wanted to follow up and see if you are still in need of any help? Please let me know if you are still having any trouble from here, as I would be happy to take a closer look and assist you further. 

Best regards,
Jake

[MissyLee5]

Yes, the issue has never been resolved. I've tried all of the recommended steps and still getting double responses. 

[gloamcreature]

Yes, still having this issue. Happened as recently as yesterday.

[Jake]

Hey all,

Sorry again for the late reply, and to hear you are still having trouble with the device. Do you mind me asking what troubleshooting steps you have already tried? I would be happy to reivew, and assist you further with the issue. Please let me know.

Best regards,

Jake

[MissyLee5]

The steps I followed were sent to me in a previous response in this thread. Specifically....

"This article shows you how to handle the Assistant response between your phone and your devices on a home network: https://bit.ly/31tyDI9

If you run through the steps suggested there and still have issues, please let me know and we can look at other steps to take."

I followed the steps given in that article. Making sure both device are on the same wifi & under the same Gmail account. Resetting the Google mini. I even got a new phone recently and issue still persists. This issue is not uncommon, I have seen many people complain about this for about a year now. Surely Google must recognize this issue and be working on a fix after a year? 

[Jake]

Hey all,

Sorry for the delayed reply once again. I wanted to follow up and see if you are still having issues with your device. Please let me know, as I would be happy to escalate this to a higher team.

Best regards,

Jake

[Mariah245]

The issue still persists for me. At least once, my phone assistant popped up and asked me which device I expected to respond to my last request, and I told it the nest mini. It hasn't changed. I have to ignore my phone saying "Sure. But first you'll have to unlock your device." and just keep repeating the request. (like turn on the lights) Eventually the speaker will respond, but it's horribly delayed. My husband wants me to throw it out because it is so inconvenient. 

[gloamcreature]

Yes. Same as Mariah245. 

[MissyLee5]

Yes Jake, this issue has been going on for a long time as you can see as this post originated nearly a year ago and had been going on for some time prior to. Every few months I get an unhelpful response like "please let me know if this issue is still happening". So please do escalate this.

It's been incredibly aggravating having to watch my phone every time I say they phrase and tap the back button to get my Google home mini to reply and not my phone. I'm about to just turn off assistant response on my phone and use Bixby when I need my phone to do something as it's far more intelligent than Google anyway. 

[MissyLee5]

Forgot to mention, I also had the same question pop up like Mariah said, and selected my mini and still my phone persists. 

[Jake]

Hey all,

I am truly sorry for the trouble and frustration that you are having with the device. I understand that is not the most ideal situation, and I am more than happy to assist. Since you have exhausted all troubleshooting steps, I would like to escalate this to a higher team.

If you could please fill out this form, our Team would then be in contact with you for additional support. Please let me know if you have any questions from here as well.

Best regards,
Jake

[MissyLee5]

Done. 

[Jake]

Hey there, 

It looks like we received your filled out form, and we have passed this on to the correct team where they will be reaching out to you about your issue. I'm going to go ahead and lock this thread.

Best regards,

Jake

[gloamcreature]

Hi, 

I'm having the same issue. The article you linked claims says under the section "Talk to Google Home":

Say "Hey Google." (Your phone shouldn’t respond).

However, my phone DOES respond. I never want it to respond when I'm at home. I have 3 Nest/home minis and at any place in my house, at least one of them can hear me. (I know this because sometimes 2 of them will set 2 separate timers when I ask for one; not being able to sync timers across devices is a complaint for another day).

This is particularly annoying because I have my phone voice locked for when I'm away from the house. I shouldn't have to change my security settings on my phone to be able to turn lights on and off in my own house.

[Mariah245]

My Samsung phone and Google mini speakers worked seamlessly untill a pretty big Samsung update a few months ago. Now the mini speaker is practically worthless. When I say hey Google turn on the lights, the mini will light up and think, then my phone assistant will say "ok, but first you have to unlock your device." If I repeat the same thing again, sometimes the speaker will finally turn on the lights, but not always. I can't help but feel this is a problem with Samsung, because after the update is when the problems started. Either way, the mini speaker is pretty much useless at this point, and it has made controlling all my smart devices with my voice more of a nuisance than it's worth. 

[gloamcreature]

I've had this issue for well over a year, so for me does not seem Samsung update related. I had the issue with my phone responding (and not completing the action) last night. I also followed all the steps in that article. I would love for only my Nest devices to respond when I'm home, but the most frustrating thing is the Assistant telling me I need to unlock my device to complete simple tasks like turning on the lights when my settings are already set to being able to use Assistant when my screen is locked.

[yerzhl]

Hi any Google Support here? I don't see any solution to this thread and it's almost a year since this thread started. This bug really annoys me. Please fix the issue asap. At least give us some update what google have done to this issue, and not hanging like this.