Matter in the smart home: what the published standard actually promises

What Matter is, per the Alliance

Matter is developed by the Connectivity Standards Alliance (CSA), the same industry body behind Zigbee. The CSA's published FAQ defines it as “a new, open smart home protocol that uses existing, familiar technologies, including Bluetooth Low Energy for device setup and Wi-Fi, Thread, and Ethernet for connecting devices.” The Alliance positions Matter as “the foundation for connected things” — one IP-based protocol meant to let devices, apps and cloud services from different manufacturers talk to each other.

Three structural facts from the official documents matter for buyers. First, Matter is open source: the CSA states the protocol was built with contributions from Amazon, Apple, Google and others, and the Matter Handbook describes it as implemented by an open-source SDK that runs over any IPv6 network. Second, Matter is a certification programme, not just a protocol: only certified devices may carry the Matter logo, the underlying transports (Wi-Fi, Thread) must hold their own certifications, and every certified product must be listed on the Alliance's Distributed Compliance Ledger. Third, each device ships with a device attestation certificate — issued by root certificate authorities operated by Alliance members, not the CSA itself — that verifies the device is authentic and certified.

Equally important is what Matter is not. The CSA FAQ answers the question directly: “Does Matter replace my currently used smart home platform? No.” Matter sits underneath the ecosystems; Apple Home, Google Home and Alexa remain the apps, voice assistants and automation engines.

The three promises: interoperability, local control, multi-admin

The CSA's own materials group Matter's value into simplicity, interoperability, reliability and security. Reduced to what a buyer can check, that becomes three concrete promises — each of which the platform vendors' published docs repeat in their own terms.

Interoperability. The CSA claims “devices from multiple brands work natively together.” Amazon's developer docs describe Matter as “an Internet Protocol (IP) wireless connectivity technology designed to enable interoperability between devices made by different manufacturers,” letting devices connect to Alexa “without a separate hub or smart home add-on.” Matter also supports bridges, so devices on Zigbee, Z-Wave or Bluetooth Mesh can be exposed into a Matter fabric — but, as the CSA FAQ states, there is no native interoperability between Matter and Zigbee without one.

Local control. The CSA describes Matter's reliability promise as “consistent and responsive local connectivity.” Amazon says the same operationally: a direct Matter connection “allows Alexa to control your device locally, reducing latency and improving reliability,” including during internet outages. The flip side, which the CSA also documents: Matter is a local technology, so Matter-only devices need an internet-connected controller — a hub or smart speaker — present at home to be reachable when you are away.

Multi-admin. Multi-admin is a core Matter feature that lets one device be connected to several platforms at once, with the user choosing “which apps and platforms can access each device” (CSA FAQ). Apple's support documentation shows this in practice: a Matter accessory paired in one app can be added to any other Matter-capable app, and pairings sync through iCloud Keychain, end-to-end encrypted. Amazon likewise documents the Multi-Admin feature for connecting one device to multiple platforms.

On security, the CSA documents unique device identities, encrypted communications and fine-grained access control, plus privacy practices such as data minimisation. It also concedes the boundary of its guarantee: complete privacy protection “will depend on the protections provided by service providers and device makers as well.”

Version history: 1.0 to 1.6

The Matter Handbook publishes the full release history. The Alliance aims for two minor releases a year (spring and autumn) with patch releases in between; the specification itself is split into four documents — Core, Application Cluster, Device Library and, since 1.2, Namespace. As of the Handbook's current page, the latest release is version 1.6.0, published June 2026:

The practical point for buyers: the version number on a device box says what the device implements — not what your platform supports. Amazon's documentation, for example, states its Matter-compatible Echo devices support the Matter 1.5 SDK and “a subset of Matter 1.5 and lower device types.” None of the three platform documents we read claims Matter 1.6 support.

Which devices the standard covers

The CSA FAQ lists the currently supported device categories as bridges, controllers, door locks, HVAC controls, lighting and electrical, media devices, safety and security sensors, and window coverings and shades — with use-case teams defining more, including cameras, robot vacuums, appliances, EV charging, energy management, smoke and CO, TVs and water management. (Cameras and several of those categories shipped in spec releases after that FAQ text was written.)

The Matter Handbook gives the certifiable list as of Matter 1.4, and it is long: four lighting types; plugs, mounted controls, pumps and water valves; switches including a generic switch and control bridge; thirteen sensor types from contact and occupancy to smoke/CO alarm, water leak and rain; door locks and window coverings; thermostat, fan and air purifier; six media types; robotic vacuum cleaners; eleven appliances; energy devices including EV chargers, solar, battery storage and heat pumps; and network-infrastructure types, including the Thread Border Router itself. To be certified, a device must conform to one of these approved types.

Certification, however, is the floor — not the ceiling of what works in your home. Each platform publishes its own supported list, and Google's is blunt about the gap: “Many Matter device types are supported in the Google Home ecosystem, though not all are fully supported,” and any type not on its list is “not officially supported.”

Thread vs Wi-Fi vs Ethernet

The Matter Handbook documents three link-layer transports in the current specification — Ethernet, Wi-Fi and Thread — with Bluetooth Low Energy reserved for commissioning. The Handbook is explicit that “BLE cannot be used as the sole transport technology for a Matter device”; it carries network credentials to the device during setup (via QR code, numeric code or, since later releases, optionally NFC) and then steps aside. All three operational transports are IPv6-based, and Matter is documented to work even on networks disconnected or firewalled from the global internet.

• Ethernet — the simplest case: no network credentials to hand over; the device is discovered via DNS-SD once connected. Typical for hubs and bridges.
• Wi-Fi — any approved 802.11 version and band may be used. A device must first hold Wi-Fi Alliance certification before it can be Matter-certified. Commissioning uses BLE or an existing proprietary onboarding path. Typical for mains-powered devices: plugs, speakers, appliances.
• Thread — a low-power 802.15.4 mesh protocol built for IP transport, requiring Thread Group certification and BLE for credential provisioning. Thread devices join through a Thread Border Router; Amazon documents that one “must commission Thread-based smart home devices” before Matter-over-Thread works, with Thread-enabled Echo and eero devices filling that role. Typical for battery-powered sensors and locks.

The buyer-visible consequence: a Thread-only device is only as good as the border router in the house. Apple states Thread-based accessories require a Thread-enabled home hub such as Apple TV 4K, HomePod (2nd generation), HomePod mini or a compatible third-party border router; Google and Amazon each publish which of their hubs and routers provide Thread border-router support.

What Apple, Google and Amazon publish

Each major platform maintains public Matter documentation, and the three differ in ways that should shape a purchase:

Read across the three, the pattern is clear: the standard certifies a device once, but each ecosystem decides how much of it to expose. Apple's published Home app list is the narrowest — no robot vacuums or major appliances, both covered by the standard since 1.2. Google documents the widest explicit device-type table. Amazon pins its support to a specific SDK generation and a subset of that generation's types.

The limitations vendors acknowledge

The official documents are unusually candid about what Matter does not do. Everything below comes from the CSA, Apple, Google or Amazon themselves:

• No remote access without a controller. The CSA FAQ: Matter-only devices “require an internet-connected controller — such as those built into smart speakers and smart home hubs — to be present in the home” for control from away.
• No native Zigbee interoperability. The CSA states plainly that Matter and Zigbee are different protocols with “no native interoperability”; bridging is the only sanctioned path.
• Updates are at the manufacturer's discretion. Whether an existing product ever gains Matter “depends on the technical capabilities of the device, and of course, whether the product maker chooses to make an update available” (CSA FAQ).
• Door locks lose remote and voice unlock in Google's ecosystem unless they mandate a PIN. Google's docs: remote unlock “is disabled on all surfaces” for Matter locks that don't require a PIN code, and voice unlock is disabled outright.
• Matter wall switches are effectively unusable in Google Home. Because Google does not expose the Binding cluster, an On/Off Light Switch can be commissioned but “they won't be able to do anything with it afterwards, other than delete it from the home.”
• Battery (sleepy) Thread devices can degrade. Google documents a 3-second maximum sleep period for full service; longer sleep cycles “might experience degradation of service, such as the devices being identified as offline.”
• Privacy depends on more than the protocol. The CSA concedes complete privacy protection depends on service providers and device makers as well as the standard.

Two further gaps show in the publication dates. Google's supported-devices page was last updated 8 October 2026 and Amazon's 1 May 2026 — neither references Matter 1.6 features such as Joint Fabric or NFC commissioning, and Apple's page (published 7 May 2026) states no spec version at all. A 1.6-certified device bought today may exercise features no major platform has yet documented supporting. Not verified — platform roadmaps for 1.6 support are not published on the pages reviewed here.

How to buy against the standard

Matter genuinely reduces the compatibility guesswork it was designed to remove: certified devices carry a verifiable identity, join over a documented setup flow, keep working locally, and can be shared across ecosystems at once. But the badge certifies the device against the specification — not any particular platform's support for that device type, spec version or feature.

Where the three lists disagree, buy to the shortest list you depend on. And treat new-spec features — cameras (1.5), Joint Fabric and NFC commissioning (1.6) — as undelivered until your platform's documentation says otherwise.