Matter Server
Overview
Section titled “Overview”The Matter Server provides a standardized bridge for Matter-compatible devices (lights, plugs, sensors) to interact with Home Assistant. It supports both Matter-over-IP (Wi-Fi/Ethernet) and Matter-over-Thread.
| Service | Port | Protocol | Description |
|---|---|---|---|
| API | 5580 | TCP | Matter WebSocket API |
Architecture
Section titled “Architecture”The service runs as a Podman container using the ghcr.io/home-assistant-libs/python-matter-server image. It uses --network=host to ensure seamless discovery of Matter devices on the local network.
Multi-Admin Strategy (Alexa/Eero Bridge)
Section titled “Multi-Admin Strategy (Alexa/Eero Bridge)”In this homelab, we use a Multi-Admin approach for Thread devices:
- Primary Fabric: Devices are initially paired to the Alexa/Eero network using their mobile apps.
- Secondary Fabric (Home Assistant): We “share” the device from the Alexa app using a Commissioning Code (11 digits).
- Matter Server: Acts as the secondary controller, communicating with the devices via the Eero Border Router.
[!IMPORTANT] For commissioning to work, the Homelab server MUST be on the same network segment (Eero LAN) as the Alexa devices.
Troubleshooting
Section titled “Troubleshooting”Commissioning Timeout
Section titled “Commissioning Timeout”If you get a “Discovery timed out” error when adding a device:
- Ensure the server is connected to the Eero LAN port.
- Verify that
nixos.localis reachable. - Check if the device is advertising its commissioning service:
If this returns nothing, regenerate the code in the Alexa app.
Terminal window avahi-browse -rt _matterc._udp
Restarting the service
Section titled “Restarting the service”sudo systemctl restart podman-matter-serverChecking Logs
Section titled “Checking Logs”sudo journalctl -u podman-matter-server -f