| commit | ad7752d087b356cb8329f6502a8bd66bf57667a8 | [log] [tgz] |
|---|---|---|
| author | Tennessee Carmel-Veilleux <tennessee.carmelveilleux@gmail.com> | Thu Aug 21 17:37:55 2025 -0400 |
| committer | GitHub <noreply@github.com> | Thu Aug 21 21:37:55 2025 +0000 |
| tree | 309bb72bdbf4f1111f740e6a821490b57fba9cc8 | |
| parent | 4dd75066fa38d2855c2b38b4990df25e3ff04eee [diff] |
Add a new field to tracing for total message size (#40600) * Add a new field to tracing for total message size - Existing size logging was for payload at the exclusion of all headers. This means that it was not possible to get the full UDP/TCP payload size for messages which prevented measuring some overhead. - This PR adds trace logging of the payload size prior to consumption of any headers. - Output of that tracing is added only to the JSON sink as the other sinks do not give any of the internal details in the MessageReceived and MessageSend tracing (i.e. they don't care). - Fixed the docs/tests where needed. Testing done: - Validated with existing Python tests with `--trace-to json:log` that the new field is present, and larger, and did side-by-side compare with a `tcpdump packet capture`: Logging (`grep messageTotalSize`): ``` [MatterTest] 08-14 16:03:50.980 INFO "messageTotalSize" : 42, [MatterTest] 08-14 16:03:51.458 INFO "messageTotalSize" : 1207, [MatterTest] 08-14 16:03:51.523 INFO "messageTotalSize" : 42, [MatterTest] 08-14 16:03:52.038 INFO "messageTotalSize" : 1209, [MatterTest] 08-14 16:03:52.099 INFO "messageTotalSize" : 42, [MatterTest] 08-14 16:03:52.217 INFO "messageTotalSize" : 203, [MatterTest] 08-14 16:03:52.258 INFO "messageTotalSize" : 42, [MatterTest] 08-14 16:03:52.353 INFO "messageTotalSize" : 48, [MatterTest] 08-14 16:03:52.452 INFO "messageTotalSize" : 34, [MatterTest] 08-14 16:03:54.594 INFO "messageTotalSize" : 78, ``` packet capture recorded at same time, from `tshark`, including multicast. ``` $ tshark -r udp.pcap | grep Len 42 2025-08-14 20:03:50.983461 15.337208 fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 → fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb 40720 → 5540 Len=42 UDP 104 43 2025-08-14 20:03:51.450893 15.804640 fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb → fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 5540 → 40720 Len=1207 UDP 1269 44 2025-08-14 20:03:51.526845 15.880592 fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 → fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb 40720 → 5540 Len=42 UDP 104 45 2025-08-14 20:03:52.031937 16.385684 fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb → fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 5540 → 40720 Len=1209 UDP 1271 46 2025-08-14 20:03:52.102664 16.456411 fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 → fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb 40720 → 5540 Len=42 UDP 104 47 2025-08-14 20:03:52.212991 16.566738 fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb → fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 5540 → 40720 Len=203 UDP 265 48 2025-08-14 20:03:52.263048 16.616795 fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 → fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb 40720 → 5540 Len=42 UDP 104 49 2025-08-14 20:03:52.349836 16.703583 fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb → fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 5540 → 40720 Len=48 UDP 110 50 2025-08-14 20:03:52.596886 16.950633 fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 → fddc:d9f1:83b9:1:2a48:dd7d:12ba:f8bb 40720 → 5540 Len=34 UDP 96 51 2025-08-14 20:03:54.600395 18.954142 fdd2:a7fd:11ea:0:1691:82ff:fe3b:f646 → ff35:40:fd00::100:103 40720 → 5540 Len=78 UDP 140 ``` * Restyled by clang-format * Fix compile error on some platforms * Update src/transport/tests/TestCryptoContext.cpp * Update test to remove change detector * Fix some crypto const-ness and duplicate constants * Restyled by clang-format --------- 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.
