Matter, explained by what it actually does

The one sentence that fixes most confusion#

There is no Matter radio. A Matter device is a Wi-Fi device, a Thread device or an Ethernet device that happens to speak a common application language on top. That single fact resolves the two questions people ask most: "Matter or Wi-Fi?" is a category error, and Matter vs Thread is not a versus at all. What Matter is, in plain terms works through the layer model with the buying consequences attached.

Underneath every Matter purchase there is still a radio decision, and the radio decides the things people actually complain about: battery life, range through walls, and whether the lock responds. Which radio for which job is where that decision lives.

What Matter genuinely fixed#

Three things, and they are real:

• One commissioning flow. Scan a code, join a network, done. No vendor hub, no account for the device itself. Matter pairing explained breaks down what the code contains and where the flow breaks.
• Multi-admin. The same physical device can belong to several ecosystems at once, each with its own credentials. Devices are required to support at least five of these security domains. Sharing a Matter device across ecosystems has the per-platform steps.
• A shared data model. A dimmable light is the same object everywhere, so a controller can support a device class rather than a device. How Matter actually works explains the model and ties each piece to something you have already seen in your app.

What it did not fix#

Matter standardizes the boring 80 percent of a device and leaves the interesting part in the vendor app. A color bulb with animated effects reduces to on, off, brightness and a solid color. A robot vacuum exposes start and stop, and no maps, no-go zones or schedules. A camera can be certified and still require a subscription to review a recording. What Matter still cannot do is the full list, and it is the page to read before you spend money.

The other half of the problem is that certification is not behavior. There is no alliance "Works with Matter" badge, so the "works with" logos on retail boxes are ecosystem programs, not Matter conformance. Works with Matter vs Matter certified decodes the box at the shelf.

Where the specification ends and your app begins#

The alliance publishes a release. Your ecosystem implements it months or years later, or not at all. As of September 2026 this is the state of the features people ask about:

Read that table as a buying instruction rather than a scoreboard. A device type that your controller does not implement will either not appear at all or will appear as a stripped-down version of itself. The Matter feature gap tracker keeps the detail current.

The number that matters more than the version number#

Matter 1.6 defines 92 device types. No consumer ecosystem is close to all of them. Reporting from the alliance's June 2026 event summarized Apple, Google and Amazon as being "barely at 1.3", and Google shipped the Matter 1.2 appliance types in September 2025, roughly 23 months after that specification was published. Every Matter version and what shipped in each has the full release history with dates, and which device types Matter supports sorts the categories into supported, partial and absent.

Start here#

• What Matter is, in plain termsThe layer model explained: why "Matter vs Wi-Fi" is a category error, what Matter guarantees, and the five things it does not.
• How Matter works: fabrics, nodes and clustersThe Matter data model for people who have to live with it: fabrics, nodes, endpoints, clusters, subscriptions, groups, and the ghost device problem.
• Every Matter version, and what shipped in eachThe full Matter release history with dates and device types, plus the corrections that circulate widely and the controller support gap.
• Which device types Matter supportsCategory by category: what Matter covers well, what it covers badly, and what it does not cover at all, plus how to check before you buy.
• Matter pairing explained: QR, BLE and NFCThe anatomy of a Matter setup code and the commissioning flow stage by stage, with the specific failure that belongs to each stage.
• Sharing a Matter device across ecosystemsMulti-admin step by step, the five fabric floor, the orphaned slot problem only a factory reset clears, and what Joint Fabric in 1.6 fixes.
• Matter bridges and what you lose through oneWhat an aggregator endpoint is, why bridged sub-devices never get firmware updates over Matter, and the specific features Hue, SwitchBot and Aqara drop.
• What Matter still cannot doWhere the specification stops, where the controllers lag, and where certification does not predict behavior. Ending with the parts Matter genuinely fixed.
• Matter vs Thread, and why the difference mattersThe one sentence answer, the layer model in plain words, and the four buying decisions that actually depend on knowing the difference.
• Works with Matter vs Matter certifiedThe Matter logo means certification. The works-with badges are ecosystem programs. Neither tells you whether your controller supports the device type.
• Matter cameras in 1.5: what is actually realSignaling in Matter, media over WebRTC, 42 certified SKUs from four vendors, and exactly one ecosystem where a Matter camera works end to end.
• Matter for energy: EV, solar, batteries, tariffsWhich energy features arrived in Matter 1.3, 1.4 and 1.5, which controllers actually expose them, and how to buy energy hardware that will not strand you.

If you already own things#

Matter does not replace your existing gear, it sits alongside it. A hub can present Zigbee, Z-Wave or cloud devices to a Matter controller as bridged devices, which is the cleanest on-ramp for a house full of older kit. Matter bridges and what you lose through one names what gets dropped, and why a bridged device never gets a firmware update over Matter.

If something is already broken, start at Matter pairing fails, which is ordered by likelihood rather than by how easy each fix is to write.