Matter bridge vs native devices: which is better
Matter bridge, native Matter device, or Zigbee on your own coordinator: which to pick for a local Home Assistant setup, and what a bridge can and cannot do.
On this page
Neither a Matter bridge nor a native device is universally better, whether the native device speaks Matter itself or is a Zigbee device on your own coordinator. The right choice depends on the hardware you already own, which hub you run, and how much complexity you’re willing to manage.
Short version: for new purchases, prefer native Matter (over Thread or Wi-Fi) when budget allows. Reach for a bridge only when you have existing Zigbee hardware worth keeping and want it visible in a Matter ecosystem. And if Home Assistant is your hub, native Zigbee through your own coordinator is the better default, because ZHA or Zigbee2MQTT talks to Zigbee directly and you may not need Matter bridging at all.
What each one is
Three terms get muddled constantly:
- Zigbee is a low-power mesh radio protocol. To use Zigbee devices directly you need a Zigbee coordinator (a USB stick or networked dongle) plus software like ZHA or Zigbee2MQTT.
- Matter is an application-layer standard - a common “language” for smart home devices. Matter devices run over Wi-Fi, Ethernet, or Thread. It does not run over Zigbee; Zigbee devices only reach a Matter ecosystem through a bridge.
- Thread is a separate low-power mesh radio (a competitor to Zigbee’s radio layer). Thread devices need a Thread border router to reach your network.
Two more things get swapped constantly:
- A Matter bridge is not a Thread border router. A Matter bridge exposes non-Matter accessories (typically a hub’s Zigbee devices) to Matter controllers; it translates between protocols. A Thread border router routes traffic between a Thread mesh network and your regular IP network (Wi-Fi/Ethernet); it does not translate Zigbee or any other protocol into Matter. Some hubs do both jobs, but they are distinct functions.
- No consumer hub bridges both Zigbee and Z-Wave to Matter just by having the right software. Bridging a radio requires the matching radio chip. A device can only bridge Zigbee if it has a Zigbee radio, and only bridge Z-Wave if it has a Z-Wave radio.
That second point matters because of a very common myth: that an Apple HomePod, HomePod mini, or a Home Assistant Green can “bridge Zigbee and Z-Wave to Matter.” They cannot. HomePods have no Zigbee or Z-Wave radio - they act as Matter controllers and Thread border routers, nothing more. A Home Assistant Green has no built-in radios at all; you add a USB Zigbee/Thread stick to give it one. Neither is a Zigbee-or-Z-Wave-to-Matter bridge.
What you’re choosing
A native Matter device speaks Matter out of the box over Wi-Fi, Ethernet, or Thread, with no translation layer. Examples include Eve Energy, Eve Door & Window, and the Nanoleaf Essentials A19 Thread bulb (model NF080B03), all of which use Matter over Thread.
A Matter bridge takes devices that don’t speak Matter (usually Zigbee) and presents them to Matter controllers. The Aqara Hub M3 is a good example. To be precise about the M3: it is a Zigbee hub, a Thread border router, and a Matter controller, and it can act as a Matter bridge to expose its connected Aqara Zigbee devices. It does not speak Z-Wave.
A native Zigbee setup means a Zigbee coordinator plugged into (or networked to) your Home Assistant host, talking directly to your Zigbee devices, with no Matter in the path at all.
The difference matters because a bridge adds a hop and a potential point of failure. Native Matter devices, and Zigbee devices on your own coordinator, skip the middleman.
When a bridge makes sense
A bridge earns its place in one scenario: you already have an investment in Zigbee (or other non-Matter) devices and want to surface them in a Matter ecosystem without replacing everything.
The classic example is the Philips Hue Bridge, which has a Zigbee radio internally and can expose its Hue lights to Matter. The Aqara Hub M3 fits here too. It keeps your existing Aqara Zigbee devices, such as the Aqara Motion Sensor P1 or Aqara Temperature and Humidity Sensor (both of which I run), working while bridging them to Matter.
Two cases where that is the right call:
- You already own a hub (Hue, Aqara, SmartThings) and want its devices visible to additional ecosystems - for example exposing Hue lights to Apple Home, Google Home, and Home Assistant at once.
- You want one device to appear across multiple controllers without each controller needing its own integration.
The tradeoffs: you’re adding a hub in the middle, which is one more thing that can go offline or lag. A bridge typically exposes a subset of a device’s features over Matter, so advanced or vendor-specific attributes may not come through. And it does not magically unify protocols a hub doesn’t physically support.
That said, if you run Home Assistant, you often don’t need a Matter bridge at all. Home Assistant talks to Zigbee directly through ZHA or Zigbee2MQTT with a Zigbee coordinator. Bridging Zigbee to Matter and back into Home Assistant usually adds latency and complexity for no benefit. A Matter bridge is most useful when you want those Zigbee devices visible in Apple Home, Google Home, or another Matter controller, not when Home Assistant is your hub.
If you’re starting from scratch, a bridge is an extra layer you probably don’t need.
When native Matter wins
Native Matter devices are simpler to add and easier to debug. They appear as Matter endpoints directly in Home Assistant with nothing in between.
For lighting, the Nanoleaf Essentials A19 Thread bulb, model NF080B03, is Matter over Thread and works without a vendor hub (you do need a Thread border router on your network). Check the model code before you order: Nanoleaf now sells a Matter-over-Wi-Fi A19 under the same Essentials name (NL7501K0302A010), and a Wi-Fi bulb joins no Thread mesh. Pair them with Eve Door & Window sensors for presence-based automation. If lighting is the part you are actually shopping for, the Matter over Thread light bulbs roundup lays out the picks and the Wi-Fi lookalikes to avoid.
The Philips Hue Bridge is a middle ground. It is technically a bridge, but it exposes your Hue lights to Matter while keeping the Hue app’s scene management and local control. In Home Assistant, the native Hue integration over your local network is usually the better path than going through Matter.
For sensors and plugs, Eve makes solid native Matter-over-Thread hardware. The Eve Energy smart plug and Eve’s sensor line are fully local with no Eve cloud, no account, and no tracking.
When native Zigbee on your own coordinator wins
The advantages are direct control with no extra hop, since Home Assistant talks straight to the devices and there’s no intermediary hub to fail or add latency; deep device support, because Zigbee2MQTT and ZHA support a very large range of devices and often expose more attributes than a Matter bridge would pass through; local by default, with nothing leaving your network; and cost, since one coordinator (for example a ConBee III or a Sonoff Zigbee 3.0 dongle) handles a whole house of Zigbee devices.
This is the setup most local-first Home Assistant users land on for Zigbee gear. Use a Matter bridge instead only when you already have a hub whose devices you want to share across ecosystems, or when a device is only available that way. For the Thread-versus-Zigbee radio question itself, see Zigbee vs Thread real world differences.
The Home Assistant factor
Home Assistant’s Matter integration is mature. You add Matter devices through the native Matter integration, and it handles both native devices and bridge-attached devices.
A note on radios: Home Assistant Green has no built-in Zigbee, Thread, or Matter radio. To use Thread or Zigbee with Green (or a Raspberry Pi), you plug in a USB radio such as the Home Assistant Connect ZBT-2 (the successor to the now-discontinued Connect ZBT-1, formerly SkyConnect). Home Assistant Yellow does include a built-in Zigbee/Thread radio, though it has since been discontinued (existing units still work). None of these are “firmware you run” on the device; they are physical USB or onboard radios.
For Hubitat or HomeKit users, the trade-offs shift. Apple Home treats Matter bridges and native Matter devices nearly identically. Hubitat supports Matter but is often happier with its native Z-Wave and Zigbee stacks.
Z-Wave is a third radio
If you have Z-Wave devices, none of the paths above covers them - you need a Z-Wave controller (such as a Zooz or Aeotec stick) running Z-Wave JS. If you want one box to handle Zigbee, Z-Wave, and Matter/Thread, you need a hub that physically contains all of those radios, not a HomePod or a bare Home Assistant Green. The Aeotec Smart Home Hub is the example people reach for, and it does carry Zigbee, Z-Wave and Thread radios, but it is a rebadged SmartThings hub rather than a Home Assistant adapter: it is driven by the SmartThings app, and Home Assistant reaches it through the cloud-based SmartThings integration. Skip it if local control is the whole point.
Tradeoffs to accept
No setup is perfect. Bridges can lose sync during firmware updates or network resets. Native Matter devices sometimes lack the advanced features their vendor-specific firmware offers. Matter’s groups and scenes support is still catching up to mature local ecosystems like Hue or Lutron.
Budget matters too. A native Matter device often costs more than a comparable plain Zigbee one. If you already own a bridge-capable hub, the effective cost of bridging existing devices can be lower than buying all-new Matter hardware.
If you are shopping rather than architecting, the Matter devices worth buying lists what is worth the money.