Matter for Installers: Controllers, Border Routers, Bridges and What to Promise a Client
What each Matter role does on a real job, what you need on site before commissioning, how a device ends up in more than one app, and a plain list of what you can and cannot promise a client.
By Abhi Bavishi, Founder, Smartify
Technical review pending
At a glance
You will learn
- Know what a controller, a border router and a bridge each do
- Check what a site needs before commissioning
- Know what you can and cannot promise a client
You need
- The apps the household uses
- A phone with Bluetooth for commissioning
Key takeaway
Promise local control of the core functions of certified devices, not that every feature will appear in every app.
Key terms in this lesson (4)
- Bridge
- Makes devices from another system, such as a Zigbee hub, visible to Matter controllers. It exposes only the functions it chooses to map.
- Fabric
- One controller's Matter network. A device can belong to several fabrics at once, which is how it can be used in more than one app.
- Matter controller
- The role that commissions Matter devices and sends them commands. A hub, speaker, TV box or server can provide it.
- Setup code
- The QR code or numeric code printed on a Matter device. You need it to commission the device again after a reset, so photograph it at installation.
Short answer: plan a Matter controller for each ecosystem, a Thread border router for Thread devices and a home network that passes local IPv6 traffic. A bridge exposes only supported functions. Promise tested local core control, not every feature in every app.
Start with the visual guide and Matter reference. Matter supplies a common device language over IP; it does not supply its own radio or repair a poorly configured network.
The roles in plain words
| Role | Job | Important distinction |
|---|---|---|
| Matter device | Speaks Matter over Wi-Fi, Ethernet or Thread | Features still depend on model and app |
| Controller | Commissions and controls devices | A role supplied by a hub, speaker, TV box or server |
| Fabric | A Matter network associated with controllers | Logical membership, not a physical radio network |
| Thread border router | Passes IP traffic between Thread and home network | Not a Matter controller; cannot read encrypted Matter traffic |
| Bridge | Exposes supported devices from another system | Not a guarantee of every device or feature |
One physical box may provide several roles. A Thread logo alone does not mean Matter support: check the Matter logo and exact device documentation too.
What you need on site
- Household apps and controllers. Check each ecosystem’s current requirements. The Apple and Google support pages cited below describe home-hub requirements; qualifying models differ. Do not order based on the word “hub” alone.
- Thread border router where needed. Wi-Fi-only Matter devices do not need one. For Thread devices, verify both the supported model and coverage at their installation positions.
- Local IPv6 and multicast. Home Assistant documents that IPv6 multicast must pass freely to its controller; an IPv6 internet connection is not required. VLANs, filtering and router settings can block discovery. Include this in the site survey.
- Commissioning connectivity. Check the Wi-Fi band’s requirements. Home Assistant’s instructions advise the same 2.4 GHz network for commissioning its usual Wi-Fi devices. Keep a Bluetooth-capable phone near the device: Bluetooth commonly hands over credentials, then control uses Wi-Fi or Thread.
- Setup codes. Photograph the QR or numeric code for the inventory. You need it again after a factory reset.
Commissioning, in order
Choose the household’s primary app before starting and agree who owns the setup. A new device should be in setup mode; a used one may need a documented reset, so locate its code first.
- Scan the setup code in the controller app and follow its prompts.
- Let the device join its Wi-Fi or Thread network.
- Name the room and device consistently with the handover inventory.
- Share from the first app to additional apps using their commissioning flow. This creates another fabric; the same device can belong to multiple fabrics.
- Test every promised control in every app, including with internet disconnected. See local-control testing.
Do not factory-reset a working shared device merely to add another app without checking the supported sharing procedure. Preserve the household’s existing setup and record which controllers own each fabric.
Bridges: useful, with limits
A Matter bridge can expose an existing Zigbee or proprietary system. Its mapping may include only selected device types and basic functions. A native integration can offer scenes or effects that the Matter path omits.
Before quoting a bridge, verify the client’s actual device list, the functions exposed for each device and whether the bridge’s control path depends on cloud services. Demonstrate the promised function in the destination app; success in the maker’s own app does not establish that mapping.
What you can and cannot promise
Matter is designed for local core control, with commands travelling over the home network. The client still needs suitable controllers, network equipment and supported apps.
Promise the tested devices, apps and functions. Do not promise universal compatibility, future-update features or freedom from re-commissioning. A specification feature may not yet exist in a particular device’s firmware or app.
Test and document
Test each app and another phone, then repeat with internet disconnected. Restart the controller and each border router and check recovery. Where multiple border routers coexist, test them individually and verify the update path as well as everyday commands.
Use the platform map where available to inspect Wi-Fi, Thread or Ethernet paths. Record controllers, border routers, bridges, models, firmware, setup codes and account ownership in the handover pack.
Common mistakes
Do not sell a logo without checking the household apps, confuse Thread with Matter, forget border-router coverage, block local IPv6 discovery, or reset without a setup code. Never promise functions the bridge does not expose.
Where to go next
Check yourself.
Questions from real jobs. Think first, open the answer, then say how you did. The score is for you and stays on this device.
You reset a Matter device. What do you need to add it again?
Its QR code or numeric setup code, so photograph it at installation and store it with the inventory.
Does a Thread border router replace a Matter controller?
No. A border router passes traffic between the Thread mesh and the home network. The controller commissions and controls devices.