Skip to content

v0.4.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@rerasool rerasool released this 13 Oct 15:52
v0.4.0
e4771af

Silicon Labs Matter GitHub v0.4.0

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

Versions

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

Features

This is the v0.4.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, contact 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

  • Wi-Fi support has been added for the MG24 + SiWx917 NCP hardware combination
  • xGM240x BRD4316A, BRD4317A, BRD4319A support has been added for Thread examples
  • On/Off plug example has been added
  • Unify Matter Bridge (Alpha) has been added
  • Precompiled demos have been added for Simplicity Studio through Matter Enablement Package

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 provided 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
    • Matter EFR32 Flash Savings Guide

Changes in this release:

  • Matter SDK issue fixed - Unsupported Certificate Format error during commissioning (project-chip#20996).

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
  • Thermostat
  • On/Off plug

Wi-Fi

In order to run Matter over Wi-Fi, a developer must have either a Silabs RS9116 or WF200 or SiWx917 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 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 Kit

    • RS9116
    • WF200
    • SiWx917
    • 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
  • On/Off plug

Wi-Fi support for the following device combinations:

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

Changes in this release:

  • Added support for the EFR32xG24 + SiWx917 NCP device combination in Light, Lock, Thermostat and On/Off Plug Apps
  • Added On/Off Plug App with support for all device combinations
  • Added support for Certificate Injection on EFR32MG12 + RS9116 device combination

Supported:

  • 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 with RS9116/SiWx917
  • Certificate Injection for Matter Device Attestation Credentials for EFR32MG12 with RS9116

Not supported in this release:

  • Certificate Injection for Matter Device Attestation Credentials with WF200 for EFR32MG12/EFR32xG24 (planned in a future release)
  • Connection to AP's that have disabled IPv6 (planned in a future release)
  • LCD Display on EFR32xG24 (planned in a future release)
  • External Flash on EFR32xG24 with RS9116 or SiWx917 (planned in a future release)
  • OTA Updates on EFR32xG24 (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 or SiWx917 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 (planned in a future release)
  • OTA Updates with internal flash with the WF200 (planned in a future release)
  • 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 AP's using Enterprise security modes (only Personal WPAx security modes are supported)
  • Connection to AP's from WF200 using WPA3 security mode

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
  • Identity
  • Group
  • Color Control
  • Temperature Measurement
  • Occupancy Sensing

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

  • Chip-tool

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 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 pre-built version of the Open Thread Border Router (OTBR) and chip-tool. 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 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

  • MG24 + WF200 commissioning does not work when compiled with isdebug=false
  • Address Resolve Error occurs occasionally during commissioning. Commissioning should work on the next attempt.
    • This has been seen to occur more frequently with one specific access point – MI Router 4C
  • WLAN connection may rarely fail from RS9116 with an “access point not found” error. Commissioning should work on the next attempt.
  • WFX Connection Timeout error may be rarely seen with WF200 with EFR32MG12 or EFR32xG24. Commissioning should work on the next attempt.
    • 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).
    • 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-WiFi interference when connected over the 2.4GHz channel. 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.

Unify

  • Endpoint 0 of the bridge shows support for the Identify cluster, but identify commands have no effects.
  • When using Google Home with the Unify Matter Bridge only commissioning works. All Unify nodes appear as offline after commissioning.
Assets 7
Loading