Smart home interoperability
A smart home combines light bulbs, thermostats, security cameras, locks, and controllers. Before Matter, products used different protocols and platforms. A Zigbee bulb and a Z-Wave switch required separate integration, as did a Google Home display and a device designed only for Apple HomeKit. Each vendor could describe a device state, light command, or temperature report differently, so compatibility had to be checked for particular models.
Fragmentation required compatibility tables, several control apps, and multiple hubs or bridges connected to the router. Wi-Fi, Bluetooth, Zigbee, and Z-Wave carried data, while products from different ecosystems still needed a shared application model for device types, attributes, and commands. Sharing IP or a radio frequency did not define the meaning of the messages, so the problem was at the service layer rather than only at the radio range.
In 2019, Amazon, Apple, Google, and the Zigbee Alliance formed the Project CHIP working group, or Connected Home over IP. The Zigbee Alliance now operates as the Connectivity Standards Alliance. That project produced the open Matter standard. Matter is not a new wireless radio or a replacement for Wi-Fi. It is an application layer above existing network technologies, so products with certified capabilities can use a shared data model. Transport, power, and the supported feature set still depend on the particular product.
Matter as an application layer over IP
Matter defines an over . Operational Matter networks use Wi-Fi, Thread, or Ethernet according to the device capabilities.
A Matter device communicates on a local IP network through a supported transport. A Thread node uses IPv6, and a Thread Border Router carries traffic between Thread and Wi-Fi or Ethernet. Zigbee and Z-Wave products can participate through a Matter Bridge that maps their functions into the Matter model. For a native Matter device, a command from a phone to a bulb is IP traffic on the local network. A bridge is needed when an older product does not speak Matter and requires translation between its model and Matter clusters.
Matter standardizes device types, clusters, attributes, and commands. A light-on command has a defined format within its cluster, while compatibility depends on the certified capabilities of the device and controller. Philips Hue, Nanoleaf, and other brands can use this model when they implement the required device type. The Controller must still support the relevant endpoint and cluster, and certification does not mean that every application exposes every optional feature.
Matter transports and commissioning
Matter separates operational transport from commissioning. Wi-Fi, Thread, and Ethernet carry IP traffic, while BLE supports discovery and credential transfer in the profiles that implement it.
- Wi-Fi for higher-throughput devices
Matter uses Wi-Fi for mains-powered devices that require higher throughput. Wi-Fi is already present in most home networks, so it suits products that do not need to trade throughput for low energy use. This transport fits:
- Smart security cameras and video doorbells that stream high-definition video.
- Smart TVs and streaming media players.
- Smart home hubs and controllers that need a constant, high-speed connection to the internet.
For these devices, the Matter application protocol runs directly over the Wi-Fi connection.
- Thread for low-power devices
Thread serves devices that run for long periods on batteries and exchange small data payloads. For a door sensor or basic thermostat, a constant Wi-Fi connection could increase power use without helping the application. is another open, IP-based protocol designed specifically for the IoT. Its key features are:
- Mesh networking: Mains-powered Thread routers forward traffic between nodes, while sleepy end devices can save energy and wake on demand. If one path fails, routing can use other routers when the topology and power supply provide such a path.
- Low power: Door sensors and thermostats can operate on batteries for long periods, and in suitable profiles for years, when their wake cycle, traffic, and configuration allow it.
- Latency: Short mesh paths support responsive devices such as light switches, although the result depends on topology and load.
Thread uses IPv6. A Thread Border Router provides communication between the Thread subnet and Wi-Fi or Ethernet and can be separate from the Matter Controller.
- Bluetooth Low Energy for commissioning
BLE supports device discovery and credential transfer in many commissioning flows. The phone creates a temporary channel through which the device can receive credentials without moving operational traffic to Bluetooth. Wi-Fi, Thread, or Ethernet remains the operational transport. Matter 1.4.2 added Wi-Fi-only commissioning, and Matter 1.6 added full commissioning over NFC.
When you bring a new Matter device home, the process is simple:
- You scan a Matter QR code on the device with your smartphone.
- Your phone uses Bluetooth LE when the device supports that discovery and setup path.
- Through this Bluetooth LE link, your phone securely passes the credentials for your Wi-Fi or Thread network to the new device.
- The device uses the credentials to connect to its supported IP network. Later communication uses Wi-Fi, Thread, or Ethernet according to its certification, and BLE ends its role in this flow. When a product is already reachable over IP, discovery and setup can use the IP mechanisms defined for that profile.
Matter network components
A Matter network includes certified end devices, controllers, IP transports, and, for Thread, border routers. A typical home therefore combines endpoints, an app or hub acting as Controller, and infrastructure that provides local addressing and service discovery.
- Matter devices (nodes or endpoints): These products include smart bulbs, thermostats, sensors, blinds, and locks certified for specific device types and transports. They may use Wi-Fi, Thread, or Ethernet depending on the implementation. The shared data model describes the device function, but it does not remove differences in power, throughput, or available hardware options.
- Matter Controllers and Admins: A Commissioner sets up devices and assigns credentials. An Administrator manages security and privileges for the fabric, while a Controller controls devices and communicates with endpoints. Matter supports Multi-Admin, so more than one platform can receive access. A Controller can be:
- A smartphone app (e.g., Apple Home, Google Home, Amazon Alexa, Samsung SmartThings).
- A smart speaker or display (e.g., an Apple HomePod Mini, Google Nest Hub, or Amazon Echo).
- A dedicated third-party smart home hub.
Multi-Admin can share the same device set with an iPhone using Apple Home and an Android phone using Google Home when both platforms support the required features and credentials. It does not automatically unify the application interface, automation rules, or naming between platforms.
- Thread Border Router: This component connects a Thread subnet to other IP networks when a home includes Thread devices. A forwards IPv6 traffic and service discovery between Thread and Wi-Fi or Ethernet. A phone on Wi-Fi can then send a command to a Thread lock through the shared IP infrastructure. A border router may be built into a hub or smart speaker such as an Apple HomePod Mini, a Google Nest product, or an Amazon Echo device. Its networking role remains separate from the Matter Controller role. It does not have to be the Matter Admin, because its primary task is IPv6 connectivity and service discovery between network segments.
Matter standard benefits and limits
Matter organizes data models and access procedures across certified devices, platforms, and IP transports. The benefit concerns both users, who can combine products from different brands, and manufacturers, who describe features through shared types and certification procedures.
- Interoperability: The Matter logo indicates certification for specified device types, transports, and features. Certified products can interoperate with a Controller that supports the same clusters and procedures, for example in Apple Home, Google Home, or Amazon Alexa. It is not a promise that every optional feature is exposed, because the product and application must share the relevant scope.
- Simpler commissioning: QR codes and numeric setup codes support a common onboarding flow. BLE, Wi-Fi-only commissioning, or NFC is available according to the Matter version and product capabilities, so a device may require the setup path covered by its certification.
- Security: Matter defines device authentication and encrypted application sessions. Protection also depends on the certified product, Controller, network configuration, and updates.
- Local control: Devices can exchange data on a local IP network without sending every command through a cloud service. An automation, such as a motion sensor switching on a light, can continue after an internet outage when the local Controller, bridges, and required devices remain available. Remote and cloud-dependent features still require internet access.
- Standard development: The CSA extends Matter with new device types and features. Each device declares supported versions, endpoints, and clusters, so new capabilities require support from the product and Controller. The open standard supports incremental development, but an update to the specification does not automatically add a feature to hardware that is already certified.