Home Assistant announced official Matter certification on 10 March 2025. That was an exciting milestone for an open-source smart-home platform, whether you run Home Assistant on a Raspberry Pi or in a VM. Understanding what was certified, and what your home network still needs, makes the announcement more useful than treating the badge as a guarantee that every smart device will work effortlessly.
What was actually certified?
The official announcement distinguishes two components: the Open Home Foundation Matter Server as a certified software component, and Home Assistant as a certified User Interface Component using it. The certification covered the Matter 1.3 device types described in that announcement. Home Assistant already supported Matter before receiving the badge; certification did not require users to re-pair all their existing devices.
The distinction also allows other projects to use the server component through their own appropriate certification process. It does not mean that every vendor-specific feature, every future Matter device type or every network configuration has been tested. Check current integration support and the specific product's capabilities when buying or troubleshooting a device.
Home Assistant's role in the system
Home Assistant connects integrations, devices and entities so you can build automations across a household. Matter is one integration route within that platform. A non-Matter device connected through another integration does not automatically become a Matter accessory that Apple Home or another controller can import. Certification concerns the stated Matter components, rather than converting every existing integration into a Matter bridge.
For communicating with Matter devices, the integration connects to a separate Matter Server process over a WebSocket connection. The server operates the controller and manages its Matter fabric. Home Assistant OS with the supported Matter Server app, formerly called an add-on, is the documented supported path. A separately managed Container deployment has its own host/network requirements and is not covered by the same supported installation path.
What is Matter?
Matter defines an interoperable application-level way to control supported smart-home devices. It runs over IP networks such as Wi-Fi, Ethernet or Thread; it is not a new Wi-Fi band or a replacement radio built into every product. It uses IPv6 communication locally, even when your internet service supplies only IPv4.
Supported Matter functions can be controlled locally without sending every command through a vendor cloud. Some products still require vendor account setup, bridges or vendor software for firmware updates and additional functions. “Local Matter control” is therefore a useful capability to verify, not a promise that the entire product never communicates with its manufacturer.
Three roles that are easy to confuse
| Role | Purpose | What it does not imply |
|---|---|---|
| Matter controller | Commissions and controls devices in its fabric | Every controller supports every possible device feature |
| Thread border router | Routes between the Thread mesh and the local IP network | It is automatically your Home Assistant controller |
| Matter bridge | Exposes supported functions from other devices through Matter | All features of every attached device are exported |
A Thread logo alone is not proof of Matter support. Some Thread devices use HomeKit instead. Similarly, a manufacturer's Matter bridge may expose only a subset of its attached devices or controls. Confirm the logo, model and documented feature set, then compare the entities actually created in Home Assistant.
Wi-Fi/Ethernet versus Thread
A Wi-Fi Matter device uses an existing suitable Wi-Fi network. A Thread Matter device needs a nearby Thread border router and the correct Thread-network credentials. Thread is a low-power IEEE 802.15.4 mesh operating at 2.4 GHz, rather than ordinary Wi-Fi. Ethernet has no radio frequency, so grouping it into a “2.4/5 GHz” table would be misleading.
Home Assistant's Thread documentation lists supported border-router options. Examples include appropriate Apple/Google devices and Home Assistant with a compatible radio and OpenThread Border Router app. Check the exact Apple TV model rather than assuming every Apple TV 4K contains Thread hardware.
Detecting a border router does not automatically import its credentials or make that network preferred. Follow the documented phone/platform-specific credential sharing and preferred-network procedure. Home Assistant Connect radios also need the correct Thread setup; do not assume a radio running Zigbee is already a Thread border router. If using a VM, the selected radio must be available to that guest.
Prepare the network and add one device
Read the Matter integration guide before commissioning. The host, phone and device need working local IPv6 reachability and discovery. An IPv6 internet plan or DHCPv6 server is not required, but disabling IPv6 or blocking multicast can break local operation. A guest SSID, isolated VLAN or limited NAS-container kernel can create different problems even when ordinary internet browsing works.
Start with one supported device on a suitable reachable network. Use the Home Assistant Companion app and the manufacturer's setup code, keeping the phone near the device for Bluetooth commissioning. The phone performs that initial exchange; the device normally uses its Wi-Fi or Thread transport afterward. Merely having Bluetooth on the server is not the same setup path.
When a device already belongs to another Matter ecosystem, use that ecosystem's documented sharing/commissioning flow to obtain a new code, then add it to Home Assistant. This is different from using the original box code indiscriminately or factory-resetting the device. Multi-admin permits more than one fabric, but membership and credentials remain separate for each controller.
Check supported functions, rather than brand names alone
Apple Home, Google Home and supported Amazon Alexa controllers participate in Matter, but exact hardware, software and supported device types matter. A generic app name is not a complete compatibility specification. For a lock, thermostat or sensor, list the controls and state information you actually need, including any vendor-only functions.
After adding a device, send a harmless command and check the physical response and reported state. Test the same function from a second controller if you use multi-admin, then try a normal Home Assistant restart. A successful setup-code scan alone does not verify sustained communication, correct state reporting or every automation.
Interoperability still needs maintenance
Matter reduces dependence on proprietary control paths, but it does not remove network maintenance or firmware requirements. Keep records of the model, firmware, controller membership and required border router. Check the supported backup/recovery process before replacing the Matter Server or radio, rather than deleting its data when troubleshooting discovery.
Firmware updates can have separate limitations. Home Assistant currently documents Matter-over-Thread update problems when Apple border routers do not forward the necessary update-provider discovery; another ecosystem may offer its own update route. Local control working today does not prove that every OTA update will use the same path.
A milestone with a practical next step
Certification is a meaningful recognition of Home Assistant's Matter implementation and the wider open-source effort. Its value is clearest when paired with supported products, suitable local networking and a verified device workflow. Start with one device and its required functions, then expand the system after checking sharing, restarts and recovery. That gives the original enthusiasm for an interoperable smart home a concrete foundation.
