Google Home phone actions are being discontinued from smart home automations in the first week of May 2026, Google confirmed after user notifications sparked confusion about whether the entire automations feature was being axed. The company is not killing automations—only the phone-specific controls that let users check battery levels, toggle Do Not Disturb, or adjust phone volume through their smart home routines.
Key Takeaways
- Google Home phone actions disappear May 2026, but automations feature remains fully functional.
- Affected controls: battery check, Do Not Disturb toggle, phone volume adjustment.
- Home-related automations (Nest Hub, Nest Mini) continue working without interruption.
- Only users with phone actions in existing routines will see removal notifications.
- Phone actions required starting automation from the phone itself, not from Nest displays.
What Google Home Phone Actions Are Being Removed
Google Home phone actions refer to three specific automation capabilities: checking your phone’s battery level, setting or unsetting Do Not Disturb mode, and controlling your phone’s volume from within a routine. These actions appeared in automations triggered by voice commands like “Good morning,” “Good night,” or “I’m home,” typically displayed on Nest speakers and smart displays. The removal affects any user who built these phone controls into their existing routines.
The distinction Google is making matters: automations themselves—the entire feature that lets users create triggered actions in their smart homes—are staying put. What’s vanishing is the narrow slice of those automations that controlled phone behavior. Home-related actions, such as controlling a Nest Hub, Nest Mini, or other smart home devices, remain fully supported and will continue functioning normally.
Why This Change Matters for Google Home Users
The confusion around this announcement reveals why the distinction matters. When Google Nest Community Specialist jenniffert responded to user concerns, they acknowledged the frustration: “I realize how inconvenient it is to lose features you rely on for your ‘Goodnight’ routine, as I know how important it is for your smart home to function as expected”. For users who set Do Not Disturb automatically before bed or silenced their phone as part of a morning routine, this removal breaks a workflow that felt seamless.
The timing is also worth noting. Rumors circulated in mid-to-late April 2026 after users received notifications on their devices warning that “phone actions and automations will no longer be available starting in the first week of May”. That vague phrasing triggered panic that Google was abandoning automations entirely, when in reality only phone-specific controls were on the chopping block. Google’s clarification came after the damage was done—users had already started worrying about losing a core smart home feature.
How Google Home Phone Actions Worked
Phone actions required a specific setup: the automation had to be triggered from your phone, not from a Nest Hub or other smart display. This architectural limitation meant these controls were always somewhat niche compared to home-based automations, which could run from any device in your ecosystem. A user might say “Hey Google, good night” on their phone to trigger a routine that set DND and lowered volume, but the same voice command on a Nest Hub couldn’t execute those phone actions. This limitation likely contributed to Google’s decision to deprecate the feature—supporting phone-initiated automations created complexity across the ecosystem without reaching the majority of users.
Will Your Other Automations Be Affected
No. Google was explicit: “We are not removing automations in May. We are removing phone-related actions in automations (i.e., check the battery level, set/unset Do Not Disturb, and set the volume of your phone). Home automations will continue to work, and any Home-related actions will remain part of your automations and fully functional”. If your routines control lights, adjust thermostats, lock doors, or manage other smart home devices, they will keep working unchanged. Only the three phone-specific actions are being removed.
Users will receive notifications only if they actually have phone actions in their automations. If you’ve never used these features, you won’t see a warning or experience any disruption. Google’s approach here is targeted—only notify the affected users, not the entire user base.
What You Should Do Before May 2026
If you’ve built phone actions into your routines, you have until the first week of May to decide whether to remove those actions manually or let Google remove them automatically. Removing them now gives you control over the process and prevents surprises when the deadline hits. Open your Google Home app, review any automations that include battery checks, DND toggles, or volume controls, and either delete those specific actions or delete the entire routine if phone control was its only purpose.
For users relying on these automations, no direct replacement exists within Google’s ecosystem. The company has not announced an alternative way to automate these phone functions through Google Home. This is a deprecation without a migration path, which is why the community response has been frustrated despite Google’s clarification that the broader automations feature survives.
How This Compares to Google’s Smart Home Direction
This move reflects Google’s broader focus on home-centric automation rather than phone-centric control. Amazon Alexa and Apple HomeKit both emphasize controlling home devices over controlling the phone itself, making Google’s decision to eliminate phone actions consistent with industry trends toward unified smart home ecosystems. Google is consolidating its automation platform around what it does best: managing connected home devices, not phone settings.
Why Did Google Make This Decision
Google has not publicly explained the reasoning behind the removal, but the technical architecture suggests efficiency. Phone actions required the automation to originate from the phone, creating a separate code path from home-based automations that can trigger from any device. Removing this edge case simplifies the automation engine and reduces the surface area for bugs and inconsistencies. For a company managing millions of smart home automations globally, eliminating a rarely-used feature that complicates the platform makes sense operationally.
When Exactly Does This Happen
The first week of May 2026 is the cutoff. Google has not specified an exact date, only a week-long window. Users should expect the removal to take effect sometime between May 1 and May 7, 2026. If you have phone actions in automations, plan to address them before that window closes.
Can You Still Use Phone Actions After May
No. Once the first week of May arrives, phone-related actions will no longer be available in automations. Google is not offering a grace period or a way to keep using these features after the deadline. This is a hard cutoff, not a gradual deprecation.
What If I Rely Heavily on Phone Automations
Unfortunately, Google is not providing an in-ecosystem alternative. Users who depend on automating Do Not Disturb, battery checks, or volume control through Google Home will need to find workarounds outside the platform—perhaps using Android’s native automation tools like Tasker or IFTTT if they want to preserve similar functionality. This is a gap that Google’s competitors (particularly Apple, which integrates iPhone automation deeply into HomeKit) handle differently, though those ecosystems come with their own trade-offs and limitations.
The removal of Google Home phone actions represents a strategic narrowing of the platform’s scope, not a sign that automations themselves are at risk. Users with home-focused routines can breathe easy—their automations will persist unchanged. Those who built phone control into their smart home workflows will need to adapt before May arrives.
This article was written with AI assistance and editorially reviewed.
Source: Android Central
