Hub, bridge, controller, border router: the four words explained
Most smart home confusion is one of these four words standing in for another.
The four words, side by side#
| Word | What it is | Its one job | What it cannot do |
|---|---|---|---|
| Hub | A product category | Bundle the roles below into one box | Nothing specific. The word implies no capability |
| Matter controller | A software role on a phone, hub or server | Hold fabric credentials, commission devices, send commands | Give a device a radio it lacks |
| Bridge | A device speaking two protocols | Represent non-Matter devices to Matter controllers | Preserve features with no Matter equivalent |
| Thread border router | A network function | Route IPv6 between mesh and LAN, advertise services | Own devices, run automations or join a fabric |
Products combine these arbitrarily. A HomePod mini is a hub, a controller and a border router. A Philips Hue Bridge is a hub and a bridge and neither of the other two. A $199 Apple TV is a hub and a controller and not a border router. Nearly every purchasing mistake here comes from assuming one role implies another.
Controller, precisely#
A Matter fabric is a set of nodes sharing a root of trust and a fabric ID, explained in how Matter actually works. A controller is a node holding administrative credentials for that fabric: it commissions devices, issues operational certificates and sends commands. Your iPhone is a controller. So is the Home app on an Apple TV, and the Matter Server inside Home Assistant.
Two consequences:
- A controller is not a radio. Adding a second controller does not give you Zigbee, Z-Wave or Thread. It gives you another administrator for devices you can already reach.
- Controllers do not share fabrics automatically. To add a device already in Apple Home to Home Assistant, you generate a new pairing code in Apple Home and commission it a second time. The device joins a second fabric and keeps both. That is multi-admin, and it is still the only mechanism in practice: Joint Fabric arrived in Matter 1.6 in June 2026, and no major consumer ecosystem had shipped it as of September 2026.
The forgotten role is the commissioner, usually your phone. It reads the pairing code, talks to the device over Bluetooth LE or Wi-Fi, and hands over the credentials it needs to join, which is why pairing can fail while everything else works. Matter pairing explained covers the stages.
Bridge, precisely#
A Matter bridge is a Matter node representing devices that are not Matter devices. It exposes an aggregator endpoint, and each bridged device sits beneath it as its own endpoint with a device type and a set of clusters. To your controller it looks like one product presenting twelve lights.
The translation is lossy in one specific direction: anything the vendor invented that has no Matter equivalent has nowhere to go.
| What you lose | Why |
|---|---|
| Lighting effects | Govee and Nanoleaf effects have no Matter cluster, so bridged bulbs reduce to on, off, dim and a solid color |
| Vendor scenes and groups | Scene definitions live in the vendor app, not in the bridged model |
| Firmware updates | The device updates through its own ecosystem, not your controller |
| Fine-grained state | Battery detail, signal quality and diagnostics are commonly dropped |
| Advanced features | Robot vacuum maps and no-go zones do not cross, so you get start and stop |
That is not a complaint about any one bridge. It is what translation is. Matter bridges and what you lose through one names the losses per category, and smart lighting that stays compatible covers the effect problem.
A bridge is also a single point of failure with an unusual shape. Bridged devices are not Matter nodes, so if the bridge goes, they do not show up as offline. They stop existing. Removing a Hue Bridge does not orphan twelve Matter lights, it deletes one Matter node that represented twelve lights.
Border router, precisely#
A Thread border router is a mains-powered device with an 802.15.4 radio on one side and your LAN on the other. It does four things:
- Bidirectional IPv6 routing between the mesh and your Ethernet or Wi-Fi network, including advertising an on-mesh prefix so the two sides can address each other.
- Service registration. Thread devices register services with an SRP server on the border router, which then runs an advertising proxy publishing mDNS records on the LAN for devices that are asleep.
- Address translation in Thread 1.4, through NAT64 and DNS64 plus DHCPv6 prefix delegation.
- Commissioning relay, so a joining device can reach a commissioner that is not on the mesh.
What it does not do is the important half. It holds no fabric credentials, cannot add a device to your account, runs no automations, has no app and translates no protocols. It is plumbing between two IP networks, and it feels like more only because it usually arrives inside a speaker that is also a controller.
Which product is which#
| Product | Hub | Controller | Bridge | Border router |
|---|---|---|---|---|
| Your iPhone or Android phone | No | Yes | No | No |
| HomePod mini | Yes | Yes | No | Yes |
| Apple TV 4K 3rd gen, 64 GB | Yes | Yes | No | No |
| Apple TV 4K 3rd gen, 128 GB | Yes | Yes | No | Yes |
| Nest Hub 2nd gen | Yes | Yes | No | Yes |
| Nest Mini, Nest Audio | Yes | Yes | No | No |
| Echo Dot, Echo Pop | Yes | Yes | No | No |
| Echo Hub, Echo Dot Max | Yes | Yes | Yes, for Zigbee | Yes |
| eero 6 and 7 routers | No | No | No | Yes |
| SmartThings Station | Yes | Yes | Yes, for Zigbee | Yes |
| Philips Hue Bridge | Yes | No | Yes | No |
| Home Assistant Green, no dongle | Yes | Yes | Yes, for cloud integrations | No |
| Home Assistant Green plus ZBT-2 | Yes | Yes | Yes | Yes, if the dongle runs Thread |
| Hubitat C-8 Pro | Yes | Yes | Yes, for Zigbee and Z-Wave | No |
| Homey Pro 2026 | Yes | Yes | Yes, for six protocols | Yes, its own network only |
| Aqara Hub M3 | Yes | Yes | Yes, for Zigbee | Yes |
| IKEA DIRIGERA | Yes | Yes | Yes, for Zigbee | Yes |
Read the bridge column carefully. A hub that owns Zigbee devices is a bridge only if it exposes them to other ecosystems as Matter. Hubitat and Home Assistant can, but it is a feature you turn on, not a consequence of having the radio.
Five symptoms, and the confusion behind each#
"I added a border router and my app still shows no devices." Border router confused with controller. The mesh now has a path to your LAN, but nothing has been commissioned into a fabric. That is a separate step, done in a controller app.
"The device is unresponsive in the app but the automation still fires." Discovery, not radio. The device is healthy and the mDNS records published on its behalf are not reaching your controller: client isolation on an IoT SSID, IGMP snooping, or a VLAN with no reflector. Start with a device shows as unresponsive, not with re-pairing.
"My bulbs lost their effects when I moved them to Matter." Bridge confused with a pass-through. A bridge sends what Matter can describe. Keep the vendor app for effects and use Matter for on, off, brightness and triggers.
"I bought a second hub and none of my Thread devices moved to it." Two things did not happen: the hub did not join your Thread network, and it did not receive your fabric credentials. Credential sharing is user triggered and single use, and joining a fabric needs a pairing code from the controller that already owns the device.
"I reset my hub and my Zigbee devices never came back." Hub confused with controller. In Zigbee the hub is the coordinator and Trust Center, so the network is bound to that specific device. Resetting it destroys the network and every device has to be re-paired.
Four rules that follow from the definitions#
- A border router never reduces the number of hubs you need. It solves coverage and reachability. It does not solve ownership.
- A bridge always downgrades a device into Matter. Buy the bridge for compatibility, keep the native app for capability.
- Adding a controller adds an administrator, not a radio. If the radio is missing, no software fixes it.
- "Hub" on a box is marketing. Check the four roles individually, which is what hubs compared by the radios they carry does product by product.
Is a Thread border router a hub?
No, though it usually lives inside one. A border router routes IPv6 between the Thread mesh and your LAN and publishes device services over mDNS and SRP. It holds no fabric credentials, so it cannot add a device to your account or run an automation. A HomePod mini is both at once, which is why the roles get merged.
Is a Matter controller the same as a Matter bridge?
No. A controller administers a fabric and commissions devices into it. A bridge is a device inside a fabric that represents non-Matter devices, such as Zigbee bulbs, as Matter endpoints. Many hubs are both, but the roles fail differently: losing a controller costs you administration, while losing a bridge makes every device behind it disappear.
Do I need a border router for each ecosystem?
You need at least one border router on each Thread network in use, and by default each ecosystem forms its own. If you share Thread credentials between ecosystems, one physical network can carry devices commissioned into different fabrics, and every border router on that network helps. See why you have three Thread networks.
Can one device be a bridge and a border router at once?
Yes. The SmartThings Station, Aqara Hub M3, IKEA DIRIGERA and Homey Pro all bridge Zigbee into Matter while acting as Thread border routers. The functions are unrelated: one translates an application protocol, the other routes IPv6 packets for a mesh.
Does adding a second border router split my Thread network?
Not by itself. Several border routers on one Thread network is the recommended setup and improves resilience. A split happens when the new border router belongs to a different ecosystem and forms its own network with its own credentials, which is the default behavior, and the reason the Thread border router directory flags which hardware you already have.
Is my phone a hub?
It is a controller, not a hub. A phone commissions Matter devices and controls them on the local network, but it leaves the house, so it cannot host automations or answer remote requests. That is the real argument for buying a hub: see do you need a smart home hub?
Primary sources
Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.