google_assistant component allows you to control things via Google Assistant (on your mobile or tablet) or a Google Home device.
The Google Assistant component 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.
To enable this, add the following lines to your
# Example configuration.yaml entry google_assistant: project_id: someproject-2d0b8 client_id: [long URL safe random string] access_token: [a different long URL safe random string] agent_user_id: [a string to identify user] api_key: [a Homegraph API Key generated for the Google Actions project] exposed_domains: - switch - light - group entity_config: switch.kitchen: name: Custom Name for Google Assistant aliases: - bright lights - entry lights light.living_room: expose: false room: living room
(string)(Required)Project ID from the Google Developer console (looks like
(string)(Required)A long random URL safe string (no spaces or special characters) that will be used for Implicit OAuth (example
(string)(Required)Another different long random URL safe string (example
(string)(Optional)A string to identify the user, e.g., email address. If not provided, the component will generate one.
(string)(Optional)An API Key generated for the project from Google Console which allows you to update devices without unlinking and relinking an account (see step 9 below). If not provided then the
google_assistant.request_syncservice is not exposed. 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 setup this component you will need to call this service (or command) each time you add a new device that you wish to control via the Google Assistant integration.
(boolean)(Optional)Expose devices in all supported domains by default. If set to false, you need to either expose domains or add the expose configuration option to each entity in entity_config and set it to true.
Default value: true
(list)(Optional)List of entity domains to expose to Google Assistant.
(map)(Optional)Entity specific configuration for Google Assistant
(map)(Optional)Entity to configure
(string)(Optional)Name of the entity to show in Google Assistant
(boolean)(Optional)Force an entity to be exposed/excluded.
(list)(Optional)Aliases that can also be used to refer to this entity
(string)(Optional)Allows for associating this device to a Room in Google Assistant. This is currently non-functional, but will be enabled in the near future.
Currently, the following domains are available to be used with Google Assistant, listed with their default types:
- group (on/off)
- input boolean (on/off)
- scene (on)
- script (on)
- switch (on/off)
- fan (on/off)
- light (on/off/brightness/rgb color/color temp)
- cover (on/off/set position (via set brightness))
- media_player (on/off/set volume (via set brightness))
- climate (temperature setting)
It’s very important that you use very long strings for
access_token. Those are essentially the credentials to your Home Assistant instance. You can generate them with the following command:
$ cat /dev/urandom | fold -w 120 | head -n 1 | base64 -w 0 | tr -dc '0-9A-Za-z' | cut -c -80
If you’re not using Linux, you can use sites such as this one to generate a random string (containing mixed case letters and numbers) of up to 80 characters.
- Create a new project in the developer console.
a. Add/Import project
b. Click on
Smart homecard c. Type in your home assistant url:
https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant, replace the
[YOUR HOME ASSISTANT URL:PORT]with the domain / ip address and the port under which your Home Assistant is reachable. d. Click
Done. Then click on
Overview, which will lead you to the app details screen.
- You’ll need to fill out most of the information on that page, but none of it really matters since you won’t be addressing the App directly, only through the Smart Home functionality built into Google Assistant.
- The final item on that page
Account linkingis required for your app to interact with Home Assistant. a. Grant type:
Implicitb. Client ID: The
client_idfrom your Home Assistant configuration above c. Authorization URL (replace with your actual URL):
https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth. If you have set
api_password:add this password to the URL
https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth?api_password=[YOUR API PASSWORD]) d. Configure your client. Add scopes for
name. e. Testing instructions: Enter anything. It doesn’t matter since you won’t submit this app.
- Back on the main app draft page. Click
Test Draft. That will take you to the simulator (which won’t work so just close that window).
- If you haven’t already added the component configuration to
configuration.yamland restarted Home Assistant, you’ll be unable to continue until you have.
- Open the Google Assistant app and go into
Settings > Home Control
- Click the
+sign, and near the bottom, you should have
[test] your app name. Selecting that should lead you the screen where you can set rooms for your devices or nicknames for your devices.
- If you want to allow other household users to control the devices:
a. Go to the settings for the project you created in point 1 in the developer console.
b. Under the gear icon, click
Add, type the new user’s e-mail address and choose
Project -> Editorrole d. Have the new user go to developer console and repeat steps starting from point 4
- If you want to use the
google_assistant.request_syncservice, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project: a. Go to the cloud console b. Select your project and click Enable Homegraph API c. Go to Credentials, which you can find on the left navigation bar under the key icon, and select API Key from Create Credentials d. Note down the generated API Key and use this in the configuration
The 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.
The 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 developer console. Resolve this by:
- Removing your project from the developer console.
- Add a new project to the cloud console. Here you get a new
- Enable Homegraph API to the new project.
- Generate a new API key.
- Again, create a new project in the developer console. Described above. But at the step ‘Build under the Actions SDK box’ choose your newly created project. By this, they share the same