Modified yaml scripts Jan 09 (#31312)

* modified files as per latest test-plan.
PICS.yaml
TC_ACE_1_1
TC_ACE_1_5
TC_ACFREMON_1_1
TC_ACFREMON_2_1
TC_ACL_2_1
TC_ACL_2_10
TC_ACL_2_3
TC_ACL_2_9
TC_AIRQUAL_1_1
TC_AIRQUAL_2_1
TC_ALOGIN_1_12
TC_APBSC_1_10
TC_APBSC_9_1
TC_APPLAUNCHER_1_3
TC_APPLAUNCHER_3_5
TC_APPLAUNCHER_3_7
TC_APPLAUNCHER_3_8
TC_APPLAUNCHER_3_9
TC_AUDIOOUTPUT_1_8
TC_AUDIOOUTPUT_7_1
TC_AUDIOOUTPUT_7_2
TC_BINFO_1_1
TC_BINFO_2_1
TC_BINFO_2_2
TC_BOOL_2_1
TC_BRBINFO_1_1
TC_BRBINFO_2_1
TC_CADMIN_1_10
TC_CADMIN_1_16
TC_CC_2_1
TC_CC_5_1
TC_CC_6_1
TC_CNET_1_3
TC_CNET_4_5
TC_CNET_4_9
TC_CONTENTLAUNCHER_1_11
TC_DD_1_8
TC_DD_3_1
TC_DD_3_2
TC_DGETH_2_1
TC_DGGEN_1_1
TC_DGGEN_2_1
TC_DGGEN_2_3
TC_DGTHREAD_1_1
TC_DGTHREAD_2_4
TC_DGWIFI_2_1
TC_DGWIFI_2_3
TC_DISHM_2_1
TC_DISHM_3_1
TC_DISHM_3_2
TC_DISHM_3_3
TC_DRLK_2_1
TC_DRLK_2_10
TC_DRLK_2_5
TC_DRLK_2_6
TC_DRLK_2_7
TC_DRLK_2_9
TC_FAN_1_1
TC_FAN_2_1
TC_FAN_2_2
TC_FAN_2_3
TC_FAN_2_4
TC_FAN_2_5
TC_FAN_3_1
TC_FAN_3_2
TC_FAN_3_6
TC_FLABEL_1_1
TC_FLABEL_2_1
TC_FLDCONC_1_1
TC_FLDCONC_2_1
TC_FLW_1_1
TC_FLW_2_1
TC_FLW_2_2
TC_GRPKEY_1_1
TC_GRPKEY_2_1
TC_GRPKEY_2_2
TC_G_1_1
TC_G_2_1
TC_G_2_3
TC_G_2_4
TC_HEPAFREMON_1_1
TC_HEPAFREMON_2_1
TC_ICDM_1_1
TC_IDM_1_1
TC_IDM_2_1
TC_IDM_2_2
TC_IDM_3_1
TC_IDM_3_2
TC_ILL_1_1
TC_ILL_2_1
TC_ILL_2_2
TC_I_1_1
TC_I_2_1
TC_I_2_2
TC_I_2_3
TC_KEYPADINPUT_1_2
TC_KEYPADINPUT_3_3
TC_LCFG_1_1
TC_LCFG_2_1
TC_LOWPOWER_1_1
TC_LOWPOWER_2_1
TC_LTIME_1_2
TC_LTIME_3_1
TC_LUNIT_1_2
TC_LUNIT_3_1
TC_LVL_1_1
TC_LVL_2_1
TC_LVL_2_2
TC_LVL_3_1
TC_LVL_4_1
TC_LVL_5_1
TC_LVL_6_1
TC_LVL_7_1
TC_LWM_1_1
TC_LWM_2_1
TC_LWM_3_1
TC_LWM_3_2
TC_LWM_3_3
TC_MEDIAINPUT_1_4
TC_MEDIAINPUT_3_10
TC_MEDIAINPUT_3_11
TC_MEDIAINPUT_3_12
TC_MEDIAINPUT_3_13
TC_MEDIAPLAYBACK_1_7
TC_MEDIAPLAYBACK_6_1
TC_MEDIAPLAYBACK_6_2
TC_MEDIAPLAYBACK_6_3
TC_MEDIAPLAYBACK_6_4
TC_MOD_1_1
TC_MOD_3_1
TC_MOD_3_2
TC_MOD_3_3
TC_MOD_3_4
TC_NDOCONC_1_1
TC_NDOCONC_2_1
TC_OCC_2_3
TC_OCC_3_1
TC_OO_1_1
TC_OO_2_1
TC_OO_2_2
TC_OO_2_3
TC_OO_2_4
TC_OPCREDS_1_2
TC_OPCREDS_3_7
TC_OPSTATE_1_1
TC_OZCONC_1_1
TC_OZCONC_2_1
TC_PRS_1_1
TC_PRS_2_1
TC_PRS_2_2
TC_PSCFG_1_1
TC_PS_1_1
TC_PS_2_1
TC_PS_2_2
TC_REFALM_1_1
TC_REFALM_2_3
TC_RH_1_1
TC_RH_2_1
TC_RH_2_2
TC_RNCONC_1_1
TC_RNCONC_2_1
TC_RVCCLEANM_1_1
TC_RVCCLEANM_3_1
TC_RVCCLEANM_3_3
TC_RVCOPSTATE_1_1
TC_RVCRUNM_1_1
TC_RVCRUNM_3_3
TC_SC_5_1
TC_SMOKECO_2_2
TC_SMOKECO_2_3
TC_SMOKECO_2_4
TC_SMOKECO_2_5
TC_S_1_1
TC_S_2_1
TC_S_2_2
TC_S_2_3
TC_S_2_4
TC_TCCM_1_1
TC_TCCM_3_1
TC_TCCM_3_2
TC_TCCM_3_3
TC_TGTNAV_1_9
TC_TGTNAV_8_1
TC_TIMESYNC_1_1
TC_TMP_1_1
TC_TMP_2_1
TC_TMP_2_2
TC_TSTAT_1_1
TC_TSTAT_2_2
TC_TSUIC_1_1
TC_TSUIC_2_1
TC_TSUIC_2_2
TC_TVOCCONC_1_1
TC_TVOCCONC_2_1
TC_ULABEL_1_1
TC_ULABEL_2_1
TC_ULABEL_2_2
TC_ULABEL_2_3
TC_ULABEL_2_4
TC_WAKEONLAN_1_5
TC_WAKEONLAN_4_1
TC_WASHERCTRL_1_1
TC_WASHERCTRL_2_1
TC_WASHERCTRL_2_2
TC_WNCV_1_1
TC_WNCV_2_1
TC_WNCV_2_2
TC_WNCV_2_3
TC_WNCV_2_4
TC_WNCV_2_5
TC_WNCV_3_1
TC_WNCV_3_2
TC_WNCV_3_3
TC_WNCV_3_4
TC_WNCV_3_5
TC_WNCV_4_1
TC_WNCV_4_2
TC_WNCV_4_3
TC_WNCV_4_4
TC_WNCV_4_5
modified:  ci-pics-values

* Auto generated files

* modifed FAN-2.1 file

* Restyled by whitespace

* Restyled by prettier-yaml

* Modified files:
TC_CNET_1_3.yaml
TC_DISHM_3_2.yaml
TC_PCC_2_1.yaml
TC_PCC_2_2.yaml
TC_PCC_2_3.yaml
TC_PCC_2_4.yaml
TC_TCCM_2_1.yaml
TC_TSTAT_2_1.yaml

* Revert back the PICS and functionality changes.

---------

Co-authored-by: Restyled.io <commits@restyled.io>
185 files changed
tree: c47cfd339bfafa69b1f84296591f2c24f4c8e496
  1. .devcontainer/
  2. .githooks/
  3. .github/
  4. .vscode/
  5. build/
  6. build_overrides/
  7. config/
  8. credentials/
  9. data_model/
  10. docs/
  11. examples/
  12. integrations/
  13. scripts/
  14. src/
  15. third_party/
  16. zzz_generated/
  17. .actrc
  18. .clang-format
  19. .clang-tidy
  20. .default-version.min
  21. .dir-locals.el
  22. .editorconfig
  23. .flake8
  24. .gitattributes
  25. .gitignore
  26. .gitmodules
  27. .gn
  28. .isort.cfg
  29. .mergify.yml
  30. .prettierrc.json
  31. .pullapprove.yml
  32. .restyled.yaml
  33. .shellcheck_tree
  34. .spellcheck.yml
  35. BUILD.gn
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. gn_build.sh
  39. kotlin-detect-config.yaml
  40. lgtm.yml
  41. LICENSE
  42. NOTICE
  43. README.md
  44. REVIEWERS.md
  45. SPECIFICATION_VERSION
README.md

Matter

Builds

Builds

Android Ameba ASR BouffaloLab Darwin TI CC26X2X7 TI CC32XX EFR32 ESP32 Infineon i.MX Linux K32W with SE051 Linux ARM Linux Standalone Linux Standalone Mbed OS MW320 nRF Connect SDK Open IoT SDK QPG STM32 Telink Tizen

Tests

Unit / Integration Tests Cirque QEMU

Tools

ZAP Templates

Documentation

Documentation Build

About

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.

What is Matter?

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.

Project Overview

Development Goals

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.

Architecture Overview

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: Matter Architecture Overview

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:

Matter Stack Architecture

  1. Application: High-order business logic of a device. For example, an application that is focused on lighting might contain logic to handle turning on/off the bulb as well as its color characteristics.
  1. Data Model: The data layer corresponds to the data and verb elements that help support the functionality of the application. The Application operates on these data structures when there is an intent to interact with the device.
  1. Interaction Model: The Interaction Model layer defines a set of interactions that can be performed between a client and server device. For example, reading or writing attributes on a server device would correspond to application behavior on the device. These interactions operate on the elements defined at the data model layer.
  1. Action Framing: Once an action is constructed using the Interaction Model, it is serialized into a prescribed packed binary format to encode for network transmission.
  1. 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.

  2. 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.

  1. IP Framing & Transport Management: After the final payload has been constructed, it is sent to the underlying transport protocol for IP management of the data.

Current Status of Matter

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.

How to Contribute

We welcome your contributions to Matter. Read our contribution guidelines here.

Building and Developing in Matter

Instructions about how to build Matter can be found here .

Directory Structure

The Matter repository is structured as follows:

File/FolderContent
buildBuild system support content and built output directories
build_overridesBuild system parameter customization for different platforms
configProject configurations
credentialsDevelopment and test credentials
docsDocumentation, including guides. Visit the Matter SDK documentation page to read it.
examplesExample firmware applications that demonstrate use of Matter
integrations3rd party integrations
scriptsScripts needed to work with the Matter repository
srcImplementation of Matter
third_party3rd party code used by Matter
zzz_generatedZAP generated template code - Revolving around cluster information
BUILD.gnBuild file for the GN build system
CODE_OF_CONDUCT.mdCode of conduct for Matter and contribution to it
CONTRIBUTING.mdGuidelines for contributing to Matter
LICENSEMatter license file
REVIEWERS.mdPR reviewers
gn_build.shBuild script for specific projects such as Android, EFR32, etc.
README.mdThis file

License

Matter is released under the Apache 2.0 license.