- Google Assistant integration not set up (Nabu Casa or manual)
- Devices/entities not exposed to Google
- Sync not run after adding devices
Problem Description
Home Assistant isn't responding to Google Home voice commands, or your HA devices don't appear in the Google Home app. This is an integration/exposure problem — HA connects to Google Assistant via Nabu Casa (Home Assistant Cloud) or a manual setup, and devices must be exposed and synced.
Why This Happens in Real Homes
Controlling Home Assistant with Google requires two things: the Google Assistant integration set up (easiest via Nabu Casa cloud, or a fiddly manual Actions project) and each entity explicitly exposed to Google. Missing or unsynced exposures are why devices don't appear or respond.
Start by confirming the integration is configured, then expose the specific entities you want to Google and run a device sync ("Hey Google, sync my devices"). Nabu Casa handles reachability for you; a manual setup adds project and key configuration that's easy to get wrong, so it's the usual suspect when links fail.
Symptoms
- Google does not control HA devices
- Devices missing in Google Home
- Voice commands ignored
- Link fails
- Devices not syncing
- Some devices work, others do not
- Duplicate devices
- Errors after adding devices
Recognize these? Here's what usually causes it.
Common Causes
- Google Assistant integration not set up (Nabu Casa or manual)
- Devices/entities not exposed to Google
- Sync not run after adding devices
- Account link expired
- Manual setup misconfigured (project/keys)
- Unsupported entity types
- Naming conflicts
- HA not reachable from Google's cloud
Most fixes happen in the first 3 steps.
Do not factory reset your hub unless absolutely necessary as this removes all paired devices, automations, and settings. You will need to re-pair every single device from scratch which can take hours for a large setup. Always try a simple restart first.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Set up the Google Home integration
In Home Assistant, go to Settings > Devices & Services > Add Integration > search for 'Google Assistant.' There are two methods: Home Assistant Cloud (Nabu Casa subscription — easiest, no port forwarding needed) or manual setup (requires a Google Cloud project and OAuth credentials). For Nabu Casa: enable Google Assistant in your cloud account settings. For manual: create a project in the Google Actions Console, set up account linking, and enter the OAuth credentials in Home Assistant.
Expose entities to Google Home
Not all Home Assistant entities are exposed to Google Home by default. Go to Settings > Voice Assistants > Google Assistant > Exposed Entities. Toggle on the devices you want to control with Google Home. Each entity type maps to a Google device type: switches become switches, lights become lights, covers become blinds, climate entities become thermostats. Rename entities with friendly names that are easy to say — 'Living Room Light' works better with voice than 'light.hue_color_lamp_2.'
Sync devices with Google Home
After exposing entities, say 'Hey Google, sync my devices' or go to the Google Home app > Settings > Works with Google > your Home Assistant link > resync. Google Home pulls the updated entity list from Home Assistant. New devices should appear in the Google Home app within 30 seconds. If devices do not appear, check the Home Assistant log for errors related to the Google integration.
Fix devices showing offline in Google Home
If Home Assistant devices show 'offline' in Google Home: Home Assistant must be accessible from the internet. For Nabu Casa users: check your subscription status and cloud connection (Settings > Home Assistant Cloud). For manual setup: verify your Home Assistant URL is reachable externally (HTTPS required). Check that the URL in the Google Actions Console matches your actual external URL. A certificate error, expired DuckDNS domain, or changed IP breaks the connection.
Fix voice commands not working correctly
If Google responds 'Sorry, I can't reach Home Assistant': the cloud connection is down. Check your internet and Nabu Casa/manual external access. If Google says 'I don't know how to do that': the entity type may not be supported or the entity name conflicts with a built-in Google command. Rename the entity — avoid names like 'TV' or 'Lights' that conflict with Google's built-in device categories. Use specific names like 'Bedroom Lamp' or 'Kitchen Fan.'
Quick Solutions
Still having issues? This is usually the deeper cause below.
If voice commands stopped working after relinking the account, check that the skill or action is still enabled — relinking sometimes disables it silently.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- Google Assistant integration not set up (Nabu Casa or
- Devices/entities not exposed to Google
- Sync not run after adding devices
- Account link expired
- Manual setup misconfigured (project/keys)
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Home Assistant owners.

Home Assistant Connect ZWA-2 | Connect Z-Wave devices to ...

Zooz 800 Series Z-Wave Long Range GPIO Module ZAC93 LR (U...

Home Assistant Connect ZBT-2 | Connect Zigbee, Thread, or...
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Home Assistant provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Home Assistant.
Source: home-assistant.io
Need More Help? Home Assistant Support
Note: The contact information below connects you directly to Home Assistant's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.




