Matter Protocol Explained

What Matter is and is not

Matter is:

• An application-layer protocol — clusters, attributes, commands for device interaction.
• A commissioning standard — how devices join a network and authenticate.
• A security framework — certificates, attestation, fabric isolation.
• A device data model — standard schemas for lights, switches, thermostats, locks, etc.
• An IPv6-based protocol that runs over WiFi, Thread, and Ethernet.

Matter is NOT:

• A radio standard — it does not specify what wireless medium devices use.
• A replacement for Zigbee or Z-Wave radios — they continue to exist, used by bridges.
• A cloud service — it works fully locally, with optional cloud features for remote access.
• A consumer app — the controller apps (HomeKit, Google Home, etc.) provide the user experience.

The Matter stack

┌─────────────────────────────────────────┐
│ Application                             │
│ (Clusters: OnOff, LevelControl, etc.)   │
├─────────────────────────────────────────┤
│ Matter (application protocol)           │
│ Commissioning, fabrics, attestation     │
├─────────────────────────────────────────┤
│ UDP / TCP                               │
├─────────────────────────────────────────┤
│ IPv6                                    │
├─────────────────────────────────────────┤
│ WiFi  /  Thread (802.15.4)  /  Ethernet │
└─────────────────────────────────────────┘

The clear separation: Matter sits at the application layer; the network layer is standard IPv6; the radio is whichever the device has. This is the key to interoperability — once a device has an IPv6 address, any Matter controller can speak to it regardless of how it got connected.

Clusters: the data model

Matter uses "clusters" (inherited from Zigbee Cluster Library) as its application data model. Each cluster represents a capability:

Each cluster has attributes (state to read) and commands (actions to invoke). A light might expose the OnOff cluster (attribute: on/off state; commands: Toggle, On, Off), LevelControl (attribute: brightness; commands: MoveToLevel), and ColorControl (attributes: hue, saturation; commands: MoveToColor).

The Matter spec defines clusters for every common device class. A controller that understands the OnOff cluster can control any light, plug, or switch from any vendor that exposes it — no per-brand integration code needed.

Fabrics: the security boundary

A "fabric" is a logical group of devices and controllers sharing a common trust root. Each fabric has its own:

• Root Certificate Authority (RCA) — the trust anchor.
• Device certificates issued under that RCA.
• Network of devices that have been commissioned into the fabric.

A device can be in multiple fabrics simultaneously. A Hue light might be in both the HomeKit fabric (controlled by an iPhone) and the Google Home fabric (controlled by a Pixel) and a SmartThings fabric, all at the same time. Each controller sees the device independently; commands from one fabric cannot be observed by another.

This multi-fabric design is the key to "multi-admin" — the use case where a household has both Apple and Android users and wants both to control the same devices. Older smart home protocols required choosing one ecosystem; Matter lets devices belong to several.

Commissioning: how devices join

Adding a Matter device to your network:

1. Device enters commissioning mode. Usually triggered by power-on or button press. The device starts broadcasting via BLE.
2. User scans QR code. Printed on the device or its packaging. The QR encodes a vendor ID, product ID, discriminator, and commissioning passcode.
3. Controller initiates pairing. The phone app connects to the device via BLE using the passcode to derive a secure session via PASE (Password Authenticated Session Establishment).
4. Device attestation. Device proves its identity via a Device Attestation Certificate signed by the manufacturer.
5. Fabric onboarding. Controller adds the device to the fabric — issues a certificate, assigns a node ID, configures operational network credentials (WiFi password or Thread credentials).
6. Switch to operational network. Device disconnects from BLE and joins the WiFi or Thread network using the credentials it just received.
7. Operational use. Device responds to standard Matter commands over IPv6.

For multi-admin, after the first controller commissions the device, the user can add the device to additional fabrics by generating a sharing code in one app and entering it in another.

Thread border routers: where networks meet

A Matter network typically uses Thread for low-power devices and WiFi for everything else. The two are different networks at the radio layer but unified at the IPv6 layer via a Thread Border Router (TBR).

A TBR:

• Speaks both Thread and WiFi/Ethernet.
• Routes IPv6 packets between Thread devices and the main IP network.
• Advertises the Thread network credentials so devices can join.
• Provides redundancy if multiple TBRs are on the network.

Common TBR devices in 2026:

• Apple HomePod mini, HomePod (2nd gen), Apple TV 4K.
• Google Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro.
• Amazon Echo (4th gen+), Echo Hub, Echo Show 10.
• eero Pro 6E, Pro 7, mesh routers.
• Samsung SmartThings Hub v3, Aeotec Smart Home Hub.
• Home Assistant Yellow, Home Assistant Connect ZBT-1.

Best practice: deploy multiple TBRs (typically 2-3) for redundancy. A single failed TBR breaks Thread connectivity for the whole house; with multiple, the network self-heals.

Matter bridges: integrating legacy devices

For Zigbee, Z-Wave, and proprietary devices, a Matter bridge translates between the legacy protocol and Matter:

• Bridge runs both protocols simultaneously.
• Each bridged device appears in the Matter fabric as if it were a native Matter device.
• Controllers see one virtual device per legacy device.
• Commands from controllers are translated to the legacy protocol and forwarded.

Common Matter bridges:

• Philips Hue Bridge — bridges Zigbee Hue lights to Matter.
• Aqara M3 Hub — bridges Zigbee Aqara devices.
• SmartThings Station / Hub — bridges Zigbee and Z-Wave.
• Aeotec hubs — Z-Wave to Matter.
• Home Assistant — software-based bridge for many protocols (Zigbee, Z-Wave, custom integrations).

This is the migration path: keep existing Zigbee devices, add a Matter bridge, and they suddenly appear in HomeKit and Google Home alongside native Matter devices.

Matter versions and what's in them

Matter has released several versions:

• Matter 1.0 (October 2022): Initial release. Core device categories: lighting, plugs, switches, sensors, locks, blinds, HVAC.
• Matter 1.1 (May 2023): Improvements, no major new device types.
• Matter 1.2 (October 2023): Added refrigerators, dishwashers, washing machines, robotic vacuums, smoke/CO alarms, air quality sensors, fans.
• Matter 1.3 (May 2024): Added energy reporting, EV chargers, water heaters, kitchen appliances, microwaves.
• Matter 1.4 (November 2024): Multi-admin improvements, heat pumps, water heaters, solar inverters, batteries.
• Matter 1.5 (2025): Cameras, occupancy sensing improvements, expanded media controls.

The 2026 trajectory: Matter is gradually absorbing every device category that previously needed a proprietary app.

What Matter does well

• Local control. Devices work without internet. Matter is designed for local-first operation.
• Multi-admin. Genuinely solves the "iPhone user + Android user in same household" problem.
• Standardized device data models. A new Matter light works in every Matter app immediately.
• Security. Strong cryptographic attestation; per-fabric isolation; device certificates from manufacturers.
• Backwards compatibility via bridges. No need to throw out existing Zigbee or Z-Wave investments.

What Matter still struggles with

• Vendor-specific features. If your light has a special "candle flicker" mode, that mode is not in standard Matter clusters — only generic features are interoperable.
• Multi-admin complexity in practice. Adding a device to a second fabric is sometimes finicky; some bridges only expose devices to one fabric at a time.
• Camera support is new. Most cameras still use proprietary protocols + per-vendor apps in 2026 despite Matter 1.5 adding cameras.
• Energy reporting and complex appliances. Specs exist but few devices yet implement them.
• Onboarding still bumpy. First-pairing experience has gotten better but is not yet "scan and done" reliably.

The strategic implication

Matter normalizes the smart home at the application layer the way HTTP normalized the web. The radio layer (Thread, Zigbee, Z-Wave, WiFi) and the app layer (HomeKit, Google Home, Alexa, SmartThings) both continue to exist and compete, but they meet in the middle at Matter. Users get to choose their preferred controller and use it with any certified device. Vendors get to compete on device features without lock-in.

For a new smart home installation in 2026, the rough plan: buy Matter-certified devices wherever available; use Thread for battery-powered devices; use WiFi for high-bandwidth devices; deploy multiple Thread border routers; pick the ecosystem you like (HomeKit, Google Home, Alexa, or Home Assistant) and add others as needed via multi-admin.

Frequently Asked Questions

What is Matter and what does it solve?

Matter is a unified application-layer standard for smart home devices, developed by the Connectivity Standards Alliance (formerly Zigbee Alliance) with Apple, Google, Amazon, Samsung, and others. It solves the long-standing problem that smart home devices needed separate apps and hubs per brand — a Hue bulb required a Hue bridge, an Ecobee thermostat needed Ecobee's app, etc. Matter normalizes the device protocol so any Matter-compatible controller (HomeKit, Google Home, Alexa, SmartThings) can control any Matter-certified device.

Does Matter replace Zigbee, Z-Wave, and Thread?

Matter is layered above the radio. It runs natively over Thread, WiFi, and Ethernet. Zigbee and Z-Wave devices participate via "Matter bridges" that translate between the legacy protocol and Matter. So Matter does NOT replace these radios — it sits on top of Thread directly and on Zigbee/Z-Wave via bridges. The radio standards continue to exist; Matter normalizes the application layer regardless of which radio is underneath.

What is a Matter fabric?

A fabric is a logical security boundary that contains a set of Matter devices and the controllers that operate them. Each fabric has its own root CA and device certificates. A device can be commissioned into multiple fabrics simultaneously — for example, both HomeKit and Google Home — which is how Matter enables true multi-ecosystem control. Each fabric sees the device independently; commands from one controller cannot be intercepted by another fabric.

How does Matter commissioning work?

A device in commissioning mode broadcasts via BLE (Bluetooth Low Energy). The user opens their controller app (HomeKit, Google Home, etc.), scans a QR code on the device, and the controller initiates a secure pairing handshake. After commissioning, the device joins the appropriate fabric and switches to its operational network (WiFi or Thread). The QR code contains a device identifier and a commissioning passcode used to establish the initial secure channel.

Why does Matter need both Thread and WiFi?

Different device classes need different network properties. Battery-powered devices (door sensors, contact sensors, leak detectors) need low-power mesh networking — Thread is purpose-built for that. Mains-powered devices with high bandwidth needs (cameras, displays, hub devices themselves) need WiFi's throughput. A unified Matter network includes both — a Thread border router (also a WiFi device) bridges the two so the user sees one logical home network.