Zigbee, Thread and Matter: What Is the Difference?

Zigbee, Thread and Matter often appear together, but they are not three technologies at the same layer. Understanding the distinction helps prevent buying the wrong hub, planning the wrong infrastructure or expecting compatibility that the system cannot provide.

Quick comparison: Zigbee, Thread and Matter

Zigbee in the Aqara ecosystem

Many Aqara sensors, switches and other devices use Zigbee. They connect to a compatible Aqara Hub. If the hub supports Matter Bridge, selected Zigbee devices can be exposed to a Matter ecosystem without changing the radio protocol used by the original device.

Thread is an IP-based mesh network

Thread uses IPv6 and is designed for low-power devices. Matter-over-Thread devices require suitable Thread infrastructure, and a Thread Border Router connects the Thread mesh to the home's wider IP network.

Matter is an interoperability layer, not a radio type

Matter can run over Thread, Wi-Fi or Ethernet depending on the device. A Matter logo therefore does not tell you whether a device uses Thread or Wi-Fi; the exact model still needs to be checked.

Matter Controller, Thread Border Router and Matter Bridge are different roles

• Matter Controller: commissions and controls Matter devices within an ecosystem.
• Thread Border Router: connects the Thread mesh to an IP network; required for Matter-over-Thread devices.
• Matter Bridge: represents selected devices from another protocol, such as compatible Aqara Zigbee devices, to a Matter ecosystem.
• One hardware device can perform several roles, but the roles are not synonymous.

How should dual-protocol Aqara devices be understood?

Some Aqara devices support Thread/Zigbee and allow the appropriate operating mode to be selected. In Thread mode, the device can participate in a compatible Matter ecosystem when a Thread-enabled Matter Controller is present. In Zigbee mode, the device connects through an Aqara Hub and can retain Aqara-specific functions depending on the model.

Example architectures

How to choose during deployment

• Check the protocol of the exact model rather than inferring it from the product family name.
• Define the primary ecosystem: Aqara Home, Apple Home or a multi-platform Matter setup.
• Check the hubs/controllers/Border Routers already present.
• Do not replace a stable Zigbee system merely to make protocol names look consistent.
• Design radio coverage around the real floor plan and physical obstacles.

Further reading

See Matter & Thread, Apple Home and Aqara Products.