Suddenly stopped working on Google home.
-
I left for work everything was working
I came back 8 hours later and it wouldn't work anymore
Now when I say, hey Google speak to triggercmd, it replies with: "I'm really sorry about this, but triggercmd is not available on devices set up for South African English"I don't know what could have changed.. Definitely not anything on my phone (which is set to USA English)
Any suggestions?
-
I'm really annoyed now... Triggercmd works via app/web, and even when I log in to Google assistant in some weird way online.. But voice commands simply keep saying its set to south Africa English... And its not!
Has anyone else had this issue?
-
When I open the assistant app... Interrupt the "Google listening" and enter my usual voice commands by typing it on the cellphone keyboard. Then GA Works
... Why would GA voice not work but GA keyboard does?
-
@atmosphere, I don't know what to do about that. For what it's worth, I see that these are the only English locales available to me in Google Assistant developer console right now:
English (United States)
English (United Kingdom)
English (Australia)
English (Canada)
English (India) -
I think it's something Google have done... All my devices are now on US English... Yet it still harps on about South African English!
-
and magically it all works again... i logged a support call with google... they eventually phoned me back to say that they were having issues after an OTA for the google home mini/hub devices.
they did not know at the time the full extent of the problems - but it had to do with routines and location/geo locked devices. it was not just triggercmd... but all other services were affected in the same way
-
@atmosphere, wow, I'm glad that was it because I had no idea what I could do about that.