Skip to content

v0.3.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@rerasool rerasool released this 08 Sep 21:03
v0.3.0
90648b1

Silicon Labs Matter GitHub v0.3.0

Releases notes may be truncated on GitHub. Full text can be found here: github.com/SiliconLabs/matter/releases/tag/v0.3.0

Versions

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

Features

This is the v0.3.0 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 through VS Code.

This release is currently not certifiable. We will provide certifiable solution in a future release. For now, please reach out to your FAE or go to the public CSA release for certifications.

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

Highlights of this release

  • Support added for Wi-Fi for the MG24 + WF200 hardware combination
  • Lock and Lighting examples added for existing Wi-Fi hardware combinations where it was missing (MG12/24 + RS9116/WF200)
  • Thermostat example added for Thread and all existing Wi-Fi hardware combinations (MG12/24 + RS9116/WF200)
  • BRD2703A, BRD2601B support added for Thread examples
  • Matter Device Attestation Credentials support added (except for MG12+Wi-Fi)
  • Precompiled demos available in Simplicity Studio through Matter Enablement Package
  • Documentation updated to include sections on using Simplicity Studio tools with Matter

General

  • Documentation provided for running pre-compiled demos and for building examples manually, for example, through VS Code development environment
    • Instructions are provided for building on Linux, Mac and Windows
  • Reference guides added for the following:
    • Building a Custom Matter Device using ZAP
    • Matter OTA Software Update
    • Matter Attestation Credentials for EFR32
    • Using Simplicity Studio's Pin Tool and Project Configurator with Matter
    • Using Simplicity Studio's BLE GATT Configurator with Matter
    • Using Simplicity Studio's Energy Profiler with Matter
    • Using Wireshark to Capture Network Traffic in Matter

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:

  • 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

  • MG24 boards:

    • BRD4186C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm
    • BRD2601B / MG24 Explorer Kit
    • BRD2703A / MG24 Explorer Kit

Thread support for the following applications:

  • Light
  • Light-switch
  • Lock
  • Window
  • Thermostat

Wi-Fi

In order to run Matter over Wi-Fi, a developer must have either a Silabs RS9116 or WF200 development kit and a Silabs EFR development kit (WSTK) with a single EFR32. This is because the EFR32 is used as a host processor and for its BLE capabilities.

Wi-Fi support for the following boards:

  • MG12 boards:

  • MG24 boards:

    • BRD4186C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm -

  • Wi-Fi Dev Kit

    • RS9116
    • WF200
    • 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 applications:

  • Light
  • Lock
  • Thermostat

Wi-Fi support for the following device combinations:

  • EFR32xG24 + RS9116
  • EFR32xG24 + WF200
  • EFR32MG12 + RS9116
  • EFR32MG12 + WF200

Changes in this release:

  • Added support for Door Lock and Thermostat Apps for EFR32MG24 + RS9116 device combination
  • Added support for Lighting, Door Lock and Thermostat Apps for EFR32xG24 + WF200 device combination
  • Added support for Door Lock and Thermostat Apps for EFR32MG12 + RS9116 device combination
  • Added support for Lighting and Thermostat Apps for EFR32xG12 + WF200 device combination
  • Added support for Certificate Injection for Matter Device Attestation Credentials for EFR32xG24
  • Multi-Fabric support beyond 2 controllers on EFR32MG12 and EFR32xG24
  • Fixed the following Known Issues from the Release Notes of the v0.2.0 Release:
    • In IoT networks or networks with more than 12 devices, failure to establish a CASE session occurs from WF200 during commissioning due to high network traffic.
    • WLAN connection fails from WF200 in rare instances with an "access point not found" error. Commissioning should succeed on re-running.

Supported:

  • Networks with up to 12 devices including up to 6 IoT devices, and a single EFR-9116 or EFR-WF200 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

Not supported in this release:

  • Certificate Injection for Matter Device Attestation Credentials for EFR32MG12 (planned in a future release)
  • Connection to AP's that have disabled IPv6 (planned in a future release)
  • LCD Display on EFR32xG24 with RS9116 or WF200 (planned in a future release)
  • External Flash on EFR32xG24 + RS9116 (planned in a future release)
  • OTA Updates on EFR32xG24 with RS9116 or WF200 (planned in a future release)
  • Wi-Fi Diagnostics cluster on WF200 with EFR32MG12 or EFR32xG24 (planned in a future release)
  • Switching between WPA/WPA2 and WPA3 security types on RS9116 at runtime (planned in a future release). To switch the security type from either WPA or WPA2 to WPA3 and vice versa, RS9116 Lighting App (for MG12 or MG24) will need to be re-built with/without the build parameter enabling the WPA3-only mode: --rs91x_wpa3_only
  • Group commands in Thermostat App
  • Debugging of WF200 firmware with the EFR32xG24
  • OTA Updates with internal flash for WF200 with EFR32MG12 or EFR32xG24
  • Changing the WLAN connection region at runtime on RS9116 and WF200
  • Connection to AP's using Enterprise security modes (only Personal WPAx security modes are supported)
  • Connection to AP's from WF200 using WPA3 security mode

Known Issues

General

  • 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 please 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.

Thread

  • Silicon Labs has provided a complete image file for the RaspberryPi that can be flashed onto an SD card to create the "Matter Hub", which is a Raspberry Pi running Ubuntu and including a prebuilt version of the Open Thread Border Router (OTBR) and ChipTool. The image we have provided is quite large, ~4GB. 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 this whole 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

  • MG24 + WF200 commissioning does not work when compiled with isdebug=false
  • Address Resolve Error occurs occasionally during commissioning. Commissioning should work on attempting it again.
    • This has been seen to occur more frequently with one specific access point – MI Router 4C
  • WLAN connection may fail rarely from RS9116 with an “access point not found” error. Commissioning should work on attempting it again.
  • WFX Connection Timeout error may be seen rarely with WF200 with EFR32MG12 or EFR32xG24. Commissioning should work on attempting it again.
    • This has been seen to occur more frequently with one specific access point – ASUS 88U
  • Commissioning fails with an "out of memory" error when there is an OpenThread device in the same network 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.
  • Timeout error occurs after running the Thermostat App for 1 hour or more on the EFR32xG24 + RS9116 device combination.
  • Matter SDK Issues (https://github.com/project-chip/connectedhomeip)
    • Move to Level command fails when a Transition Time other than 0 is specified (project-chip#16332).
    • Unsupported Certificate Format error occurs occassionally during commissioning (project-chip#20996). Commissioning should work after deleting files from the /tmp folder on the CHIP tool device.
    • BLE Connection/Timeout error occurs occassionally 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-WiFi interference when connected over 2.4GHz channel, so this is resolved by connecting the CHIP tool device to a 5GHz SSID and the end device to a 2.4GHz SSID for the same Wi-Fi network.
Assets 5