Connecting Google Assistant to Home Assistant lets Google Home and Nest speakers, and the Google Home app, control the entities you choose. There are two ways to set it up: Home Assistant Cloud (Nabu Casa), which is the simpler route, and a manual setup with your own Google Cloud project.
Either way, Google’s cloud handles the voice request. The local fulfillment section later in this guide explains what that does and does not mean.
Before you start
Decide which entities Google should see, and expose only those. Go to Settings > Voice assistants > Expose and turn on the Google Assistant toggle for each one. Exposing everything clutters the Google Home app, so start small and add more later.
Sign in with the same Google account you use for your Google Home devices.
Option 1: Home Assistant Cloud (Nabu Casa)
This is the easiest route. The Home Assistant Cloud subscription costs about $6.50 a month or $65 a year in the US at the time of writing, and the price varies by region. A free trial is available.
- Go to Settings > Home Assistant Cloud and enable Google Assistant.
- In the Google Home app, select +, then Set up device, then Works with Google.
- Search for Home Assistant Cloud by Nabu Casa, then link your account.
Nabu Casa syncs newly exposed entities automatically. If a device is missing, say “Hey Google, sync my devices.”
Option 2: Manual setup with Google Cloud
The manual route gives you more control, and it needs more work. You will need:
- External access to Home Assistant over HTTPS on port 443.
- A Google Cloud project with the HomeGraph API enabled.
- A cloud-to-cloud integration set up in the Google Home Developer Console.
- A service account JSON key. It enables state reporting and automatic sync, through the
report_statesetting.
Then add a google_assistant: block to configuration.yaml. This example exposes lights and switches:
google_assistant:
project_id: your-project-id
service_account: !include SERVICE_ACCOUNT.JSON
report_state: true
exposed_domains:
- light
- switch
Keep the JSON file in your Home Assistant configuration folder, and make the file name match the !include line.
Rooms in Google Home can be set from Home Assistant areas, using the room setting in entity_config. Check the Home Assistant documentation for the exact format.
The Google Cloud console steps change often. Follow the current Home Assistant documentation for them, rather than screenshots from older guides.
Locks, garage doors and alarms
Locks, garage covers and alarms are sensitive. With the manual setup, the secure_devices_pin option adds a PIN that Google asks for before it acts on those devices. Choose a PIN that is not easy to guess.
A PIN is a safeguard, not a reason to expose more. Anyone within earshot of a speaker can make a request, so think carefully before you expose these devices at all.
Local fulfillment
Google’s cloud still processes the voice request, whichever setup you use. Local fulfillment is a separate feature. When Home Assistant and the Google device share a network, local fulfillment can carry some commands directly on your network. It is generally limited to devices that do not require a PIN.
So the phrase “local” covers the final action, not the voice request.
Google Assistant SDK: the other direction
The separate Google Assistant SDK integration works the other way. It lets Home Assistant send text commands and broadcasts to Google devices, using Google Cloud OAuth credentials. It does not let Google control Home Assistant.
Google Home and the move to Gemini
Google is replacing Google Assistant with Gemini on Nest speakers and phones. The Home Assistant integration still works, but the steps in the Google Home app may look different from older guides. If a step does not match what you see, follow the current Home Assistant documentation first.
Nest speakers cannot run Home Assistant Assist. For a voice satellite you control, see Home Assistant voice control. Gemini as an AI agent inside Home Assistant is a separate product, covered in AI in Home Assistant.
Troubleshooting sync
If a device does not appear in Google Home:
- Check that the entity is exposed to Google Assistant.
- Ask Google to sync: “Hey Google, sync my devices.”
- For the manual setup, check that the HomeGraph API is enabled and that the service account key is in place.
Common misconceptions
- Google commands to Home Assistant still start in Google’s cloud. Local fulfillment can carry some commands on your network, but the voice request does not stay local.
- The Google Assistant SDK does not let Google control Home Assistant. It works in the other direction.
- Exposing everything clutters Google Home. Expose only what you need.
- Nest speakers cannot run Home Assistant Assist.