Matter

Matter is the Connectivity Standards Alliance's application-layer standard for smart home devices: the layer that makes a device work with Apple Home, Google Home, Amazon Alexa, and Home Assistant through one certification rather than several separate ecosystem integrations. This subtopic covers Matter at the implementation level: choosing a transport, and building on the two most common embedded platforms.

What Is Matter Implementation?

This subtopic covers what it takes to actually ship a Matter device: choosing between Thread, Wi-Fi, and Ethernet as the underlying transport, and implementing the Matter stack on ESP32 (esp-matter) or a Nordic nRF5340-based design (nRF Connect SDK). For the protocol fundamentals (the data model, the fabric model, commissioning), see What Is Matter?.

This subtopic is part of the Wireless topic.

Why Matter Implementation Matters

• Transport choice is a power, cost, and infrastructure commitment, not a minor setting. Thread needs a Border Router somewhere in the home and suits battery-powered devices; Wi-Fi needs no additional infrastructure but costs materially more power; the choice shapes the product's BOM, certification path, and battery life simultaneously.
• Commissioning failures are one of the most common Matter bring-up issues, and they're easy to misdiagnose. A discriminator/passcode mismatch after a firmware rebuild looks identical, from the user's perspective, to several other distinct failure modes — getting the diagnosis wrong wastes debugging time on the wrong fix.
• The platform SDK choice (esp-matter vs nRF Connect SDK) determines which underlying transport is realistic. ESP32's Matter support is Wi-Fi-first (with Thread on newer H2/C6 variants); Nordic's nRF5340 is a Thread-native platform via its dual-core architecture — picking the SDK effectively pre-commits much of the transport decision.
• Matter certification is a real, non-optional step for a commercial product, distinct from Wi-Fi/Bluetooth radio certification, and needs to be planned into the product timeline rather than treated as a formality at the end.

Key Concepts

• Fabric — a Matter network's logical boundary; multiple ecosystem controllers (Apple Home, Google Home) can share commissioning of devices onto the same fabric, enabling true multi-admin control without vendor lock-in.
• Commissioning (PASE/CASE) — the process of securely adding a new device to a fabric: PASE (Passcode-Authenticated Session Establishment) for the initial unauthenticated pairing over BLE, followed by CASE (Certificate-Authenticated Session Establishment) once the device has fabric credentials.
• Discriminator and passcode — the values (typically encoded in a QR code or manual pairing code) a commissioner uses to find and securely pair with a specific device during PASE; regenerated by some SDKs on every firmware rebuild, which is a common source of "the QR code doesn't work anymore" failures.
• Transport (Thread / Wi-Fi / Ethernet) — Matter is an application-layer standard, not a radio protocol; it runs over any of these three transports, each with different power, infrastructure, and range trade-offs. See Matter over Thread vs Matter over Wi-Fi.
• Matter Bridge — a device that exposes existing non-Matter devices (Zigbee, Z-Wave) to a Matter fabric as bridged endpoints, letting established ecosystems participate in Matter automation without hardware replacement.

Common Questions

Should I build a Matter device on ESP32 or on a Nordic nRF5340?

Choose based on the transport your product actually needs. ESP32 (via esp-matter) is the straightforward choice for a Wi-Fi-transport Matter device, with Thread support available on the newer ESP32-H2/C6 variants. The nRF5340 is the more natural choice for a Thread-native, battery-powered device, using its dual-core architecture (network core for OpenThread, application core for Matter/Zephyr) via the nRF Connect SDK. See Matter on ESP32 and Matter on nRF Connect SDK for the platform-specific implementation detail.

Why does my device's QR code stop working after a firmware update?

The most common cause is that the firmware rebuild silently regenerated the device's discriminator and/or passcode: values that are supposed to remain stable across updates but can change if they're derived from something that isn't fixed (a random seed re-initialised at build time, for instance) rather than being persisted or provisioned deterministically. The printed QR code then no longer matches what the device actually advertises, and PASE commissioning fails even though the device is otherwise healthy. A distinct but similarly-presenting failure is fabric-credential loss after an update, which requires re-commissioning rather than just a new QR code. See the Matter commissioning forum thread for the full diagnostic split between these two failure modes.

Does a Matter device also need to support Bluetooth?

Effectively yes, for commissioning: even a Wi-Fi- or Thread-transport Matter device typically uses BLE for the initial PASE commissioning exchange, since it doesn't yet have network credentials to communicate any other way. Once commissioning completes, the device communicates over its actual transport (Wi-Fi, Thread, or Ethernet); BLE's role is specifically the bootstrap step. Zeus Design designs and implements Matter-certified smart home devices on ESP32 and nRF platforms.

Knowledge Base

Matter Fundamentals

• What Is Matter? — the CSA's application-layer smart-home standard, device types, the fabric model and multi-admin, QR-code/BLE commissioning, and Matter over Thread/Wi-Fi/Ethernet

Transport Selection

• Matter over Thread vs Matter over Wi-Fi: Which Transport Should You Choose? — power budget, Border Router requirements, latency/range comparison, and a decision framework for battery-powered vs mains-powered Matter devices

Platform Implementation

• How Do You Implement a Matter Device on the ESP32? — the esp-matter SDK, device type selection, commissioning with chip-tool, and Thread support on ESP32-H2/C6
• How Do You Implement a Matter Device on the nRF Connect SDK? — nRF5340 dual-core architecture, NCS Matter samples, chip-tool commissioning, and certification considerations

Forum Discussions

• ESP32 Matter device advertises fine over BLE but commissioning fails every time — a stale QR code after a firmware rebuild regenerating the discriminator/passcode, and a distinct fabric-persistence failure mode to rule out separately