Merge main into doccurator 2.8.0 20260310 (#54)

* enable CLA

* use pull_request

* use pull_request_target

* Add info on the 2.2.2 release

* update cluster.md to correct Cluster header file link

* Matter App Cluster Logic Addition

* Apps feedback

* More edits

* Addressing Apps feedback

* Apply suggestions from code review

Co-authored-by: silabs-vm <vimorrow@silabs.com>

* Link the Code Savings Guide

* Mention the doccurator branches

* Mention the doccurator branches in the PR template

* Update CONTRIBUTING.md

Fixed typo

* Update CONTRIBUTING.md

fixed typo

* Rename ZclCallbacks.cpp to DataModelCallbacks.cpp

* Adding the note for the 917SoC matter cli

* Update sld248-matter-overview-guides/serial-port-communications.md

Co-authored-by: silabs-vm <vimorrow@silabs.com>

* RS9116 deprecation documentation

* Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Revert "use pull_request_target"

This reverts commit c660e1e.

* Revert "use pull_request"

This reverts commit 5286c81.

* Revert "enable CLA"

This reverts commit 74cd27f.

* Apply copilot suggestions

* MATTER AWS Documentation

* Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: silabs-vm <vimorrow@silabs.com>

* Add the new features for the 2.7.0 Release

* Update version strings to 2.7.0

* Updates to New Features

* Updating the MatterHub link to use the 2.6.0 version

* Add missing image in Matter AWS documentation

* use shared cla action (#42)

---------

Co-authored-by: Sarthak Shaha <sarthak.shaha@silabs.com>
Co-authored-by: Sergei Lissianoi <selissia@silabs.com>
Co-authored-by: silabs-akosj <146345861+silabs-akosj@users.noreply.github.com>
Co-authored-by: davargas <daniel.vargas@silabs.com>
Co-authored-by: silabs-danielV <108473947+silabs-danielV@users.noreply.github.com>
Co-authored-by: chirag-silabs <chirag.bansal@silabs.com>
Co-authored-by: chirag-silabs <100861685+chirag-silabs@users.noreply.github.com>
Co-authored-by: Satya Naag Bollimpalli <sabollim@silabs.com>
Co-authored-by: arun-silabs <141724790+arun-silabs@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Arun Padakanti <arunkumar.padakanti@silabs.com>
Co-authored-by: Michael Duggan <miduggan@silabs.com>
Co-authored-by: Nga Nguyen <nga.nguyen@silabs.com>

Author: 11 people

.github/workflows/01-CLA-Assistant.yml

@@ -16,30 +16,7 @@ permissions:
 
 jobs:
   CLAAssistant:
-    runs-on: ubuntu-24.04
-    steps:
-      - name: Create CLA Assistant Lite bot token
-        uses: actions/create-github-app-token@v2
-        id: app-token
-        with:
-          app-id: ${{ secrets.GH_APP_ID }}
-          private-key: ${{ secrets.GH_APP_PRIVATE_KEY }}
-          owner: SiliconLabsInternal
-          repositories: contributor-license-agreements
-
-      - name: "CLA Assistant"
-        if: ${{ contains(github.event.comment.body, 'I have read the CLA Document and I hereby sign the CLA') }} || github.event_name == 'pull_request_target'
-        uses: SiliconLabsSoftware/action-cla-assistant@silabs_flavour_v2
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          PERSONAL_ACCESS_TOKEN: ${{ steps.app-token.outputs.token }}
-        with:
-          path-to-signatures: "cla_signatures_db.json"
-          path-to-document: "https://github.com/SiliconLabsSoftware/agreements-and-guidelines/blob/main/contributor_license_agreement.md"
-          branch: 'cla-database'
-          allowlist: silabs-*,bot*
-          # the following are the optional inputs - If the optional inputs are not given, then default values will be taken
-          remote-organization-name: "SiliconLabsInternal"
-          remote-repository-name: "contributor-license-agreements"
-          create-file-commit-message: "Created the CLA database file. CLA Assistant Lite bot created this file."
-          signed-commit-message: "$contributorName has signed the CLA in $owner/$repo#$pullRequestNo"
+    uses: SiliconLabsSoftware/matter_build_action/.github/workflows/cla.yml@main
+    secrets:
+      CLA_APP_ID: ${{ secrets.SILABSIN_CLA_BOT_APP_ID }}
+      CLA_APP_PRIVATE_KEY: ${{ secrets.SILABSIN_CLA_BOT_APP_PRIVATE_KEY }}

sld291-matter-wifi-run-demo/flashing-using-commander.md

@@ -10,6 +10,8 @@ Before flashing the application for EFR32 Boards, flash **bootloader images** as
 - **BRD4187C Board**
   - For MG24 + WF200: External Bootloader (bootloader-storage-spiflash-single-1024k-BRD4187C-gsdk4.1)
 
+**Note**: RS9116 is deprecated and no longer supported on Matter.
+
 Bootloader binaries are available in the respective path of codebase **third_party/silabs/matter_support/matter/efr32/bootloader_binaries** folder. Silicon Labs recommends always flashing the latest bootloader binaries from the codebase.
 
 **Note**: Bootloader binaries are flashed using Simplicity Commander only. It supports EFR32 Boards only.

sld297-matter-aws-feature/aws-configuration-registration.md

@@ -0,0 +1,43 @@
+# Amazon Web Services (AWS)
+
+Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services. Refer to [AWS Documentation](https://aws.amazon.com/what-is-aws/) for more details.
+
+## AWS CA Certificate Registration
+
+1. Open [AWS](https://aws.amazon.com/).
+2. Log in using your AWS credentials.
+
+3. Go to **Security > Policies** and select **Create Policy**. Enter the policy name (e.g., `MATTER_AWS_POLICY_`). In the policy statements, select **JSON** and replace the contents with the JSON provided below:
+
+    ```shell
+     {
+       "Version": "2012-10-17",
+       "Statement": [
+        {
+          "Effect": "Allow",
+          "Action": "*",
+          "Resource": "*"
+        }
+      ]
+     }
+    ```
+
+4. Once done, select **Create**.
+
+5. Create a client CSR certificate and a client key by following the steps in the [OpenSSL Certificate Creation](./openssl-certificate-creation.md) documentation.
+
+6. Complete the following steps to create a thing and generate certificates for your Matter application to use in the `MatterAwsNvmCert.cpp` source file:
+
+    - Go to **All Devices > Things** and select **Create Things**.
+    - Select **Create Single Thing** and click **Next**.
+    - Under **Info > Give the thing a name**, specify the thing name (this will be the client ID), then click **Next**.
+    - (Optional) Configure the device certificate under  **Info > Upload CSR**.
+    - In **Certificate > Choose file** (Choose Client CSR generated in Openssl Certificate Creation ex: `device.csr`). Click **Next**. 
+    - Use the policy (e.g., `MATTER_AWS_POLICY_`) created in AWS Certificate creation.
+    - Once the thing is successfully created, activate and download the certificate.
+
+8. Copy the contents of [AWS_CA CERT](https://www.amazontrust.com/repository/AmazonRootCA3.pem) and add it as CA certificate in `MatterAwsNvmCert.cpp`. 
+
+9. Repeat Step 5 to create a new thing for use in MQTT Explorer, using the certificate generated for MQTT Explorer during OpenSLL certificate creation (e.g., `explorer.csr`). Create a `.pem` file from the CA certificate in step 8 and use it as the server certificate in MQTT Explorer.
+
+    **Note**: The thing name must be unique as it will be used as the client ID.

sld297-matter-aws-feature/build-matter-aws.md

@@ -0,0 +1,72 @@
+# Build Procedure For Matter + AWS
+
+The following components are common for all apps and should be modified in the corresponding application-specific `.slcp` file.
+
+## How to Add the Matter + AWS Component
+
+To add the Matter + AWS component, modify the corresponding application-specific `.slcp` file.
+
+```shell
+  - id: matter_aws
+    from: matter
+```
+To enable the component in Simplicity Studio, add the following components.
+
+- Go to **Software** components, search for `Matter_Wifi`. Click on **Settings** symbol beside Matter Wi-fi component in the left panel and enable IPV4 configuration.
+    ![IPV4 Component](images/matter_aws_ipv4_enable_1.png)
+    ![IPV4 Settings Enable](images/matter_aws_ipv4_enable_2.png)
+
+- In **Software Components**, search for `aws` and install the Matter AWS component.
+
+- Next, select the dependencies for the Matter AWS component.
+ ![Default Entropy Source for Matter + AWS](images/matter_aws_dependency_1.png)
+ ![Public-Key Abstaction Layer for Matter + AWS](images/matter_aws_dependency_2.png)
+
+## How to Add the Matter + AWS Server, Client, Cluster Details.
+
+- Update the definitions for the server ID, client ID and cluster in `MatterAwsConfig.h`:    
+    - Update the AWS server name at `#define MATTER_AWS_SERVER_HOST ""`.
+    - Update the client ID at `#define MATTER_AWS_CLIENT_ID ""`.
+    - Update the cluster information at `#define ZCL_USING_THERMOSTAT_CLUSTER_SERVER`.
+
+
+## Building Matter + AWS Application
+
+- After you finish modifying the **.slcp** project file as described above, refresh the `matter-extension` in Simplicity Studio.
+
+-  On the **Launcher** tab, select **Preferences**.
+
+ ![Select Preferences](images/select-preferences.png)
+
+- Expand the **Simplicity Studio** section, and click the **SDKs** tab.
+
+ ![Select SDK](images/select-studio-sdk-option.png)
+
+- Expand **Simplicity SDK**, and click **Refresh** in the side menu.
+
+ ![Select Refresh](images/select-refresh-option.png)
+
+- Build the Matter + AWS application using Simplicity Studio as described in
+  - [Build SOC Application Using Studio](/matter/{build-docspace-version}/matter-wifi-run-demo/build-soc-application-using-studio).
+
+## Compile using new/different certificates
+
+-   Two devices should not use the same client ID. Use a different client ID for
+    your second connection.
+-   While using AWS, update the following information:
+    -   Add your AWS certificates in file
+        `examples/platform/silabs/matter_aws/matter_aws_interface/include/MatterAwsNvmCert.h`
+        -   Provide the AWS Root CA key
+            (https://www.amazontrust.com/repository/AmazonRootCA3.pem)
+        -   Provide `device_certificate` and `device_key` with your device certificate and
+            device key. For more details, refer to
+            [OpenSSL Device Certificate Creation] (./openssl-certificate-creation.md)
+    -   Add your AWS server and client ID information to the
+        `examples/platform/silabs/matter_aws/matter_aws_interface/include/MatterAwsConfig.h` file.
+        -   Provide `MATTER_AWS_SERVER_HOST` with your AWS Server name.
+        -   Provide `MATTER_AWS_CLIENT_ID` with your device/thing ID.
+        -   Provide  `ZCL_USING_THERMOSTAT_CLUSTER_SERVER` with the cluster details.
+-   The preferred certificate type to use in the application is ECDSA.
+-   AWS RootCA used in this PoC is
+    https://www.amazontrust.com/repository/AmazonRootCA3.pem
+