Test Case Software Update 2.5 (#41182) * SU 2.5 Step 1 and 2 * Added basic logic for step 3 * Added logic for step 4 * Completed step 5 ( still need to check if we can confirm the downloaded image was deleted * Added step 5 , verify downloaded file check * Changes for SUBase * Incomming changes from su_base_class branch * Added line to show when the wait time of 3 minutes has completed. * Updated wait times as the spec. Added secondary implementnation for event tracking as comments. * Ruff and isort fix * Added better reading for step2: Added attribute wait for BasicInformationCluster.Softwareversion to update it and verify it did not happend in less than the delaytime * isort check * Revert "Incomming changes from su_base_class branch" This reverts commit d43bfcaf1c429e65baf164e4c7e7bab9a1fde48a. * base class changes * Updates for 2.5 * Interval fix * New updates for handling await time after apply or delayapplyupdate * Fix invalid method for event handler * Updated to user test arguments * Revert "base class changes" This reverts commit 56823c7d09c5d886b53339e0c4a003df93f3dfef. * Integrated su_base_class branch * Updated test to use test arguments * Remove read_from_logs. Verify with update state idle * Revert "Integrated su_base_class branch" This reverts commit e044f1c0e9a243a5c3170ea56b455da65740c1b3. * Merge base class: Remove if needed * ruff Changes * Minor changes for SU 2.5. Added restart and state value tracking. * Stop the app before start. Needed to avoid port collissions for apps launched with --secure-device-port. Removed break in monitor_app_requestor to allow multiple restarts * Added terminate method * Updated startup timeout for provideradd * Port changed * Updated initialization string * Removed default port for requestor. * Added argumetn validation * Awaiting async method * Added optional values for provider log and kvs * Removed TC_SU_2_5 from CI as it takes a lot of time. * Restyled by prettier-yaml * Added custom download time for ota image. Check on download state before waiting the kDelayedOnApply * Added remove provider kvs at teardown * Added clear_kvs for provider * Ruff check changes * Clear kvs provider * Revert file added * Added await_all_period_expected_report_matches to verify the attribute does not change in the period of time. * Implemented await_all_period_expected_report_matches into 2.5. Wait sofware update is not applied then verify if the software update was applied in the device. * cancel fix after merge from master * Fix ruff check for logging to log * Fix for ruff check at logging to log * Added try catch to avoid the CancelledError on await after cancel subscription. * Catching CancelledError * Revert 4997533dea1669484d502f919f4161fe4a6a649f and 4997533dea1669484d502f919f4161fe4a6a649f and add --timeout to test run. * Revert "Revert 4997533dea1669484d502f919f4161fe4a6a649f and 4997533dea1669484d502f919f4161fe4a6a649f and add --timeout to test run." This reverts commit 356e40fea801e294c019040e6919f0007367f57c. * Success message updated * Updated requestor_restart prompt * Updated timeoutto 0 * Addressing clear_kvs issues with /private/tmp * Removed sleep after cancel. Added default timeout and flag to add the timeout to this test as is required. Removed sleep at restart_app * Added app ready pattern, restored sleep in restart to avois possible connection issues. * Added manual step in cases we need devices to apply the software update by using UserPrompts * Update imports * Remove yaml test * fix imports * Change timeouts * Typo fix * Moved image download check to CI * Fix: Updated method name to wait_all_final_values_reported_persisted and removed wait for kApply on Step5, instead wait for DownloadComplete * fix: ruff changes * Revert "Remove yaml test" This reverts commit ad275f31753d2e17d8521a4b79ae28b816e7296e. * Restored yaml test for 2.7 --------- Co-authored-by: Restyled.io <commits@restyled.io> Co-authored-by: Ramiro Recchia <rrecchia@google.com>
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.
