| commit | fd72eae01f6dec6e3bd05996eedb985521069beb | [log] [tgz] |
|---|---|---|
| author | Vatsal Ghelani <152916324+vatsalghelani-csa@users.noreply.github.com> | Mon Apr 15 14:13:07 2024 -0400 |
| committer | GitHub <noreply@github.com> | Mon Apr 15 14:13:07 2024 -0400 |
| tree | fe18423a53a99e5b26b61fb79dbd2018a8077f43 | |
| parent | 03d2fa8f2b2f71aa7616f9fec96543ef4ce1595e [diff] |
Added scripts to get metadata (runner arguments) associated with the python_testing scripts for automating the process (#32752) * Create unit test to test metadata parser * Create test script metadata parser * Create test environment file * Added Copyright Code * Added Copyright code * Added copyright code * Added run arguments comment header * Created BUILD.gn for metadata parser * Added reference to the metadata parser BUILD.gn * Added TC_RR_1_1_Test.py for testing purpose * Reverted back the testing changes done to the original file * Updated TC_RR_1_1_Test.py with comments as it was * Update test_metadata.py to correct the location for TC_RR* test script * Updated BUILD.gn with the correct naming tests * Rename env.yaml to test_env.yaml as it is for testing only * Updated test_metadata.py with the corrected test env file * Updated and rename TC_RR_1_1_Test.py to simple_run_args.py Just keeping the runner arguments required for testing purpose and removing all the unwanted test script code for this current testing use case * Updated test_metadata.py to the new name reference of the testing file * Renamed test method to test_run_metadata_parser * Removed the unwanted print method * Removed handling for int/bool/hex args and trace args * Remove try-catch block * Replaced == to is for null comparsion * Removed argument validation method * Added the dataclass to be optional * Updated the test script to be a .txt file and changed the designed to be all run arguments in one line * Rename simple_run_args.py to simple_run_args.txt * Updated BUILD.gn * Rename scripts/tests/py/test_env.yaml to env_example.yaml * Rename env_example.yaml to scripts/tests/py/env_example.yaml * Updated path of the environment file * Change the test script file type * Updated metadata_parser reference * Rename env_example.yaml to env_test.yaml * Update environment file name * Created __init__.py file * Added reference for __init__.py in the source * Created pyproject.toml file * Created setup.py file * Created setup.cfg file * Changed the path of the folder where the scripts are located * Added print statement * Updated print statement * Added inputs to the BUILD.gn file * Updated paths for file references * Added test script path to the inputs * Added sources for the file not find error fix * Updated metadata.py changes as suggested in the PR comments review * Updated test script * Updated license comment * Removed from pathlib import Path * Added Print Statement * Removed the print debug line * Updated it to use relative path instead of absolute path * Changed copyright year and removed unwanted sources * Updated copyright year to be 2024 * Updated copyright year to be 2024 * Updated copyright year to be 2024 * Updated copyright year to be 2024 * Updated copyright year to be 2024 * Updated copyright year to be 2024 * Update comment Co-authored-by: Andrei Litvin <andy314@gmail.com> * Updated the class name to MetadataReader * Updated class name to MetadataReader * Removed optional on factoryreset * Renamed env_yaml_file_path and solved inline inside constructor * Update metadata.py * Update metadata.py * Delete scripts/tests/py/simple_run_args.txt * Update BUILD.gn * Updated test_metadata.py * Updated metadata.py * Create simple_run_args.txt * Update BUILD.gn * Delete scripts/tests/py/simple_run_args.txt * Update BUILD.gn * Updated test_metadata.py * Restyled by whitespace * Restyled by gn * Restyled by prettier-yaml * Restyled by autopep8 * Restyled by isort * Fixed the spell error * Fixed comments from the PR * Removed extra print line * Restyled by autopep8 * Test via comment space * Test via removed comment space * Test via comment space * Restyled by autopep8 * Fixed mypy erros and test script line readability fixes * Restyled by autopep8 * Removed unawanted variables * Removing unused Union * Restyled by autopep8 --------- Co-authored-by: Andrei Litvin <andy314@gmail.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.