Troubleshooting¶
Find what you see, then start with the first check in its section:
- Adding the integration shows an error
- The integration doesn't load after you update Home Assistant or the integration
- The Google Home card shows 1 entry failed to set up, retrying
- Home Assistant says that authentication expired, or signing in again fails
- The integration shows no devices
- A device has only a device sensor, a reboot button, an update sensor, and disabled Wi-Fi and uptime sensors
- All entities of a device are unavailable
- A device's alarms, timers or settings stop changing
- Deleting an alarm or timer, rebooting or changing a setting shows an error
- An automation didn't run at an alarm's or timer's time
- A Bluetooth tracker shows
unavailable
If that doesn't help, see Still stuck. Some sections ask you to collect debug logs to find the cause.
Setup fails¶
When you sign in again, the form shows the same sign-in errors.
"Username/Password is incorrect"¶
Update the integration, from the Marketplace or manually, and use browser sign-in. Older versions of the integration signed in with an app password, which Google rejects for many accounts.
Browser sign-in asks for a new cookie¶
Close the private window and repeat browser sign-in from step 1, then paste the new cookie straight away. Copy the whole value, starting with oauth2_4/. The oauth_token cookie can expire quickly and works only once. The error can also appear after Google accepted the cookie but refused the next part of the sign-in.
"Google didn't accept the master token"¶
Check that you pasted the token exactly as you got it. If it was correct before and has stopped working, for example after you changed your Google password, Google no longer accepts it: use browser sign-in instead. If the integration is already set up, sign in again rather than deleting it.
"Google didn't accept the sign-in"¶
Google refused the cookie or master token for a reason that the integration doesn't know or without a reason, or it answered in a way that the integration doesn't understand. Open the log and find the warning that starts with Failed to sign in; Google's reason, if it gave one, is at the end. Open an issue with that line, after you replace any email address or token in it with xxx.
"Couldn't reach Google"¶
Home Assistant couldn't connect to Google, or Google didn't answer in time. Check that Home Assistant is connected to the internet. The integration signs in at android.clients.google.com, and gets your homes and devices from googlehomefoyer-pa.googleapis.com. If a DNS filter or firewall, such as Pi-hole or AdGuard Home, blocks either, allow it. Then try again. With browser sign-in, get a new cookie for the next attempt.
If only googlehomefoyer-pa.googleapis.com is blocked, adding the integration shows no error, but doesn't ask you to choose homes, and the integration starts without devices; see No devices appear. Once you allow it, reload the integration, and choose homes in its options if you want only some of them.
Once the integration is added, System information shows whether Home Assistant reaches both.
"Google is busy or is limiting sign-ins"¶
Google answered with a server error, or asked the integration to slow down. This doesn't mean that your cookie or master token is wrong. Wait a few minutes, then sign in again. With browser sign-in, get a new cookie, as the old one can expire quickly.
"This integration allows only one configuration"¶
You can add the integration only once, so it works with one Google account. Adding it again shows this message, or "Already configured. Only a single configuration is possible." To add devices from several homes, invite the account you signed in with to each home: the integration adds the devices of every home that account is a member of. To use another account instead, see Remove the integration.
"Failed setup, will retry"¶
When Home Assistant couldn't connect to Google as the integration started, or Google didn't answer in time, the Google Home card in Settings > Devices & services shows 1 entry failed to set up, retrying, and the integration's page shows Failed setup, will retry. Home Assistant tries again by itself, after a wait that grows up to 10 minutes. The log shows nothing about it unless debug logging is on, so Check the logs on that page finds nothing. Until the integration starts, its entities are unavailable and its actions fail.
Check that Home Assistant can reach Google; see "Couldn't reach Google". System information shows whether Google's servers answer, though ok doesn't show that Google accepts the sign-in. Once Google answers, the next try starts the integration. To try straight away, reload it: Settings > Devices & services > Google Home > ⋮ > Reload.
The integration doesn't load after an update¶
An update can stop the integration from loading: a new Home Assistant version may not be able to install the libraries that an older version of the integration needs, and a new release of the integration needs a recent Home Assistant. Settings > Devices & services > Google Home then shows Not loaded. After a restart, an Invalid config notification lists google_home under "The following integrations and platforms could not be set up". The log shows an error such as Setup failed for custom integration 'google_home': Requirements for google_home not found, and adding the integration can show "Config flow could not be loaded".
When Home Assistant is too old for the installed release, Settings > System > Repairs can also show an error that says which version the integration needs. Adding the integration then shows the same message instead of asking you to sign in. The integration's settings are kept.
- Check that your Home Assistant version is supported; see Before you start. If it's older, update Home Assistant first. To stay on your version instead, install an earlier release that supports it, then skip the next step, which would update the integration again:
- If you installed the integration from the Marketplace, or with HACS before Home Assistant moved it to the Marketplace, open Google Home in the Marketplace and select ⋮ > Install another version. Choose an earlier version under Version, install it, then restart Home Assistant.
- On a Home Assistant older than 2026.11, if you installed the integration with HACS, open Google Home in HACS and select ⋮ > Redownload. Expand Need a different version?, choose an earlier version under Release, select Download, then restart Home Assistant.
- If you installed it by hand, delete the
custom_components/google_homefolder in your configuration folder first, so that no newer files stay behind. Then follow the Manual steps under Install the integration with an earlier release. Thehomeassistantvalue in a release'shacs.jsonfile is the oldest Home Assistant version it supports.
- Update the integration to the latest release, then restart Home Assistant.
If the latest release doesn't load either, search the issues for the error, or open an issue with the error from the log.
Sign in again¶
Google can stop accepting the integration's sign-in, for example after you change your Google account's password. Home Assistant then reports that authentication expired, and the Google Home card in Settings > Devices & services shows Reconfigure. Sign in again with the same Google account to keep your devices, their entity IDs and your automations:
- Go to Settings > Devices & services and, on the Google Home card, select Reconfigure.
- Under Sign-in method, choose Browser sign-in (recommended) or Master token. Follow the instructions for that method and use the same Google account as before. Select Submit to sign in.
Home Assistant then reloads the integration with the new sign-in.
Sign in again soon. Until you do, your devices can stop updating one by one, so what Home Assistant shows for them can be out of date, and new devices don't appear. After Home Assistant restarts, the integration doesn't start until you sign in again, and Settings > Devices & services > Google Home shows a message such as "Google didn't accept the sign-in (BadAuthentication). Sign in again."
- If you closed the sign-in window, select Reconfigure again to reopen it.
- You can change the Sign-in method on the same form, including after a sign-in error. The field and instructions update as soon as you choose a method.
- If Home Assistant says that you signed in to a different Google account, see "You signed in to a different Google account".
Signing in again fails¶
The form for signing in again shows the same errors as setup; see Setup fails.
"You signed in to a different Google account"¶
Google reports that you signed in to another account than the one the integration uses, so Home Assistant didn't change anything. The form stays open: sign in there with the account the integration uses. With browser sign-in, close the private window and repeat browser sign-in from step 1, signing in to that account.
To use the other account instead, delete the integration and add it again.
Version 1.13 and older saved the email address you typed when you set up the integration. If that isn't your Google account's primary address, for example because you typed an alternate address, and the integration isn't named after the primary address either, Home Assistant refuses your own account. To keep the integration, name it after your primary address: close the sign-in window, go to Settings > Devices & services > Google Home, open the ⋮ menu, select Rename and enter the address. Then select Reconfigure and sign in again. Otherwise, delete the integration and add it again.
Devices are missing¶
No devices appear¶
The integration adds only Google Cast devices, such as Google speakers and displays. Lights, plugs, thermostats and other devices in your Google Home app don't appear; see Other Google Home devices.
The Google account you signed in with must be a member of the home your devices belong to. Open the Google Home app with that account and check that the devices are listed. If not, invite the account to your home and reload the integration: Settings > Devices & services > Google Home > ⋮ > Reload. If the devices are in a home that you deselected, select it again; see Choose homes.
If Google reports that the account isn't a member of any home when you add the integration, setup stops with "Google reports that this account isn't a member of any home, so there are no speakers or displays to add": invite the account to your home, then add the integration again. If Google reports this later, Settings > System > Repairs shows Google reports no home for your account. If the account is a member only of homes that you deselected, it shows None of your Google account's homes is selected. Each repair says how to fix it.
If you signed in with a Google Workspace account, such as many work and school accounts, it can't be a member of your home: Google doesn't allow inviting Workspace accounts. Sign in with a Gmail account, one ending in @gmail.com, that is a member of your home instead. Some users with personal Google accounts using non-Gmail addresses have also reported missing devices; switching to a Gmail account resolved the problem.
To see what Google lists for the account, collect debug logs while you reload the integration. These lines come from glocaltokens, the library the integration uses to sign in and get your devices:
Iterating in 12 homegraph devices: how many devices Google lists in all the account's homes, including lights and other devices that the integration doesn't add. With0, Google gave no devices for the account: check that it's a member of your home, as described above.'Hallway light' local_auth_token is not found in Homegraph, skipping: Google has no local token for the device, as for lights, plugs and thermostats, so the integration can't add it.- A line that ends with
local_auth_token isn't 108 characters as expected for a Cast device, skipping it: the device's token isn't a Cast device's, as for Google and Nest Wifi routers, so the integration can't add it.
If a skipped device is a speaker or display that you expected, that's why it's missing: get help with the debug logs.
If Google didn't give the integration your devices when it started, for example because Google was busy, the integration starts without devices, and the log shows Failed to fetch Google's device list with the reason the attempt failed. The integration keeps asking Google by itself: after a wait of up to 20 minutes, it asks again at the next update, so a long update interval makes the wait longer. The error says when it asks next, or to sign in again. While polling is turned off, it doesn't ask again by itself, so the error says to reload it instead, as described below. Only the first failure is logged; later ones show in debug logs until one works.
- If the reason is
UNAVAILABLE, check the Google Home section of System information for the results for both Google servers. If Home Assistant's DNS filter or firewall blocks the device list server,googlehomefoyer-pa.googleapis.com, allow it. Google may also be temporarily unavailable. - If the reason is 429, a 5xx code such as 503 or
RESOURCE_EXHAUSTED, wait for Google to stop limiting requests or recover from a temporary problem. - If the reason is
DEADLINE_EXCEEDED, check that Home Assistant can reach Google. See "Couldn't reach Google".
Once the cause is fixed, you can reload the integration to ask Google straight away.
No alarms or timers sensors¶
The integration adds the alarms sensor, timers sensor, alarm and timer event entities, Do Not Disturb switch and alarm volume for a device once the device answers successfully. Until then, a device that is offline, or that doesn't support these features, has only a device sensor, a reboot button, an update sensor, and disabled Wi-Fi and uptime sensors. Check the device sensor:
- It shows an IP address: the entities appear at the next update the device answers successfully. If they don't, the device may have no alarms and timers.
- It's unavailable on all your devices: first check that Home Assistant can reach them on your network; see Home Assistant can't reach your devices. For other causes, see When entities are unavailable.
- It's unavailable on this device: make sure the device is on and connected to your network. The entities appear at the first update it answers successfully. If the integration doesn't know the device's IP address, it gets it from the device's mDNS announcements or from your known hosts, which it asks again about every 5 minutes. It also looks for the device again each time it asks Google for your devices, about every 20 minutes.
If you don't want to wait, make sure the device is online, then reload the integration: Settings > Devices & services > Google Home > ⋮ > Reload. If that doesn't help, restart the Google Home device and then Home Assistant.
Devices without alarms and timers¶
Some Cast devices, such as Chromecast Audio, have no alarms, timers, Do Not Disturb or alarm volume. Such a device keeps only its device sensor, reboot button, update sensor, Wi-Fi sensors and uptime sensor. If it had the other entities, they become unavailable.
If this happens to a device that has alarms and timers, or a device gains these features, make sure the device is online, then reload the integration: Settings > Devices & services > Google Home > ⋮ > Reload. The integration adds the entities once the device answers for them. The integration checks the device again only when it starts, after you reload it or restart Home Assistant, so restarting the device or running google_home.refresh_devices doesn't bring them back.
Advanced: how the integration recognizes these devices
The integration recognizes such a device from how it answers, not from a list of models: the device still answers "not found" when asked for its alarms at least 10 minutes after it first did, and its information lists its features without Google Assistant. A speaker that is starting answers "not found" for a while too, so the integration keeps asking it for alarms until both are true. It then stops, and the debug log shows a line like this, with your device's name and model:
Stereo (hardware='Chromecast Audio') still answers 404 for alarms after at least 10 minutes, and its info lists its features without Google Assistant. It won't be asked for alarms, timers and settings until the integration is reloaded.
Home Assistant can't reach your devices¶
If all your devices have only a device sensor, a reboot button, an update sensor, and disabled Wi-Fi and uptime sensors, and all of them are unavailable, or all their entities became unavailable after they worked, first check that Home Assistant can find and reach the devices on your network. Entities can also be unavailable for other reasons, for example once Google no longer lists a device; see When entities are unavailable.
Check that:
- Home Assistant and the devices are on the same network.
- If Home Assistant runs in Docker, the container uses
hostnetwork mode. - If your devices are on a separate network or VLAN, Home Assistant can find them and reach them on TCP port 8443; see Add devices on another network.
If Home Assistant can't find a device's IP address, the debug log shows this message for it once, after the integration starts. To see it, enable debug logging, then reload the integration:
Failed to fetch timers/alarms information from device Kitchen. We could not determine its IP address, the device is either offline or is not compatible Google Home device. Will try again later.
If only some devices are affected, check that Home Assistant can discover and reach those devices too.
A device stops updating¶
All entities of a device are unavailable¶
Check that the device is on and connected to your network. The entities become unavailable once the device hasn't answered 5 updates in a row, and come back at the next update it answers with anything other than "not found", which a speaker answers for a while as it starts. See When entities are unavailable.
- If they become unavailable for a moment while a speaker restarts and you use a short update interval, increase the interval.
- If only the alarms sensor, timers sensor, switch and alarm volume are unavailable while the device sensor shows an IP address, the integration may have found that the device has no alarms and timers.
- An alarms or timers sensor on its own also shows
unavailablewhen nothing is coming up; see Alarms sensor. - If the entities of all your devices are unavailable, check that Home Assistant can still reach them on your network; see Home Assistant can't reach your devices.
To check that the device doesn't answer, collect debug logs for a few updates while the entities are unavailable. For a device that doesn't answer, each update logs a line such as Failed to connect to Kitchen device. The device is probably offline. or Kitchen device timed out while performing a request to it, usually followed by Kitchen didn't answer when asked for its info. A device without alarms and timers is asked only for its information, so it logs only that last line, and no lines that start with Requesting endpoint. If debug logging was already on when the entities became unavailable, the log also has this line, which appears only once:
Kitchen didn't answer 5 updates in a row. Its entities are unavailable until it answers with something other than "not found".
A device whose IP address Home Assistant doesn't know isn't asked, so it logs none of these lines; see Home Assistant can't reach your devices.
Alarms, timers or settings stop changing¶
If a device's alarms, timers and settings stop changing in Home Assistant while its entities stay available, collect debug logs for a few updates. A line such as Kitchen rejected its token means that the device refuses the token the integration has for it.
A device's token can change, for example when the device restarts. The integration then gets the new token from Google straight away. If Google can't give it, the device's entities keep the values they had, and the integration keeps asking Google by itself. While polling is turned off, it asks only at an update you ask for: run Refresh devices after the time that System information shows under Retry not before.
If Home Assistant asks you to sign in again, do that first. Otherwise, open the log and find the error that starts with Failed to fetch Google's device list. Use the reason in that error to decide what to check.
- If the reason is
UNAVAILABLE, check whether Home Assistant can reach the device list server. See No devices appear. - If the reason is 429, a 5xx code such as 503 or
RESOURCE_EXHAUSTED, wait for Google to stop limiting requests or recover from a temporary problem. - If the reason is
Cannot connect to host ...,TimeoutErrororDEADLINE_EXCEEDED, check that Home Assistant can reach Google. See "Couldn't reach Google".
If the log instead has an error such as Kitchen rejected the token that Google gave it. Google is asked for a new one at the first update after 2 min; further rejections are logged at debug level until it accepts one, Google answered, but with a token that the device rejects too. Right after a device restarts, Google can give its old token for a short while, so the integration asks Google again a minute later, and logs this error only if the device rejects that token as well.
The integration then doesn't ask Google for that device at every update: it asks again at the first update after the time in the error, then after 5 and 10 minutes, and then every 20 minutes, until the device accepts a token. Meanwhile, another device whose token changes still gets its new token straight away. System information shows the device list as fetched, without Retry not before. Once the device accepts a token, its alarms, timers and settings change again, and with debug logging on, the log shows Updating Kitchen works again. While polling is turned off, the integration doesn't wait like this: each Refresh devices asks Google. If the device's alarms, timers and settings still don't change, or the error comes back, get help with debug logs.
Once the cause is fixed, you can reload the integration to ask Google straight away: Settings > Devices & services > Google Home > ⋮ > Reload.
If the log instead has an error such as Failed to parse fetched alarms and timers for device Kitchen - API returned unknown json structure, Kitchen sent a reply to setup/assistant/alarms that isn't valid JSON, Kitchen sent a reply to setup/assistant/alarms/volume that isn't a JSON object or Kitchen sent an alarm volume that isn't a number, the device answered with something the integration can't read. The entities that reply is for keep the values they had, which may be out of date, until a reply can be read again. The device's other entities still update, but alarm and timer events aren't fired for that update or the next one that works. If the error keeps coming back, get help and attach diagnostics.
An action or setting fails¶
Deleting alarms or timers, rebooting, turning Do Not Disturb on or off and setting the alarm volume fail with an error, rather than look successful, when a device may not have done what you asked. Most errors name the device and say why. To let your automation or script carry on after an error, see Continue after an error.
A delete fails¶
The four delete actions show these errors:
- "Couldn't get the current alarms and timers from Kitchen, so nothing was deleted from it. Check that it's online and try again later". The device didn't send its current alarms and timers, for example because it has just become unreachable or, while polling is on, rejects its token, so it got no delete request.
- "Kitchen didn't confirm deleting the alarms or timers, so they may still be set. Check that it's online and try again later". The device stopped answering, refused or sent an unexpected reply, and may still have deleted them. Unless
skip_refreshistrue, the action asks the device for an update, which shows what it has. - While polling is turned off, when the device rejected its token, either error ends with this instead of "Check that it's online and try again later": "It rejected its token. Polling is turned off, so the integration doesn't ask Google again by itself: run the Refresh devices action, then try again". Run Refresh devices once, then try the delete again. If that doesn't help, see the same message under A setting or reboot fails.
- If several devices fail, one error names them all. When none of them sent its current alarms and timers: "Couldn't get the current alarms and timers from these devices, so nothing was deleted from them: Bedroom, Kitchen. Check that they're online and try again later". Otherwise: "Couldn't delete alarms or timers from these devices, or confirm that they were deleted: Bedroom, Kitchen. Check that they're online and try again later". While polling is turned off, the error is this instead when at least one of them rejected its token: "Couldn't delete alarms or timers from these devices, or confirm that they were deleted: Bedroom, Kitchen. At least one of them rejected its token. Polling is turned off, so the integration doesn't ask Google again by itself: run the Refresh devices action, check that the devices are online, then try again". Refresh devices updates all of them, so you don't need to know which one it was.
- "Couldn't find the alarm alarm/6ed06a56-8a58-c6e3-a7d4-03f92c9d8a51 on the devices you targeted. It may already have gone off or been deleted", or the same for a timer. Every device the action checked sent its current list without the ID. A device that Home Assistant skipped, because its sensor is unavailable, hidden or disabled, may still have it. After a device didn't confirm a delete, this error on a retry means that the devices it checked no longer have it.
- "“alarm/123” isn't an alarm ID. Copy the ID, which starts with alarm/, from the alarms attribute of the device's alarms sensor", or the same for a timer. The ID doesn't start with
alarm/ortimer/, or has the wrong length, so no device was asked.
A setting or reboot fails¶
Turning Do Not Disturb on or off, setting the alarm volume, pressing Reboot and the Reboot device action show these errors:
- "Couldn't reach Living Room. Check that it's on and connected to your network, then try again". The device refused the connection or your network reports it as unreachable, or Home Assistant doesn't know its IP address.
- "Living Room didn't confirm that it did this: it didn't answer in time, or its answer was cut off. Check that it's online and try again". The device didn't answer within about 5 seconds, or its answer was cut off. The next update shows the device's current Do Not Disturb setting and alarm volume.
- "Living Room rejected its token. The integration keeps asking Google for one, so try again later". The integration keeps asking Google for a new token by itself, at the first update after a wait of up to 20 minutes; see Alarms, timers or settings stop changing. If Home Assistant asks you to sign in again, do that first.
- "Living Room rejected its token. Polling is turned off, so the integration doesn't ask Google again by itself: run the Refresh devices action, then try again". Run Refresh devices once, then try the action again. If System information shows Retry not before, a refresh before that time doesn't help. If the action still fails after that, see Alarms, timers or settings stop changing to find out why the token is still being rejected. If Home Assistant asks you to sign in again, do that first.
- "Living Room answered “not found”. It may still be starting up, so try again later, or it may not support this".
- "Couldn't do this on Living Room. For details, see the Home Assistant log". The device answered with another error, or the request failed for another reason. Open the log to see what it was.
- "These devices didn't confirm that they'll reboot: Bedroom, Kitchen. Check that they're online and try again later". Reboot device gives this when more than one device fails. It still reboots every device that answers.
An action fails while the integration isn't loaded¶
While the integration isn't loaded, its actions, such as google_home.delete_alarm, fail whatever you target, and nothing is sent to your devices: "Config entry you@example.com for integration google_home is not loaded". Instead of you@example.com, it shows the integration's name, usually your Google account. This happens, for example, when Google didn't accept the master token at startup, while Home Assistant waits to try setting up the integration again, or while it's still setting it up after a restart.
Open Settings > Devices & services > Google Home to see why it isn't loaded, and if Home Assistant asks you to, sign in again. Once the integration is loaded, the actions run again.
Check System information¶
Home Assistant's System information has a Google Home section. It shows whether Home Assistant can reach Google, whether the integration has your devices from Google, and how many of them don't answer. Unlike diagnostics, it's there once you've added the integration, even if it then fails to set up. It isn't there while you add the integration for the first time, so it can't help when adding the integration shows an error. It isn't there either if your integration version is 1.16.0 or earlier.
In your instance, go to Settings > System > Repairs, open the ⋮ menu, select System information and find Google Home. You can also open System information directly.
The section shows:
- Reach Google sign-in server (
android.clients.google.com) and Reach Google device list server (googlehomefoyer-pa.googleapis.com) each showokif their host answered an HTTP request. An HTTP response confirms basic host reachability only. Sign-in and the gRPC request for the device list can still fail. If a check fails, it showsunreachableortimeoutwith a more info link to "Couldn't reach Google". - Google's device list:
fetched: the integration's devices come from a time when Google gave the list. It doesn't say when that was.not fetched: Google hasn't given the list since the integration started, or a device's token changed and the list is to be fetched again.sign-in rejected: Google rejected the master token during an earlier attempt, and no attempt has worked since. It stays even if Google later answers with a server error or asks to try later. Sign in again.
- Retry not before: while the list needs to be fetched again and the integration waits after a failed attempt, the earliest time it asks Google again, at the first update after that time. While polling is turned off, it asks only when something updates the devices, such as Refresh devices.
- Polling for changes:
falsewhile polling is turned off. Bluetooth tracking:trueif you turned it on in the options. - Devices in Google's list and Devices not answering: how many devices the integration has from Google, without those in homes that you deselected, and how many of them don't answer. These show once Google has given the list, even an empty one.
- A device without an IP address doesn't answer; see Home Assistant can't reach your devices.
- A device that missed 5 updates in a row counts until it answers again after it finishes starting.
- A device that you disabled isn't asked, so it isn't counted as not answering. It's still in Google's list.
If the integration fails to set up, the section shows only whether Home Assistant can reach Google. Open Settings > Devices & services > Google Home to see why setup failed.
The values are in English in every language. The Google Home section has no names, email addresses, IDs or IP addresses. Copy copies the whole of System information, though, with the other integrations' sections and details about your system: check the text before you post it.
Download diagnostics¶
The diagnostics file shows:
- The integration's options.
- For each device: its model, whether it answers, whether Home Assistant has received its mDNS announcements since the integration loaded, its last reply about alarms and timers, as the device sent it, its firmware versions and release channel, whether it says a firmware update is waiting, its Wi-Fi signal strength, and its estimated last boot time (
booted_at, before Home Assistant smooths it). - Bluetooth tracking (
bluetooth), which isnullwhen Bluetooth tracking is off or no devices are tracked. Each tracker shows its lateststate, includingunavailable. For each speaker, it shows:- Whether it's
excluded(including disabled speakers) orunsupported. - Whether it has ever returned scan results since the integration last loaded (
answered). - Whether it has scanned without a break for the last 90 seconds (
covers_presence_window), and the end of its covered scan interval (covered_until, not the time results were read). - Whether it's active (
participating). An active speaker whosecovers_presence_windowisfalsekeeps trackers from making a newnot_homedecision, as described in Tracker is unavailable. - How many seconds ago it last returned usable scan results (
last_success_age), and how many seconds it stays active if it returns no more (remaining_lease). Both include results from before a restart or reload, so a speaker can beparticipatingwhileansweredisfalse. Both arenullwhen no recent results are recorded for it.
- Whether it's
- How many other Cast devices on your network have announced themselves since the integration loaded but aren't in Google's device list, such as TVs with Chromecast built in, or speakers in another Google account. Only the number, not their names or addresses. Devices in homes that you deselected don't count.
- When you downloaded it.
Attach the file and debug logs when you open an issue, and paste the Google Home section of System information. Versions 1.16.0 and earlier have neither the diagnostics file nor that section.
- Go to Settings > Devices & services > Google Home.
- Open the ⋮ menu and select Download diagnostics. Your browser downloads the file.
The menu has Download diagnostics only while the integration is set up. If setup fails, collect debug logs instead. Once the integration is added, System information also works while it fails to set up.
Check the file before sharing it
The file replaces your email address, password, master token and Android ID, your devices' local tokens, IP addresses and Wi-Fi network names, and your known hosts with **REDACTED**. It keeps your device names and the times and labels of your alarms and timers. Home Assistant also adds details about your system, such as its version, your time zone and the custom integrations you use. Open the file and replace anything you don't want to share with xxx before you attach it to a public issue.
Collect debug logs¶
Debug logs show what the integration is doing. Attach them when you open an issue.
- Go to Settings > Devices & services > Google Home.
- Open the ⋮ menu and select Enable debug logging.
- Reproduce the problem.
- Open the ⋮ menu again and select Disable debug logging. Your browser downloads the log file.
While you add the integration for the first time, it has no ⋮ menu yet. Instead, run this action in Settings > Tools > Actions, then try to add the integration again. The action also logs glocaltokens, the library the integration uses to sign in:
action: logger.set_level
data:
custom_components.google_home: debug
glocaltokens: debug
Then open the log. It first shows only warnings and errors: select Download logs to save the whole log, or open its ⋮ menu and select Show raw logs.
Remove secrets before sharing logs
Debug logs can contain your email address, tokens and the IP addresses of your devices. Replace them with xxx before you post the log.
Still stuck¶
Search the issues for your problem. If nobody has reported it, open an issue with your diagnostics, the Google Home section of System information and debug logs. Versions 1.16.0 and earlier have neither the diagnostics file nor that section.