Matter bridge
A Matter bridge is a hub that represents its non-Matter devices — typically Zigbee — as Matter devices, so ecosystems like Apple Home can control them. The Philips Hue Bridge, Aqara hubs, IKEA DIRIGERA, and Bosch Smart Home Controller II all do this: pair a bulb to the bridge, and it appears in your Matter ecosystem as if it were a native Matter light.
In the Matter spec a bridge is an Aggregator device type: one Matter node that exposes each bridged device as a separate endpoint with its own device type. The bridged devices keep speaking Zigbee (or another protocol) to the bridge; only the bridge speaks Matter. Add or remove a device on the bridge and the change propagates to every connected ecosystem automatically.
Bridging maps the basics — on/off, brightness, color, sensor readings — but features with no Matter equivalent stay in the maker’s app: Hue’s entertainment sync and scene engine, for example, do not cross the bridge. That trade-off, and when bridging beats pairing a device natively, is covered in our guide on how Matter bridges work.
| Matter device type | Aggregator, with every bridged device on its own endpoint as a Bridged Node |
|---|---|
| Pairing codes needed | One, for the bridge — the bridged devices are never commissioned individually |
| Hubs in this dataset that bridge | Philips Hue Bridge, Aqara Hub M2 and M3, IKEA DIRIGERA, Bosch Smart Home Controller II, Home Assistant Green and Yellow |
| What is bridged | Almost always Zigbee; Home Assistant and SmartThings can also re-export Z-Wave |
| Hue Bridge capacity | 50 lights plus 12 accessories, the ceiling most Hue households hit first |
| Fabric slots consumed | By the bridge, not the devices — every ecosystem you share it with uses one |
One node, many endpoints
To a Matter controller a bridge is a single node with a lot of endpoints. Endpoint 1 is the Aggregator; every bridged device gets a dynamically allocated endpoint carrying a standard device type — Dimmable Light, Occupancy Sensor, Window Covering — plus a Bridged Device Basic Information cluster holding the original vendor name, model, and reachability flag. That last cluster is why a Hue bulb still shows up as a Hue bulb rather than as “Bridge endpoint 7”.
The endpoints are dynamic, which is the feature that makes bridging pleasant. Pair a new bulb in the Hue app and it appears in Apple Home within moments, with no code to scan; remove it and the endpoint goes away. Compare that with native pairing, where every device is its own commissioning ceremony in every ecosystem you want it in.
The bridged devices never learn Matter. They keep speaking Zigbee to the bridge over its dedicated radio, and the bridge translates in both directions. That translation is real work — unlike a Thread border router, which only routes — and it is where the feature losses come from.
What crosses and what stays behind
A bridge can expose only what Matter has vocabulary for. On/off, brightness, colour and colour temperature, contact and occupancy state, temperature and humidity readings, battery level, cover position: these map cleanly and behave like a native device. Everything the manufacturer built above the standard stays in the manufacturer’s app — Hue’s entertainment sync and gradient scene engine, Aqara’s on-hub automations, IKEA’s scene presets, per-device firmware settings.
Device-type gaps are the other half. If the bridge’s firmware predates a Matter device type, devices of that type simply do not appear on the Matter side, and even when the bridge maps them your controller has to understand the type as well. When a bridged device is missing from one ecosystem but present in another, a version gap on one of those two sides is nearly always the explanation.
Latency and state are worth a thought too. Every command now takes two hops — controller to bridge, bridge to Zigbee device — and state changes made outside Matter (a physical Hue dimmer press, an automation running on the bridge) reach your ecosystem only as fast as the bridge reports them. In practice this is fractions of a second on good bridges and visibly worse on cheap ones.
The single point of failure you are buying
A bridge concentrates risk. If it loses power, fails, or has its firmware rolled forward badly, every device behind it goes dark in every ecosystem at once — where a natively paired mesh would lose only the devices in that radio’s shadow. Weigh that against the fact that most bridges also run a well-tuned dedicated Zigbee mesh that is often more reliable than a shared one.
Fabric slots belong to the bridge, not the devices. Share a Hue Bridge into Apple Home, Google Home, and Alexa and you have used three of the bridge’s fabric slots while the 40 bulbs behind it use none. This is a genuine advantage in large installations, and it is the reason bridging scales better than native pairing when you own many devices of one brand.
Watch the counts at both ends. The Hue Bridge tops out at 50 lights and 12 accessories; ecosystems impose their own accessory ceilings per home; and a bridge that re-enumerates its endpoints after a firmware update can make devices reappear as new accessories, breaking every automation that referenced them. Back up your bridge configuration before updating it.
Frequently asked questions
Do I still need the Hue Bridge if I have Matter?
Yes, unless you pair the bulbs directly to a Zigbee coordinator instead. Hue bulbs are Zigbee devices, not Matter devices — the Bridge is what speaks Matter on their behalf. Removing the Bridge means giving up the Hue app, entertainment sync, and Hue’s firmware updates, and pairing every bulb to something like Hubitat, Zigbee2MQTT, or ZHA.
Can a Matter bridge expose Z-Wave devices?
Some can. The dedicated consumer bridges — Hue, Aqara, IKEA, Bosch — are Zigbee-only, but Home Assistant and SmartThings can re-export Z-Wave devices they own into Matter. That is currently the only realistic way a Z-Wave lock ends up in Apple Home, since Z-Wave has no native Matter path.
Is a Matter bridge the same as a Matter controller?
No, and many products are both. A bridge is a Matter device that represents other devices; a controller is what commissions and commands Matter devices. The Hue Bridge is purely a bridge — it has no ability to control your other Matter gear. The Aqara Hub M3 and Home Assistant are both bridge and controller.
Do bridged devices work without the internet?
Yes, provided the controller executes locally. Matter traffic between your controller and the bridge stays on the LAN, and the bridge-to-device link is Zigbee. Apple Home, Home Assistant, Hubitat, and Homey Pro will keep bridged devices running through an internet outage; Alexa and Google Home routines mostly will not, because the automation engine is in their cloud.
How many devices can one Matter bridge expose?
The specification does not set a hard number — the real limits are the bridge’s own radio capacity and your ecosystem’s accessory ceiling. The Hue Bridge allows 50 lights and 12 accessories; Aqara, IKEA, and Bosch hubs sit in a similar range. Large installations usually run several bridges rather than one enormous one.