Home Assistant Alexa Integration via Matter Bridge: Step-By-Step Guide

Introduction

Want to control a Home Assistant device with a command such as "Alexa, turn on the living room light"? There are four practical ways to expose Home Assistant devices to Alexa: Home Assistant Cloud, a manually configured Alexa Smart Home Skill, Emulated Hue, or a Matter bridge.

A Matter bridge is useful when you want to avoid both a Home Assistant Cloud subscription and a publicly reachable Home Assistant endpoint. It translates supported Home Assistant entities into Matter endpoints that Alexa can discover through a compatible Matter controller.

This guide compares the four Home Assistant Alexa integration options, explains where Matter Bridge fits, and shows how to expose supported Home Assistant entities to Alexa using SONOFF ZBBridge-U and Bridge Max (Bridge-M).

1. What Does Home Assistant Alexa Integration Actually Do? 

Most people searching for a Home Assistant Alexa integration want this:

• Alexa voice command → Home Assistant entity → smart device

Your light, switch, curtain, or thermostat is already available in Home Assistant. You want Alexa to discover it and provide convenient voice control through an Echo speaker or the Alexa app.

This is different from Home Assistant's Alexa Devices integration, which brings supported Echo and Alexa-enabled devices into Home Assistant for features such as announcements, sound playback, text commands, and Do Not Disturb.

In this guide, "Home Assistant Alexa integration" means exposing Home Assistant devices to Alexa for discovery and voice control.

 

2. 4 Ways to Connect Home Assistant to Alexa

There are four practical approaches to exposing Home Assistant devices to Alexa: Home Assistant Cloud, a manual Alexa Smart Home Skill, Emulated Hue, and a Matter bridge. The biggest differences are subscription cost, whether Home Assistant must be publicly reachable, setup complexity, and device capability support.

*Home Assistant Cloud and the manual Smart Home Skill generally provide broader Alexa capabilities. Emulated Hue and Matter Bridge depend more heavily on supported device and capability mappings.  

Which method should you choose?

● Home Assistant Cloud: best when ease of setup and official support matter more than avoiding a subscription.

● Manual Alexa Smart Home Skill: best for advanced users who want broader Alexa capabilities without Home Assistant Cloud and are comfortable maintaining AWS and public HTTPS.

● Emulated Hue: suitable for basic voice control, but its Hue-style device model and discovery requirements make it less flexible for a new setup. Home Assistant's own documentation notes that devices are largely presented to Alexa as Hue-style lights.

● Matter Bridge: useful when you want Home Assistant to remain locally reachable only, while exposing supported device types to Alexa through Matter.

Note: Software Matter bridges are also available. Community projects such as Home-Assistant-Matter-Hub and Matterbridge can publish Home Assistant entities to Matter without dedicated hardware. A hardware bridge uses the same basic idea but moves the bridge service onto a dedicated device rather than another Home Assistant add-on or container.

Matter bridging is now a practical option for exposing supported Home Assistant entities to Alexa without making Home Assistant publicly reachable. Its main limitation is compatibility: both the bridge and Alexa must support the corresponding Matter device type and capability.  

 

3. How Does a Matter Bridge Connect Home Assistant to Alexa?

A Matter bridge translates supported Home Assistant entities into bridged Matter endpoints that Alexa can understand. Home Assistant remains the system controlling the original device; the bridge exposes only the device types and capabilities it can map to Matter.

The architecture has two distinct flows:

During setup:

• Supported Home Assistant entity → Matter Bridge maps the capability → bridged Matter endpoint → Alexa Matter fabric  

During voice control:

• Voice request → Alexa cloud → compatible Echo or eero Matter controller → Matter Bridge → Home Assistant → target device

The Matter communication between the Alexa controller and the bridge occurs over the local network, as does the bridge's connection to Home Assistant. Alexa's voice recognition itself still normally depends on Amazon's cloud.  

👉 Amazon maintains a current list of supported Alexa Matter device types.

Does Home Assistant Have a Built-In Matter Bridge?

No. Home Assistant's built-in Matter integration makes Home Assistant a Matter controller, not a Matter bridge. It can control Matter devices and devices exposed by third-party Matter bridges, but it cannot publish arbitrary existing Home Assistant entities as Matter devices. A separate software or hardware Matter bridge is required for that use case.

This distinction also explains why Matter multi-admin is not a replacement for a bridge.

Matter Bridge vs. Matter Multi-Admin

• Matter multi-admin shares an already-native Matter device with another Matter fabric. For example, a Matter plug connected to Home Assistant can also be commissioned into Alexa.
• A Matter bridge solves a different problem: it represents supported non-Matter or platform-managed devices as Matter endpoints.

Therefore:

• Native Matter device that you want in both HA and Alexa → use multi-admin.
• Existing non-Matter HA entity that you want Alexa to control → use a Matter bridge.

 

4. SONOFF Matter Bridge for Home Assistant and Alexa

SONOFF Zigbee Bridge Ultra (ZBBridge-U) and Bridge Max (Bridge-M) provide dedicated hardware implementations of the Matter Bridge workflow described above. After local Home Assistant authorization, they can expose supported Home Assistant entities — including supported devices from other brands — to Alexa and other Matter ecosystems.

The main reason to choose this approach over a software Matter bridge is operational rather than protocol-level: you do not need to run and maintain another Matter bridge add-on or container on the Home Assistant host.

Compatibility note: Only entity types and features that the bridge can map to Matter — and that Alexa supports — will be available. Check the Bridge device and feature compatibility table before setup.  

ZBBridge-U vs. Bridge Max: Which Should You Choose?  

Both ZBBridge-U and Bridge Max support the workflow covered in this guide: Home Assistant authorization, Local Web configuration, and Matter Bridge synchronization to Alexa. They are not simply higher- and lower-end versions of the same product; their strengths are different.  

● Choose ZBBridge-U if Zigbee scale and additional hub capabilities are the priority. It supports up to 256 compatible Zigbee devices and includes substantially more memory and storage.

● Choose Bridge Max if broader connectivity matters more. It supports up to 128 compatible Zigbee devices, adds BTHome support, and provides dual-band 2.4/5 GHz Wi-Fi 6 in addition to Ethernet.  

For the Home Assistant-to-Alexa Matter Bridge workflow in this article, both products provide the required Matter Bridge and Local Web functions.

 

5. How to Connect Home Assistant to Alexa via a SONOFF Matter Bridge?

The steps below use ZBBridge-U, but the same Home Assistant-to-Alexa workflow is available on Bridge Max; menu layout may vary slightly by firmware.  

This setup has two parts:

1. Commission the SONOFF Matter bridge into Alexa's Matter fabric.
2. Connect the Matter bridge to Home Assistant and select the supported entities you want Alexa to discover.

This guide shows the Alexa-specific workflow in full.   For the same Matter Bridge workflow with other ecosystems, see How to Bridge Home Assistant Devices to Matter Fabrics.  

Before You Start

You need:

• Home Assistant with the target devices and entities working correctly
• Matter Bridge (ZBBridge-U or Bridge Max) running current firmware  
• The current Alexa app on your phone  
• A compatible Echo or eero acting as an Alexa Matter controller  
• The Alexa app is signed in to the Amazon account that manages that controller

For initial setup, keep the bridge, phone, and Alexa Matter controller on the same LAN. Home Assistant must also be locally reachable by the bridge. Advanced VLAN setups may work, but Matter commissioning depends on IPv6 and multicast discovery and may require additional network configuration.  

The Alexa app is used for setup but is not itself the Matter controller. Check Amazon's current Matter-compatible Echo and eero list.

Tip: Use short, distinct entity names before syncing. Avoid exposing multiple devices with nearly identical Alexa names, which can make voice targeting ambiguous.  

Step 1: Open the Local Web Interface

Power the bridge and connect it to your local network. From a phone or computer on the same network, open:  http://zbbridgeu.local/. If the .local address does not resolve, use the bridge's IP address shown by your router.  

👉 Bridge Max users should open the bridge's own Local Web address or follow the Bridge Max Local Web setup guide.

During the first login, follow the prompts to set the time zone and create a local password.  

Step 2: Add the Matter Bridge to Alexa

From the Local Web home page, find Matter Bridge and select Start Pairing. You can also open Matter Bridge from the left navigation menu and start pairing from the Pairing tab.  

The bridge displays a Matter QR code and the numeric pairing code. The pairing session remains active for approximately 15 minutes.  

In the Alexa app:

1. Open Devices.
2. Select + → Add Device.
3. Choose Matter.
4. Scan the QR code or enter the numeric pairing code.
5. Follow the on-screen instructions to complete setup.

Alexa menu labels may vary by app version and region.

After pairing, open Matter Bridge → Matter Fabrics in the Local Web interface to confirm that the bridge has joined a Matter fabric. Removing that fabric will also make its bridged devices appear offline or unavailable in Alexa.

Step 3: Connect the Bridge to Home Assistant

In the bridge's Local Web interface, select: Home Assistant → Sync Home Assistant Entities to Matter Fabrics. 

Select Get Started. The bridge scans the local network for available Home Assistant instances.  

If your server is found, select it and continue. If automatic discovery fails, choose Manual Configuration and enter:

• The local IP address or domain name of Home Assistant.
• The Home Assistant port — normally 8123, unless you changed it.

Select Sign in to Home Assistant, enter your Home Assistant credentials on the authorization page, and approve access.

After authorization, the bridge loads the Home Assistant devices and entities it can evaluate for Matter synchronization.

Step 4: Select Home Assistant Entities to Expose to Alexa

In the bridge's Local Web interface, open Home Assistant → Sync Home Assistant Entities to Matter Fabrics → Sync Management.

The list shows whether each entity is:  

• Not Synced: supported and available for selection
• Synced: already exposed to a Matter fabric
• Not Supported: cannot currently be mapped by the bridge

Check only the supported entities you want Alexa to discover, then select Save.

Avoid exposing diagnostic or update entities. Also avoid sending the same device to Alexa via both a manufacturer skill and the Matter Bridge, because multiple integration paths can create duplicate Alexa devices.  

An entity visible in Home Assistant is not automatically available for synchronization. Its entity type must be supported by the bridge and map to a capability supported by Alexa. Consult the Bridge device and feature compatibility table when an expected entity or control is unavailable.  

Step 5: Confirm the Devices and Test Alexa Voice Control

Allow Alexa a moment to refresh the bridged endpoints. If necessary, start device discovery from the Alexa app. Assign the discovered devices to the appropriate Alexa rooms, then start with a basic request such as "Alexa, turn on the desk lamp."  

If on/off control works, test any additional supported capabilities, such as brightness, color temperature, curtain position, or thermostat setpoint.

Using Zigbee devices? These steps assume the devices you want to expose are already available in Home Assistant. If devices managed by ZBBridge-U or Bridge Max have not yet been synchronized to Home Assistant, see How to Sync Zigbee Sub-devices to Home Assistant via MQTT first.

 

6. Home Assistant Alexa Matter Bridge Troubleshooting

Alexa Cannot Find the Matter Bridge

Confirm that you have a compatible Echo or eero Matter controller. Check IPv6 and multicast traffic, avoid guest Wi-Fi or client isolation, and start a new Matter pairing session before rescanning the code.

Alexa Finds Duplicate Devices

A device may reach Alexa through a manufacturer skill, direct Matter commissioning, and the Home Assistant Matter Bridge at the same time. Decide which path should be authoritative, disable or remove the others, then run discovery again. If you intentionally keep multiple paths, rename them clearly to prevent Alexa routines and room assignments from targeting the wrong endpoint.

A Home Assistant Device or Feature Is Missing in Alexa  

A device can fail at several points between Home Assistant and Alexa. Check the path in this order:

1. Confirm the device works in Home Assistant. If the entity itself is unavailable or cannot be controlled in Home Assistant, fix that integration first.
2. Check whether the bridge can see the entity. Open the Home Assistant synchronization page in Local Web and confirm that the device/entity appears.
3. Check its synchronization status. If it shows Not Supported, the bridge cannot currently map that entity or capability to Matter. If it shows Not Synced, select it and save the configuration.
4. Check the SONOFF compatibility table. A Home Assistant entity type may contain several capabilities, and the bridge may expose only the Matter-compatible subset.
5. Check Alexa's Matter support. Even if the bridge can create the Matter endpoint, Alexa may not expose every Matter device type, cluster, or feature.
6. Refresh Alexa discovery. If the entity is successfully synchronized but does not appear, run device discovery again and check whether it was added under a different device name or room.

For example, a smart plug may expose on/off control successfully while power or energy measurements remain unavailable. The important distinction is that device support and feature support are not the same thing.

 

Home Assistant Alexa Integration FAQs

Q1: Can Home Assistant connect to Alexa without Nabu Casa?

Yes. Options include a manually configured Alexa Smart Home Skill, Emulated Hue for limited use cases, and Matter bridge solutions.

Q2: Does Alexa control Matter devices locally?

The Matter command between a compatible Alexa Matter controller and the Matter device or bridge is local. Alexa voice processing still normally relies on Amazon's cloud.

Q3: Do I need an Echo for Home Assistant Matter Bridge?

You need a compatible Alexa Matter controller, such as a supported Echo or eero device. The Alexa mobile app alone is not the Matter controller.