Google Home keeps getting confused about who’s talking, but Google is on it

Google Home has had a rough few weeks, from broken automations and outages to Gemini talking to itself. Now, some users are reporting an even more basic frustration: their speakers are failing to reliably identify who’s talking. Complaints have become frequent enough that Google has stepped in, not only acknowledging the problem but also confirming that it’s working to improve Voice Match quality.

That matters because voice is still the primary way most people interact with Google Nest and Google Home speakers and displays. In a Reddit thread, users reported having to repeat commands several times before their devices would accept them, especially when adding items to shopping lists. Others said Google Home sometimes identified them as another person in the household and sent requests to the wrong personal list.

Google Nest support has now responded to those complaints, saying it has flagged the issue to the team and that work is underway to improve Voice Match quality. Google hasn’t provided a timeline for when those improvements will arrive.

We’ve flagged this to the team and they are working to improve Voice Match quality. While we work on improving Voice Match, for a more immediate way to help your experience, we recommend trying to retrain Voice Match.

For now, Google recommends retraining Voice Match through the Google Home app. If that doesn’t help, support suggests turning Voice Match off and enabling personal results instead. Google’s support documentation confirms that personal results can work without Voice Match, but there’s an obvious trade-off: anyone using that shared device could potentially access your personal results.

That workaround may get things moving again, but it also highlights why this issue is so frustrating. Voice Match is supposed to tell household members apart so that Google Home can surface the right lists, reminders, and other personal information without forcing users to deal with repeated voice-verification errors.

It’s difficult to say exactly when the problem started. The Reddit reports Google responded to are about a week old, though some users say they’ve experienced unreliable Voice Match behavior for much longer.

Still, Google’s acknowledgment is a positive step. But what it hasn’t said is when the fix will arrive. We’re hoping the fix arrives sooner rather than later.