Home Assistant Alexa & Google Home Integration Guide

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

Getting Alexa or Google Home to control a Home Assistant setup used to come down to one choice: pay for the easy path, or spend an afternoon wiring up AWS Lambda yourself. That choice still exists in 2026, but it's no longer the whole story — a local Matter bridge has matured to the point where it's a legitimate third option, and the free Google Assistant route that used to work has quietly become unreliable enough that most guides recommending it are out of date.

This matters because the three paths trade off differently on cost, reliability, and how much of the integration lives on someone else's server. Nabu Casa's Home Assistant Cloud is a paid subscription that trades a few dollars a month for a setup that takes minutes and stays working. The free official routes — an AWS Lambda skill for Alexa, a Google Home Developer Console project for Google — cost nothing but ask for real setup time, and on the Google side, increasingly don't work at all. The local Matter Hub add-on sits apart from both: no subscription, no cloud round-trip, but it depends on owning the right kind of Alexa or Google hardware to act as a Matter controller.

This guide walks through all five practical routes — Alexa via Nabu Casa, Alexa via free Lambda, Google via Nabu Casa, Google via the free Developer Console (and why to skip it), and the local Matter Hub — with the exact prerequisites, steps, and the specific error messages people hit along the way.

This one's for anyone running Home Assistant who wants voice control without guessing which integration is current, and for anyone who tried the free Google path last year and got stuck on a 404.

What You'll Need

• A Home Assistant instance on a recent release (2026.x) — either Home Assistant Green or any self-hosted install
• An Alexa-enabled device (Echo speaker or display) if targeting Alexa
• A Google Assistant device (Nest/Google Home speaker or display) if targeting Google
• For the paid path: a Nabu Casa Home Assistant Cloud subscription (30-day free trial available)
• For the free Alexa path: an Amazon Developer account, an AWS account, and a domain with a trusted SSL certificate on port 443
• For the local Matter path: the community Matter Hub add-on and an Alexa or Google device that itself supports Matter (not every Echo or Nest unit does)
• 10 minutes to several hours, depending on the path chosen

Before You Start — Which Path Fits Your Setup

Three names get thrown around interchangeably and shouldn't be: the Alexa Smart Home Skill lets Alexa control Home Assistant entities; the Alexa Devices integration (added in HA 2025.6) does the reverse — it lets Home Assistant control Echo devices; and Alexa Media Player, a community HACS integration, adds advanced Echo control but breaks more often since it isn't official. This guide covers the Smart Home Skill, since that's what actually answers "how do I ask Alexa to turn off the living room lights."

The decision that matters most upfront is whether local control is worth the setup cost. Nabu Casa's Cloud service handles both Alexa and Google in a few clicks with no port forwarding, with a 30-day free trial available. The free official routes remove the subscription but add real complexity — and on the Google side, current reports describe account linking failing outright, with the developer console's test project expiring roughly every 30 days and needing manual reactivation. The Matter Hub add-on is free and fully local, but only works if there's a Matter-capable Alexa or Google device already on the network — an Echo Dot Max or Nest Hub, not every Echo model qualifies.

Aliases are another asymmetry worth knowing before choosing a path: Google Assistant supports naming aliases for exposed entities, so "the lamp" and "reading light" can both refer to the same entity. Alexa does not support aliases, so entity names need to be set correctly the first time.

Step 1 — Connect Alexa via Home Assistant Cloud (Recommended)

This is the fastest route and the one worth trying first for anyone not committed to a fully local stack.

1. Go to Settings > Home Assistant Cloud and sign up or log in (30-day free trial, no card commitment required to start).
2. Navigate to Settings > Voice assistants and enable Alexa.
3. On the Expose tab, select at least one entity to expose to Alexa — nothing syncs until something is exposed.
4. In the Alexa app: More > Skills & Games, search "Home Assistant," enable the skill, and link it to the Nabu Casa account.
5. Say "Alexa, discover devices."

Total time is roughly 10–15 minutes, and no HTTPS setup or port forwarding is needed since Nabu Casa handles the secure tunnel. If discovery comes back empty, confirm entities are actually exposed on the Expose tab and re-run discovery — this single step accounts for most "no devices found" reports. If the skill won't link, log out of the Nabu Casa account in the Alexa app and log back in.

An Echo Dot (5th Gen) is the cheapest way to get an Alexa voice front-end into a room purely for this purpose — it has no Matter or Thread radio, so it's a pure voice endpoint rather than a bridge, which is fine for this path since Nabu Casa handles connectivity in the cloud.

Step 2 — Connect Alexa the Free Way (AWS Lambda Smart Home Skill)

This route removes the subscription cost but replaces it with real setup time and ongoing maintenance risk — expect roughly one to two hours, most of it in the AWS and Amazon Developer consoles.

1. Set up HTTPS remote access for the Home Assistant instance on port 443 with a valid (non-self-signed) certificate — the DuckDNS add-on paired with Let's Encrypt is the simplest route for most self-hosted setups.
2. In the Alexa Developer Console: Create Skill > Smart Home > Provision your own, using the v3 payload. Note the Skill ID.
3. In AWS: create an IAM role with the AWSLambdaBasicExecutionRole policy, then create a Lambda function using Home Assistant's provided code. The Lambda function must be created in the AWS region matching the Amazon account's locale — a mismatch here is the single most common reason this integration silently fails.
4. Point the skill's Smart Home service endpoint at the Home Assistant instance's /api/alexa/smart_home path.
5. Complete account linking (OAuth) between the skill and Home Assistant.
6. Enable the skill in the Alexa app and run device discovery.

If discovery fails, the AWS region is the first thing to check. A "Token Invalid and no Refresh Token Available" error — a documented Home Assistant troubleshooting case — means account linking needs to be redone from scratch rather than retried in place. This path also depends on that HTTPS certificate staying valid; a lapsed cert quietly breaks the whole integration until renewed.

Step 3 — Connect Google Home via Home Assistant Cloud (Recommended)

The Google-side equivalent of Path A, and just as fast:

1. Go to Settings > Home Assistant Cloud and log in.
2. Navigate to Settings > Voice assistants and enable Google Assistant.
3. On the Expose tab, select at least one entity.
4. In the Google Home app: + > Set up device > Works with Google, search "Home Assistant," and link the Nabu Casa account.
5. Devices sync automatically — no manual discovery command needed.

If linking returns a request_sync (404) error or devices don't appear, re-toggle Google Assistant off and on in the Cloud configuration, then re-link from the Google Home app. Since Google supports aliases, this is also the point to add any alternate names for entities that get requested in casual phrasing.

A Google Nest Hub (2nd Gen) works well as a Google-side voice and visual front-end for this setup, and doubles as a Thread border router if a Matter-over-Thread device gets added to the network later.

Step 4 — Why the Free Google Assistant Path Isn't Worth Trying in 2026

The free route via the Google Home Developer Console still exists on paper, but current reports describe it as broken for most new setups, and it's worth understanding why before spending an evening on it.

1. Set up HTTPS remote access with a valid hostname and SSL certificate.
2. Create a project in the Google Home Developer Console (the older Actions on Google console is retired) and record the Project ID.
3. Configure the google_assistant integration in configuration.yaml with the project ID and a service account.
4. Enable the HomeGraph API and generate a service account key.
5. Link the resulting "[test]" project inside the Google Home app.

The failure mode reported most often is account linking rejecting the connection outright with a "Could not reach [test]…" error, and even when linking succeeds, the test project expires roughly every 30 days and requires manual reactivation — a maintenance burden with no equivalent on the Alexa side. This stems from Google's sunset of Conversational Actions, which pulled the ground out from under the workflow most existing guides still describe. Unless there's a specific reason to avoid Nabu Casa entirely, Path C or the Matter Hub below are the more durable choices for Google integration.

Step 5 — Local Matter Hub: One Bridge for Alexa, Google, and Apple

This is the option worth considering for a fully local setup that skips both the subscription and the free-Google headache — at the cost of needing the right hardware already in place.

1. Install the Home Assistant Matter Hub add-on (the actively maintained fork, since the original project was discontinued in early 2026) or run it via Docker.
2. Configure a bridge and select which entities to expose through it.
3. In the Alexa, Google Home, or Apple Home app, add a new Matter device and scan the generated QR code or pairing code.
4. Devices appear locally on the chosen ecosystem — no port forwarding, no subscription, no cloud round-trip for control.

This only works if there's a Matter-capable controller device already on the network: for Alexa, that means an Echo Dot Max or newer Echo with built-in Zigbee, Matter, and Thread radios — the standard Echo Dot does not qualify. For Google, a genuine Nest or Google Home Hub is required. Expect roughly 30–60 minutes for setup. Alexa has a practical limit of around 80–100 devices per bridge before pairing gets unreliable, and any VLAN or firewall segmentation on the network will break Matter's local discovery unless multicast traffic is explicitly reflected across segments. For more detail on getting Matter running correctly, see the dedicated Matter integration setup guide and the broader Matter explainer for how Thread border routers fit into the picture.

Common Mistakes to Avoid

• Confusing the three "Alexa" integrations. The Smart Home Skill (Alexa controls HA), the Alexa Devices integration (HA controls Echoes), and the community Alexa Media Player each do different jobs — installing the wrong one wastes the setup time above.
• Skipping the Expose tab. Enabling a voice assistant in Home Assistant Cloud does nothing on its own; entities have to be explicitly exposed before any discovery command finds them.
• Running AWS Lambda in the wrong region. The Lambda function must match the AWS region tied to the Amazon account's locale — a mismatch causes silent discovery failures with no obvious error.
• Assuming the free Google path still works like it did a year ago. Conversational Actions are gone; the current Developer Console flow is documented as unreliable, with test projects expiring on a roughly 30-day cycle.
• Buying a standard Echo Dot expecting Matter support. The base Echo Dot (5th Gen) has no Zigbee, Matter, or Thread radio — only the Echo Dot Max and select newer Echo models can serve as a Matter controller.
• Ignoring VLAN segmentation with the Matter Hub. Matter's local discovery relies on multicast traffic that doesn't cross network segments by default; a segmented network needs explicit multicast reflection.

Frequently Asked Questions

Conclusion

For most setups, Home Assistant Cloud is the right starting point for both Alexa and Google — it's the only path that treats both ecosystems the same way, takes minutes rather than hours, and doesn't depend on a free Google workflow that's been quietly falling apart since Conversational Actions was retired. The free AWS Lambda route for Alexa remains genuinely viable for anyone willing to spend an hour or two in the AWS console and keep an SSL certificate current, but the equivalent free path for Google isn't worth the time it costs right now.

The Matter Hub add-on is the one to watch: it's free, fully local, and works across Alexa, Google, and Apple Home from a single bridge — but it only pays off if a Matter-capable device like an Echo Dot Max or a genuine Nest Hub is already part of the setup. Anyone building out that hardware layer should also look at Home Assistant hardware options to make sure the host itself can keep up, and at how Zigbee, Z-Wave, and Matter fit together before deciding which devices to bridge through it. Once voice control is working, pairing it with a few practical automations is usually the next logical step.