{"id":13428445,"url":"https://github.com/project-chip/connectedhomeip","last_synced_at":"2025-09-09T20:51:20.697Z","repository":{"id":36966908,"uuid":"244694174","full_name":"project-chip/connectedhomeip","owner":"project-chip","description":"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.","archived":false,"fork":false,"pushed_at":"2025-05-12T16:07:33.000Z","size":719383,"stargazers_count":7903,"open_issues_count":2158,"forks_count":2157,"subscribers_count":210,"default_branch":"master","last_synced_at":"2025-05-12T16:44:46.941Z","etag":null,"topics":["build-with-matter","chip","connected-devices","connected-home","connectedhomeip","connectivity-standards-alliance","csa-iot","internet-of-things","iot","matter","standard"],"latest_commit_sha":null,"homepage":"https://buildwithmatter.com","language":"C++","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/project-chip.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2020-03-03T17:05:10.000Z","updated_at":"2025-05-12T16:07:38.000Z","dependencies_parsed_at":"2025-05-05T16:00:01.532Z","dependency_job_id":null,"html_url":"https://github.com/project-chip/connectedhomeip","commit_stats":{"total_commits":11408,"total_committers":425,"mean_commits":"26.842352941176472","dds":0.8764901823281908,"last_synced_commit":"804892e2f86317df0e9ce4cf589d0458cd78f30d"},"previous_names":[],"tags_count":33,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/project-chip%2Fconnectedhomeip","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/project-chip%2Fconnectedhomeip/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/project-chip%2Fconnectedhomeip/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/project-chip%2Fconnectedhomeip/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/project-chip","download_url":"https://codeload.github.com/project-chip/connectedhomeip/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253785011,"owners_count":21963903,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["build-with-matter","chip","connected-devices","connected-home","connectedhomeip","connectivity-standards-alliance","csa-iot","internet-of-things","iot","matter","standard"],"created_at":"2024-07-31T01:00:57.418Z","updated_at":"2025-05-12T18:21:58.337Z","avatar_url":"https://github.com/project-chip.png","language":"C++","readme":"# Matter\n\n[![Builds](https://github.com/project-chip/connectedhomeip/workflows/Builds/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/build.yaml)\n\n**Builds**\n\n[![Android](https://github.com/project-chip/connectedhomeip/workflows/Android/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/android.yaml)\n[![Ameba](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Ameba/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-ameba.yaml)\n[![ASR](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20ASR/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-asr.yaml)\n[![BouffaloLab](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20BouffaloLab/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-bouffalolab.yaml)\n[![Darwin](https://github.com/project-chip/connectedhomeip/workflows/Darwin/badge.svg)](https://github.com/project-chip/connectedhomeip/blob/master/.github/workflows/darwin.yaml)\n[![TI CC26X2X7](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20TI%20CC13XX_26XX/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-cc13xx_26xx.yaml)\n[![TI CC32XX](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20TI%20CC32XX/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-cc32xx.yaml)\n[![EFR32](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20EFR32/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-efr32.yaml)\n[![ESP32](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20ESP32/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-esp32.yaml)\n[![Infineon](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-infineon.yaml/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-infineon.yaml)\n[![i.MX Linux](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20i.MX%20Linux/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-linux-imx.yaml)\n[![K32W with SE051](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20K32W%20with%20SE051/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-k32w.yaml)\n[![Linux ARM](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Linux%20ARM/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-linux-arm.yaml)\n[![Linux Standalone](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Linux%20Standalone/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-linux-standalone.yaml)\n[![Linux Standalone](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Linux%20Standalone/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-linux-standalone.yaml)\n[![Mbed OS](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Mbed%20OS/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-mbed.yaml)\n[![MW320](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20MW320/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-mw320.yaml)\n[![nRF Connect SDK](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20nRF%20Connect%20SDK/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-nrfconnect.yaml)\n[![Open IoT SDK](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Open%20IoT%20SDK/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-openiotsdk.yaml)\n[![QPG](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20QPG/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-qpg.yaml)\n[![STM32](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20stm32/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-stm32.yaml)\n[![Telink](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Telink/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-telink.yaml)\n[![Tizen](https://github.com/project-chip/connectedhomeip/workflows/Build%20example%20-%20Tizen/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/examples-tizen.yaml)\n\n**Tests**\n\n[![Unit / Integration Tests](https://github.com/project-chip/connectedhomeip/workflows/Unit%20/%20Integration%20Tests/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/unit_integration_test.yaml)\n[![Cirque](https://github.com/project-chip/connectedhomeip/workflows/Cirque/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/cirque.yaml)\n[![QEMU](https://github.com/project-chip/connectedhomeip/workflows/QEMU/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/qemu.yaml)\n\n**Tools**\n\n[![ZAP Templates](https://github.com/project-chip/connectedhomeip/workflows/ZAP/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/zap_templates.yaml)\n\n**Documentation**\n\n[![Documentation Build](https://github.com/project-chip/connectedhomeip/actions/workflows/docbuild.yaml/badge.svg)](https://github.com/project-chip/connectedhomeip/actions/workflows/docbuild.yaml)\n\n-   [Matter SDK documentation page](https://project-chip.github.io/connectedhomeip-doc/index.html)\n\n# About\n\nMatter (formerly Project CHIP) creates more connections between more objects,\nsimplifying development for manufacturers and increasing compatibility for\nconsumers, guided by the Connectivity Standards Alliance.\n\n# What is Matter?\n\nMatter is a unified, open-source application-layer connectivity standard built\nto enable developers and device manufacturers to connect and build reliable, and\nsecure ecosystems and increase compatibility among connected home devices. It is\nbuilt with market-proven technologies using Internet Protocol (IP) and is\ncompatible with Thread and Wi-Fi network transports. Matter was developed by a\nWorking Group within the Connectivity Standards Alliance (Alliance). This\nWorking Group develops and promotes the adoption of the Matter standard, a\nroyalty-free connectivity standard to increase compatibility among smart home\nproducts, with security as a fundamental design tenet. The vision that led major\nindustry players to come together to build Matter is that smart connectivity\nshould be simple, reliable, and interoperable.\n\nMatter simplifies development for manufacturers and increases compatibility for\nconsumers.\n\nThe standard was built around a shared belief that smart home devices should be\nsecure, reliable, and seamless to use. By building upon Internet Protocol (IP),\nMatter enables communication across smart home devices, mobile apps, and cloud\nservices and defines a specific set of IP-based networking technologies for\ndevice certification.\n\nThe Matter specification details everything necessary to implement a Matter\napplication and transport layer stack. It is intended to be used by implementers\nas a complete specification.\n\nThe Alliance officially opened the Matter Working Group on January 17, 2020, and\nthe specification is\n[available](https://csa-iot.org/developer-resource/specifications-download-request/)\nfor adoption now.\n\nVisit [buildwithmatter.com](https://buildwithmatter.com) to learn more and read\nthe latest news and updates about the project.\n\n# Project Overview\n\n## Development Goals\n\nMatter is developed with the following goals and principles in mind:\n\n**Unifying:** Matter is built with and on top of market-tested, existing\ntechnologies.\n\n**Interoperable:** The specification permits communication between any\nMatter-certified device, subject to users’ permission.\n\n**Secure:** The specification leverages modern security practices and protocols.\n\n**User Control:** The end user controls authorization for interaction with\ndevices.\n\n**Federated:** No single entity serves as a throttle or a single point of\nfailure for root of trust.\n\n**Robust:** The set of protocols specifies a complete lifecycle of a device —\nstarting with the seamless out-of-box experience, through operational protocols,\nto device and system management specifications required for proper function in\nthe presence of change.\n\n**Low Overhead:** The protocols are practically implementable on low\ncompute-resource devices, such as MCUs.\n\n**Pervasive:** The protocols are broadly deployable and accessible, by\nleveraging IP and being implementable on low-capability devices.\n\n**Ecosystem-Flexible:** The protocol is flexible enough to accommodate\ndeployment in ecosystems with differing policies.\n\n**Easy to Use:** The protocol provides smooth, cohesive, integrated provisioning\nand out-of-box experience.\n\n**Open:** The Project’s design and technical processes are open and transparent\nto the general public, including non-members wherever possible.\n\n## Architecture Overview\n\nMatter aims to build a universal IPv6-based communication protocol for smart\nhome devices. The protocol defines the application layer that will be deployed\non devices and the different link layers to help maintain interoperability. The\nfollowing diagram illustrates the normal operational mode of the stack:\n![Matter Architecture Overview](docs/images/Matter_Arch_Overview.png)\n\nThe architecture is divided into layers to help separate the different\nresponsibilities and introduce a good level of encapsulation among the various\npieces of the protocol stack. The vast majority of interactions flow through the\nstack captured in the following Figure:\n\n![Matter Stack Architecture](docs/images/Matter_Layered_Arch.png)\n\n1. **Application:** High-order business logic of a device. For example, an\n   application that is focused on lighting might contain logic to handle turning\n   on/off the bulb as well as its color characteristics.\n\n2) **Data Model:** The data layer corresponds to the data and verb elements that\n   help support the functionality of the application. The Application operates\n   on these data structures when there is an intent to interact with the device.\n\n3. **Interaction Model:** The Interaction Model layer defines a set of\n   interactions that can be performed between a client and server device. For\n   example, reading or writing attributes on a server device would correspond to\n   application behavior on the device. These interactions operate on the\n   elements defined at the data model layer.\n\n4) **Action Framing:** Once an action is constructed using the Interaction\n   Model, it is serialized into a prescribed packed binary format to encode for\n   network transmission.\n\n5. **Security:** An encoded action frame is then sent down to the Security Layer\n   to encrypt and sign the payload to ensure that data is secured and\n   authenticated by both sender and receiver of a packet.\n\n6. **Message Framing \u0026 Routing:** With an interaction encrypted and signed, the\n   Message Layer constructs the payload format with required and optional header\n   fields; which specify the message's properties and some routing information.\n\n7) **IP Framing \u0026 Transport Management:** After the final payload has been\n   constructed, it is sent to the underlying transport protocol for IP\n   management of the data.\n\n# Current Status of Matter\n\nMatter’s design and technical processes are intended to be open and transparent\nto the general public, including to Working Group non-members wherever possible.\nThe availability of this GitHub repository and its source code under an Apache\nv2 license is an important and demonstrable step to achieving this commitment.\nMatter endeavors to bring together the best aspects of market-tested\ntechnologies and redeploy them as a unified and cohesive whole-system solution.\nThe overall goal of this approach is to bring the benefits of Matter to\nconsumers and manufacturers as quickly as possible. As a result, what you\nobserve in this repository is an implementation-first approach to the technical\nspecification, vetting integrations in practice. The Matter repository is\ngrowing and evolving to implement the overall architecture. The repository\ncurrently contains the security foundations, message framing and dispatch, and\nan implementation of the interaction model and data model. The code examples\nshow simple interactions, and are supported on multiple transports -- Wi-Fi and\nThread -- starting with resource-constrained (i.e., memory, processing) silicon\nplatforms to help ensure Matter’s scalability.\n\n# How to Contribute\n\nWe welcome your contributions to Matter. Read our contribution guidelines\n[here](./CONTRIBUTING.md).\n\n# Building and Developing in Matter\n\nInstructions about how to build Matter can be found [here](./docs/README.md) .\n\n# Directory Structure\n\nThe Matter repository is structured as follows:\n\n| File/Folder        | Content                                                                                                                                               |\n| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |\n| build              | Build system support content and built output directories                                                                                             |\n| build_overrides    | Build system parameter customization for different platforms                                                                                          |\n| config             | Project configurations                                                                                                                                |\n| credentials        | Development and test credentials                                                                                                                      |\n| docs               | Documentation, including guides. Visit the [Matter SDK documentation page](https://project-chip.github.io/connectedhomeip-doc/index.html) to read it. |\n| examples           | Example firmware applications that demonstrate use of Matter                                                                                          |\n| integrations       | 3rd party integrations                                                                                                                                |\n| scripts            | Scripts needed to work with the Matter repository                                                                                                     |\n| src                | Implementation of Matter                                                                                                                              |\n| third_party        | 3rd party code used by Matter                                                                                                                         |\n| zzz_generated      | ZAP generated template code - Revolving around cluster information                                                                                    |\n| BUILD.gn           | Build file for the GN build system                                                                                                                    |\n| CODE_OF_CONDUCT.md | Code of conduct for Matter and contribution to it                                                                                                     |\n| CONTRIBUTING.md    | Guidelines for contributing to Matter                                                                                                                 |\n| LICENSE            | Matter license file                                                                                                                                   |\n| REVIEWERS.md       | PR reviewers                                                                                                                                          |\n| gn_build.sh        | Build script for specific projects such as Android, EFR32, etc.                                                                                       |\n| README.md          | This file                                                                                                                                             |\n\n# License\n\nMatter is released under the [Apache 2.0 license](./LICENSE).\n","funding_links":[],"categories":["Development","HarmonyOS","C++","\u003ca name=\"cpp\"\u003e\u003c/a\u003eC++","Real-World Projects","Framework"],"sub_categories":["Windows Manager","Embedded Development"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fproject-chip%2Fconnectedhomeip","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fproject-chip%2Fconnectedhomeip","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fproject-chip%2Fconnectedhomeip/lists"}