Everytime I say 12 my google hears 1 - 2

[tereev]

I want to set a 12 minute timer but when I say the word twelve google does 1 - 2 and will only do a 2 minute timer.  I have to spell the word twelve for google to understand.  When I ask for the timer it comes up as twelve while I am talking but then changes to 1 - 2 when it sets the timer.??

[Alex_S]

Hi tereev,
 

That’s odd. When did you first notice it? Have you already taken any troubleshooting steps? If not, try to unplug its power cord for 2 minutes > Plug it back in, and test again. If the issue persists, check if other members in your home get the same behavior if they use Google Nest Hub Max to set a 12-minute timer.

Regards,
Alex

[credmond]

This is also happening to me and has been for a couple of months.

[Alex_S]

Hello credmond,
 

Thanks for posting. Have you already tried to factory reset your Google Home device and then set it up? 

Kind regards,
Alex

[credmond]

Just did a full reset. Problem still persists. Exact same as described by OP. 

[Alex_S]

Hi there,
 

That’s strange. Can you share with us a video showing this behavior? Also, kindly get its Cast firmware and Fuchsia/software version. Swipe up from the bottom of the screen > Settings > Device information.

Best,
Alex

[credmond]

Sure, https://youtu.be/K4H-ROV7Ty8?si=Lc8HrutSLsNv92H8

[83ldn]

Noticed this too today

[Alex_S · Accepted solution]

Hey there,
 

credmond, thanks for the video. What is the language and region set on your Google Nest Hub 2nd gen? Try to set English US as the primary language > Force close the Google Home app > Reboot the Google Nest Hub 2nd gen device > Give it another command. I’ll look forward to your response.

83ldn, have you had the chance to try the suggestions above? Can you also provide the Cast firmware and Fuchsia/software version of your Google Home/Nest device?

Warmly,
Alex

[credmond]

It was English (Ireland), I changed it to English (United States), and the same problem occurs (and her accent changed, so I know it was applied). You can clearly see it hears "12" but adjusts it to "1 - 2".

I didn't see anywhere to change a "region" beyond the language settings.

Note, this problem does not happen on my phone (same "Assistant").

[Alex_S]

Hi credmond,
 

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

Thanks,
Alex

[Alex_S]

Hey credmond,
 

We haven’t seen your form submission come through—were you able to access it alright? Let us know if you’re running into trouble or still need our help.

Sincerely,
Alex

[Alex_S]

Hi everyone,
 

credmond, 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 so the team can further assist you. If you have other questions or concerns aside from this, let me know.
 

83ldn, were you able to fix your Google Home device? 

Best regards,
Alex

[Artee60]

I have the same problem, language is en-gb as that is the closest to my location, which is Ireland. System firmware is 12.20230611.1.67, cast firmware is 1.70.377722. 

[Barry2217]

I have found that if I say “ set a timer for 12 minutes” it sets one for two minutes however if I say “ set a 12 minute timer” it will set one for 12 minutes.I’ve tried this on two of my assistants and the result is always the same.🤷‍♂️

[Redtembo]

This works for me too. Just have to reprogram my brain now! 

[83ldn]

No, still not working. I’ve just started to ask for an eleven minute and 59 second timer if I need a 12 minute countdown. Was working fine until a few weeks ago. 

[Alex_S]

Hello there,
 

Have you had the chance to try the troubleshooting steps above? I marked it as a recommended answer for the meantime. Let me know if it will fix this issue.

Kind regards,
Alex

[Darat]

No, it doesn't change anything. There is at the moment no solution people with devices can use apart from setting a timer for "11 minutes and 59 seconds" to get near to a 12 minute timer! This is device independent, it happens on phones, displays, speakers, on all devices that use Googel Assistant. You must have access to a Google Assistant, have you tried it for yourself - it's very easy to check "Hey Google, set a timer for 12 minutes".

[credmond]

It isn't device independent. It doesn't occur on my phone, using the same Google Account, as I mentioned earlier in the thread.

[Darat]

Happens on my phone, my partner's phone and about 6 people's phones last night when we were talking about this in the pub. Happens on my 2 mini devices, happens on my two display devices, both of my tablets - one is an iPad, my watch and on my old original Google Home speaker. I think it is fair to say it is device independent!

[credmond]

Again, it doesn't happen on my phone, so it isn't device independent. Nor do any of the glitches I pointed out in my video. Your anecdotal pub and homelife observations are irrelevant unfortunately.

[Darat]

As I said it is device independent. As evidenced by the various devices it happens on, watches, phones, tablets, speakers and displays. That is the entire plethora of google hardware.

Even if it does work on your watch, it doesn't mean it isn't device independent. It means there are some devices - not type of devices - it still works on.  This affects all Google hardware types that you can set a timer with a voice command.

[credmond]

Where is there a recommended answer when it does not solve the problem or change the outcome at all?

[Alex_S]

Hi credmond,

Apologies for the confusion. I just marked the response as the "Recommended answer" for the meantime so that 83ldn can easily find the steps and give it a try. A senior specialist from our team will contact you to further check on your case.

Kind regards,
Alex 

[SJ7680]

Hi @Alex_S  also having the same issue. Tried the above steps but it is not changing anything.

[Mikeyp17982]

I've also noticed this problem occurring over the last couple of weeks, system is really struggling to work out some numbers, hearing 14 as 40, and picking up 12 as 1-2.  This has historically never been an issue, but there was an update to the unit not long ago

[drate_j]

Also started happening for me a few weeks ago. Tried all the above troubleshooting steps but no joy

[tereev]

I think it might be a glitch because mine has now stopped doing that and seems to be working properly again.

[Alix9]

Hi, I'm having the same problem as it keeps hearing "set a 12 minute timer" as "1-2" and then proceeds to set a 2 minute timer

[Alix9]

I completely unplugged my Google device and left it for 10 minutes, after restarting it, the issue seems resolved

[Alix9]

Just checked after seeing all of the responses and yep, the issue has returned for me too. Thought we'd cracked it, but sadly not

[AA75]

It is doing this for me too, last few days (UK English, I'm in the UK). Does it for all the family. Timer for 12 minutes, interprets spoken "twelve" as 1-2. Weird and annoying. 

[Gedsmith]

We have the same. 12 minute timer appears as 1-2 minute timer. 11 and 13 and all others are fine. If you ask what is 12 * 2 it works - gives 24. In UK with UK English. Have rebooted, does the same for all home members. 

[Bobutler]

We've recently started having this problem too. 12 minutes is our pasta checking time so we know it used to work. Now, 12 minutes is always interpreted as 2 on multiple mini devices.

System firmware version: 375114

Cast firmware: 2.57.375114

Language: en-GB

[Bobutler]

So I read Alix9's response and thought I'd try unplugging one for 10 minutes. Before I unplugged it, I checked to see if was still doing it and... it's fine. 12 minute timer set.

All my minis were unfailingly setting 2 (instead of 12) minute timers for about 4 weeks and suddenly, like magic, they're all ok again. Go figure.

[dustinblack]

Same Problem here. Just chiming in to follow the issue.

[Mikeyp17982]

Following Alix's response I've also powered down and then left off overnight, on restarting issue seems to have gone.

[Gedsmith]

I also have turned off the device, left it for ten minutes and restarted and it seems to have solved the problem. 

[ShivKaushal]

This was fixed for me too, but has re-appeared today 😥