The 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 the Add the Add services in the Google Home App (Note that app versions may be
slightly different.) If you’ve added Home Assistant to your phone’s home
screen, you have to first remove it from 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: If you want to support active reporting of state to Google’s server (configuration option 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: The HTTP integration must not be configured to use an SSL certificate with the 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. You can debug the setup by following these instructions. Now add your setup to your Configuration Variablesproject_id string Required Project ID from the Actions on Google console (looks like secure_devices_pin string (Optional) Pin code to say when you want to interact with a secure device. service_account map Required Service account information. You can use an include statement with your downloaded JSON file, enter data here directly or use secrets file to populate. private_key string Required Private key in PEM format client_email string Required Service email address report_state boolean (Optional, default: false) 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_by_default boolean (Optional, default: true) Expose devices in all supported domains by default. If exposed_domains list (Optional) List of entity domains to expose to Google Assistant if entity_config map (Optional) Entity specific configuration for Google Assistant YOUR_ENTITY_ID map (Optional) Entity to configure name string (Optional) Name of the entity to show in Google Assistant expose boolean (Optional, default: true) Force an entity to be exposed/excluded. aliases list (Optional) Aliases that can also be used to refer to this entity room string (Optional) Allows for associating this device to a Room in Google Assistant. Available domainsCurrently, the following domains are available to be used with Google Assistant, listed with their default types:
Some of these devices may not display correctly in the Google Home app, such as media_player, however voice commands will still work. Secure DevicesCertain devices
are considered secure, including anything in the By default these cannot be opened by Google Assistant unless a For the Alarm Control Panel if a code is set it must be the same as the Room/Area supportEntities 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 Climate Operation ModesThere 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:
TV ChannelsThere is no TV channel object in Home Assistant. TV channel can only be changed by number, not by name (for example, Troubleshooting404 errors on request syncSyncing 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 Syncing from Home Assistant will always work and will automatically update entity changes. The The
Verify that the Google Assistant is available on 403 errors on request syncThe 404 errors on report stateIf 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 Error during linking: “Could not update the setting. Please check your connection”Your fulfillment URL may be
invalid or unreachable. Recheck the NGINXWhen using NGINX, ensure that your
Unlink and relinkIf you’re having trouble with Account linking failed after you unlinked your service, try clearing the browser history and cache. Failed linking - Could not update the setting. Please check your connectionIf you’re having trouble linking your account, with the error message Help us to improve our documentationSuggest an edit to this page, or provide/view feedback for this page. How do I fix Google Home connection?General troubleshooting. Reboot speaker or display. Disconnect the power cable from your speaker or display. ... . Force close and reopen the Google Home app.. Try to manually connect to the device's hotspot from your phone or tablet's Wi-Fi settings. Go to the Wi-Fi settings on your mobile device.. How do I get to connection settings?Open your phone's Settings app.. Tap Network & internet. Internet. If you can't find it, search for the setting you want to change. ... . At the bottom, tap Network preferences.. Tap an option. These vary by phone and Android version. Turn on Wi-Fi automatically: Have Wi-Fi automatically turn on near saved networks.. Why is my Google Home not connecting to WiStart by rebooting your router. Next, power your Google Home off and then back on again by disconnecting and then reconnecting the power cable. Take the device you're using for setup (the device you installed the app on), and turn the Wi-Fi off and back on.
|