Google Home made users say the weirdest thing to set an alarm, but that’s over now
It's a small fix, but a welcome one for anyone who relies on voice alarms daily.
Some Google Home devices experienced a glitch that stopped setting alarms via voice command for several days. This issue impacted both Google Assistant and Gemini for Home, affecting Nest speakers, displays, and third-party devices such as Lenovo smart displays. Google has confirmed the resolution of the bug, and tests indicate alarms are now setting and triggering as intended.
August has been a busy month for Google Home, with numerous updates enhancing Gemini for Home's intelligence and introducing new smart home capabilities. Despite these advancements, a basic function like setting an alarm unexpectedly ceased working for some users. Reddit users reported that commands like "Hey Google, set an alarm for 8:30 AM" were ignored.
Some users found that alarms would only set when the exact hour was specified, while others had to first instruct Google to set an alarm and then provide the time when prompted. Interestingly, one workaround involved saying "Hey Google, hi" before issuing the alarm command.
Written by urgent.news from Android Authority's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
