google_assistant integration allows you to control your Home Assistant devices via Google Assistant on your mobile, tablet, or Google Home device.
If you want to send commands to Google Assistant to control devices supported by Google Assistant but not by Home Assistant, or broadcast messages to Google Assistant speakers and displays without interrupting music/video playback, take a look at the Google Assistant SDK integration.
With Home Assistant Cloud, you can connect your Home Assistant instance in a few simple clicks to Google Assistant. With Home Assistant Cloud you don’t have to deal with dynamic DNS, SSL certificates, or opening ports on your router. Just log in via the user interface and a secure connection with the cloud will be established. Home Assistant Cloud requires a paid subscription after a 30-day free trial.
For Home Assistant Cloud users, documentation can be found here.
The Google Assistant integration (without Home Assistant Cloud) requires a bit more setup than most due to the way Google requires Assistant Apps to be set up.
To use Google Assistant, your Home Assistant configuration has to be externally accessible with a hostname and SSL certificate. If you haven’t already configured that, you should do so before continuing. If you make DNS changes to accomplish this, please ensure you have allowed up to the full 48 hours for DNS changes to propagate, otherwise, Google may not be able to reach your server. Once you have confirmed you can reach your Home Assistant from outside your home network, you can set up the Google integration:
Create a new project in the Actions on Google console.
- Select New Project and give your project a name.
- Select the Smart Home card, then select the Start Building button.
- Under Quick Setup, select Name your Smart Home action. Give your Action a name - Home Assistant will appear in the Google Home app as
[test] <Action Name>
- Select the Overview tab at the top of the page to go back.
- Select Build your Action, then select Add Action(s).
- Add your Home Assistant URL:
https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistantin the Fulfillment URL textbox, replace the
[YOUR HOME ASSISTANT URL:PORT]with the domain / IP address and the port under which your Home Assistant is reachable.
- Select Save.
- Select the three little dots (more) icon in the upper right corner, select Project settings.
- Make note of the Project ID that are listed on the General tab of the Settings page.
Account linking is required for your app to interact with Home Assistant.
- Start by going back to the Overview tab.
- Select on Setup account linking under the Quick Setup section of the Overview page.
- If asked, leave options as they default No, I only want to allow account creation on my website and select Next.
- Then if asked, for the Linking type select OAuth and Authorization Code. Select Next.
- Enter the following:
- Client ID:
[YOUR_PROJECT_ID]with your project ID from above)
- Client Secret: Anything you like, Home Assistant doesn’t need this field.
- Authorization URL:
https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize. (Replace
[YOUR HOME ASSISTANT URL:PORT]with your values.)
- Token URL (replace with your actual URL):
https://[YOUR HOME ASSISTANT URL:PORT]/auth/token. (Replace
[YOUR HOME ASSISTANT URL:PORT]with your values.) Select Next, then Next again.
- Client ID:
- In the Configure your client Scopes textbox, type
nameand select Add scope again.
- Do NOT check Google to transmit clientID and secret via HTTP basic auth header.
- Select Next, then select Save.
Select the Develop tab at the top of the page, then, in the upper right hand corner, select the Test button to generate the draft version Test App. If you don’t see this option, go to the Test tab instead, select the Settings button in the top right below the header, and ensure On device testing is enabled (if it isn’t, enable it).
Enable device sync (see below for more information).
- Go to Google Cloud Platform.
- Go to Select a project.
- In the window that popped up, select your newly created project from step 1.
- Go to the menu and select APIs and Services and next Credentials.
- In the Credentials view, select Create credentials and next Service account.
- Service account name: Give your account a self-selected name.
- Select Create and Continue.
- Under Select a role, select Service Accounts > Service Account Token Creator.
- Select Continue and then Done.
- Under Service Accounts, there should now be an account called [name from 4.1]@[projectname].iam.gserviceaccount.com.
- Select the pencil button of that service account.
- Go to Keys and Add key.
- Create a private key in JSON format.
- This will start a download of a JSON file.
- Rename the file to
- Add this file to your config-folder. This will be the same folder as your
- Rename the file to
- Go back to Google Cloud Platform and select Close.
- Then select Save.
- Go to the Search products and resources and search for Homegraph API and select it.
- Enable the HomeGraph API.
google_assistantintegration configuration to your
configuration.yamlfile and restart Home Assistant following the configuration guide below.
Add services in the Google Home App (note that app versions may be slightly different).
- Open the Google Home app.
- Select the
+button on the top left corner, select Set up device. In the Set up a device screen, select Works with Google. You should have
[test] <Action Name>listed under Add new. Selecting that should lead you to a browser to login your Home Assistant instance, then redirect back to a screen where you can set rooms and nicknames for your devices if you wish.
If you’ve added Home Assistant to your phone’s home screen, you have to first remove it from the home screen. Otherwise, this HTML5 app will show up instead of a browser. Using it would prevent Home Assistant redirecting back to the Google Home app.
If you want to allow other household users to control the devices:
- Open the project you created in the Actions on Google console.
- Select Test on the top of the page, then select Simulator located to the page left, then click the three little dots (more) icon in the upper right corner of the console.
- Select Manage user access. This redirects you to the Google Cloud Platform IAM permissions page.
- Select Grant access at the top of the page.
- Enter the email address of the user you want to add.
- Select Select a role and choose Project > Viewer.
- Select Save.
- Copy and share the Actions project link (
https://console.actions.google.com/project/YOUR_PROJECT_ID/simulator) with the new user.
- Have the new user open the link with their own Google account, agree to the Terms of Service popup. Then select Start Testing, select Version - Draft in the dropdown, and select Done.
- Have the new user go to their Google Assistant app to add
[test] your app nameto their account.
If you want to support active reporting of state to Google’s server (configuration option
report_state) and synchronize Home Assistant devices with the Google Home app (
google_assistant.request_sync service), you will need to create a service account. It is recommended to set up this configuration key as it also allows the usage of the following command, “Ok Google, sync my devices”. Once you have set up this component, you will need to call this service (or command) each time you add a new device in Home Assistant that you wish to control via the Google Assistant integration. This allows you to update devices without unlinking and relinking an account (see below).
The service account is created by following Step 4 (Enable device sync) in the previous section Google Cloud Platform configuration.
Try it with “OK Google, sync my devices” - the Google Home app should import your exposed Home Assistant devices and prompt you to assign them to rooms.
Google Assistant devices can send their commands locally to Home Assistant allowing them to respond faster.
Your Home Assistant instance needs to be connected to the same network as the Google Assistant device that you’re talking to so that it can be discovered via mDNS discovery (UDP broadcasts).
Your Google Assistant devices will still communicate via the internet to:
- Get credentials to establish a local connection.
- Send commands that involve a secure device.
- Send commands if local fulfillment fails.
This is because the Google Assistant device will connect directly to the IP of your Home Assistant instance and will fail if it encounters an invalid SSL certificate.
For secure remote access, use a reverse proxy such as the NGINX SSL add-on instead of directing external traffic straight to Home Assistant.
- Open the project you created in the Actions on Google console.
- Select Develop on the top of the page, then select Actions located in the hamburger menu on the top left.
app.jsfrom step 3.1.
app.jsfrom step 3.1.
- Check the box Support local query under Add capabilities.
- Add device scan configuration:
- Select + New scan config if no configuration exists.
- Select MDNS.
- Set MDNS service name to
- Select Add field, then under Select a field, choose Name.
- Enter a new Value field set to
- Save your changes.
- Either wait for 30 minutes, or restart all your Google Assistant devices.
- Restart Home Assistant Core.
- With a Google Assistant device, try saying “OK Google, sync my devices.” This can be helpful to avoid issues, especially if you are enabling local fulfillment sometime after adding cloud Google Assistant support.
You can debug the setup by following these instructions.
Now add your setup to your
configuration.yaml file, such as:
# Example configuration.yaml entry
service_account: !include SERVICE_ACCOUNT.JSON
Pin code to say when you want to interact with a secure device.
Service account information. You can use an include statement with your downloaded JSON file, enter data here directly or use secrets file to populate.
Actively report state changes on entities. This speeds up response time for actions affecting multiple entities since Google Assistant knows pre-hand what state they are. It is also required for some features on visual controls.
Expose devices in all supported domains by default. If
exposed_domains domains is set, only these domains are exposed by default. If
expose_by_default is set to false, devices have to be manually exposed in
List of entity domains to expose to Google Assistant if
expose_by_default is set to true. This has no effect if
expose_by_default is set to false.
Entity specific configuration for Google Assistant
Entity to configure
Currently, the following domains are available to be used with Google Assistant, listed with their default types:
- alarm_control_panel (arm/disarm)
- button (scene)
- camera (streaming, requires compatible camera)
- climate (on/off, temperature setting, hvac_mode)
- cover (on/off/set position/stop/start=toggle cover)
- event (only entities with device class
- fan (on/off/speed percentage/preset mode)
- group (on/off)
- humidifier (humidity setting/on/off/mode)
- input_boolean (on/off)
- input_select (option/setting/mode/value)
- light (on/off/brightness/rgb color/color temp)
- media_player (on/off/set volume (via set volume)/source (via set input source)/control playback)
- scene (on)
- script (on)
- sensor (temperature setting for temperature sensors and humidity setting for humidity sensors)
- switch (on/off)
- vacuum (dock/start/stop/pause)
- valve (open/close/set position/stop/start=toggle valve)
- water_heater (on-off/temperature setting/operation mode)
Some of these devices may not display correctly in the Google Home app, such as media_player, however voice commands will still work.
Certain devices are considered secure. This includes devices in the
lock domain, the
alarm_control_panel domain, as well as
covers with device types
By default, secure devices cannot be opened by Google Assistant unless a
secure_devices_pin code is set up. To allow opening, set the
secure_devices_pin to something. You will then be prompted to speak the pin when opening the device. Closing or locking these devices does not require a pin.
If a code is set for the Alarm control panel, it must be the same as the
code_arm_required is set to
false, the system will arm without prompting for the pin.
Entities that have not been explicitly assigned to rooms but have been placed in Home Assistant areas will return room hints to Google with the devices in those areas.
Some devices, such as
script, must be assigned to an
area before other members of a shared Google Home Household can use them. This is because household members in a shared Google Home will not be able to view devices that are not assigned to a room unless they were the user who linked the service to Google Home. This issue isn’t immediately apparent because
scene devices aren’t visible in the main Google Home dashboard.
The automatic room assignment will not work when multiple homes are set up in your Google account.
There is not an exact 1-1 match between Home Assistant and Google Assistant for the available operation modes. Here are the modes that are currently available:
- heatcool (auto)
There is no TV channel object in Home Assistant. TV channel can only be changed by number, not by name (for example,
Turn to channel two).
Syncing from Google Assistant may fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say “Ok Google, sync my devices” and get the response “Unable to sync Home Assistant” (or whatever you named your project), this can usually be resolved by going back to your test app in the Actions on Google console and clicking
TEST. Regenerate the draft version Test App and try asking Google to sync your devices again. If regenerating the draft does not work, go back to the
Action section and just hit the
enter key for the URL to recreate the Preview.
Syncing from Home Assistant will always work and will automatically update entity changes.
request_sync service requires that the initial sync from Google includes the
agent_user_id. If not, the service will log an error that reads something like “Request contains an invalid argument”. If this happens, then unlink the account from Home Control and relink.
request_sync service may fail with a 404 if the
project_id of the HomeGraph API differs from the
project_id of the Actions SDK found in the preferences of your project on Actions on Google console. Resolve this by:
- Removing your project from the Google Cloud API Console.
- Add a new project to the Actions on Google console Here you get a new
- Run through the previously mentioned [Actions on Google console] setup instructions until the step to create a
- Once you begin to create a new
service_accountin the [Google Cloud API Console], ensure you select the project created in [Actions on Google console] by verifying the
- Enable HomeGraph API to the new project.
Verify that the Google Assistant is available on
https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant If it is working it should return
405: Method Not Allowed when opened in a browser or via curl.
request_sync service may fail with a 403 if the HomeGraph API is not enabled. Go to Google API Console and verify that HomeGraph API is enabled for your project.
If you receive 404 errors linked to reporting state in your log, Home Assistant is reporting state for entities that were never synced to Google. Ask your Google Home to
Sync my devices or run the service
Your fulfillment URL may be invalid or unreachable. Recheck the
Fulfillment URL as specified in Manual Setup and verify that it’s publicly reachable.
This error may occur if the service key is invalid. Try deleting and creating a new service account and key.
When using NGINX, ensure that your
proxy_pass line does not have a trailing
/, as this will result in errors. Your line should look like:
If you’re having trouble with Account linking failed after you unlinked your service, try clearing the browser history and cache.
If you’re having trouble linking your account, with the error message
Could not update the setting. Please check your connection after logging into your Home Assistant instance, try setting
expose_by_default: false then exposing a single simple device (light or switch preferably). It is also worth checking if any home ad blocker is disabled if you are having issues.