Google’s Gemini assistant is turning a routine drive into an exercise in frustration for smart home owners. According to multiple reports surfaced this week by autoevolution, Gemini fails to execute Google Home routines when drivers ask through Android Auto, even though the same commands work perfectly on the same phone just moments earlier.
A Broken Promise of Hands‑Free Control
Google pitches Gemini as a smarter, conversational upgrade for Android Auto — one that understands natural language and can handle multi‑step tasks without rigid phrasing. But for a growing number of drivers, that upgrade comes with a painful regression: the assistant simply ignores or rejects spoken commands that trigger Google Home routines.
The failure isn’t theoretical. A user report highlighted by autoevolution describes a driver who routinely unlocks a car charger after pulling into the driveway. The command works immediately on the phone while standing next to the vehicle, but when spoken through the car’s Android Auto microphone, Gemini either stays silent or returns a generic error. The charger stays locked, forcing the driver to pull out the phone manually — an act that defeats the purpose of hands‑free control.
Not every user sees the fault. Some Android Auto owners report that routines still function as expected, which points to a messy picture: the problem may stem from a specific account configuration, phone model, regional server rollout, connected‑home provider, or a silent server‑side change to Gemini. Google’s own documentation adds to the confusion. Its support pages state that the mobile Gemini app can start Google Home routines via voice or typed commands on Android, and Android Auto’s help center positions Gemini as a hands‑free assistant for compatible cars. The capability is supposed to exist, but it’s become unreliable the moment an Android Auto session takes over.
Why This Hurts More Than a Missed Reminder
Google Home routines are the glue of many smart homes. They automate sequences of actions — turning off lights, adjusting the thermostat, locking doors, starting a robot vacuum, or powering on an EV charger at a specified time. Drivers who built routines around departure (“leaving home”) and arrival (“I’m back”) rely on them to seamlessly bridge the gap between the car and the house. When those routines fail silently, the automation breaks down at the worst possible moment: when the user’s hands are on the wheel and attention should be on the road.
Google itself warns that Home controls and routines are convenience features, not safety‑ or security‑critical systems. That caveat is sensible, but it doesn’t erase the basic expectation that an assistant marketed as “hands‑free” should behave consistently whether you tap a phone or speak through a car display. Drivers who have come to trust the simple command “run my arrival routine” are now left to wonder if their smart home will respond — or if they’ll have to park, dig out the phone, and trigger the action manually.
How We Got Here: The March to Replace Assistant
Google has been steering Android users toward Gemini for more than a year. The May 2026 Android announcement made it official: Gemini for Android Auto is the designated replacement for the classic Google Assistant experience when Gemini is selected as the phone’s default assistant. The company’s marketing, including a detailed guide on android.com, promises a raft of AI‑powered improvements — summaries of group chats, smart replies, contextual navigation for coffee shops with drive‑thrus, and even generative music playlists.
But assistant migrations are judged on the mundane commands first. Before anyone asks for a summary of a chat or a fun fact about the city they’re driving through, they say “call Mom,” “navigate home,” or “run my good‑night routine.” When those fail, the glitter of AI summaries disappears.
This isn’t the first rough patch for Gemini in Android Auto. Community threads and articles on TechRadar and Tom’s Guide have chronicled a string of regressions: broken calling, misunderstood navigation requests, responses that cut off mid‑sentence, and erratic smart‑home controls. None of those complaints have been tied together by a single official Google defect, but the pattern is clear. For Windows users who remember Cortana’s uneven handoff from novelty assistant to discontinued product, the comparison is easy to draw. The question is not whether Gemini can produce richer answers; it’s whether it can reliably perform the short, repeatable actions that users built into their routines.
What You Can Do Right Now
If your Google Home routines have stopped working in the car, you have a few immediate options — though none are permanent fixes.
-
Test your setup first. Before hitting the road, try a simple routine on your phone with Gemini as the default assistant. Then plug into Android Auto and repeat the same command. If it works on the phone but not in the car, you’re likely seeing the reported bug.
-
Switch back to Google Assistant. The most reliable workaround is to revert your phone’s default assistant. Open the Gemini app, tap your profile picture, go to Settings → Digital assistants from Google, and select Google Assistant. This will restore Assistant on both the phone and Android Auto. You’ll lose Gemini’s conversational features, but basic commands and routine execution should return to normal. Bear in mind that Google has been aggressively pushing users toward Gemini, and some newer devices or regional rollouts may not offer the option to switch back. Even where the toggle exists today, it may disappear in a future update.
-
Use phone‑side workarounds. If switching assistants isn’t possible, you can manually trigger routines from your phone before starting the ignition or after parking. While this defeats hands‑free convenience, it ensures your home reacts when you still need it — especially for time‑sensitive actions like unlocking a charger or deactivating an alarm.
-
Report the issue. Google’s developer and support teams need feedback to pinpoint the problem. Adding your experience to the ongoing thread on Google’s support forums (the one titled “What happened to routines with Android Auto in Gemini?”) can help engineers connect the dots. Include your phone model, Android version, Android Auto version, Google Home device types, and a description of which routines fail.
-
Keep an eye on server‑side changes. Because the bug appears to be inconsistent — working for some and failing for others — it may stem from a server‑side configuration or A/B test rather than a client app. That means a fix could arrive without any visible update to the Gemini or Android Auto apps. Subscribe to relevant news outlets or official Google blogs for announcements.
Looking Ahead
Google hasn’t publicly acknowledged the routine‑execution gap, let alone provided a timeline for a fix. But the drumbeat of complaints on support threads and tech publications makes it likely the company is aware. For a feature as fundamental as home automation, the pressure to resolve the regression will grow as more users are migrated to Gemini.
In the longer term, the episode underscores a broader tension in Google’s AI strategy. Gemini’s ambition to be a truly conversational companion is compelling, but it cannot succeed in the car if it stumbles on the most utilitarian of tasks. Android Auto’s entire reason for existing is to keep drivers connected without distraction; when the assistant fails silently, it creates the very distraction it was meant to prevent. Windows watchers will recall that Cortana’s downfall wasn’t a lack of clever features — it was the slow erosion of trust when basic commands stopped working. Google’s assistant transition is now facing the same test.
For now, the safest bet for routine‑dependent drivers is to stick with Google Assistant where the option remains available. If you can’t switch back, test your setup frequently and be ready to use manual triggers. The promise of a smarter car assistant is still worth believing in, but it won’t arrive until the simple stuff actually works.