Skip to content

Configuration and management

After you set up the integration, use this page to change how it checks your devices, manage devices and homes, or remove it. If Home Assistant asks you to sign in again, see Sign in again.

Change the update interval

The integration checks your devices for changes every 15 seconds by default.

To change the interval, go to Settings > Devices & services > Google Home and select Configure. Enter the number of seconds under Update interval (seconds) and select Submit. Shorter intervals update alarms and timers sooner but send more requests to your devices.

Around an alarm's or timer's time, and while it rings, the integration checks that speaker more often than the interval, so that ringing shows within seconds and its end within about 10 seconds even with a long interval. These checks add requests while an alarm or timer is due or ringing. See How quickly ringing shows.

If a speaker or display with alarms and timers often shows false in the available attribute of its device sensor while it's on, or its entities become unavailable for a moment while it restarts, increase the interval, for example to 180 seconds, the default before version 1.16.

Configure shows the interval in use. If you saved these options in version 1.15 or older, for example to add known hosts, it's the interval you saved, which was 180 seconds unless you changed it. To use the new default, enter 15 and select Submit.

The interval must be at least 1 second. If you saved 0 or less in an earlier version, the integration checks every 15 seconds while polling is on, and Configure shows the saved value, not the interval in use. Until you save a valid interval, Settings > System > Repairs shows The saved update interval is below 1 s. Select it, then choose:

  • Use the default of 15 s: saves 15 seconds, and the repair goes away.
  • Turn off polling instead: saves 15 seconds, turns off polling and reloads the integration. An interval of 0 stopped only the regular checks; turning off polling also stops Bluetooth scans and the adding of new devices that mDNS finds. The Polling for changes is turned off repair starts hidden, as if you had chosen Keep polling off and hide this repair in it.

To use another interval instead, enter it in Configure; the repair goes away once you save it. While polling is off, the interval isn't used, so the repair shows only once you turn polling back on.

To update immediately, use the Refresh devices action.

Turn off polling

You can stop the integration from checking your devices on its own: go to Settings > Devices & services > Google Home > ⋮ > System options and turn off Enable polling for changes. Most of what the integration shows then changes only when you ask for an update, so turn polling off only if you update your devices yourself, for example from an automation.

While polling is off:

  • When Home Assistant starts or the integration reloads, the integration gets your devices from Google and asks each device once, so its entities show current values.
  • Alarms, timers and the other entities update only when you run Refresh devices or homeassistant.update_entity, or after an action that deletes alarms or timers. The other actions still work.
  • A device that goes offline keeps its entities available until it misses 5 of these updates in a row.
  • The speakers don't scan for Bluetooth devices on their own, so Bluetooth trackers show unknown.
  • Devices and homes that you add in or remove from the Google Home app change in Home Assistant only at these updates: the integration gets your devices from Google at the first of them at least 20 minutes after it last did; see Add a device and Remove a device. To see a change straight away, reload the integration.
  • When a device's access token changes, usually within a day, the integration gets the new token from Google at the device's next update. If an action fails because the device rejected its token, run Refresh devices, then try the action again.

This automation updates your devices every 5 minutes. List the device sensor of each device to update:

alias: Update Google Home devices
triggers:
  - trigger: time_pattern
    minutes: "/5"
actions:
  - action: homeassistant.update_entity
    target:
      entity_id:
        - sensor.kitchen_device
        - sensor.living_room_device

homeassistant.update_entity updates only the devices you list, even one whose sensors are unavailable. To update all your devices instead, use Refresh devices with any Google Home sensor as its target. It also runs when that sensor is unavailable, for example after its device missed 5 updates in a row.

While polling is off, Settings > System > Repairs shows Polling for changes is turned off. Select it, then choose:

  • Turn polling back on: the integration reloads, checks your devices at the update interval again, and the repair goes away. Turning Enable polling for changes back on in System options does the same once the integration reloads.
  • Keep polling off and hide this repair: Home Assistant hides the repair, also after a restart. It shows again if you turn polling on and later off again. To find it while it's hidden, open the ⋮ menu in Repairs and select Show ignored repairs.

Closing the repair without choosing changes nothing.

Stop checking some devices

To stop checking only some devices, rather than turning off polling for all of them, disable them in Home Assistant: on the device's page, select the pencil icon (Edit settings), turn off Enable device and select Update. Home Assistant disables the device's entities with it, and the integration stops checking that device, also when you run Refresh devices. A disabled speaker doesn't scan for Bluetooth tracking either.

Home Assistant hides disabled devices in Settings > Devices & services > Devices. To find one again, go to Settings > Devices & services > Google Home and select the link with the number of devices: that list includes disabled ones. To check the device again, select Enable on its page. Home Assistant reloads the integration about 30 seconds later.

Add a device

When you add a speaker or display in the Google Home app, the integration adds it without a reload, unless it's in a home that you deselected:

  • If Home Assistant receives the device's mDNS announcements, for example because it's on the same network, the device usually appears about a minute after it joins your network, if Google lists it by then.
  • Otherwise, or if Google doesn't list the device yet by then, it appears within about 20 minutes, when the integration next asks Google for your devices.

To add the device straight away, reload the integration: Settings > Devices & services > Google Home > ⋮ > Reload. The device appears only once Google lists it, and some of its entities only once Home Assistant can reach it; see Entities.

If the integration finds your devices only through known hosts, add the new device's IP address there instead. Saving it reloads the integration, which then reaches the device at that address.

To add back a speaker or display that you removed from the Google Home app, or to replace one with another device:

  1. If you're replacing a device, remove the old one from the Google Home app, even if it no longer works. Until you do, the integration keeps it and you can't delete it.
  2. If the old device is still in Home Assistant, delete it. First reload the integration: Settings > Devices & services > Google Home > ⋮ > Reload. Then open the old device's page, open the ⋮ menu and select Delete. You can also wait until the integration removes it, usually 20 to 40 minutes after you removed it from the app; see Remove a device. If the old device is still there when the new one appears, the new device's entities get IDs such as sensor.kitchen_alarms_2 instead of sensor.kitchen_alarms, and keep them after the old device is removed.
  3. If you're adding back the same device, factory reset it. Restarting it isn't enough.
  4. Set up the device in the Google Home app. To get entity IDs like the old device's, give it the same name.

Google gives the device a new ID, so the integration adds it as a new device with new entities. Home Assistant doesn't carry over the old device's settings, such as its area, its name in Home Assistant and the entity IDs you changed. With the same name, the new entity IDs are usually the old device's original ones, such as sensor.kitchen_alarms. In some languages they're translated, such as sensor.kitchen_wecker in German, even if the old ones are in English; see Entity names in other languages.

If an automation, script or manually configured dashboard card uses an old entity ID that the new device doesn't have, update it. You can also give the new entity the old ID once the old device is gone: on the device page, select the entity, then the settings (gear) icon, change Entity ID and select Update.

Add devices on another network

The integration finds your devices on your network with multicast DNS (mDNS). mDNS usually doesn't reach other networks, such as a separate VLAN for smart home devices, or a Home Assistant container that doesn't use host network mode. Those devices then have only a device sensor, a reboot button, an update sensor, and disabled Wi-Fi sensors and an uptime sensor, and all of them are unavailable.

For devices on another network, Home Assistant needs:

  • A way to find the devices. Choose one:
    • Give Home Assistant a network interface on the devices' network, such as a second network adapter or a VLAN interface. Home Assistant usually uses only one interface for mDNS, so go to Settings > System > Network, clear Autoconfigure under Network adapter, also select the interface on the devices' network, select Save and restart Home Assistant. With this interface, Home Assistant also connects to the devices directly, so a firewall on your router doesn't need to allow TCP 8443.
    • Set up an mDNS reflector or repeater between the networks, for example on your router.
    • Add the devices' IP addresses as known hosts, as described below.
  • TCP port 8443 on each device. The integration connects to the devices over HTTPS on this port. If a firewall is in between, allow these connections from Home Assistant and their replies. A rule that allows only the Google Cast port, TCP 8009, isn't enough. The devices don't need to connect to Home Assistant.
  • Internet access for Home Assistant. The integration gets the device list and the devices' access tokens from Google when it loads, and again later, for example when the tokens expire.

To add devices as known hosts:

  1. Go to Settings > Devices & services > Google Home and select Configure.
  2. Under Known hosts, add the IP address of each device that the integration can't find. Hostnames aren't accepted.
  3. Select Submit. The integration reloads, asks each address which device it is, and uses the address for that device.

A device that was offline when the integration loaded is found at its known host within about 5 minutes of coming back online, or at the first update after that with a longer interval. While polling is off, the integration asks known hosts only at the updates you ask for, so with an automation that updates your devices every 5 minutes it can take up to about 10 minutes. With a network interface on the devices' network or an mDNS reflector, the integration gets a device's address as soon as the device announces itself, as on the same network.

Give these devices fixed IP addresses in your router, so the addresses don't change. For a speaker pair, add the addresses of both speakers. Only the speaker that leads the pair reports it, so the integration uses that one and ignores the other.

Choose homes

If your Google account is a member of several homes, you can choose the homes whose speakers and displays the integration adds. It adds every home's devices unless you deselect some. The integration doesn't add the devices of homes you deselect, even if it finds them on your network or at a known host, and doesn't check them for alarms and timers.

When you add the integration, it asks which homes to add if your account has more than one. If Google doesn't give the integration your homes at that point, it adds every home's devices, and you can choose later.

You can change the homes later under Homes in the integration's options. Homes appears when your account has more than one home, or when its only home is one that you deselected. If Homes is missing although your account has several homes, reload the integration first.

Homes are listed by the names they have in the Google Home app. If two of your homes have the same name, rename one of them in the app first, so that you can tell them apart. The home attribute of each device's device sensor shows the name of its home, so automations and templates can tell which home a device is in. The attribute is hidden while the sensor is unavailable.

To change the homes:

  1. Go to Settings > Devices & services > Google Home and select Configure.
  2. Under Homes, select the homes whose devices to add. At least one home must stay selected; otherwise the form shows "Choose at least one home."
  3. Select Submit. If you changed the homes, the integration reloads.

When you deselect a home, the integration removes its devices from Home Assistant, with their entities, as it reloads. Automations, scripts and dashboards that use them stop working. If Google doesn't give the integration your device list as it reloads, the devices stay, unavailable, until it next gets the list.

When you select a home again, its devices come back with the names, areas and other settings you gave them, except a device that was factory reset meanwhile, which comes back as a new device. As with a removed device, an entity gets its old ID back only if no other entity has taken that ID meanwhile.

Homes that your account joins later are added. A new home appears under Homes once the integration next gets your device list from Google, usually within about 20 minutes. To see it sooner, reload the integration: Settings > Devices & services > Google Home > ⋮ > Reload. If the options were already open, close them and select Configure again. To leave the new home out, deselect it.

If your account is left with only homes that you deselected, for example after you leave the home you selected, the integration doesn't add their devices. Once it next gets your homes from Google, Settings > System > Repairs shows None of your Google account's homes is selected. To fix it, select a home under Homes as described above: the integration reloads, and the repair goes away. If your account joins another home instead, the integration adds it and removes the repair once it next gets your homes from Google. With polling turned off, the integration doesn't ask Google by itself: reload it after your account joins the home.

If you keep the homes deselected on purpose, open the repair and select Ignore. Home Assistant hides the repair, also after a restart. It shows again if none of your homes is selected after the integration reloads. To find it while it's hidden, open the ⋮ menu in Repairs and select Show ignored repairs.

Track phones and other Bluetooth devices

Your speakers can tell whether your phone or another Bluetooth device is home. This is off until you turn it on. See Bluetooth tracking.

Remove a device

When you remove a device from the Google Home app, or Google drops it from your home after a factory reset, the integration removes it from Home Assistant, with its entities, once Google's device list has lacked it twice in a row. The integration asks Google for your devices every 20 minutes, so this usually takes 20 to 40 minutes. It doesn't remove a device while Google still has it in one of your homes, even if the integration can't use the device, unless you deselect that home.

As soon as Google's device list first lacks the device, its entities are unavailable. An attempt that can't get the list from Google doesn't count, and reloading the integration or restarting Home Assistant starts the count again.

To remove a device sooner, delete it yourself. First reload the integration so that it notices straight away: Settings > Devices & services > Google Home > ⋮ > Reload. Then open the device's page in Home Assistant, open the ⋮ menu and select Delete.

Home Assistant offers Delete for every device of the integration, but you can't delete one that Google still lists in your home, even if it shows as unavailable: it would come back the next time the integration loads. Until the integration has noticed that Google no longer lists a device, you can't delete that one either. You also can't delete a speaker or display while the integration isn't loaded, or until it gets your device list from Google after it loads. Home Assistant then shows "Failed to remove device entry, rejected by integration". You can delete a tracked Bluetooth device at any time: it isn't in Google's list, the integration never removes it, and deleting it stops tracking it.

If Google briefly leaves a working device out of your home in two lists in a row, the integration removes it and adds it back the next time Google lists it. A device you deleted yourself also comes back the next time Google lists it. In both cases, Home Assistant restores the settings you changed, such as its area and its entities' names and IDs, as long as no other entity has taken those entity IDs meanwhile.

To use a device again that you removed from the Google Home app, factory reset it first; see Add a device.

Remove the integration

If you installed from the Marketplace, or with HACS before Home Assistant 2026.11:

  1. Open Google Home in the Marketplace, or go to Settings > Marketplace, search for Google Home and open it. The first time you open the Marketplace, accept its notice, as in Install the integration.
  2. Open the ⋮ menu and select Uninstall.
  3. The Marketplace says that Google Home is in use: select Delete and uninstall, then Delete and uninstall again to confirm. It deletes the Google Home entry, with its devices, entities and the master token Home Assistant stored, then uninstalls the integration. If the entry is already deleted, the Marketplace asks "Uninstall Google Home?" instead: select Uninstall.
  4. Restart Home Assistant. If a repair under Settings > System > Repairs offers the restart, you can use it.

You can also start in Settings > Devices & services > Google Home: open the ⋮ menu and select Delete. Home Assistant then asks "Also uninstall Google Home?". Select Uninstall and restart Home Assistant as in step 4; Keep leaves the files installed.

If you installed manually:

  1. Go to Settings > Devices & services > Google Home, open the ⋮ menu and select Delete. Home Assistant deletes the master token it stored.
  2. Delete the custom_components/google_home folder.
  3. Restart Home Assistant.

To use another Google account, delete the integration in Settings > Devices & services, select Keep if Home Assistant asks whether to also uninstall it, and add it again. Deleting it also deletes its settings: the update interval, known hosts, deselected homes and Bluetooth options in Configure, the Bluetooth devices you track, and whether polling is turned off. Note them first, and set them again after you add the integration.

Deleting the integration doesn't stop the master token from working, and the integration can't revoke it. If the token might have been copied, for example from a Home Assistant backup:

  • If you created a separate Google account for the integration, delete that account.
  • Otherwise, change the Google account's password. Google then signs you out on most devices and apps, but it lists exceptions, so this isn't guaranteed to stop the master token.