Matter, Thread and Zigbee: Smart Home Standards Explained

Smart home standards are easy to confuse because the names are used loosely. Matter is an application layer that defines how devices describe and control each other over IP networks. Thread is a low-power IPv6 mesh network that Matter can run over. Zigbee is an older, complete stack with its own network and application layers. This article separates the layers and explains what each choice means for a device design.

At a glance

802.15.4
The low-power radio standard used by both Thread and Zigbee.
3 networks
Matter runs over Wi-Fi, Thread and Ethernet, with Bluetooth LE used for commissioning.
IPv6
Every Thread device has an IPv6 address and reaches the home network through a border router.
Multi-admin
A Matter device can be controlled by several ecosystems at the same time.

The problem

Before Matter, a device maker targeting several ecosystems often had to build several integrations, each with its own certification and cloud connection. Matter aims to replace that with one local protocol that participating ecosystems all speak, maintained by the Connectivity Standards Alliance.

Matter does not remove every decision. Wi-Fi suits mains-powered devices with higher data needs, Thread suits battery sensors and needs a border router in the home, and an existing Zigbee base may still need supporting through a bridge.

Choose the network for the device and the application layer for the market. Matter, Thread and Zigbee answer different questions.

What building for Matter involves

A Matter device implements a data model of clusters, such as on/off or temperature measurement, and carries a device attestation certificate showing it is a certified product. Commissioning establishes trust with a controller, and control then runs over the local network without a cloud round trip.

Certification goes through the Connectivity Standards Alliance and its authorised test labs, and requires membership. Open-source SDKs and chip vendor support reduce firmware effort, but certification, attestation and test time still need a place in the plan.

What good looks like

Decide the power source and data needs first; these choose between Wi-Fi, Thread and Ethernet for a Matter device.

Check that the device type you need is defined in the current Matter specification, and which features each ecosystem supports for it in practice.

Budget for certification, attestation certificates and interoperability testing with each controller ecosystem you intend to support.

Where each standard sits
StandardLayerRadioIP based
MatterApplicationWi-Fi, Thread or EthernetYes
ThreadNetwork (mesh)IEEE 802.15.4, 2.4 GHzYes, IPv6
ZigbeeNetwork and applicationIEEE 802.15.4, mostly 2.4 GHzNo
Wi-FiLinkIEEE 802.11Carries IP
Simplified. Zigbee also defines sub-GHz options in some regions.
Thread and Zigbee
ThreadZigbee
AddressingIPv6Zigbee-specific
Matter supportNative transportThrough a bridge
Single coordinatorNot requiredRequired
Installed baseGrowingLarge and long established
Both use the same radio standard; they differ above it.

What it changes

Ecosystem Reach

One Matter implementation can work with several controller ecosystems.

Local Control

Commands travel over the home network without depending on a cloud service.

Low Power

Thread suits battery devices that must stay reachable without the power cost of Wi-Fi.

Clear Scope

Certification and testing costs are known before development begins.

Where to go next

If Zigbee products are already in the field, a Matter bridge can expose them to Matter controllers while new products adopt Matter natively.

Check that chips and modules support the Matter and Thread versions you need, with enough flash and RAM for the stack and updates.

Problems this prevents

  • Comparing standards at different layers
  • A battery sensor forced onto Wi-Fi
  • Certification costs discovered late
  • Device types no ecosystem supports yet

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.