TC-SU-4.1 python test (#39980) * Initial commit.. * Initial commit with partial implementation. * Implemented Step 1, still not functional. * Implemented Steps from 2 to 4, partial functional. * Refactor: Implemented Steps from 1 to 2 functional, with TH3 added and commissioning. * Refactor: Implemented Steps from 1 to 4 working as expected. * Implemented Step 5. * Refactor: Implemented Step 5. * Refactor: Implemented partial Step 6. * Refactor: Implemented partial Step 4 debbuging for potential bug. * Debug: Investigate potential bug in step 4 impacting step 6. * Debug: Investigate potential bug in step 5 impacting step 6. * Refactor: Updated Step 4 based on bug 40294. * Updated Step 6 * Updated Step 7 * Updated Step 8 * Step 9 skipped per test plan refinement. * Fix: Restyle errors. * Fix: Restyle errors v2. * Fix: code-lints errors. * Fix: Restyle errors v3. * Fix: code-lints errors v2. * Fix: Corrected CI test arguments to use endpoint 0. * Fix: Updated CI test arguments. * docs: Added docstring. * docs: add comment explaining unused OTA cluster variable kept for future reference. * Fix: Use self.cluster_otar instead of direct reference. * Fix: Replace assert_equal with assert_true. * Fix: Updated CI arguments for app. * CI: Added OTA_REQUESTOR and OTA_PROVIDER to 'Generate an argument environment file' workflow to file 'test_env.yaml'. * CI: Added build step for chip-ota-requestor-app. * Fix: Refactor build step for linux-x64-ota-requestor to enable test run. * Clean branch: revert accidental merges; restore branch to correct state. * Fix: Address Ruff. * Fix: Updated test to be compatible with latest master. * Refactor: In Step 5 reuse create_acl_entry for TH4 with Admin + View permissions. * Refactor: - Updated CI test arguments to remove --nodeId, vendor and product ID, and port. - Removed unused imports and the write_acl() function; now using acl_entry for ACLs. - Reordered and restyled library calls for consistent style. * Refactor and test improvements: - Refactor steps 1, 3, and 5 to use set_default_ota_providers_list fn and improve logging. - Add explanatory note in step 6 regarding multiple providers and ConstraintError. - Update teardown_test to clear KVS after test. - Include OTA_REQUESTOR_APP environment variable in CI. * Update: Added clarifications in Step 7 feedback. * Update: Clean up test comments and logging,and address Copilot suggestions. * Update: Code-lints and restyled. * Update: Addressed and clarified Copilot comments, no functional changes to test logic. * Refactor based on feedback: - Refactor the Provider NodeIDs to use variables th2_node_id, th3_node_id, and th4_node_id for clarity and maintainability.. - Extract the FabricID for TH3 to a variable th2_fabric_id. * Update: Removed comments for clean-up. * Update: Include an assertion in Step 7 to check that UpdatePossible is True. * Refactor based on feedback to align with test plan and verification: - Use TH as the admin controller across the test - Refactor Step 5 to match test verification (no TH4 controller) - Update Step 6 to validate fabric when clearing DefaultOTAProviders - Update Steps 7 and 8 to read attributes via TH on Fabric 1 - Clarify comments to align with test expectations. * Update: Copilot comments suggestions. * Update: Step 5 now verifies DefaultOTAProviders on both fabrics after ConstraintError. * Solve comments for TC_SU_4_1 * Revert "Solve comments for TC_SU_4_1" This reverts commit 8e0d11525b07468684eaaa785cf5e4d671875331. * Solve comments for TC_SU_4_1 * restore third party * Fix imports * fix imports * Fix imports --------- Co-authored-by: Ramiro Recchia <rrecchia@google.com> Co-authored-by: C Freeman <cecille@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.
