Home devices ignore last word platform

[wtfhits]

Creating new thread as previous thread was locked despite absolutely nothing being fixed.

https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Home-devices-ignore-last-word-or-syllab...

There is a fundamental issue with how our Google Home devices parse commands.

They ALL regularly actively ignore the last word or syllable that we say. This happens with all of our devices - Google Home Minis, Nest Hub, and Nest Hub 2nd Generation (so please don't bother telling me to reset the devices - they have been reset multiple times and the issue has persisted).

When we only had Google Home Mini devices, I thought it was just missing the last bit. But since we've had a Nest Hub and Nest Hub 2nd generation it's clear that it's an active decision by the model. This is because the command initially correctly appears. Then for no reason it simple removes the last bit before doing the command.

This, combined with the Assistant's random attempts to do something even when the command doesn't mean anything, can cause havoc.

A few examples:

"Set an alarm for 8am" -> "Set an alarm for 8" = sets an alarm for 8pm instead of 8am

"Turn off the light" -> "Turn off the" = "sorry, power control isn't available" (this happens ALL THE TIME)

"Turn off the light in the bedroom" -> "Turn off the light in the" = Randomly turning off a few lights throughout the house (but weirdly, not all the lights)

"Sleepy time" -> "Sleepy" = "You must be tired" (it should be the trigger for a routine)

I can't remember the exact commands involved, but it's also cancelled multiple timers at the same time before because of missing a word! It should NEVER cancel a timer without being sure that's what you asked for

[Juni]

Hi there,
 

Thanks for creating a new thread. We apologize if the previous thread was closed sooner than you would have liked. As Community Specialists, we occasionally do a bit of housekeeping to keep the conversations in our community fresh and relevant. This includes locking threads after a period of inactivity.

I know how it feels when something isn’t working as it should, so let’s get this resolved. Could you check the my activity section in your Google Home app and check the command that was recognized and the response from the assistant? Check the steps below on how to go to this page.

Check your Google Assistant activity history

1. Open the Google Home app .
2. At the top right, tap your account.
3. Tap My Activity .

It sounds like this has been quite an annoying issue for you, and it looks like you've already done a good amount of troubleshooting with your device. If you don’t mind, have you tried setting up one device to a new home structure and observe if this will make any difference? If so, how about setting it up using another Google account to further isolate the issue?

Looking forward to your response. 

Thanks,

Juni

[Muddi]

Hi wtfhits,

How's it going with your Google Nest Hub? Let us know by updating this thread and the Community will be happy to lend a hand.

Cheers,

Muddi

[Muddi]

Hey wtfhits,

Due to inactivity, I'll go ahead and lock this thread in 24 hours. Feel free to start a new thread if you need assistance with your Google speakers and we'd be glad to assist you further.
 

Cheers,

Muddi