Expose Home Assistant Scripts and Automations via Matter Hub

Skill level: Intermediate | Time to complete: 45-60 minutes

What you'll build: A local Matter bridge that publishes your Home Assistant scripts, scenes, and automations directly to Alexa, Apple Home, or Google Home - no cloud skill, no OAuth, no port forwarding. One pairing code, every selected entity available everywhere at once.

Why This Is Different From the Alexa Skill Route

If you have followed the Expose Automations to Alexa with Voice Commands guide on this site, you already have scripts exposed to Alexa through the official Alexa Smart Home skill - which requires HTTPS, account linking, and AWS Lambda if self-hosted.

Home Assistant Matter Hub is a completely different mechanism that achieves a similar result with much less infrastructure. It runs as an add-on (or standalone Docker container) inside your network and simulates a Matter bridge - a device type that every major smart home platform (Alexa, Apple Home, Google Home) natively understands without any cloud skill or account linking at all.

The flow: Matter Hub add-on connects to HA over the local API, you pick entities to expose (scripts, scenes, lights, switches), Matter Hub creates a bridge and generates a pairing QR code, you scan that code once in Alexa, Apple Home, or Google Home, and all selected entities appear instantly. Control happens entirely over your local network - no cloud round-trip.

The standout advantage: one pairing covers every controller you want. You do not separately configure Alexa, then Google Home, then Apple Home - you create a bridge once, and each platform pairs to it independently using its own code from the same bridge.

Important naming note: The original project was created by t0bst4r, but it was archived in January 2026. The actively maintained version today is the RiDDiX fork. This guide uses the RiDDiX version throughout - older tutorials referencing t0bst4r use outdated installation URLs.

What You'll Need

• Home Assistant - any recent version, HA OS recommended

• Scripts or automations you want to expose - e.g. the bridge scripts from the Alexa voice commands guide on this site

• A Long-Lived Access Token - generated from your HA profile

• Multicast/mDNS working on your network - Matter relies on local network discovery, some WiFi access points disable multicast by default, which breaks pairing

• Alexa, Apple Home, or Google Home app - whichever controllers you want to pair

Part 1: Install Home Assistant Matter Hub

1.1 Add the repository

Settings → Add-ons → Add-on Store → three-dot menu top right → Repositories. Add:

https://github.com/RiDDiX/home-assistant-addons

1.2 Install the add-on

Search for Home Assistant Matter Hub, select the stable version (avoid alpha/test releases), and install it.

1.3 Configure and start

In the Configuration tab, set the Log Level (info is fine normally, debug for troubleshooting). On the Info tab, enable Start on boot, Watchdog, and Show in sidebar, then click Start. Click Open Web UI to access the dashboard.

Not running HA OS? A Docker image is available at ghcr.io/riddix/home-assistant-matter-hub:latest with full functionality including the web UI on port 8482. See the RiDDiX installation docs for the Docker run command with your Long-Lived Access Token and HA URL as environment variables.

Part 2: Create a Bridge and Expose Your Scripts

The Matter Hub dashboard lets you create one or more bridges - each bridge is a single Matter pairing point that can contain multiple entities.

• Name your bridge: something descriptive, e.g. Voice Commands or HA Scripts

• Set the port: the default is generally fine

• Include entities: single device, whole areas, entity domains (script.*), wildcards, or full export. Start narrow rather than exporting everything.

• Review and create: confirm selections to generate your pairing QR code

For exposing the script-based pattern from the Alexa voice commands guide, the cleanest approach is to use the Label filter. Add a label like matter_exposed to each script you want included, then filter the bridge by that label - this keeps the bridge intentional and easy to manage as you add more scripts later.

Why scripts work well with Matter Hub

Scripts are mapped to Matter's OnOffPlugInUnit device type, the same mapping used for switches. When you turn the device on from Alexa, Apple Home, or Google Home, Matter Hub calls the script's turn_on service, running it exactly as if triggered from Developer Tools. This is functionally identical to the scene-exposure approach in the official Alexa guide on this site, but works simultaneously across every Matter controller you pair, not just Alexa.

Automations are also supported directly, mapped the same way, so you do not strictly need the bridge-script pattern if using Matter Hub - you could expose the automation entity itself. That said, the bridge-script pattern is still worth using if you want the skip_condition: true behaviour, since exposing an automation directly only lets you enable or disable it, not force-trigger it bypassing conditions.

Part 3: Pair the Bridge to Your Controllers

Pair to Alexa

Click your bridge in the Matter Hub dashboard to reveal the pairing QR code. In the Alexa app: Devices → + → Add Device → Matter → scan the QR code. Alexa will likely show a warning that the device is Uncertified - this is expected for a community bridge. Acknowledge and proceed. Within a minute or two, every entity in your bridge should appear as individual devices.

Pair to a second controller

The initial QR code is single-use. To pair a second platform to the same bridge: open the app of the first controller you paired, find the Matter Hub bridge device in its settings, enable pairing mode to generate a new manual code, then use that code on your second controller. Alternatively, create a second bridge exposing the same entities on a different port - simpler to manage long term since each bridge has its own independent pairing lifecycle.

Network Troubleshooting

This is the step most people hit a wall on. Matter relies entirely on multicast/mDNS for local discovery - if your network blocks or filters multicast traffic, pairing will hang indefinitely with no useful error message. Symptom: the controller app searches and searches but never finds the device, even though Matter Hub shows the bridge as running.

• WiFi access point multicast misconfigured: check advanced settings for Multicast Enhancement or IGMP Snooping - documented issue on enterprise APs like Aruba

• VLANs separating HA from the controller: mDNS generally does not cross VLAN boundaries without a relay. Keep HA and your Echo/HomePod/Google devices on the same VLAN

• Firewall blocking UDP 5353: check firewall rules allow local multicast on this port

If pairing hangs, check the RiDDiX network troubleshooting documentation on GitHub for current diagnostic steps, since this is an actively maintained area of the project.

Configuring Bridge Behaviour

• Do not invert percentages for covers: fixes cover percentage direction mismatches

• Swap open/close commands for covers: fixes reversed voice commands

• Alexa: Preserve brightness on turn-on: works around an Alexa quirk where turning on a light resets brightness to 100%

• Server Mode (robot vacuums only): exposes a vacuum as a standalone device, required for Apple Home/Siri vacuum support. One device per Server Mode bridge.

• Auto Force Sync: periodically pushes device states every 60 seconds, enable only if devices show as unresponsive after a few hours

Most of these only need attention if you notice specific odd behaviour - defaults work fine for scripts and switches.

Backup Your Configuration

Config Backup saves bridge configurations and entity mappings, but you will need to re-pair all bridges after restoring. Full Backup includes the Matter identity files (keypairs, fabric credentials), so restoring preserves the commissioned state without re-pairing. For a setup with multiple bridges paired to multiple controllers, a Full Backup saves significant re-pairing effort during a hardware migration.

When to Use This vs the Official Alexa Skill

Matter Hub: moderate setup complexity, works across Alexa, Apple Home, and Google Home simultaneously, no HTTPS or external access required, fully local. The official Alexa skill via Haaska/AWS: higher setup complexity (Lambda, OAuth, account linking), Alexa only, requires HTTPS.

If you are only ever going to use Alexa, the skill-based approach from the other guide on this site works fine and you already have it built. Matter Hub becomes the better choice the moment you also want the same scripts controllable from an iPhone via Apple Home, or from a Google Nest speaker - one bridge, every platform, no extra Lambda functions to maintain.

Troubleshooting

• Controller can't find the bridge: almost always a multicast/mDNS network issue - see the Network Troubleshooting section above

• Script doesn't run when triggered: check the Matter Hub log for the incoming command, confirm the script is included in the bridge's entity filter

• Device shows Uncertified warning: expected for community Matter bridges, acknowledge and proceed

• Renamed entity or changed label not reflected: bridges check for changes every 30 seconds. Force an update by editing the bridge (save without changes) or restarting the add-on

• Second controller won't pair: the first QR code is single-use. Generate a new code from inside the already-paired controller's app, or create a second bridge

Guide written by a Home Assistant enthusiast in Utrecht. One pairing code, every platform - sometimes the most local solution is also the simplest one.