Merge pull request #32 from SiliconLabsSoftware/merge-2.7.0-into-main

Merge doccurator/2.7.0 into main

Author: silabs-vm

.github/CONTRIBUTING.md

@@ -18,7 +18,7 @@ As a contributor, you'll want to be familiar with the Silicon Labs tooling:
 
 Read the Silicon Labs [coding guidelines](https://github.com/SiliconLabsSoftware/agreements-and-guidelines/blob/main/coding_standard.md).  
 ## Git Setup
-We need to know who you are, and how to contact you. Please ass the following information to your Git installation:
+We need to know who you are, and how to contact you. Please add the following information to your Git installation:
 ```
 git config --global user.name "FirstName LastName"
 git config --global user.email "[email protected]"
@@ -92,7 +92,7 @@ Please follow the official GitHub [guide](https://opensource.guide/how-to-contri
 When you created an issue and based on the discussion you want to contribute with your source-code.
 Branching is disabled on the public Silicon Labs repositories. You need to fork your own repo first.
 Please follow the official GitHub [guide](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project).
-You can create your branch on your own forked repo now.
+You can create your branch on your own forked repo now. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to (for example, `doccurator/2.6.2`.
 
 ### Branch Naming Convention
 Branch naming shall follow the following template: *IssueNumber-issue-title-goes-here*  
@@ -115,7 +115,7 @@ Another line of really good description
 ```
 
 ## Pull Request Guideline
-Okay you finished your work committed all your changes to your branch. Time to create a pull request.  
+Okay you finished your work committed all your changes to your branch. Time to create a pull request. Pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to (for example, `doccurator/2.6.2`). 
 Refer to the general pull request [guideline](https://opensource.guide/how-to-contribute/#opening-a-pull-request) from GitHub.  
 What to consider when raising a Pull Request:  
 1. **Pull Request Naming**  

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,5 +1,6 @@
 ## Description
 <!-- Provide a brief description of the changes in this pull request. -->
+<!-- Note that the pull requests must be merged into the doccurator branches corresponding to the Matter release the change applies to, for example doccurator/2.6.2 . -->
 
 ## Related Issue
 <!-- If this pull request addresses an issue, link to it here. -->

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

@@ -1,33 +1,32 @@
-name: CLA validation
+name: 01-CLA-Assistant
+## This workflow is used for public repositories
 
 on:
-  issue_comment:
-    types: [created]
-  pull_request_target:
-    types: [opened, synchronize, reopened]
+  workflow_dispatch:
+ #issue_comment:
+ #  types: [created]
+ #pull_request_target:
+ #  types: [opened,closed,synchronize,reopened]
 
 permissions:
   actions: write
-  contents: read 
+  contents: read # this can be 'read' if the signatures are in remote repository
   pull-requests: write
   statuses: write
 
 jobs:
   CLAAssistant:
-    runs-on: ubuntu-latest
+    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.SILABSIN_CLA_BOT_APP_ID }}
-          private-key: ${{ secrets.SILABSIN_CLA_BOT_APP_PRIVATE_KEY }}
+          app-id: ${{ secrets.GH_APP_ID }}
+          private-key: ${{ secrets.GH_APP_PRIVATE_KEY }}
           owner: SiliconLabsInternal
           repositories: contributor-license-agreements
 
-      - name: Mask generated token
-        run: echo "::add-mask::${{ steps.app-token.outputs.token }}"
-
       - 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
@@ -43,4 +42,4 @@ jobs:
           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"
+          signed-commit-message: "$contributorName has signed the CLA in $owner/$repo#$pullRequestNo"

sld120-matter-wifi-getting-started/04-light-switch-step-by-step-example.md

@@ -40,7 +40,7 @@ Matter hub/chip-tool are ready and working. Keep the PuTTY session open for the
 
    4. Open the Example Projects and Demos tab, select the **Matter** filter and enter "_Wi-Fi_" in **Filter on keywords**.
 
-   5. Select the _Matter - SoC Lighting over Wi-Fi_ example for RS9116, click **Create**, rename the project if you wish, and click **Finish**.
+   5. Select the _Matter - SoC Lighting over Wi-Fi_ example for SiWx917, click **Create**, rename the project if you wish, and click **Finish**.
 
    6. Once the project is created, the perspective changes to the Simplicity IDE perspective. In the Project Explorer view, right-click the project and select _Build Project_.
 

sld246-matter-faq/wifi-faq.md

@@ -82,6 +82,8 @@ Where `mySSID` is **your AP's SSID** and `mypassword` is **your AP's password**.
 
 ### 3. WLAN connection fails from RS9116 during commissioning when channel 13 is selected on the AP
 
+**Note:** RS9116 is deprecated and no longer supported on Matter.
+
 The required channel becomes available for connection when the WLAN connection region is configured during compilation to one that supports the channel, such as for Japan for channel 13.
 
 In order to use the desired channel, before building, make sure the WLAN connection region is configured correctly by reviewing/modifying the following lines in **/examples/platform/silabs/efr32/rs911x/rsi_wlan_config.h**:
@@ -168,6 +170,8 @@ Disable QR Code and enable CHIP Logging:
 
 ### 11. MG24 device sometimes loses its connection to Ozone during OTA Update with RS9116
 
+**Note:** RS9116 is deprecated and no longer supported on Matter.
+
 While performing an OTA Update with the EFR32MG24 + RS9116 device combination, when the device is reset and bootloading begins with the new image, the Ozone Debugger sometimes loses its connection.
 
 There are two possible workarounds to this:

sld247-matter-overview/index.md

@@ -39,6 +39,7 @@ The following boards are supported for the Matter over Wi-Fi demos and developme
     - MG24 with WSTK: [xG24-PK6010A](https://www.silabs.com/development-tools/wireless/efr32xg24-pro-kit-20-dbm?tab=overview)
 - **Wi-Fi NCP Dev Kits & boards**
   - **RS9116**
+    (**Note:** RS9116 is deprecated and no longer supported on Matter.)
     - SB-EVK1 / Single Band Wi-Fi Development Kit / 2.4GHz
       - [RS9116X-SB-EVK1](https://www.silabs.com/development-tools/wireless/wi-fi/rs9116x-sb-evk-development-kit)
     - SB-EVK2 / Single Band Wi-Fi Development Kit / 2.4GHz

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

@@ -120,3 +120,5 @@ To run matter shell on the Silicon Labs Platform, refer to the [Software Require
       ./chip-tool doorlock read-event door-lock-alarm "node_id" "endpoint"
 
   **Note**: Type **help** in matterCli terminal for more information about supported features.
+
+  **Note**: For 917SoC ICD-enabled devices, only five UULP pins are supported. As a result, the Matter shell is not functional with sleepy applications because they are not mapped to UULP pins. To enable the Matter shell for sleepy 917SoC devices, the P37 pin must be pulled up. Additionally, boards BRD2708A, BRD2911A, and BRD4343A have only three UULP GPIO pins, which prevents the shell from functioning. To enable the shell on these boards, users must repurpose existing UULP GPIO pins.

sld249-matter-prerequisites/matter-artifacts.md

@@ -4,7 +4,7 @@ This page provides links to pre-built software image "artifacts" that can be use
 
 Images for the items listed below are available under the "Assets" section at the bottom of this page:
 
-https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.1
+https://github.com/SiliconLabs/matter_extension/releases/tag/v2.7.0
 
 ## Matter Hub Raspberry Pi Image
 
@@ -16,25 +16,27 @@ https://www.silabs.com/documents/public/software/SilabsMatterPi_2.6.0-1.4-extens
 
 The Radio Co-Processor firmware is used to turn an EFR into an RCP that can be used with a Raspberry Pi to allow the Raspberry Pi's Open Thread Border Router to access the Thread network. Radio Co-Processor (RCP) images are available in the Assets section of this page:
 
-https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/ot-rcp-binaries-2.6.1-1.4.zip
+https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/ot-rcp-binaries-2.7.0-1.4.zip
 
 ## Matter Accessory Device Images
 
 The Matter Accessory Device Images are used to turn an EFR into a Matter device. These are pre-built binary images for the Matter Demo. Matter Accessory Device Images are located in the Assets section of this page:
 
-https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/matter-accessory-device-images_2.6.1-1.4.zip
+https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/matter-accessory-device-images_2.7.0-1.4.zip
 
 ## Matter Bootloader Binaries
 
 All Silicon Labs board supporting Matter require that a bootloader binary is flashed to the device along with the application image. Bootloader binaries for all of the Matter supported devices are available here:
 
-https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/bootloader_binaries_matter_extension_v2.6.1-1.4.zip
+https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/bootloader_binaries_matter_extension_v2.7.0-1.4.zip
 
 ## RS9116 Firmware
 
+**Note**: RS9116 is deprecated and no longer supported on Matter.
+
 The RS9116 firmware (`rs9116_firmware_files_with_rev.zip`) is used to update the RS9116 which can be found in the Assets section of this page:
 
-https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/rs9116_firmware_files_with_rev_2.6.1-1.4.zip
+https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/rs9116_firmware_files_with_rev_2.7.0-1.4.zip
 
 **Note**:
 RS9116 chip/module needs to be flashed with proper firmware as mentioned below:
@@ -46,7 +48,7 @@ RS9116 chip/module needs to be flashed with proper firmware as mentioned below:
 
 The SiWx917 firmware(SiWx917_firmware_files.zip) is used to update the SiWN917 NCP and SiWG917 SOC which can be found in the Assets section of this page:
 
-https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/SiWx917_firmware_files_2.6.1-1.4.zip
+https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/SiWx917_firmware_files_2.7.0-1.4.zip
 
 **Note**:
 
@@ -64,12 +66,12 @@ https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/SiWx917
 
 The SiWx917 RCP folder (siwx917_rcp_files.zip) contains the Matter Linux all-cluster-app, which can be run on a Raspberry Pi, and the wfx-sdio-overlay.dts file, a Device Tree Source file used to configure the SDIO interface on the Raspberry Pi to detect and communicate with the SiWx917 RCP.
 
-https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/siwx917_rcp_files.zip
+https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/siwx917_rcp_files.zip
 
 ## SiWx917 SoC Configuration Files For JLink RTT Logging
 
 To check device logs on JLink RTT for the Matter Application on the SiWx917 SoC, the **JLink RTT** must be configured for the SiWx917 SoC device by following the instructions on the [JLink RTT SOC Support](/matter/{build-docspace-version}/matter-wifi-enabling-features/jlink-soc-setup) for SiWx917 SoC.
 
-The [JLinkDevices.xml](https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/JLinkDevices.xml.zip) and [RS9117_SF_4MB_42bsp.elf](https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/RS9117_SF_4MB_42bsp.elf.zip) files referenced in the instructions may be found in the Assets section of this page.
+The [JLinkDevices.xml](https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/JLinkDevices.xml.zip) and [RS9117_SF_4MB_42bsp.elf](https://github.com/SiliconLabs/matter_extension/releases/download/v2.7.0/RS9117_SF_4MB_42bsp.elf.zip) files referenced in the instructions may be found in the Assets section of this page.
 
 >**Note**: For EFR32MG2x devices, JLink RTT Logging support is already enabled.

sld249-matter-prerequisites/software-requirements.md

@@ -36,10 +36,14 @@ Below are the software tools both optional and required for developing Matter ov
 
 2. [WiSeConnect SDK v2.x for RS9116 NCP](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation#installation-of-wiseconnect-sdk-v2x-or-v3x-extension), which can be installed as part of the Simplicity Studio tool installation.
 
+   **Note:** RS9116 is deprecated and no longer supported on Matter.
+
 3. [WiSeConnect SDK v3.x for SiWx917 NCP](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation#installation-of-wiseconnect-sdk-v2x-or-v3x-extension), which can be installed as part of the Simplicity Studio tool installation.
 
 4. [Firmware for RS9116 NCP](./matter-artifacts.md#rs9116-firmware)
 
+   **Note:** RS9116 is deprecated and no longer supported on Matter.
+
 5. [Firmware for SiWx917 NCP](./matter-artifacts.md#siwx917-firmware-for-siwn917-ncp-and-siwg917-soc)
 
 ## Software Packages Required for Wi-Fi SiWx917 SoC Devices

sld250-matter-references/versioning-release-maintenance.md

@@ -62,13 +62,15 @@ Update digits based on the following criteria:
 |  v2.1.0-1.1  |  27-July-23    | v4.3.1                         | v3.0.10  | 1.1 | Obsolete   |
 |  v2.1.1-1.1  |  9-Oct-23      | v4.3.2, v4.3.3                 | v3.1.0   | 1.1 | Monitored |
 |  v2.2.0-1.2  |  13-Dec-23     | v4.4.0, v4.4.1                 | v3.1.1   | 1.2 | Obsolete   |
-|  v2.2.1-1.2  |  10-Apr-24     | v4.4.1, v4.4.2                 | v3.1.4   | 1.2 | Maintained |
+|  v2.2.1-1.2  |  10-Apr-24     | v4.4.1, v4.4.2                 | v3.1.4   | 1.2 | Obsolete |
+|  v2.2.2-1.2  |  7-May-24      | v4.4.3                         | v3.2.0   | 1.2 | Maintained |
 |  v2.3.0-1.3  |  18-June-24    | 2024.6.0                       | v3.3.0   | 1.3 | Obsolete |
 |  v2.3.1-1.3  |  14-August-24  | 2024.6.1                       | v3.3.1   | 1.3 | Obsolete |
 |  v2.3.2-1.3  |  10-Oct-24     | 2024.6.2                       | v3.3.2   | 1.3 | Maintained     |
 |  v2.4.0-1.4  |  11-Nov-24     | 2024.6.2                       | v3.3.4   | 1.4 | Maintained     |
 |  v2.5.0-1.4  |  18-Dec-24     | 2024.12.0                      | v3.4.0   | 1.4 | Obsolete     |
 |  v2.5.1-1.4  |  12-Feb-25     | 2024.12.1                      | v3.4.1   | 1.4 | Obsolete     |
 |  v2.5.2-1.4  |  10-Apr-25     | 2024.12.2                      | v3.4.2   | 1.4 | Maintained     |
-|  v2.6.0-1.4  |  18-Jun-25     | 2025.6.0                       | v3.5.0   | 1.4 | Maintained     |
-|  v2.6.1-1.4  |  23-Jul-25     | 2025.6.1                       | v3.5.1   | 1.4 | Active     |
+|  v2.6.0-1.4  |  18-Jun-25     | 2025.6.0                       | v3.5.0   | 1.4 | Obsolete     |
+|  v2.6.1-1.4  |  23-Jul-25     | 2025.6.1                       | v3.5.1   | 1.4 | Maintained     |
+|  v2.7.0-1.4  |  25-Sep-25     | 2025.6.2                       | v3.5.1   | 1.4 | Active     |