Google is working to fix two more frustrating Home bugs affecting routines and smart lights

Smart speakers earn their keep in the little moments: turning off a light from bed, setting a kitchen timer, or launching a morning routine when your alarm goes off. You barely notice how useful that is until a basic command suddenly goes nowhere. Google Home has had several of those moments lately, from broken TV automations to weird accent glitches, and now users are reporting a fresh round of trouble with alarms and routines. The good news? Google says it knows about the problem and is working on a fix.

The main complaint involves alarm-linked Google Assistant routines in the Google Clock app. Users say tapping “Add Google Assistant Routine” or trying to edit an existing alarm routine can dump them into Google Assistant settings instead of the routine editor. Others report previously configured routines no longer firing after dismissing an alarm.

The behavior is inconsistent. Some said the feature briefly worked again before breaking again, while others found that uninstalling recent Google app updates restored it. That workaround did not help everyone, so the exact trigger remains unclear.

Google Nest support has now acknowledged the issue, saying its team is actively working on a fix and will update users once it rolls out.

This appears different from the alarm bug Google fixed last month. That earlier problem prevented some Nest speakers, displays, and Assistant- or Gemini-powered devices from setting alarms correctly through voice commands. These newer reports primarily concern routines attached to alarms in Google Clock, although complaints about failed voice timers suggest Google may still have related reliability problems to investigate. Google has asked one affected timer user to submit a voice feedback report.

Alarms are not the only headache. Another user says Nest Minis stopped controlling lights with Swedish names, even though English names still work. Google has confirmed the issue as well and says a fix should arrive within 24 to 48 hours. Notably, the user says they are still using Google Assistant, not Gemini, so this particular bug cannot be blamed solely on the Gemini transition.