- A recent Google Home bug prevents smart speakers and displays from setting alarms for 12:30am.
- Google Assistant-equipped Home devices like the Nest Hub and the Nest Audio recognize standard alarm command phrasing, like “Okay Google, set an alarm for twelve thirty am,” but they set the alarm for 12:30 p.m. instead.
- Saying “zero zero thirty” aloud appears to be the only working time input for setting an alarm for 12.30am.
Update, June 16, 2025 (04:50 AM ET): A Nest spokesperson informed us that Google is aware of the issue and working on a resolution. The issue seems fixed at the time of this update, as we could no longer reproduce the bug across several Google Home devices. All of them now correctly set the alarm for 12.30am when prompted.
Original article, June 13, 2025 (06:50 AM ET): Google Home is no stranger to more than the occasional bug like bricked Nest Hubs and gimped Thermostat commands. To Google’s credit, the company does roll out updates that fix the issues, but these issues are often embarrassing to have occurred in the first place. You can now add another bug to the list, with Google Home smart speakers and smart displays strangely unable to set a very specific alarm.
