| commit | 30391ddeeb83f49cfc89f43fdb3186f0fa25545d | [log] [tgz] |
|---|---|---|
| author | Jake Ororke <jororke@csa-iot.org> | Thu Apr 24 11:26:49 2025 -0700 |
| committer | GitHub <noreply@github.com> | Thu Apr 24 18:26:49 2025 +0000 |
| tree | 906eecbf072b0e03dddd768f34e8dc7a77d39f55 | |
| parent | bc7f2a425b322079f0a2a5281e73dd9574714bf1 [diff] |
Creating ACL 2 4 python3 test module (#38314) * Modifying how ACL Attribute is written: making it use a non-empty initial ReplaceAll list * removing Test modifications on ACL Extensions * adding reference to issue in TODO comment * integrating comments * integrating comments * Revert "removing Test modifications on ACL Extensions" This reverts commit 055af80d6c71e40ddeef081b6046263bc06ef141. * Testing removing one of the template functions * WriteClient: Encoding as many items as possible into a single list as part of ReplaceAll item operation * fixing failures * Fix to Error Handling in User-Label Cluster: return RESOURCE_EXHAUSTED when the number of items in list exceeds kMaxUserLabelListLength * chip-repl: support for preencoded attributes * Fixing ACL 2.3 and 2.5 * Validating ACLs Upfront: This is done to make sure we reject the whole list if any of the entries within it are non conforming * more yaml test changes * Restyled by prettier-yaml * Fix Unit Testing Cluster (Test Cluster Server) to process ReplaceAll operations * fix PutPreencodedAttribute * Cleaning code * More Code Clean Up * Unit Test Cleanup * more cleanup * Adding testcases to TestAccessControlCluster * Fixing comments * Making IsValid method in AccessControl Static * Adding comments * Make IsValid a member function of AccessControl::Entry * Adding WriteClient class member mIsWriteRequestChunked * making TestWriteChunkig more Robust * Adding ACL_2_4 python3 test module: - Adding python3 ACL_2_4 test module - This uses base branch of Amine's PR #38263 to create this test module: This is a follow-up PR to that PR from Amine, once Amine's PR is merged this one can come out of WIP state. * Restyled by autopep8 * Updating TC_ACL_2_4 python3 test module: - Changing expect clause for test step 29 * Updating TC_ACL_2_4: - Resolving linting errors * Apply commit suggestions from code review from Amine Updating to include commit suggestions to test steps and comments from @Alami-Amine. These suggestions made the code cleaner and more readable, thank you! Co-authored-by: Amine Alami <43780877+Alami-Amine@users.noreply.github.com> * Updating TC_ACL_2_4 python3 test module to resolve commits from Amine, making the code cleaner and better: - Updating to change type of ID from "fabric-scoped node ID" with correct type "invalid Group Node ID" - Updating test step 4 description to be more detailed. * Restyled by autopep8 * Update src/python_testing/TC_ACL_2_4.py Changing hex values for CAT1-CAT4 in test step 21 as suggested by Amine who gathered these from the test spec Co-authored-by: Amine Alami <43780877+Alami-Amine@users.noreply.github.com> * Updating TC_ACL_2_4 python3 test module: - Replacing duplicate CAT4 value in test step 21 and replaced it with value from Amine that did not replicate CAT3's value * Updating TC_ACL_2_4 test module: - Updating to match test steps in test plan PR: https://github.com/CHIP-Specifications/chip-test-plans/pull/5052 * Pulling in files from upstream master to make sure that everything is in sync * Updating TC_ACL_2_4 python3 test module: - Removing try except blocks - Replacing self.print_step() with logging.info() * Restyled by autopep8 * Updated TC_ACL_2_4 python3 test module: - Added new test step method to step 29 - Updated test steps after test step 29 include the test step ordering - Updated test 29 and 30 to include the correct verbiage for the definitions and expected results * Updated TC_ACL_2_4 test module: - Actually updated TC_ACL_2_4 python3 test module to correct expected results verbiage for test steps 32-44 * Restyled by autopep8 * Update src/python_testing/TC_ACL_2_4.py Co-authored-by: Amine Alami <43780877+Alami-Amine@users.noreply.github.com> * Removing Test_TC_ACL_2_4.yaml script * Updating TC_ACL_2_4 python3 test module: - Replaced enumerate blocks with asserts.assert_in() checks to verify that structs are read correctly throughout the test - Removed some unneeded comments in the test module * Restyled by autopep8 * Updating TC_ACL_2_4 python3 test module: - Added in validation of admin entry only to end of test steps 32-44 - Removed duplicate validation of admin entry only in test step 31 --------- Co-authored-by: Alami-Amine <aalami90@gmail.com> Co-authored-by: Restyled.io <commits@restyled.io> Co-authored-by: Amine Alami <43780877+Alami-Amine@users.noreply.github.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.