Skip to content

v2.0.0-1.1
Compare
Choose a tag to compare
@rerasool rerasool released this 18 May 16:11
v2.0.0-1.1
a108d1e

Silicon Labs Matter GitHub v2.0.0-1.1

Releases notes may be truncated on GitHub. Full text can be found here: github.com/SiliconLabs/matter/releases/tag/v2.0.0-1.1

Versions

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

Features

This is the v2.0.0-1.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.

Highlights of this release

  • Quality-tested Matter 1.1 GA solution for Thread (MG12, MG24), and Wi-Fi NCP platforms (MG24/RS9116, MG24/WF200, MG24/SiWx917) and Wi-Fi SoC platform (SiWx917).
  • Proven to work for both Thread and Wi-Fi in the Google and Apple ecosystems (see the Ecosystem section below).
  • An outline of new features included in this release is provided in the New Features section of the documentation.
  • Adds Wi-Fi Direct internet connectivity support for all standard applications.
  • Adds Wi-Fi Sleepy End Devices (SED) support for selected applications (see the 'Wi-Fi support for the following standard applications' section below).  
  • Adds support for Matter Shell, device rebooting on the SiWx917 SoC Dual Flash Device.  
  • Adds support for Commander tool v1.14.5 flashing image (.s37, .rps) on the SiWx917 SoC
  • Adds Unify Matter Bridge with full support for Lighting Devices and Sensors.
  • The release binary of the Unify Matter Bridge is now a 64-bit ARM binary compiled for Debian Bullseye.
  • Adds support for Matter Custom Part Manufacturing Service (CPMS).
  • Improved sleepy performance.

Issues fixed in this release

  • Simplicity Commander generation of .gbl files for Matter apps fails, preventing app signing and secure boot. There is a workaround for v1.1.0-1.1, but Silicon Labs recommends updating to v2.0.0-1.1. (UID: 1113978)
  • Due to an issue in Thread building, Matter apps with is_debug=false could not commission on MG24. Incorporating the certified OpenThread library with --use_ot_lib option was a workaround in SMG v1.1.0-1.1, corrected in SMGv2.0.0-1.1. (UID: 1129676) 

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 Reference Guides.

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
    • BRD4319A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm
    • BRD2703A / MG24 Explorer Kit

  • 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

Thread support for the following applications:

  • Light
  • Light-switch
  • Lock
  • Window Covering
  • Thermostat
  • On/Off plug
  • Sensor

Wi-Fi

In order to run Matter over Wi-Fi, a developer must have an SiWx917 Dual Flash SoC Device. For Network Co-Processor (NCP) variants, a developer must have either a Silabs RS9116 development kit, WF200 expansion board or SiWx917 expansion board; and a Silabs EFR32 development kit (WSTK) - the EFR32 is used as a host processor and, with the WF200, provides Bluetooth LE capabilities.

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 -
  • MG12 boards:
  • Wi-Fi Dev Kits:
    • RS9116
    • SiWx917
      • NCP mode:
        • BRD8036A / Expansion Board / 2.4GHz
      • SoC mode
        • BRD4325B with Dual Flash / Dual Flash Radio Board / 2.4GHz
    • 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
    • With chip-tool, Google Nest and Apple HomePod Mini controllers
    • With all device combinations
  • Lock
    • With chip-tool, Google Nest and Apple HomePod Mini controllers
    • With all device combinations
  • Light Switch 
  • Window Covering
    • With chip-tool and Apple HomePod Mini controllers
    • With all device combinations
  • On/Off plug
  • Thermostat
    • With chip-tool, Google Nest and Apple HomePod Mini controllers
    • With all NCP Mode device combinations (SiWx917 SoC not supported)

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

  • Lock
    • With chip-tool
    • With EFR32xG24 with RS9116, WF200 and SiWx917 
  • Window Covering
    • With chip-tool 
    • With EFR32xG24 with RS9116, WF200 and SiWx917 
  • Thermostat
    • With chip-tool
    • With EFR32xG24 with RS9116, WF200 and SiWx917

Wi-Fi support for the following device combinations:

  • SoC mode:
    • SiWx917
  • NCP mode:
    • EFR32xG24 + SiWx917
      • BLE is configurable to run either from the EFR32xG24 or SiWx917, with the build flag.  
    • EFR32xG24 + RS9116
      • BLE is configurable to run either from the EFR32xG24 or RS9116, with the build flag 
    • EFR32xG24 + WF200
    • EFR32MG12 + RS9116
    • EFR32MG12 + WF200 - Supported with Matter 1.0 - https://github.com/siliconlabs/matter/tree/release_1.0.2-1.0

Changes in this release:

  • GA Release of Matter 1.1 Standard Apps (see the supported apps and combinations above).
  • Added Wi-Fi Direct internet connectivity support for all the standard apps (see the supported apps and combinations above).
  • Added Wi-Fi Sleepy End Devices (SED) support for selected apps (See the supported apps above).
  • Enabled Matter Shell, Device rebooting, and Commander flashing support on the SiWx917 SoC Dual Flash Device.

Note: SiWx917 firmware is only available to Alpha customers. Contact Silicon Labs support to obtain the WiseMCU SDK A.1.0.0.0.23. and install it as per the instructions in the Software Requirements page in the documentation.

Supported:

  • Commander tool v1.14.5 support for flashing image (.s37, .rps) on the SiWx917 SoC 
  • Matter Demos (pre-built binary images) on the SiWx917 Dual Flash SoC Device (included with the WiseMCU SDK obtained from Silicon Labs support as per the Software Requirements page)
  • Networks with up to 12 devices including up to 6 IoT devices, and a single EFR-9116 or EFR-WF200 or EFR-917 NCP mode device combination
  • WPA and WPA2 AP connection security modes by default
  • WPA3 support may be enabled by adding the build parameter --rs91x_wpa3_only
  • Enabling WPA3 during build will disable support for WPA and WPA2
  • Certificate Injection for Matter Device Attestation Credentials for EFR32xG24

Not supported in this release:

  • LCD on EFR32xG24 with RS9116 or SiWx917 NCP and SiWx917 SoC (planned in a future release).
  • External Flash on EFR32xG24 with RS9116 or SiWx917 (planned in a future release).
  • OTA Updates with External Flash on EFR32xG24 with RS9116 or SiWx917 (planned in a future release).
  • Switching between WPA/WPA2 and WPA3 security types on RS9116 or SiWx917 at runtime (planned in a future release). To switch the security type from either Open/WPA/WPA2 to WPA3, RS9116 or SiWx917 NCP Matter Application (for MG12 or MG24) should be built with the build parameter to enable the WPA3-only mode: --rs91x_wpa3_only.
  • OTA Updates with Internal Flash on EFR32xG24 with WF200.
  • Debugging of WF200 firmware with the EFR32xG24 (planned in a future release).
  • 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).
  • Connection to APs from WF200 using WPA3 security mode.
  • OTA Updates on SiWx917 SoC.
  • Certification injection on SiWx917 SoC.
  • Matter 1.1 Apps are not supported on MG12+WF200 device combination (planned in future release).

Unify

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

Controlling the Z-Wave/Zigbee devices is supported with the following Matter controllers:

  • Chip-tool
  • Google Home

Ecosystems

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

Google

  • Silabs Device:
    • Wi-Fi: BRD4325B, SiWx917 SoC, lighting-app
    • Thread: BRD4186C, EFR32MG24, lighting-app
  • Google Hub:
    • Hardware: Google Nest Hub Gen 2
    • Software: Hub Software Version: 1.56.324896
  • Phone
    • Hardware: Pixel 5a
    • Software: Android version 12 
  • App Software:
    • Google Home version: 3.1.18.1-dogfood
  • Wi-Fi Access Point:
    • Eero AP

Apple

  • Silabs Device:
    • Wi-Fi: BRD4325B, SiWx917 SoC, lighting-app
    • Thread: BRD4186C, EFR32MG24, lighting-app
  • Apple Hub:
    • Hardware: Apple Home Pod Mini
    • Software: 16.4.1
  • Phone:
    • Hardware: iPhone 12 mini
    • Software: 16.4.1
  • App Software:
    • Apple Home version: 16.4.1
  • Wi-Fi Access Point:
    • Eero AP

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 documentation located within this repo at ./docs/silabs/
  • Sending 10+ chip-tool commands may result in “Invalid CASE Parameters” error. Fixed by resetting the device.
  • Window app: Current position tilt and configuration status are out of range.
  • 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.

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.

Wi-Fi

  • The Ozone Debugger may not immediately run the Matter application on the SiWx917 SoC Device. The application runs on resetting the device.
  • When Setting up the Ozone Debugger on Mac the location of the JLinkDevices.xml file has moved, Follow this documentation (https://wiki.segger.com/J-Link_Device_Support_Kit#JLinkDevices_folder) in order to place it in the proper location.
  • OTA Update Bootloading sometimes does not work with WF200 with EFR32xG24. This issue is resolved by applying the workaround described in the Wi-Fi FAQ.
  • 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.
  • 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 one specific access point: ASUS RT-AX88U.
  • Simplicity Commander does not erase the complete flash of SiWx917.
  • Google ecosystem sends a timeout in multi admin long run test.
  • Sometimes the Wi-Fi DUT disconnects from the network in ecosystems testing with Google Home in the long runs. 

Unify

  • The Attribute Illuminance Measurement Type is not parsed correctly from the MQTT Side.
  • 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.
  • For Identify Cluster, failure in writing to identify-time attribute to endpoint 1 of Unify Matter Bridge.
  • Attribute read of the ColorControl Attributes: Options and EnhancedColorMode fails with some Zigbee devices.
Assets 9
Loading