Building Matter Smart Home Devices 101

by May 2, 2023#IoT, #HomePage

Printer Icon

Building Matter devices with the new Matter protocol has become a very exciting moment in the IoT industry, where main industry players are working toward the same goal of connectivity and plug-and-play interoperable devices for smart homes.

The Matter protocol is the next frontier in IoT, with a trusted ecosystem, the highest encryption standards, and a commitment to secure users’ privacy and confidentiality.

The Matter standard is creating a unified connectivity ecosystem backed by Google, Amazon, Apple, and many others. This multi-vendor collaborative smart home environment creates device compatibility and accelerates the development and adoption of smart home use.


The Matter protocol is an IP-based application layer and data model that unifies devices operating with different IP protocols to communicate across different platforms. It operates on top of the IP network stack (transportation).

Matter is a common layer to connect many devices on top of Matter’s supported network protocols. Matter devices are discovered, commissioned, and provisioned over an IP protocol (IPv6-based networks) such as Wi-Fi, Thread, or Ethernet for operation and Bluetooth for setup (commissioning).

Matter Application Layer 


The Matter standard is very convenient for consumers as it allows any Matter-enabled app to interact with any device in any Matter ecosystem. This common application layer delivers device interoperability.

Consumers can confidently purchase Matter smart home devices and connect them to any ecosystem or controller (control app). Matter devices can be easily set up (plug and play), paired with the home app of choice, and controlled through any voice assistance.


Matter multi-admin features allow end users to choose which ecosystems to use, and users can connect devices to more than one ecosystem, extending control of devices and simultaneous controls from multiple controllers without relying on cloud-to-cloud. In addition, users can control Matter devices within any ecosystem.


Matter devices can communicate directly with other devices (Wi-Fi or Thread) and control devices from an app, bridge, or router. For example, devices working with Zigbee, Z-Wave, or BLE mesh can interact with Matter using a Matter bridge and interact with each other using a Matter border router.

Matter allows any non-Matter network device (Zigbee, BLE mesh, Z-Wave) to integrate with a Matter fabric (ecosystem), exposing devices to nodes in the Matter fabric. Matter bridges perform the translation for device communication to take place.

Matter bridges are a key component of the Matter standard as they allow existing devices to function in the Matter ecosystem as well as create interoperability. Old devices running on existing technologies can work with Matter.


A Matter fabric or ecosystem is a trusted space in a home network that enables device communication through a common set of cryptographic keys.

Bridges follow the Matter standard commissioning to join a Matter fabric with other networks (Zigbee, Z-Wave, etc.), discover the Matter-supported devices following a specified method, perform a matching process, and add endpoints in Matter. Finally, the controllers in Matter control the device in the other network (Zigbee, Z-Wave, etc.).


IoT developers can build controller functionality into any device. For example, a smart home can have more than one controller. As users purchase different devices and technologies with special features, these devices will have their own controllers. A device might also be controlled by several controllers.

For example, a user might use a Google Home app (multi-admin feature) to control an Alexa device. Integration of services will simplify customer experiences and bring a lot of innovation to the market. (Note: Mobile phones are initially only for setting up devices and do not work as controllers.)


The Matter standard unifies smart home ecosystems and devices, creating compatibility. Matter does not require the product to have an app to operate, allowing devices to be natively integrated into Google Home, Home Kit, or other ecosystem apps. But if products have unique capabilities, developers can build native Matter apps to differentiate their services (specialized services app).

Bridge functionality is being developed to bring older devices to Matter. Using bridges (hubs) provides the translation that supports Matter and provides continuity for those devices. Manufacturers are in the process of developing unified SDKs to create bridges that incorporate older devices into Matter.

The Matter alliance is open to any company interested in developing new device types (segments), inviting them to build apps and devices and including them in their development of specifications and test cases to get them ready for future releases.

Bridges, border routers, and devices are usually System on Chip (SoC) solutions with Matter SDKs, security features, and support. IoT industry players are working on getting their SDKs ready for Matter’s first specification release (Matter 1.0).


Adding or commissioning devices (client) to the fabric entry point is done through a commissioning device API call and a return request that asks the user to establish proof of possession (scanning a Wi-Fi QR code or entering a product code).

The user accesses their account in the ecosystem platform, selects the home, and grants control of the device to the ecosystem platform. This process allows the user to access and manage devices from an ecosystem network (e.g., a Google Home app or Apple Home) on iOS or Android.

This process does not require users to add their Wi-Fi or Thread credentials, as the ecosystem app handles this. Bluetooth Low Energy streamlines commissioning as a simple process. NFC is also in the works for onboarding.


It is possible to control and manage a Matter device from the developer’s own app by commissioning the device (commission request) to the developer’s custom fabric. This is possible thanks to the multi-admin commissioning feature of Matter, which allows sharing devices with other ecosystems/fabrics and apps simultaneously. The commission request specifies the services and metadata about the device in the callback method. Additionally, Matter devices can be shared with more platforms and apps through commissioning methods to call client apps acting as commissioners.

Sharing devices with multiple fabrics allows users in a home to interact with different ecosystems and the same Matter devices.


There is a significant opportunity now for developers to create apps that work in the open Matter-enabled ecosystems and provide new or superior services to users. In addition, many product managers are building Matter devices and apps that work in all major ecosystems.

Device makers can build an app for their devices. However, products don’t need an app to operate in Matter, as they can be natively integrated into Google Home, Home Kit, Amazon Alexa, or other ecosystem apps. On the other hand, building a specialized services app is beneficial for products with unique features.

Developing Matter devices means developers build one SDK for a product and deploy it everywhere—accelerating development (time to market) and reducing development costs and complexities, as functionality is reduced to a specific ecosystem. Matter’s open-source SDK is available to IoT developers so they can start working and contributing with code if considered.

You can start working with Matter’s open-source SDK on GitHub.


Product developers continue to focus on differentiating their products. Matter standard brings many opportunities that require consideration of some aspects. First, products must have the right SoC with transmission power and receiver sensitivity to ensure reliable connectivity.

Consumers are becoming more and more sophisticated and require intelligent and intuitive solutions. We refer to Matter smart home devices with machine learning capabilities that offer smarter solutions, voice control, data-intensive, and other functionality. However, these products require faster hardware that is energy efficient and operates at the edge (IoT edge).

Environmental awareness is another aspect relevant for consumers, pushing manufacturers to build long-lasting IoT devices with low battery waste (lower battery replacement and longer recharging intervals) and high memory capacity that can handle over-the-air (OTA) updates of firmware/software.

One of the strong differentiators of Matter smart home devices is the security standards of encryption and secure end-to-end communication, offering trusted connections, device identity mechanisms, access control mechanisms, and data security. These components provide confidentiality and privacy for users.

Device attestation and verification are key components of Matter’s security features. A compliance distributed ledger is one key feature of the Matter standard, together with a rigorous certification program that makes it a trusted ecosystem. In addition, the Matter protocol specification has defined integrations of security functionality.

Builders of Matter devices must also consider choosing a System on Chip (SoC) with incorporated security features and PSA security certification to offer consumers a trusted.


Google is committed to Matter development and has built end-to-end tools to integrate devices with Google, including developing Matter apps, building automation, testing and analytics, and other resources.

Matter APIs can be used to commission devices with Google Home and access the Google ecosystem, Google Home App, Google Nest Devices, and Android Smart Home control. Matter APIs also help users connect and share devices with other apps and platforms and connect other devices to Google Home.

The Matter protocol is built into Google Play Services. It allows developers to build native Android Matter apps using the Google Home Mobile SDK to link a device with their app, share them with other apps, and participate in multiple Matter ecosystems. The following video shows a sequence diagram illustrating how Google uses its sample application for Matter to achieve smart home interoperability.

Although this article is not focused on the technical aspects of development, readers interested in a technical presentation can visit the following webinar from Silicon Labs on building Matter devices with Google.

About Us: Krasamo is a mobile-first digital services and consulting company focused on the Internet-of-Things and Digital Transformation.

Click here to learn more about our IoT services.


Embedded Development with Krasamo

Embedded Development with Krasamo

Embedded systems are computer systems designed for specific tasks, often found in applications like consumer electronics and industrial automation. They are built on microcontrollers or microprocessors and require specialized knowledge of hardware components, electronic concepts, and programming languages. Key aspects include understanding microcontrollers, using Linux BSPs or FreeRTOS for optimization, and testing methodologies for reliability. Embedded development demands diverse skills in microcontrollers, real-time operating systems, and debugging tools to create efficient and reliable systems.

Mastering IoT Fundamentals: IoT Gateways Overview

Mastering IoT Fundamentals: IoT Gateways Overview

IoT gateways bridge the gap between IoT devices and networks, enabling secure and efficient data communication, processing, and management across various use cases. These gateways are essential for IoT networks, providing device management, remote monitoring, and security measures. They play a crucial role in IoT adoption, allowing for optimized solutions and improved system performance.

How to Capture Real-Time Data with IoT Sensors

How to Capture Real-Time Data with IoT Sensors

The article discusses the importance of IoT sensors in capturing real-time data from the physical world and how careful selection of sensors is critical for capturing the right type of data for IoT use cases.