Google Home glitch shows AI's vulnerabilities

Complaints have drowned Google since last week after the voice-manipulated AI speaker stopped to give a logical response to instructions.

google home
Reuters

Google Assistant has been problematic in the last few days following the outage of Google Home. Complaints have drowned Google since last week after the voice-manipulated AI speaker stopped to give a logical response to instructions.

Google Home glitch

Possibly, thousands of Google Home owners have experienced the glitch as the smart assistant, Google Assistant, went offline, shutting down requests and instructions after dropping the wake phrase "Ok Google". According to the complaints reported, the Home speaker will only respond "There was a glitch. Try again in a few seconds" or "Hmm, something went wrong".

With this glitch, it just underpins the weaknesses of artificial intelligence. Google failed to provide an explanation as to what exactly happens with Home. Mashable reports this "might just mean the company is still working to ID the exact cause of the blackout before going public".

Some critics are still hesitant about the execution of artificial intelligence in the market today. The number of people who are dipping their toes into the AIR waters is considerably massive. But it might take time for this technology to become in full swing. In this case, Google and other companies are certainly bound to run into bigger and more complex AI quandaries soon.

Google's response

On Google Home forum on the company's website, a representative suggests rebooting the device by unplugging it from the wall outlet and wait for a minute before plugging in back in.

"We want to thank everyone for all the input, feedback and patience while we worked on this issue. We hope to have fixed this issue for everyone", writes the representative. "Please do let us know if you are still experiencing any error messages after the saying 'Ok Google' or 'Hey Google'".

Google is reportedly aware of the issue since 31 May but rolled out a fix on 3 June. However, some users have still reported the glitch even until today.

This article was first published on June 8, 2017
READ MORE