Skip to content

v2.3.0-1.3-beta.1
Compare
Choose a tag to compare
@rerasool rerasool released this 18 Mar 20:15
v2.3.0-1.3-beta.1
2a78824

Silicon Labs Matter GitHub v2.3.0-1.3-beta.1

Releases notes may be truncated on GitHub. Full text can be found here: github.com/SiliconLabs/matter/releases/tag/v2.3.0-1.3-beta.1

Versions

These versions are automatically included in our Matter release, listed here for informational purposes only.

Features

This is the v2.3.0-1.3-beta.1 release of the Silicon Labs Matter GitHub repo. This release is intended for developers who wish to run a Matter Demo over Thread (15.4) or Wi-Fi, and also manually build examples on the command line and through VS Code.

  • To get started, read these release notes for features and known issues and follow the README for instructions on how to run demos and build examples.
  • For issues, log them on the issues tab of the repo.

Release Highlights

  • Matter 1.3 Beta1 solution for Thread (MG12, MG24), Wi-Fi NCP platforms (MG24/RS9116, MG24/WF200, MG24/SiWx917) and Wi-Fi SoC platform (SiWx917).
    • Provides incremental bug fixes to support Matter 1.3 Test Event.
    • Provides alpha support for multi-OTA framework.
  • Works using Gecko SDK v4.4.1 and WiSeConnect SDK v3.1.3.2.
  • Provides targeted improvements in stability & sleep functionality for Wi-Fi SoC platform (SiWx917).
    • Added partial low-power 917 stability fixes. Some stability fixes are associated with increased power consumption.
      • Stability improvements have been added for both the TA and M4.
      • TA workaround with XTAL always enabled.
      • Tickless idle support feature has been enabled.
    • Added configuration to override M4 sleep mode:
      • By default, M4 is active and TA will be in sleep mode. This configuration provides high stability.
      • To enable both M4 and TA sleep modes, enable the flag si917_m4_sleep_enabled = true.
  • Adds Provision 2.0 support. Provision feature currently works on EFR32 only, there is a known issue with SiWx917 SoC and workaround is to use Provision 1.0.
    • New protocol support that can be used with different communication channels.
    • Provisioning and re-provisioning through BLE channel.
    • Backwards compatibility support to use v1.x provisioning protocol for older devices.
    • Support for well-known parameters. Due to this, some parameter identifier shortcuts were changed and some single letters were reused for script configuration options.

      • Changes

        Parameter Former flag New flag
        --pylink_lib -l -jl
        --vendor_id -v -vi
        --vendor_name -V -vn
        --product_id -p -pi
        --product_name -P -pn
        --unique_id -u -ui
        --discriminator -d -sd
        --part_number -pn -pm
        --key_id -ki -di
        --key_pass -kp -dp
        --common_name -cn -dn

      • New additions

        Parameter New flag
        --version -v
        --params -p
        --inputs -i
        --output -o
        --temp -t
        --device -d
        --channel -c
        --serial_number -sn
        --setup_payload -sy
        --firmware_info -fi
        --pkcs12 -dx
        --cd_cert -cc
        --cd_key -ck
        --paa_cert -ac
        --paa-key -ak
        --pai_key -ik

      • Removals

        Parameter Former flag Reason
        --config -c replaced by --inputs
        --jlink -j Reprovisioning now done by BLE
        --att_certs -xc replaced by --pkcs12

Issues fixed in this release

  • [SiWx917 SoC] Fixed OTA issues on 917 SoC where either the OTA transfer wouldn't start or after its completion, the device would not automatically - reboot (UID:1271781)
  • [SiWx917 SoC] Fixed an issue on the 917 SoC where the sleep wakeup would falsely trigger a button release event (UID:1257340)
  • [SiWx917 SoC] Use the RTC timer on the 917 SoC as sleep timer and enable tick-less idle (UID:1224024)
  • [Matter stack] Fixed an issue with UniqueID provisioning value encoding causing a failure to read the basic information unique id attribute (UID:1253986).
  • [Matter stack] Fixed an issue where some ICD app logic was not activated on the Sensor and OnOff plug apps leading to higher power consumption than expected (UID:1264649)
  • [Matter stack] Fixed the general diagnostic network-interface attribute which was not returning a valid hardware address and no IPV6 address list (UID:1264801)
  • Fixed an issue where the discovery timeout was not extended when the BLE extend announcement was enabled.

General

  • Documentation provided for running pre-compiled demos and for building examples manually, for example through the VS Code development environment.
    • Instructions are provided for building on Linux, Mac and Windows.
  • Reference guides are provided for various technical topics in the Table of Contents under Developer Reference.

Thread

In order to run Matter over Thread, a developer must have at least two Silicon Labs EFR-based devices and a Raspberry Pi with a >32 GB SD Card.

Thread support for the following boards:

  • MG24 boards:

    • BRD4186C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm
    • BRD2601B / MG24 Explorer Kit
    • BRD4316A / SLWSTK6006A / Wireless Start Kit / 2.4GHz@10dBm
    • BRD4317A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm
    • BRD4318A / SLWSTK6006A / MGM24 Module / 2.4GHz@10dBm
    • BRD4319A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm
    • BRD2703A / MG24 Explorer Kit
    • BRD2704A / SLWSTK6006A / MGM24 Module

  • MG12 boards:

    • EFR32MG12 Development Kit
    • BRD4161A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm
    • BRD4162A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4163A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm
    • BRD4164A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm
    • BRD4166A / SLTB004A / Thunderboard Sense 2 / 2.4GHz@10dBm
    • BRD4170A / SLWSTK6000B / Multiband Wireless Starter Kit / 2.4GHz@19dBm, 915MHz@19dBm
    • BRD4304A / SLWSTK6000B / MGM12P Module / 2.4GHz@17dBm 

Thread support for the following applications:

  • Light
  • Light Switch
  • Lock
  • Window Covering
  • Thermostat
  • On/Off plug
  • Sensor
  • Dishwasher

Wi-Fi

In order to run Matter over Wi-Fi, a developer must have below hardware:

  • Silicon Labs Wireless starter/development kit (WSTK)
  • Silicon Labs Wi-Fi development Kits & boards
    • For SoC variants, SiWx917 SoC Common flash boards (refer to the board details below).
    • For Network Co-Processor (NCP) variants,
      • Silicon Labs EFR32 - is used as a host processor and, with the WF200, provides Bluetooth LE capabilities
      • Silicon Labs Wi-Fi Processor
        • RS9116 development kit
        • WF200 expansion board
        • SiWx917 NCP expansion board
  • Raspberry Pi with a >32 GB SD Card

Wi-Fi support for the following boards:

  • MG24 boards:
    • BRD4186C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm -
  • Wi-Fi Dev Kit
    • RS9116
    • SiWx917
      • NCP mode:
        • SiWx917-EB4346A
      • SoC mode
    • WF200
      • WF200 / Single Band Wi-Fi Expansion Board / 2.4GHz
      • WFM200S / Single Band Wi-Fi Expansion Board / 2.4GHz
    • Interconnect board (included in the Wi-Fi kits)
    • SPI Cable (included in the RS9116 kit)
    • Jumper Cables (included in the RS9116 kit)

Wi-Fi support for the following standard applications:

  • Light
  • Lock
  • Light Switch
    • Note: This App is supported for SiWx917 SoC device combination only.
  • Window Covering
  • On/Off plug
  • Thermostat
    • Note: This App is supported for SiWx917 SoC device combination but with alpha quality.
  • Dishwasher
  • Sensor

Wi-Fi Sleepy End Device (SED) support for the following applications:

  • Lock
    • With chip-tool
    • With EFR32xG24 with RS9116, WF200, SiWx917 NCP, SiWx917 SoC
  • Window Covering
    • With chip-tool 
    • With EFR32xG24 with RS9116, WF200, SiWx917 NCP, SiWx917 SoC
  • Thermostat
    • With chip-tool
    • With EFR32xG24 with RS9116, WF200, SiWx917 NCP
  • Light Switch
    • With chip-tool
    • With SiWx917 SoC

Reference guide to enable the sleepy functionality for Wi-Fi: Wi-Fi Sleepy End devices.

Changes in this release:

  • Adds Matter support for new WiSeConnect 3.1.3.2 SDK on SiWx917 SoC & NCP boards.
  • Adds support for ICD functionality improvements on SiWx917 SoC.

Note: Firmware for RS9116, SiWx917 NCP & SiWx917 SoC can be found in the Matter Software Artifacts page within the documentation or Assets section of the release notes.

Supported:

  • Matter Demos (pre-built binary images) on the SiWx917 Common Flash device.
  • Networks with up to 12 devices including up to 6 IoT devices, and a single EFR-9116 or EFR-WF200 or EFR-SiWx917 NCP mode device combination.
  • OTA functionality on SiWx917 SoC.
  • LCD functionality on SiWx917 SoC & NCP devices.
  • ICD functionality on SiWx917 SoC & NCP devices.
  • WPA3 functionality on SiWx917 SoC & NCP devices.

Not supported in this release:

  • SiWx917 SoC features
    • PSA crypto
    • Key wrapping
    • Flash locking
  • SiWx917 SoC 1.6 MB Common flash board variants - BRD4338A are no longer supported.
    • Note: Please contact Silicon Labs to convert 1.6MB to 1.8MB mode.
  • External Flash on EFR32xG24 with RS9116 or SiWx917 (planned in a future release).
  • OTA Updates with Internal Flash on EFR32xG24 with WF200.
  • Changing the WLAN connection region at runtime on RS9116 and WF200.
  • Connection to APs using Enterprise security modes (only Personal WPAx security modes are supported).

Unify

Unify Matter Bridge

In order to expose Zigbee and Z-Wave devices to a Matter fabric with the Unify Matter Bridge, you need to set up the Unify ecosystem with a Raspberry Pi 4, Z-Wave, and a Zigbee protocol controller. A more detailed guide on setting up this ecosystem can be found in the Unify documentation.

The Unify Matter Bridge supports bridging the following clusters for Z-Wave/Zigbee devices:
  • Bridge Device Information
  • Level
  • OnOff
  • Identify
  • Group
  • Color Control
  • Occupancy Sensing
  • Temperature Measurement
  • Illuminance Measurement   
  • Pressure Measurement     
  • Flow Measurement      
  • RelativeHumidity Measurement
  • Thermostat
Controlling the Z-Wave/Zigbee devices is supported with the following Matter controllers:
  • Chip-tool
  • Google Home

Matter Protocol Controller

The Unify Matter Protocol Controller enables Matter capable thread devices on a Matter fabric accessible on a Unify network. Currently, this is an alpha release with limited support to only the OnOff cluster.

Ecosystems

This release has been tested for commissioning and control with the following Ecosystems on the hardware and software versions listed below:

Google

  • Silicon Labs Device:
    • Thread: BRD4187C EFR32MG24
      • App: lighting-app
    • Wi-Fi: SiWx917 SoC
      • App: lock-app
  • Google Hub:
    • Thread
      • Hardware: Google Nest Hub
    • Wi-Fi
      • Hardware: GUIK2
      • Software: Hub Software Version: Chromcast 3.71.396338
  • Phone
    • Thread
      • Hardware: iPhone 13
      • Software: 17.4
    • Wi-Fi
      • Hardware: OPPO Reno CPH1919
      • Software: Android version 12
  • App Software:
    • Thread
      • Google Home version: 3.12.1.6
    • Wi-Fi
      • Google Home version: 3.13.1.4
  • Wi-Fi Access Point:
    • ASUS XT8 (Thread/Wi-Fi)

Apple

  • Silicon Labs Device:
    • Thread: BRD4186C EFR32MG24
      • App: lighting-app
    • Wi-Fi: SiWx917 SoC
      • App: lock-app
  • Apple Hub:
    • Thread
      • Hardware: Apple Home Pod Mini (Model A23472)
      • Software: 16.5.1
    • Wi-Fi
      • Hardware: Apple Home Pod Mini (Model A2374)
      • Software: 17.4
  • Phone:
    • Thread
      • Hardware: iPhone 13
      • Software: 17.4
    • Wi-Fi
      • Hardware: iPhone SE
      • Software: 17.4
  • App Software:
    • Apple Home version: 17.4
  • Wi-Fi Access Point:
    • ASUS XT8 (Thread/Wi-Fi)

Samsung

  • Silicon Labs Device:
    • Thread: BRD4186C EFR32MG24
      • App: lighting-app
    • Wi-Fi: SiWx917 SoC
      • App: lock-app
  • Samsung Hub:
    • Hardware: Smart Things Station
    • Thread: Software: 1.8.12.21
    • Wi-Fi: Software: 2.3.29-7
  • Phone:
    • Thread
      • Hardware: iPhone 13
      • Software: 17.4
    • Wi-Fi
      • Hardware: Pixel 5a
  • App Software:
    • SST 1.8.12.21
  • Wi-Fi Access Point:
    • ASUS XT8 (Thread/Wi-Fi)

Amazon

  • Silicon Labs Device:
    • Thread: BRD4187C EFR32MG24
      • App: lighting-app
    • Wi-Fi: SiWx917 SoC
      • App: lock-app
  • Amazon Hub:
    • Thread
      • Hardware(model): Amazon Echo 4
      • Device Software version: 9698487172
    • Wi-Fi
      • Hardware(model): Amazon Echo 4
      • Device Software version: 0010101200772
  • Phone:
    • Thread
      • Hardware: iPhone 13
      • Software: 17.4
    • Wi-Fi
      • Hardware: Pixel 5a
  • Wi-Fi Access Point:
    • ASUS XT8 (Thread/Wi-Fi)

Known Issues

General

  • After you sync your development repo to this latest release you may run into build errors such as a ZAP version validation:
    • Checking ZAP from ['zap-cli']: !!! Version validation failed: required at least 2023.4.27, got 2023.4.5 instead
    • This error indicates that your build environment needs to be updated. To do this run bootstrap via the following command: $source ./scripts/bootstrap.sh
  • The Amazon Ecosystem requires additional advertising functionality in the device. The Demo images included in this release DO NOT include this functionality. In order to work with the Amazon Ecosystem a developer must build their device image from scratch including the following arguments: chip_enable_additional_data_advertising=true chip_enable_rotating_device_id=true An example of a build line would be:
    • ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32 out/lighting-app-additional_advertising BRD4186C chip_enable_additional_data_advertising=true chip_enable_rotating_device_id=true"
  • The Matter device images require approximately 700k in flash space. As a result only a subset of EFR32MG12 and EFR32MG2x devices are supported. For a complete list of devices supported consult the Hardware Requirements page in the documentation.
  • Matter SDK Issues (https://github.com/project-chip/connectedhomeip)
    • BLE Connection/Timeout error occurs occasionally during commissioning with the chip-tool running on Raspberry Pi or Linux (project-chip#16178). Running on these platforms requires an access point with both 2.4GHz and 5GHz capabilities. There is BLE-Wi-Fi interference when connected over the 2.4 GHz channel. This is resolved by connecting the chip-tool device to a 5 GHz SSID and the end device to a 2.4 GHz SSID for the same Wi-Fi network.
  • Timeout can sometimes happen during operationalSessionStatus.
  • Get incorrect state error sometimes while commission another fabric.
  • Ecosystems: Unable to control the sleepy enabled Lock App device with Google
  • Missing of mandatory attributes of the Network commissioning cluster. SupportedThreadFeatures and ThreadVersion or SupportedWiFiBands shall be enabled in the application's zap config matching the product network technology (Thread or WiFi)

Thread

  • Silicon Labs has provided a complete image file for the Raspberry Pi that can be flashed onto an SD card to create the "Matter Hub", which is a Raspberry Pi running Ubuntu and including a pre-built version of the Open Thread Border Router (OTBR) and chip-tool. The image we have provided is quite large, ~4 GB. As a result it can take quite a while to download the .zip file and flash it onto an SD card. Depending on your connection the process could take up to half an hour. Regardless, the demo and development experiences using this pre-built image is a much faster process than building the Matter Hub from scratch.
  • Self provisioning through RTT with MGM24x modules unavailable.

Wi-Fi

  • Issues observed on SiWx917 SoC:
    • Provision feature does not work on SiWx917 SoC currently. Provision 1.0 can still be used with SiWx917 SoC by reverting commit eae4864844.
    • Unable to commission with certain APs/hotspots.
    • Provision 2.0 is not supported at time of release on SiWx917 SoC.
    • Although improvements seen over previous release, sleepy apps are yet to be stabilized.
    • OTA Upgrade with LCD/M4 sleep enabled (Sleepy Apps), soft reset does not work. Manual reboot is required post upgrade.
    • NVM (discriminator) got erased after factory reset the device 2 or 3 times.
    • The device got lost within 10-15 minutes after commissioning on sending the unicast commands every 5 seconds on the non-sleepy app.
    • Randomly observing "Timeout issues" and "resource busy" while sending commands
    • Window covering app instability and issues with open/close.
    • Intermittent commissioning failure with step 29 as DUT fails to give response for sigma 1 after connecting to the network.
    • Matter shell on SiWx917 SoC will only work when pins 4 & 6 are connected with USB to UART converter.
    • Ecosystems: Unable to Commission the DUT with Lock App when sleepy is enabled with Amazon
    • Commission second fabric after CW duration is done on lock-app.
  • This release is not validated on the following SiWx917 SoC boards.
    • BRD4325B
    • BRD4325C
    • BRD4325G
  • Issues observed on SiWx917 NCP:
    • Although improvements seen over previous release, sleepy apps are yet to be stabilized.
    • Ensure to short R100 pin on SiWx917 NCP board to resolve BlueZ errors shown-up during commissioning.
    • "Cancelling incomplete address resolution as device is being deleted" is observed when trying to send any unicast command.
  • EFR32xG24 with WF200 device combination fail to commission sleepy Lock app
  • Matter coverage was done on WPA3 & WPA2 APs, observed interoperability issues with one specific AP.
  • Sometimes Hard fault error is observed on RS9116 EVK with light/Thermostat/Window apps.
    • Workaround: In order to reset the RS9116 EVK device properly when LCD is enabled, press the reset button until the Silabs logo appears back on the LCD.
  • If the user modifies the discriminator in CHIProjectconfig.h, the modified discriminator is not updated in QR code.
  • RSI Send failure sometimes occurs within 1 hour of commissioning with the RS9116 EVK with Apple/Google Home. To recover from this issue, try one of the following:
    • Reboot the device and wait for 5-10 minutes, or
    • Erase the flash, re-flash the application and repeat commissioning.
  • OTA Update: sometimes bootloading with latest image does not work with WF200 & EFR32xG24 device combination. This issue is resolved by applying the workaround described in the Wi-Fi FAQ.
  • Commissioning fails with an "out of memory" error when an OpenThread device in the same network was added using an Apple HomePod Mini.
  • Commissioning step 18 failure occurs occasionally:
    • This has been seen to occur more frequently with one specific access point – MI Router 4C
    • When this issue occurs, try the following steps to run commissioning successfully:
      • Delete all files in your chip-tool's /tmp folder
      • Factory reset your access point
  • TriggerEffect command in Identify cluster does not work on EFR32xG24 with RS9116/WF200.
  • Group commands do not work for some specific access points.
  • When Setting up the Ozone Debugger on Mac the location of the JLinkDevices.xml file has moved, Follow this documentation in order to place it in the proper location.

Unify

Unify Matter Bridge
  • Unify Matter Bridge does not do clean shutdown, occasionally the application hangs when shutting down.
  • For OnOff cluster, on a Z-Wave-based Unify bridged endpoint the OnWithTimedOff command does not function as specified in combination with other OnOff commands.
  • For OnOff cluster, on a Z-Wave-based Unify bridged endpoint the OffWaitTime attribute for calculation is incorrect if OffWithEffect/Off command is sent after OnWithTimedOff command.
  • Attribute read of the ColorControl Attributes: Options and EnhancedColorMode fails with some Zigbee devices.
  • Chip Test Suite TC-DGSW-2_03 fails intermittently since CurrentHeapUsed value is greater than CurrentHeapHighWatermark.
Unify Matter Protocol Controller
  • LT feature specific attributes and commands for OnOff cluster are not handled.
  • Recommissioning of UMPC with new node ID fails.
Assets 12