Gemini for Home Is Failing the Basics, Users Say

Google’s Gemini for Home was supposed to make voice control smarter. Instead, a growing number of Google Home owners say the switch to Gemini made the basics worse — wrong lights, failed routines, and long delays for commands that used to just work. With no official way back to the old Google Assistant, some frustrated users are rebuilding their voice control around Home Assistant instead.

The latest account comes from XDA Developers, where a writer described moving his voice control to Home Assistant on November 14, 2026, after Gemini repeatedly mishandled everyday commands. It is not an isolated complaint: a second XDA piece a week earlier, a How-To Geek column in October, and a thread on Google’s own support forum describe the same pattern.

“Kitchen light number two” turned on every light

The November 14 XDA report centers on the kind of precise, high-frequency commands that smart homes run dozens of times a day. Asking Google to switch on “kitchen light number two” switched on all of the kitchen lights — and the assistant reported success anyway. Custom automations and routines tied to explicit phrase triggers frequently fail or misfire since the Gemini migration, the author wrote, and neither relinking third-party device accounts nor rebuilding routines in the Google Home app fixes the problem. He traced it to what he called core entity-mapping regressions caused by Gemini: the assistant no longer reliably knows which device a command refers to.

The delays are just as striking. The author reported waiting in darkness for more than eight seconds for lights to switch on, along with far more “Sorry, I couldn’t reach X device” errors and phantom success confirmations — the assistant claiming a command worked when nothing happened. A separate XDA piece published November 7 described the same eight-second waits on Nest speakers and the same conclusion: the writer replaced cloud-dependent speakers with a local voice setup.

How-To Geek’s October 24 column painted a broader picture, pointing to the r/GoogleHome subreddit, where departure announcements have become common. “The things Google Home used to do well, have become a chore,” one user wrote there; another estimated that “easily a third of my commands have some form of unexpected response.” The column also described a particularly maddening failure mode: Google Home often responds that it cannot play a song or turn off a device, then executes the command when the user follows up with “yes, you can.”

The same complaints on Google’s own forum

The frustration is not limited to tech publications. A user posting on Google’s support forum under the name Banano78 wrote that basic smart home functionality “that worked reliably for years has become unreliable or simply stopped working” since the move from Google Assistant to Gemini for Home. The routines themselves are fine — they work when started manually, the user wrote — which points the finger at Gemini rather than the devices.

The examples are specific. A Bedtime routine that switches off the TV and lights no longer starts reliably by voice. On a Galaxy Watch 5 Pro, Gemini says “I can’t start routines,” even though the same routine can be started manually from Google Home on the watch. Basic voice commands on a Nest Hub, including setting an alarm, have become unreliable, and commands given on one device sometimes produce unexpected spoken feedback on other devices in the house. Sometimes, the user wrote, Gemini appears to interpret a smart home command itself instead of simply executing the existing routine, producing a different or incomplete action.

Perhaps the most telling detail: the user did not choose the switch. Gemini for Home is still described as Early Access, the post notes, “yet returning my Home to Google Assistant is apparently no longer possible.” The plea was direct: prioritize reliability and feature parity, and at least let users who hit regressions temporarily switch back.

Why a large language model struggles with light switches

There is a technical reason behind the pattern. Google Assistant used rule-based intent parsing: a command matched a known pattern and executed a known action. Gemini replaces that with a large language model that interprets natural language — powerful for open-ended conversation, but probabilistic where a light switch demands determinism. As the November 14 XDA piece put it, toggling a specific light, adjusting a thermostat set point, or triggering a custom routine requires deterministic precision rather than natural language creativity.

The architecture adds latency at every step. As described by XDA, each voice request now requires audio digitizing, cloud streaming, Gemini model inference, tool payload formatting, and a round trip to third-party cloud APIs. Cloud voice assistants already routed commands through vendor servers even when the device sat a few feet away on the same local network; adding LLM inference on top of that round trip made simple commands slower, not faster.

What Google has fixed — and what is still missing

To be fair, Google has been patching. A bug-fix update on September 2, 2026, addressed several problems that frustrated early-access users, including broken alarm and list creation, Gemini garbling combined commands such as “turn off the lights and stop the music,” and a Settings bug that wrongly told some users Google Keep was no longer supported. Google’s November 11 update, covered here earlier this week, added visual answers, faster timers and Broadcasts, plus Google Home app upgrades including Eco Mode Everywhere and digital home keys in Google Wallet.

But gaps remain. According to a detailed rundown of the September update, Gemini for Home still lacks default app selection, so users cannot set a preferred music or news service and must name the app in every request. Interpreter Mode, the real-time two-way translation feature, is absent entirely — Google moved it into the standalone Google Translate app. Quick Phrases, which let users trigger routines without saying “Hey Google,” are gone, and the settings menu is noticeably thinner than the old Assistant’s.

The broader context matters too. Google began retiring the old Google Assistant from Android phones, tablets, Wear OS watches, and compatible earbuds on September 4, 2026. Smart speakers and Nest displays move to Gemini on a separate, unconfirmed timeline, and Gemini for Home remains an opt-in early-access rollout for those devices — but for users already moved over, the door back appears closed.

Why Home Assistant is the escape hatch

That combination — worse basics, no rollback — is what pushes users toward Home Assistant. Unlike Google Home, Home Assistant keeps a local state machine and talks to devices directly over Zigbee, Z-Wave, Matter, Thread, or local Wi-Fi APIs such as ESPHome, bypassing vendor cloud servers entirely. It runs on hardware inside the home, such as a mini PC or Home Assistant Green, so commands keep working without an internet connection and with far less latency. For users who moved for privacy reasons, the appeal is equally clear: voice processing can stay inside the house.

Voice control is the part that used to be hardest to replace, and it has matured quickly. Home Assistant’s voice architecture splits processing into local modular services using the Wyoming protocol, with its built-in conversation agent using the HassIL intent language. Users can add voice satellites around the home, including the Home Assistant Voice Preview Edition, or build their own hardware — How-To Geek pointed to the $30 ReSpeaker Lite as a starting point.

The timing is favorable for anyone considering the move. Home Assistant 2026.11, released November 4, was described in its release notes as the biggest release the project has ever shipped, adding a built-in Marketplace, a major naming rework, and support for Matter cameras, among 38 new integrations. The platform’s ecosystem keeps growing just as Google’s is under strain.

What this means for Google Home owners

None of this means Gemini for Home is doomed. Google is clearly investing in it, the September fixes were real, and many users will never hit the edge cases described above — particularly in simpler setups with a handful of devices and no complex routines.

But the pattern of complaints points to a real risk for Google. The users leaving are not casual owners; they are the power users who built elaborate routines, named individual lights, and relied on voice control dozens of times a day. They are also the people friends and family ask for smart home advice. If Google cannot restore deterministic reliability for basic commands — and cannot offer a way back while it works on it — each frustrated household becomes an advocate for the local alternative.

For now, owners have three practical options: stay on Gemini and wait for further fixes, hold off on opting in if they still run the old Assistant, or start experimenting with Home Assistant alongside their existing setup. The last option is increasingly the one frustrated users are choosing — and, judging by the November reports, they are not looking back.

Leave a Comment