Skip to content

v0.2.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@rerasool rerasool released this 18 Aug 00:43
v0.2.0
efb8612

Silicon Labs Matter GitHub v0.2.0

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

Versions

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

Features

This is the v0.2.0 release of the Silicon Labs Matter GitHub repo. This release is intended for developers who wish to run Matter pre-compiled demos 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 our examples
  • For issues, log it on the issues tab of the repo

General

  • In addition to the pre-compiled demo workflow, documentation has been added for setting up the VS Code development environment to manually build examples
    • In addition to Linux/Mac, support for building on Windows has been added (without the need for WSL and Docker)
  • Documentation has been added on using the Over the Air Bootloader (OTA) functionality 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:

  • MG24 boards:

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

Thread support for the following applications:

  • Light
  • Light-switch
  • Lock
  • Window

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:

Wi-Fi support for the following applications:

  • Light on EFR32MG24 + RS9116 device combination
  • Light on EFR32MG12 + RS9116 device combination
  • Lock on EFR32MG12 + WF200 device combination

Changes in this release:

  • Added support for Light App for EFR32MG24 + RS9116 device combination
  • Added support for Wi-Fi Diagnostics cluster for RS9116
  • Added support for connection to AP's running in access point (AP) / bridge mode
  • Added support for networks of up to 12 devices, having up to 6 IoT devices
  • Added support for WPA3 security type on RS9116 (requires re-building the image – see the “Not supported” section below).
  • Fixed the following Known Issues from the Release Notes of the v0.1.0 Release:
    • In IoT networks or networks with more than 12 devices, mDNS traffic causes an LwIP error - Failed to reply to query: 30000001 (out of memory).
    • 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.
    • In the Network Commissioning cluster for RS9116, the Scan Networks command fails on specifying an SSID to filter the results on.
    • WLAN connection fails from RS9116 during commissioning when channel 13 is selected on the AP.
      • The required channel becomes available for connection when the WLAN connection region is configured during compilation to one that supports the channel. For e.g. Japan for channel 13.
      • To configure this, edit the following lines under /third_party/silabs/matter_support/wifi/rs911x/rsi_wlan_config.h: 
        //Make sure this is set to RSI_ENABLE
#define RSI_SET_REGION_SUPPORT RSI_ENABLE
 
//! If 1:region configurations taken from user ;0:region configurations taken from beacon
// Make sure this is set to 1 to configure from RSI_REGION_CODE value below
#define RSI_SET_REGION_FROM_USER_OR_BEACON 1
 
//! 0-Default Region domain ,1-US, 2-EUROPE, 3-JAPAN
#define RSI_REGION_CODE 3

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
  • WPA3 is not supported by default on RS9116 but can 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:

  • LCD Display on MG24 + RS9116. Commissioning cannot currently be done using a QR Code (planned in a future release)
  • External Flash on MG24 + RS9116 (planned in a future release)
  • OTA Updates and Multi-Fabric support on MG24 + RS9116 (planned in a future release)
  • Multi-Fabric support beyond 2 controllers on MG12 (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
  • Changing the WLAN connection region at runtime on RS9116 and WF200
  • Wi-Fi Diagnostics cluster on WF200
  • Connection to AP's using Enterprise security modes (only Personal WPAx security modes are supported)
  • Connection to AP's that have disabled IPv6 (planned in a future release)
  • 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, ~5GB. 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 1 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

  • 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.
  • Commissioning fails with an "out of memory" error when there is an Apple Homepod Mini device in the same network.
  • WLAN connection fails from WF200 in rare instances with an "access point not found" error. Commissioning should succeed on re-running.
  • WLAN connection may fail rarely from RS9116 with an “access point not found” error. Commissioning should work on attempting it again.
  • Multi-Fabric commissioning does not work with more than 2 Fabrics.
  • Commissioning step 18 failure occurs occasionally. When this occurs, try the following steps to run commissioning successfully:
    • Delete all files in your CHIP tool's /tmp folder
    • Factory Reset your access point
  • 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
Loading