A recent bug in Google Home is causing significant frustration for users trying to set alarms for 12:30 AM. Smart speakers and displays equipped with Google Assistant, such as the Nest Hub and Nest Audio, respond to standard alarm commands. However, instead of setting the desired 12:30 AM alarm, these devices default to setting it for 12:30 PM. According to reports from users, particularly a Redditor known as ReddBroccoli, attempts to set an alarm with phrases like “Okay Google, set an alarm for twelve thirty AM” have repeatedly resulted in the same incorrect setting.
Interestingly, the only command that seems to work for setting an alarm at this time is the less conventional phrase “zero zero thirty.” This hints at a peculiar glitch where the command for midnight is not being recognized in its usual formats, leading to frustration among users who expect straightforward functionality. These types of bugs are not new for Google Home devices. Previous issues have included problems with bricked Nest Hubs and malfunctioning commands for thermostats.
While Google regularly releases updates to address these issues, the recurring nature of such problems raises questions about the reliability of their smart home technology. Although the precise cause of this latest bug remains unclear, many users recall that similar commands worked without issue in the past. In light of this frustrating experience, it may be wise for users to rely on their phones to set alarms until a fix is implemented. Google has been contacted for comments about this issue, and updates will follow as more information becomes available.
Leave a Reply