Google Home Automation Changes: What's Really Ending and What Isn't

Rumors recently swirled among Google Home users when an ambiguous message suggested that automations were being discontinued. Panic quickly spread, but the truth is far less dramatic: Google Home automations are not going away. However, Google is indeed phasing out a specific subset of features—phone-related actions. This article breaks down the confusion, explains exactly what is changing, and offers guidance on how to adapt. Below, we answer key questions to clarify the situation and help you manage your smart home setup effectively.

1. What caused the confusion about Google Home automations being killed?

An errant notification or message seen by some Google Home users hinted that automations were being eliminated. This message appeared to reference the end of automations entirely, which would have been a massive shift for the platform. However, the message was misleading. In reality, Google was referring to a narrow category of actions tied specifically to phone-based triggers and commands. The broader automation system—comprising routines, schedules, and device interactions—remains fully intact. The miscommunication likely stemmed from imprecise wording in a notice about upcoming changes. Google later clarified that only phone-related actions (such as those initiated by phone calls or SMS) are being deprecated, not the entire automation framework. Users can breathe a sigh of relief knowing their core automations are safe.

2. Are Google Home automations actually being removed?

No, Google Home automations are not being removed. The company continues to support and develop its automation platform, which allows users to create routines that control smart lights, thermostats, speakers, and more. The confusion arose from a specific subset: phone-related actions. These are actions that rely on phone state or phone-based events (e.g., “when I get a call,” “when my phone battery is low”). Google is deprecating these because they offer limited reliability and user value compared to other integration methods. All other automations—time-based, location-based, voice-triggered, and device-state-based—remain fully functional. In fact, Google is likely to expand automation capabilities in the future, focusing on more robust and cross-platform features. So if you have automations that control your living room lights at sunset or turn off your thermostat when you leave home, they will continue to work without interruption.

3. What are phone-related actions in Google Home?

Phone-related actions are a specific type of automation trigger or action that involves your phone’s native functions. For example, you might have set up a routine that silences your phone when you arrive home, or that triggers a voice announcement when you receive a call from a specific contact. These actions depend on the phone’s operating system and often require additional permissions or apps. Google has decided to remove these because they are less reliable, harder to maintain across different device brands, and can be privacy-sensitive. After the removal, such actions will no longer work. Users who rely on them will need to find alternative ways to achieve similar effects—for instance, using location-based triggers instead of call-based ones, or employing third-party services like IFTTT as a bridge. The change affects both Android and iOS phone actions, though the exact list of deprecated actions may vary.

4. Why is Google removing phone-related actions?

Google’s decision to remove phone-related actions likely stems from several factors. First, these actions have historically suffered from inconsistent performance across different phone models and operating system versions. Users often encountered bugs where a call-based automation would fail because the phone’s call detection didn’t integrate smoothly with Google Home. Second, maintaining such deep integration with phone hardware and software is resource-intensive and can conflict with privacy regulations. By eliminating phone-related actions, Google can focus its engineering efforts on more stable and widely used automation features, such as those triggered by smart home sensors, schedules, or Google Assistant voice commands. Third, the phone action feature was used by a relatively small percentage of users, making it a low priority for long-term investment. The removal aims to streamline the platform and improve overall reliability for the majority of Google Home users.

5. When will phone-related actions be removed?

Google has not announced an exact cutoff date, but the deprecation is rolling out “soon.” Some users may already see warnings in the Google Home app when editing automations that use phone actions. The change is expected to be completed within the next few months. Google typically provides a grace period for users to transition. During this time, existing phone-related actions may continue to work but will eventually stop. To avoid disruptions, users should review their automations now. Open the Google Home app, navigate to the Routines section, and look for any triggers or actions that involve phone calls, SMS, or phone status. If you find any, consider replacing them with equivalent non-phone triggers. For example, change a “when I get a call” trigger to a time-based or presence-based trigger that achieves a similar result.

6. How will this affect my existing automations?

If your automations do not rely on phone-related actions, you will see no change. All other routines—those triggered by time, location (based on your device’s GPS), voice commands, or device states (e.g., smart lock unlocked)—will continue to work normally. Only automations that specifically use the phone’s call or messaging services as a trigger or action will be affected. For example, a routine that sends you a notification when your phone battery is low will stop working after the deprecation. However, you can often replicate the functionality using alternative methods, such as setting up a custom notification in your phone’s own battery management settings. Google Home does still support location-based automations using your phone’s GPS, so you can replace a “when I arrive home” call-based action with a simple GPS arrival trigger. The key is to audit your routines and make substitutions where needed.

7. What should I do if I rely on phone-related actions?

First, don’t panic—you have time. Start by identifying any automations that use phone-related triggers or actions. In the Google Home app, go to Automations (Routines) and review each one. Look for actions like “When I get a call from…” or “When my phone is charging.” Note these down. Next, explore alternatives. For call-based triggers, you might use a smart button or a third-party service like IFTTT that bridges your phone’s call status to Google Home. However, the simplest solution is often to remove the phone action and replace it with a different trigger. For instance, if your goal was to silence your phone at home, you can set a time-based routine or use your phone’s own Do Not Disturb scheduling instead. Google also offers “presence sensing” using your phone’s location, which can replace many phone-state triggers. If you can’t find a direct substitute, you may need to adjust your workflow. As a final step, test your new routines to ensure they work as expected before the old ones are deactivated.