Home Assistant with Google Home fallback

Most smart home enthusiasts eventually hit the same fork: commit to Home Assistant and go fully local, or keep Google Home around for easy voice control. For a lot of people the answer is both, wired up so that Home Assistant owns the logic and Google is just a voice shortcut. This guide covers how to run Home Assistant as your primary local brain while keeping Google Home as a convenient voice fallback, without pretending the cloud has vanished.

Why keep Google Home in the loop

Google’s voice assistant is fast, guests already know how to use it, and it handles natural language well. One thing to know going in: the assistant is changing underneath you. Google is replacing Google Assistant on its speakers and displays with Gemini for Home, and that switch is made per home and cannot be undone. Either way the catch is the same: Google’s cloud is in the loop for voice. When you speak to a Google speaker, the audio goes to Google’s servers to be understood, and the resulting command is then handed off. That means voice control depends on your internet connection and on Google’s services being up.

Home Assistant fixes the parts that matter most by owning device state and automation logic locally. But its built-in voice assistant, while good now, is less forgiving than Google for vague phrasing. Keeping Google Home as a voice front-end, while Home Assistant makes the actual decisions, is a reasonable middle ground.

Setting up the Home Assistant Cloud bridge

The smoothest path is the Home Assistant Cloud subscription from Nabu Casa, the company behind Home Assistant. It’s a paid subscription, currently about $6.50 per month or $65 per year (plus local tax). It is not a free add-on; the fee is what funds Home Assistant development.

The Google Assistant integration in Home Assistant Cloud exposes your selected Home Assistant entities to the Google Home app. They show up alongside your other Google devices, you can group them into rooms, and you can control them by voice. Be clear-eyed about how this works, though: when you give a voice command, it still travels through Google’s cloud to be processed, and the command is then relayed via Nabu Casa to your local Home Assistant, which executes it locally. Home Assistant owns the state and the automations; Google provides the voice layer, and that voice layer is a cloud service. This is convenience, not privacy.

Setup is short. In Home Assistant, go to Settings > Home Assistant Cloud, enable the Google Assistant integration, and link it to the Google Home app per the on-screen instructions (two clicks once your account is connected). You choose which entities to expose, so you can keep sensitive devices out of Google’s view by simply not exposing them.

The subscription also includes secure remote access without opening ports on your router and encrypted off-site backups, which can be worth the price on their own.

Local voice fallback options

If you’d rather keep voice on-device and treat Google Home as the backup, there are two practical paths.

Cast displays for status and quick control. Google Cast devices such as the Google TV Streamer 4K and Nest Hub displays can show dashboards and media state. They don’t make voice local, but pairing them with a Matter-based setup means the underlying device commands run locally even when Google is just the screen.

Local Assist with dedicated hardware. Home Assistant’s Assist voice pipeline can run entirely on your own hardware. The Home Assistant Voice Preview Edition, which I run, is a roughly $59 speaker built for this. It reaches Home Assistant over 2.4 GHz Wi-Fi (it also carries a Bluetooth 5.0 radio, but the link back to HA runs over Wi-Fi), has a hardware mute switch that physically cuts the microphone, and runs ESPHome firmware with on-device wake-word detection. Commands like “turn off the living room lights” can be handled entirely within your house. Setup is in the Home Assistant UI under Settings > Voice assistants. For the full local-voice picture, see how to add voice control without Amazon or Google and my Whisper and Piper explainer.

The tradeoff is that local Assist is less flexible than Google for ambiguous requests. For straightforward on/off/dim/set commands it’s fast and reliable; for “make it comfortable in here,” Google still understands you better.

What breaks and how to plan around it

The most common annoyance is state desync. Home Assistant flips a light via a motion automation, and the Google Home app shows the old state for a few seconds until it catches up. For most uses this is cosmetic. It only matters if you let Google make decisions, so don’t.

Keep all presence detection, occupancy, and scheduling logic in Home Assistant. Google Home’s only job here is to accept a voice command and hand it off, not to decide anything.

For energy monitoring, skip Google’s cloud-based dashboard and use local hardware: a metered local device reporting into Home Assistant gives you frequent local readings instead of delayed cloud summaries. For a single circuit the current inline option is the Shelly 1PM Gen4, and the older Gen2 Shelly Plus 1PM does the same metering job if you already own one. The HomeWizard Energy Socket is a plug-in alternative with a local API, but it is sold only in an EU Type-F form factor, with no US or UK version.

Set up this way, the cloud is optional rather than mandatory: the house keeps working when the internet doesn’t, and the voice convenience is there when it does.