How Matter bridges work: Hue, Aqara and IKEA devices in Apple Home
Updated · Reviewed against the current HomeHubAtlas dataset
Short answer: a Matter bridge is a hub that re-presents its own Zigbee devices as Matter devices. Pair your Hue bulbs to the Hue Bridge as usual, enable Matter on the bridge, and every bulb appears in Apple Home, Google Home, Alexa, or SmartThings — locally controlled, no per-device re-pairing. Basics carry over; the maker's fancy features stay in the maker's app.
The mechanism: one node, many endpoints
In the Matter specification a bridge is an Aggregator device type. To your ecosystem it is a single Matter node — commissioned once, with one pairing code — that exposes each of its paired devices as a separate endpoint carrying a standard Matter device type: dimmable light, occupancy sensor, contact sensor, and so on. The bridged devices themselves never learn Matter; they keep speaking Zigbee to the bridge over its own radio, and the bridge translates in both directions.
Two properties follow directly. First, the bridged devices ride the bridge's dedicated Zigbee network, with its own mesh of routers — often more radio-robust than a young Thread mesh. Second, the bridge is a live directory: add a bulb in the Hue app and it shows up in Apple Home moments later, remove it and it disappears, with no ecosystem-side ceremony.
The bridges that matter in practice
| Bridge | What it bridges into Matter | Notes |
|---|---|---|
| Philips Hue Bridge | Hue and Friends-of-Hue Zigbee lights, plugs, sensors, dimmers | The canonical example; Matter arrived by firmware update to the existing v2 bridge |
| Aqara Hub M2 / M3 | Aqara Zigbee sensors, switches, and controllers | The M3 is also a Matter controller and Thread border router in its own right |
| IKEA DIRIGERA | IKEA's Zigbee lights, blinds, remotes, air-quality sensors | Bridging is the intended way to reach Apple/Google/Alexa homes |
| Bosch Smart Home Controller II | Bosch's Zigbee-based sensors, thermostats, and alarm devices | Notable for bridging security-adjacent device types |
| SmartThings hubs | Selected Zigbee/Z-Wave devices paired to the hub | SmartThings acts as both controller and bridge ("Hub Everywhere") |
What carries over — and what stays in the app
A bridge can only expose what Matter has words for. On/off, brightness, color and color temperature, sensor readings, battery levels: these map cleanly, and day-to-day control in the ecosystem app is indistinguishable from a native device. What does not cross the bridge is everything the manufacturer built above the standard: Hue's entertainment sync and gradient scene engine, Aqara's on-hub automations, IKEA's scene presets. Those remain exclusive to the maker's app, which keeps working alongside Matter — the bridge adds an interface rather than replacing one.
Expect device-type gaps, too. If a bridge's firmware predates a Matter device type (say, air quality sensors), those devices simply do not appear on the Matter side until a firmware update adds the mapping — and then your controller must also support the type. When a bridged device seems missing, the answer is almost always a version gap on one side or the other.
Bridged vs native: which to choose
Many Zigbee devices could instead be paired directly to a Zigbee coordinator — a Hubitat C-8, a coordinator dongle running Zigbee2MQTT or ZHA — with no bridge in the middle. The trade, covered in depth in the bridged-vs-native glossary entry, comes down to this:
- Bridge when you own many devices of one brand and the maker's app earns its keep — firmware updates, polished scenes, a tuned mesh. Hue with more than a handful of bulbs is the textbook case.
- Pair natively when you want fewer boxes, one consolidated Zigbee mesh, or features that only DIY platforms expose. You give up the maker's app entirely for those devices.
- Remember the ceiling: a bridged device is only as capable as the bridge's Matter implementation, and a natively paired one only as capable as your platform's device support. There is no option that costs nothing.
Setting one up
The flow is the same everywhere: update the bridge's firmware, enable Matter in its app to get a pairing code, then add the bridge in Apple Home, Google Home, Alexa, or SmartThings like any Matter device. Thanks to multi-admin, the same bridge can join several ecosystems at once. To see what a given hub can reach — bridged and native — start from the hub directory and the per-hub works-with pages, which are computed from the same dataset as the rest of this site, from smart lights to contact sensors.