1. Introduction to Matter
1.1. Introduction
Matter is a new technology for smart homes that enables various devices to collaborate seamlessly, without being restricted by their brand or manufacturer. It is designed to simplify the smart home experience while maintaining security and privacy. One of the benefits of Matter is that it is an open standard, which means that any device manufacturer can use it. Matter is an initiative of the Connectivity Standards Alliance (CSA). It is developed through a collaboration among all the leaders of the IoT industry.
Matter is an application protocol that relies on IPv6 and runs on top of different network interface technologies such as Thread®, Wi-Fi®, and Ethernet.
The Matter software is provided as open source by CSA and is available under GitHub.
1.2. Device roles in Matter network
Smart homes use Wi-Fi or Thread technologies to operate connected devices. Each device has a distinct role within the Matter network.
- End devices are connected objects designed for final applications such as thermostats, light bulbs, door locks, and other smart home devices, which can be controlled through a smart home platform.
- Bridges are devices that enable communication between devices using different communication protocols. For example, a bridge can enable a device that uses Wi-Fi to communicate with a device that uses Zigbee®.
- Controllers refer to devices such as smartphones or tablets used to connect an end device to a Matter network via Bluetooth® LE. They serve as the central hub for the smart home network.
- Thread border router is a device that acts as a gateway between a Thread network and other IP-based networks, such as the Wi-Fi or other local networks. The border router plays a crucial role in a Matter ecosystem.
1.3. Matter stack overview
The Matter protocol is designed to be compatible with existing IP-based networks, making it easier for manufacturers to adopt and integrate into their products.
The Matter stack is composed of the following layers:
- Application layer: This layer includes the application-specific functionality and user interfaces that are built on top of the Matter protocol. It includes the presentation and the session layers.
- Transport layer: This layer includes the transport protocols used to transmit data over the network, such as TCP and UDP. BTP is provided as a transport protocol for commissioning. TCP and UDP are provided as transport protocols for operational messaging.
- Network layer: This layer includes the IPv6 network layer, which provides end-to-end connectivity for devices and services on the network.
- Link layer: This layer includes the data link layer, which provides the transmission of data frames over the physical layer.
The link and physical layers can vary depending on the type of network being used, such as Thread®, Wi-Fi®, or Ethernet.
Bluetooth® LE is used for device commissioning.
1.4. STM32 based Matter accessories
The STM32WBA and STM32WB series of microcontrollers are ideal for Matter networks because they can run Thread and Bluetooth® LE concurrently, which are used for device commissioning. Some of STM32 microcontrollers in these series are used as Matter device, and other as Radio Co-Processor (RCP).
- STM32 microcontrollers used as Matter device
- - STM32WBA65RI
- Based on an Arm® Cortex®-M33 core with Arm® TrustZone®, the STM32WBA65RI microcontroller has 2 Mbyte of flash memory and 512 Kbytes of RAM. It equips the STM32WBA65I-DK1[1] Discovery kit with external flash memory, a screen, audio sensor and audio codec.
- - STM32WB5MMG
- Dual-core MCU composed of an Arm® Cortex®-M0+ as radio coprocessor and an Arm® Cortex®-M4 for user application, the STM32WB5MMG module has 1 Mbyte of flash memory and 256 Kbytes of RAM to support application layer and connectivity stacks. Additionally, it features QUADSPI peripherals to extend the memory size externally. These features allow over-the-air firmware updates, regardless of the application and the connectivity stack. The STM32WB5MMG module equips the STM32WB5MM-DK[2] Discovery kit with sensors, external flash memory, a screen, and touch sensors.
- STM32 microcontrollers used as RCP
- - STM32WBA55CG
- Based on an Arm® Cortex®-M33 core with Arm® TrustZone®, the STM32WBA55CG microcontroller has 1 Mbyte of flash memory and 128 Kbytes of RAM. It equips the NUCLEO-WBA55CG[3] Nucleo-64 board which can be used as an RCP combined with an STM32MP1 to form an OpenThread Border Router (OTBR).
- - STM32WB55RG
- Dual-core MCU composed of an Arm® Cortex®-M0+ as radio coprocessor and an Arm® Cortex®-M4 for user application, the STM32WB55RG microcontroller has 1 Mbyte of flash memory and 256 Kbytes of RAM to support application layer and connectivity stacks. The STM32WB55RG equips the NUCLEO-WB55RG[4] Nucleo-64 board. In the Matter use case, this board can be used as an RCP combined with an STM32MP1 to form an OpenThread Border Router (OTBR).
- Samples for Matter demonstration
We propose several samples demonstrating the usage of Matter:
- - Matter end device [5]:
This package contains several sample applications of Matter end devices. These examples are based on Matter and behave as Matter accessories communicating over an 802.15.4 Thread network.
- - Matter bridge [6]:
The Matter bridge sample provides an example of a Matter bridge with the NUCLEO-H753ZI-Q board with Ethernet connectivity. Basically, it adds the non-Matter device as endpoints on a bridge acting as a Matter device.
- - Matter gateway STM32MP1 border router [7]:
The STM32MP1 OpenThread Border Router is composed of a NUCLEO-WB55RG or NUCLEO-WBA55CG as radio coprocessor and an STM32MP135F-DK Discovery kit, which are connected through a serial connection using an FTDI cable for NUCLEO-WB55RG or a USB cable for NUCLEO-WBA55CG.
2. Getting started with Matter
Demonstrate ED with delivered binaries: This is the fastest way as there is no need to compile the project.
Follow the following steps:
Step 1: Select the network interface technology (Thread or Wi-Fi)
Step 2: Select an ED platform supporting the chosen network interface technology
Step 3: Get the X-CUBE-MATTER
Step 4: Get binaries corresponding to the chosen platform and application device type. For binary location, refer to the projects folder within Folder structure. For example:
- - for Window-App on STM32WBA65I-DK1, the binary is stored in the binaries folder under X-CUBE-MATTER\Projects\STM32WBA65I-DK1\Applications\Matter\Window-App\Binaries
- - for Lighting-App on STM32WB5MM-DK, the binary for M4 core is stored in the binaries folder under X-CUBE-MATTER\Projects\STM32WB5MM-DK\Applications\Matter\Lighting-App\Binaries, and the binary for M0 core can be found in X-CUBE-MATTER\Projects\STM32WB_Copro_Wireless_Binaries\STM32WB5x.
Step 5: Program firmware to the end devices as indicated in End devices How To
Step 6: From now, the device can be commissioned in the chosen Matter Fabric ecosystem presented in Test and demonstrate.
3. Acronyms and definitions
| Term | Definition |
|---|---|
| BTP | Bluetooth transport protocol |
| ED | Matter End device |
| OTBR | OpenThread Border Router |
| RCP | Radio Co-Processor |
| TCP | Transmission control protocol |
| UDP | User datagram protocol |
4. References
Pages in category "Discover Matter"
The following 6 pages are in this category, out of 6 total.