Google Home automations did not experience a single, iOS-exclusive failure in 2026, despite user confusion about platform-specific issues. Rather, a series of overlapping problems affected both iOS and Android users, each requiring separate fixes rolled out incrementally rather than in a coordinated repair. The confusion stems partly from May’s widespread Nest app outage, which impacted all platforms equally, and partly from specific iOS crashes in the Automations tab that Google addressed independently.
The timeline reveals no announced repair date for an iOS-specific automation failure because the core problems were either cross-platform or have already been patched. Users experiencing automation issues today are more likely dealing with ongoing reliability problems—delayed notifications, inconsistent camera event triggers, or scripted automation failures—that persist across both operating systems. Understanding what actually broke and when separates real troubleshooting steps from chasing solutions for problems that may not exist on your device.
Table of Contents
- What Went Wrong With Google Home Automations Across Platforms
- The May Nest App Outage and Widespread Service Disruption
- iOS-Specific Crashes in the Automations Tab
- Scripted Automations as a Reliability Bottleneck
- Ongoing Reliability Issues Affecting Both Platforms
- The Sunset of Phone-Related Automations
- No Single iOS Repair, Multiple Staggered Fixes
- Frequently Asked Questions
What Went Wrong With Google Home Automations Across Platforms
In January 2026, Google Home users discovered that YAML-based automations created through the script editor had stopped firing entirely. However, automations built through the standard Google Home app interface continued to work normally, suggesting the problem was narrowly scoped to advanced users relying on direct code editing. A workaround emerged: editing the affected routine to add or remove a dummy “OK Google” trigger would restore functionality, though this required manual intervention for each broken automation.
This issue affected both ios and Android users equally, affecting anyone who used Home Assistant-style scripted automations or similar advanced configuration methods. That same month, Google discontinued phone-related automations entirely across all platforms, removing the ability to set Do Not Disturb status, read battery percentage, or adjust device volume through automations. This was not an iOS-specific deprecation—it was a universal decision to sunset these capabilities. Many users with automations relying on phone-detection or device state missed the discontinuation until their routines silently stopped executing, creating the false impression of platform-specific breakage.
The May Nest App Outage and Widespread Service Disruption
On May 15, 2026, both iOS and Android Nest app users woke to an error message: “There was a problem connecting to the Nest service.” The outage lasted several hours and affected Nest functionality equally across both platforms, making it a rare moment where neither iOS nor Android users had an advantage. This incident was particularly frustrating because Nest app users could not fall back to the full Google Home app—the Nest app is purpose-built for controlling smart home security products, and service unavailability meant temporary loss of control over cameras, locks, and other devices.
The Nest outage demonstrated a critical limitation in Google’s architecture: a single service failure can cascade across an entire ecosystem. Users could not receive camera alerts, adjust security settings, or unlock doors during the outage period. While Google restored service relatively quickly, the incident highlighted that iOS users were not uniquely vulnerable; the problem was systemic and affected the platform at its foundation rather than at the operating system level.
iOS-Specific Crashes in the Automations Tab
Google did address iOS-specific stability issues in its app. Users reported that switching to the automations tab on certain iOS devices would trigger a crash, preventing them from viewing or editing automations at all. Additionally, the Wi-Fi category and Climate category within automations crashed on some iOS devices, as did tapping notification permission settings.
These were genuine platform-specific bugs—Android users could navigate these sections without crashes. Google fixed these crashes through app updates, though the rollout was gradual and some users reported crashes persisting longer than others. A user unable to access the Automations tab on their iPhone due to repeated crashes faced a real barrier to managing their routines, but once the fix reached their device via app store distribution, the problem resolved. These crashes were not indicators of broader automation failure; they were UI stability issues that prevented access to an otherwise functional system.
Scripted Automations as a Reliability Bottleneck
For users relying on advanced scripted automations, the January 2026 incident represented the most significant failure. Unlike standard automations, which fired reliably once fixes were applied, scripted automations required users to understand YAML syntax and the underlying automation trigger structure—a skill most casual users lacked. When scripted automations stopped firing, workarounds were not immediately obvious.
The dummy trigger workaround (editing the routine to toggle an “OK Google” condition off and back on) proved effective but unintuitive. Users had to know this trick existed, or they remained stuck with broken automations indefinitely. This created a two-tier support experience: standard automation users saw fixes arrive via app updates, while scripted automation users had to manually re-engage each routine. The limitation here is that Google Home has never provided a one-click “repair all automations” tool, leaving advanced users to diagnose and fix each routine individually.
Ongoing Reliability Issues Affecting Both Platforms
Beyond the specific incidents of January and May, persistent reports describe automations that fail to fire consistently. Automations involving camera events—such as “send me a notification when motion is detected”—experience delays or skip notifications entirely. Presence detection automations, which trigger based on whether household members are home or away, sometimes misfire or fail to execute at all. Multi-step routines, where one action should trigger a series of others, sometimes halt mid-sequence.
These ongoing issues are not iOS-exclusive; they appear in user reports from both platforms with equal frequency. The root causes remain unclear—whether they stem from cloud infrastructure overload, network routing problems, or bugs in how automations queue and execute. Google’s support documentation acknowledges automation failures as a known issue without providing a specific timeline for resolution. Users experiencing these problems are advised to simplify their automations, avoid complex multi-step routines, and rely on motion sensors with their own notification systems rather than depending solely on Home automation notifications.
The Sunset of Phone-Related Automations
In May 2026, Google’s quiet discontinuation of phone-related automations removed capabilities that some users had built entire routines around. Automations that checked device battery percentage, toggled Do Not Disturb, or changed volume settings no longer function. Users who relied on these features to create context-aware automations—for example, a routine that disables automations when a phone’s battery drops below 20 percent—lost that functionality overnight with no migration path or warning.
Unlike the crashes and outages that were fixed, this discontinuation is permanent. There is no repair coming, no iOS-specific workaround, and no way to restore the feature. Users must redesign their automations to work around the removed capabilities or accept the loss of that control layer. This represents the clearest example of a platform-wide limitation rather than a bug: Google made a product decision to remove features, and both iOS and Android users must adapt.
No Single iOS Repair, Multiple Staggered Fixes
There is no announced “repair date” for iOS automations because the problems were never singular and never exclusively iOS-focused. Google has released fixes incrementally: app updates addressing crashes, backend adjustments to the Nest service, and script editor patches for YAML automations. These rolled out as part of regular maintenance cycles rather than as a coordinated iOS recovery effort.
Users on older app versions may still experience crashes or failures that were fixed months ago, but the user must manually update their app—there is no forced repair that arrives on a schedule. The frustration many iOS users experienced stemmed from feeling abandoned by platform-specific problems, but the reality is messier: most issues were cross-platform, some were already fixed, and some (like the phone automations sunset) were intentional product decisions. For users still experiencing automation failures in 2026, the solution is not to wait for a repair but to audit their existing automations, check app version currency, and redesign routines around the current limitations of the platform.
- —
Frequently Asked Questions
Did Google Home automations fail exclusively on iOS?
No. The Nest app outage, scripted automation failures, and most reliability issues affected both iOS and Android users equally. Some iOS-specific crashes in the Automations tab were fixed separately, but the core problems were cross-platform.
When will Google fix automations that don’t fire consistently?
Google has not announced a specific repair date for ongoing reliability issues like delayed notifications or missed camera triggers. These persist on both platforms and appear to be a known limitation rather than a bug with a pending fix.
Can I use a workaround for broken scripted automations?
Yes. If a YAML-based automation stops firing, editing the routine to toggle an “OK Google” trigger condition off and back on will usually restore it. This must be done manually for each affected automation.
Are phone-related automations coming back?
No. Google permanently discontinued automations involving Do Not Disturb, battery percentage, and volume control across all platforms in May 2026. No repair or restoration is planned.
Should I update my iOS app to fix automations?
Update to the latest version if you experience crashes when accessing the Automations tab or specific categories. However, if automations are simply not firing, app updates alone may not resolve the issue.
What’s the difference between standard and scripted automations?
Standard automations are built through the Google Home app interface and have remained stable. Scripted automations use YAML code and experienced failures in January 2026 that required manual fixes per automation.
