| commit | 372360c4ec05a139e577f6f5d3a28ef8d3af86db | [log] [tgz] |
|---|---|---|
| author | Andrei Litvin <andy314@gmail.com> | Mon Apr 14 12:05:51 2025 -0400 |
| committer | GitHub <noreply@github.com> | Mon Apr 14 12:05:51 2025 -0400 |
| tree | ebe67e08feaf7e1fdb6dafc99cc4dddbd52a38eb | |
| parent | e139a44b66f76583a1aff0702b78f4cb611cfcb3 [diff] |
Add individual cluster metadata generation (and build targets) that is generated based on controller-clusters (#38151) * Start to support some metadata generation * Fix import * Clean up sources * Add generated metadata * Remove extra comma to make this a valid build.gn * Restyle * Updated content a bit: cluster ID is also fixed * Temporary workaround...but will look for something better * Better code reuse * Restyle * Restyle and add missing file * Remove some todo comments * make linter happy * Fix one case for namespace end comment * move generation to zzz_generated * rename path a bit more * Updated structure to zzz_generated/clusters/<NAME>' to contain individual cluster information * Update generated code: generate IDs that are compatible with old IDs (naming and namespace wise) * Add extra files * Fix up data type for events * More arrangement of things ... it almost works * Things now compile with dependencies. Need to figure out globals and then use the IDs * Start adding some global attribute handling * Update the code generator file list * Global attributes work * Update naming and add pragma once * Add response command IDs * All clusters app now compiles * update paths to one more level of indirection * Update darwin projects to add data_model whenever app-common is there * Update more include paths, make ASR compile by fixing platform dependencies * Fix qpg compilation * Fix more builds: nrf, nxp, stm32, telink * Fix ameba compilation * Restyle * fix MW320 builds * Fix bouffalolab compiles * Fix TI compilation * Add ids dependencies to darwin * Add ids dependencies to NuttX * Fix tizen build * Fix android build * Restyle * fix zephyr * match zap gen * more nxp fixes for ids * more nxp fixes for ids * make silabs/efr32 compile * Bulk-add depdendencies on IDs on all platforms * Update more cmake files to include directories that include data_model whenever app-common was included * Cleanup NXP dependencies * NuttX code cleanup: generate does a real generate, cleanup the target boards usage * darwin framework tool compile fix * Disabled NuttX builds - platform maintainer has been notified * Look to move items to reduce blast radius of changes * Start updating the structure to reduce stutter * Move into clusters * Fix include path * Regenerate and better sorting * Fix build files * Now that paths moved, re-enable nuttx * Update namespacing for attribute metadata entries * Restyled by autopep8 * Remove references to data_model name * Fix darwin framework tool build: its dependencies are just bad * Restyled by gn * Cleanup dependencies, we do not need util types * Fix path in Ids.h * Fix case typo in Clusters/clusters namespace * Zap regen * Address some code review comments: spacing, extra deps, format of cluster id * Fix typo * Update paths in metadata to pass compiler (at least LSP), update spacing a bit and regen * Fix namespace ordering --------- Co-authored-by: Andrei Litvin <andreilitvin@google.com> Co-authored-by: Restyled.io <commits@restyled.io>
Builds
Tests
Tools
Documentation
Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.
Matter is a unified, open-source application-layer connectivity standard built to enable developers and device manufacturers to connect and build reliable, and secure ecosystems and increase compatibility among connected home devices. It is built with market-proven technologies using Internet Protocol (IP) and is compatible with Thread and Wi-Fi network transports. Matter was developed by a Working Group within the Connectivity Standards Alliance (Alliance). This Working Group develops and promotes the adoption of the Matter standard, a royalty-free connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet. The vision that led major industry players to come together to build Matter is that smart connectivity should be simple, reliable, and interoperable.
Matter simplifies development for manufacturers and increases compatibility for consumers.
The standard was built around a shared belief that smart home devices should be secure, reliable, and seamless to use. By building upon Internet Protocol (IP), Matter enables communication across smart home devices, mobile apps, and cloud services and defines a specific set of IP-based networking technologies for device certification.
The Matter specification details everything necessary to implement a Matter application and transport layer stack. It is intended to be used by implementers as a complete specification.
The Alliance officially opened the Matter Working Group on January 17, 2020, and the specification is available for adoption now.
Visit buildwithmatter.com to learn more and read the latest news and updates about the project.
Matter is developed with the following goals and principles in mind:
Unifying: Matter is built with and on top of market-tested, existing technologies.
Interoperable: The specification permits communication between any Matter-certified device, subject to users’ permission.
Secure: The specification leverages modern security practices and protocols.
User Control: The end user controls authorization for interaction with devices.
Federated: No single entity serves as a throttle or a single point of failure for root of trust.
Robust: The set of protocols specifies a complete lifecycle of a device — starting with the seamless out-of-box experience, through operational protocols, to device and system management specifications required for proper function in the presence of change.
Low Overhead: The protocols are practically implementable on low compute-resource devices, such as MCUs.
Pervasive: The protocols are broadly deployable and accessible, by leveraging IP and being implementable on low-capability devices.
Ecosystem-Flexible: The protocol is flexible enough to accommodate deployment in ecosystems with differing policies.
Easy to Use: The protocol provides smooth, cohesive, integrated provisioning and out-of-box experience.
Open: The Project’s design and technical processes are open and transparent to the general public, including non-members wherever possible.
Matter aims to build a universal IPv6-based communication protocol for smart home devices. The protocol defines the application layer that will be deployed on devices and the different link layers to help maintain interoperability. The following diagram illustrates the normal operational mode of the stack: 
The architecture is divided into layers to help separate the different responsibilities and introduce a good level of encapsulation among the various pieces of the protocol stack. The vast majority of interactions flow through the stack captured in the following Figure:
Security: An encoded action frame is then sent down to the Security Layer to encrypt and sign the payload to ensure that data is secured and authenticated by both sender and receiver of a packet.
Message Framing & Routing: With an interaction encrypted and signed, the Message Layer constructs the payload format with required and optional header fields; which specify the message's properties and some routing information.
Matter’s design and technical processes are intended to be open and transparent to the general public, including to Working Group non-members wherever possible. The availability of this GitHub repository and its source code under an Apache v2 license is an important and demonstrable step to achieving this commitment. Matter endeavors to bring together the best aspects of market-tested technologies and redeploy them as a unified and cohesive whole-system solution. The overall goal of this approach is to bring the benefits of Matter to consumers and manufacturers as quickly as possible. As a result, what you observe in this repository is an implementation-first approach to the technical specification, vetting integrations in practice. The Matter repository is growing and evolving to implement the overall architecture. The repository currently contains the security foundations, message framing and dispatch, and an implementation of the interaction model and data model. The code examples show simple interactions, and are supported on multiple transports -- Wi-Fi and Thread -- starting with resource-constrained (i.e., memory, processing) silicon platforms to help ensure Matter’s scalability.
We welcome your contributions to Matter. Read our contribution guidelines here.
Instructions about how to build Matter can be found here .
The Matter repository is structured as follows:
| File/Folder | Content |
|---|---|
| build | Build system support content and built output directories |
| build_overrides | Build system parameter customization for different platforms |
| config | Project configurations |
| credentials | Development and test credentials |
| docs | Documentation, including guides. Visit the Matter SDK documentation page to read it. |
| examples | Example firmware applications that demonstrate use of Matter |
| integrations | 3rd party integrations |
| scripts | Scripts needed to work with the Matter repository |
| src | Implementation of Matter |
| third_party | 3rd party code used by Matter |
| zzz_generated | ZAP generated template code - Revolving around cluster information |
| BUILD.gn | Build file for the GN build system |
| CODE_OF_CONDUCT.md | Code of conduct for Matter and contribution to it |
| CONTRIBUTING.md | Guidelines for contributing to Matter |
| LICENSE | Matter license file |
| REVIEWERS.md | PR reviewers |
| gn_build.sh | Build script for specific projects such as Android, EFR32, etc. |
| README.md | This file |
Matter is released under the Apache 2.0 license.