I say to a Next Hub Gen 2:
"Hey Google, one hundred fifty divided by thirty four"
It recognises, "150/30 for" (shows that on screen) and gives me the result for 150/3. At no point did I say "zero" or "naught."
I re-tried it multiple times, saying "34" quickly, or more quickly.
I tried this on a Pixel 7 with a Tensor 2 chip. It heard "50/34"
There are a many issues:
Why does Assistant voice recognition typing on Android let you pause, and stay open, but Assistant on Nest Hub or Mini will act on your words the moment you pause? Why is there no "continued input window" like there's a "continued conversation" option? I'd rather have a manual word to say to get it to process what I said, then have it try to auto-determine that and get it wrong constantly, or cause me to rush, or have to think through what I want to say before I say it, instead of while I say it.
Every time I want to report an issue like this, I have to boot up a computer, write it up, and post it. I can send feedback on the device, but how can I do it accurately if it can't interpret what I'm trying to report? Why isn't there some way to flag an interaction, or manually correct feedback reports with an on screen keyboard after dictating them, like you can on Chromecast?
I hope you are beginning to see that EVERY DAY, these Google Home devices fail at doing basic things and I am forced to either
Which means there's no point to having smart home devices.
This is not the experience we want you to have, let me help you. A few questions: which Nest speakers are we working with? When did your issue begin? Were there any recent changes made?
It would help a lot if you could do a sequential reboot first:
By the way, is the wrong response happening on all commands? Could you give me another example for us to isolate further?
I look forward to your response.
Thanks for helping, MplsCustomer.