What makes Matter different from every other smart-home standard?

Why the alliance says this is not just another protocol

The Connectivity Standards Alliance posted a page titled "Alliance Members on Matter: Building More Connected Smart Home Experiences" on September 3, 2026. The page collects statements from companies that belong to the alliance. They describe Matter as a way to get interoperability across brands and ecosystems. They call out the flexibility of IP-based connectivity. They say the result is less friction for the people who use connected products every day.

The specification defines how devices speak to each other on a local network. It runs on top of Internet Protocol. That means a light bulb, a lock, and a thermostat can exchange packets the same way a laptop talks to a printer. No proprietary bridge is required. No vendor cloud is required for basic control.

This communication does not release a new version number. It does not announce a new certification program. It is a communication piece. The purpose is to show that member companies are shipping products that work together today.

How IP-based connectivity removes the middleman

These devices join the home Wi-Fi or Thread network directly. They receive an IP address from the home router. They advertise themselves with mDNS. A controller — a phone, a speaker, a hub — discovers them locally. The controller sends a command over the local network. The device executes it. The path is short. The vendor cloud is optional. It can be used for remote access or analytics. It is not in the critical path for turning on a light.

Thread is a low-power mesh based on IPv6. Wi-Fi and Ethernet are also supported. The specification does not force a single radio. It forces a common application layer on top of IP. That layer defines device types, clusters, attributes, and commands. A Matter light bulb from Brand A exposes the same OnOff cluster as a Matter light bulb from Brand B. A controller that knows the cluster can operate both.

What changes when you buy a Matter device

Setup uses a QR code or a numeric code printed on the device. The code contains a passcode and a discriminator. The controller scans the code. It opens a PASE session with the device. It verifies the device attestation certificate against the Distributed Compliance Ledger. The ledger is a blockchain-anchored registry operated by the alliance. It proves the device passed certification. The controller then commissions the device onto the local network. It installs the operational certificate. It configures the device with network credentials. The device is now reachable by any authorized controller on the same fabric.

A fabric is a logical group of devices that share a root certificate. A home can have multiple fabrics. A device can belong to multiple fabrics simultaneously. That means the same lock can be controlled by Apple Home, Google Home, and Samsung SmartThings at the same time. Each ecosystem adds its own fabric. The device stores multiple operational certificates. Each fabric has its own access control lists. The user does not see the complexity. The user sees a device that appears in every app.

According to the page, this creates more connected, consistent experiences across smart homes and buildings. It does not quantify how many products are certified. It does not list specific brands. It does not give performance numbers. It does not mention latency, throughput, or battery life. It does not discuss security vulnerabilities. It does not describe the certification test suite. It does not explain how the Distributed Compliance Ledger reaches consensus. Those details live in other documents.

Where the explanation stops

The page is a collection of quotes. It does not contain a technical specification. It does not contain a compliance checklist. It does not contain a list of certified product IDs. It does not contain a timeline for future specification releases. It does not contain a comparison matrix against Zigbee, Z-Wave, or proprietary protocols. The reader who wants to implement a Matter controller must go to the developer resources section of the CSA site. The reader who wants to certify a product must follow the certification process described there. The reader who wants to know which devices exist today must search the certified products database. The announcement points to those resources. It does not replace them.