Skip to content

v1.1.0-1.1
Compare
Choose a tag to compare
@rerasool rerasool released this 24 Feb 22:03
v1.1.0-1.1
3e9f43e

Silicon Labs Matter GitHub v1.1.0-1.1

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

Versions

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

Features

This is the v1.1.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 through VS Code.

  • 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

  • Quality tested Matter 1.1 alpha solution for Thread (MG12, MG24), and Wi-Fi NCP and SoC platforms (RS9116, WF200, SiWx917)
  • Adds support for the additional features on the SiWx917 SoC Dual Flash Device, such as buttons, LED, and factory reset
  • Adds support for the On/Off Plug application on the SiWx917 SoC Dual Flash Device
  • Adds support for faster commissioning performance on the SiWx917 SoC Dual Flash Device
  • 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
  • Added new configurable Sensor reference application

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 provided for the following:
    • Commissioning Process Overview
    • Security Overview
    • 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

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 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 -
  • Wi-Fi Dev Kit
    • 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 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
    • With CHIP Tool, Google Nest and Apple HomePod Mini controllers
    • With all device combinations
  • Thermostat
    • With CHIP Tool, Google Nest and Apple HomePod Mini controllers
    • With all NCP Mode device combinations (SiWx917 SoC not supported)

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 - Supported with Matter 1.0 with RS9116 & WF200 platforms - https://github.com/siliconlabs/matter/tree/release_1.0.2-1.0

Changes in this release:

  • Alpha Release of Matter 1.1 Apps (see supported apps and combinations above)
  • BLE support is added on SiWx917 and RS9116
  • On/Off plug app supported on the SiWx917 SoC
  • Faster commissioning performance on the SiWx917 SoC (~14sec)
  • Added SiWx917 SoC features - LED interface, Button interface, commissionable data provider, factory reset

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 EFR23xG24

Not supported in this release:

  • Matter Demos on the SiWx917 Common Flash SoC Device
  • LCD on EFR32xG24 with RS9116 or SiWx917 (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 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
  • 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
  • Matter Shell on the SiWx917 SoC (planned in future release)
  • OTA Updates on SiWx917 SoC

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

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

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, ~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

  • The Ozone Debugger may not immediately run the Matter application on the SiWx917 SoC Device. The application runs on resetting the device.
  • 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.
  • Matter Shell does not fully work with WF200 with EFR32xG24. Entered commands will not echo back to the terminal, and command outputs will not be seen. However, the commands are successfully processed.
  • RSI Send failure sometimes occurs within 1 hour of commissioning with the RS9116 or SiWx917 with Apple 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.
  • Timeout error occurs after running the Thermostat App for 1 hour or more on the EFR32xG24 + RS9116 device combination.
  • Matter Commissioning sometimes fails with a BlueZ disconnection error with RS9116 (NCP) and SiWx917 (NCP and SoC).

Unify

  • Endpoint 1 of the bridge shows support for the Identify cluster, but identify commands have no effects.
  • The Attribute Illuminance Measurement Type is not parsed correctly from the MQTT Side.
  • Unify Matter Bridge does not do clean shutdown, occasionally the application hans when shutting down.
  • General Diagnostic Cluster: AcceptedCommandList has command 0 listed twice on endpoint 0.
  • Groups Cluster: FeatureMap does not show in endpoint 1, but does show on all bridged endpoints.
  • Some chip-tool tests fails, see the test results in the bridge documentation for details.
  • For OnOff cluster, OnWithTimedOff command when used on a Z-Wave based Unify bridged endpoint, does not function as specified in combination with other OnOff commands.
  • For OnOff cluster, OffWaitTime attribute for a Z-Wave based Unify bridged endpoint calculation gets wrong if OffWithEffect/Off command is sent after OnWithTimedOff command.
Assets 9
Loading