Matter bridges: use your Zigbee devices with Matter

The principle in one paragraph

Google’s Matter documentation defines a bridge as a device that is a member of both a Matter network and another, bridged, IoT technology. It names Zigbee, Bluetooth Mesh and Z-Wave as examples. Your Zigbee sensors still talk Zigbee to the bridge. The bridge translates their state and commands into Matter, so a Matter controller sees them as ordinary Matter devices. Google adds that all devices behind a bridge appear normally to the user in Google Home, while the bridge itself shows as a control bridge entry in the app. Apple’s Home app also lists bridges among its supported categories.

Do you need a bridge?

What a bridge exposes

A bridge is limited by two lists: the device types it can translate and the device types your controller can display. Google supports 31 device types in Google Home and says other types are not officially supported. Apple’s Home app lists lights, outlets, switches, locks, thermostats, blinds, and several sensors. A typical Zigbee bulb, plug, contact sensor, motion sensor or temperature sensor falls within those lists. A Zigbee smoke alarm, a siren or an unusual multi-function device might not.

• Lights and plugs: on and off, brightness and, usually, color temperature. Special effects stay in the Zigbee hub’s app.
• Sensors: state changes such as open or closed, motion, temperature and humidity.
• Locks and thermostats: only if the bridge and controller both support those types, so check before you buy.
• Buttons and remotes: exposure varies by bridge; test one before moving many.

What you give up

• Single point of failure. If the bridge hub loses power or its firmware has a bug, every bridged device disappears from the controller.
• An extra hop. Commands go from controller to bridge to device, which can add delay compared with a direct Zigbee automation inside the hub.
• Limited detail. Fine settings, firmware updates and advanced behaviors remain in the hub’s own app.
• Two places to manage. Rooms, names and automations live in the controller, while pairing and the mesh live in the hub. See Matter multi-admin for how apps share a device.
• Battery drain. More polling or reporting can shorten battery life on some sensors; watch the first weeks.

How to set one up

1. Check support. Confirm the hub says it works as a Matter bridge, and that your Zigbee device types are on its list.
2. Update everything. Update the hub’s firmware and your ecosystem app.
3. Leave the Zigbee devices where they are. Do not remove them from the hub. The bridge works on top of the existing pairing.
4. Turn on the bridge feature in the hub’s app and pair it with your controller using the QR or numeric code it shows.
5. Select which devices to share. Start with five or ten, not everything, and check that each appears under the right type.
6. Rebuild any automations in the controller, or keep them in the hub and let the controller only display state.

If the bridge or the hub is the problem, the pairing fixes guide covers the common causes.

Home Assistant and other hubs

If you run Home Assistant, ZHA or Zigbee2MQTT already talk to your Zigbee devices through a USB coordinator; see setting up a Zigbee coordinator. Home Assistant’s Matter documentation also lists bridge as one of the Matter device roles it understands. Whether a specific hub or Home Assistant setup can publish its Zigbee devices to other ecosystems depends on that product’s current features, so read its documentation before you buy hardware.

Migrating instead of bridging

Zigbee devices cannot be moved to a new coordinator without re-pairing them. If you plan to replace the whole system, a bridge is a good bridge for a season, not a permanent plan. For the comparison of the two technologies, see Matter vs Zigbee.