Smart Home

Matter

Unified smart home standard

Matter is the unified smart home application-layer standard developed by the Connectivity Standards Alliance with Apple, Google, Amazon, and Samsung. It normalizes how smart home devices communicate with controllers, so any Matter-certified device works with any compatible app (HomeKit, Google Home, Alexa, SmartThings) — solving the long-standing per-brand-ecosystem fragmentation.

For an in-depth treatment, see Matter Protocol Explained. This page is a quick reference.

What Matter is

  • An application-layer protocol — defines device clusters, attributes, commands.
  • A commissioning standard — how devices join networks securely.
  • A security framework — fabrics, certificates, attestation.
  • 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 — it normalizes the application layer regardless of which radio is underneath. This is the key insight: Matter sits above Thread/WiFi/Ethernet, and Zigbee/Z-Wave devices participate via Matter bridges.

What problem Matter solves

Before Matter, smart home devices were ecosystem-fragmented:

  • Philips Hue bulbs required the Hue Bridge.
  • Ecobee thermostats required the Ecobee app.
  • Ring cameras required the Ring app.
  • Cross-ecosystem control (iPhone user + Android user in same household) was awkward at best.

Matter normalizes the device protocol so any Matter-certified device works with any Matter-compatible controller. The user picks a controller (HomeKit, Google Home, Alexa, SmartThings) and uses it for any Matter device. Multiple controllers can control the same device (multi-admin).

Matter fabrics

A fabric is a logical security boundary — a set of Matter devices and the controllers that operate them, sharing a common trust root. Each fabric has its own root CA, device certificates, and node IDs.

A device can be commissioned into multiple fabrics simultaneously. A Hue light might be in HomeKit AND Google Home AND SmartThings, each fabric controlling it independently. Each fabric sees the device as if it were the only fabric; commands from one controller cannot be observed by another fabric.

How devices commission

  1. Device enters commissioning mode (button press, first boot).
  2. Device broadcasts via BLE advertising.
  3. User opens controller app, scans QR code printed on device.
  4. Controller initiates secure pairing using passcode from QR.
  5. Device attests its identity via manufacturer certificate.
  6. Controller issues a fabric certificate.
  7. Device joins the operational network (WiFi or Thread).

For multi-admin, additional fabrics commission via sharing codes generated by the first controller and entered in the second.

Thread border routers

Thread is IPv6-native, and Matter low-power devices typically use Thread. A Thread border router bridges Thread to the WiFi/Ethernet network so all Matter devices appear on one logical IP network. Common border routers in 2026:

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

Best practice: deploy 2-3 border routers for redundancy.

Matter versions

VersionYearNotable additions
1.02022Initial release: lighting, sensors, locks, blinds, HVAC
1.22023Refrigerators, dishwashers, washing machines, vacuums, smoke/CO
1.32024Energy reporting, EV chargers, water heaters, microwaves
1.42024Multi-admin improvements, heat pumps, batteries, solar
1.52025Cameras, expanded media controls

What Matter does well

  • Local control. Devices work without internet.
  • Multi-admin. iPhone + Android in the same household just works.
  • Standard device data models. A new light works in every Matter app immediately.
  • Security. Strong cryptographic attestation; per-fabric isolation.
  • Backwards compatibility via bridges for Zigbee and Z-Wave devices.

What Matter struggles with

  • Vendor-specific features (custom modes, advanced effects) are not in the standard clusters.
  • Multi-admin in practice is sometimes finicky.
  • Cameras are new; most cameras still use proprietary protocols + per-vendor apps.
  • Onboarding has improved but is not yet flawlessly "scan and done."

Frequently Asked Questions

What radios does Matter run on?

Natively on Thread (for battery-powered devices), WiFi (for mains-powered devices and high-bandwidth use cases), and Ethernet. Zigbee and Z-Wave devices participate via Matter bridges that translate between the legacy protocol and Matter. The radio layer is intentionally below Matter — Matter normalizes the application layer regardless of which radio is underneath.

Does Matter replace Zigbee and Z-Wave?

No. Matter sits above the radio. Thread (the IPv6-native mesh radio) is the foundation for low-power Matter devices going forward. Zigbee and Z-Wave continue to exist and are bridged into Matter via Matter bridges (Philips Hue Bridge, Aqara M3, SmartThings hubs). New deployments target Thread + Matter; existing Zigbee/Z-Wave investments continue to work via bridges.

What is a Matter fabric?

A fabric is a logical security boundary containing a set of Matter devices and the controllers operating them. Each fabric has its own root Certificate Authority. 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.

What can I do with Matter today?

As of 2026, Matter covers lights, switches, plugs, sensors, locks, blinds, HVAC, refrigerators, dishwashers, washing machines, robotic vacuums, smoke and CO alarms, air quality sensors, fans, energy meters, EV chargers, water heaters, batteries, and cameras (added in Matter 1.5). Most major brands ship Matter-certified products in these categories. Categories not yet in Matter (some sensor types, specific appliances) use the next-best protocol or vendor app.

Related Terms

More From This Section