Skip to content

v0.1.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@rerasool rerasool released this 26 Jul 20:56
v0.1.0
08a2b4e

Silicon Labs Matter GitHub v0.1.0

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

Versions

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

Features

This is the v0.1.0 (first) 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. 

This release is intended for demo purposes only. For certification, please reach out to your FAE or go to the public CSA release.

Thread

In order to run the Thread Matter Demo, a developer must have at least two Silicon Labs EFR based devices and a Raspberry Pi with a >32 GB SD Card. The documentation located at ./docs/silabs/README.md is focused on how to run the Matter demos using this hardware.

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 the Wi-Fi Demo, 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 EFR32MG12 + RS9116 device combination
  • Lock on EFR32MG12 + WF200 device combination

Supported:

  • Networks with up to 12 non-IoT devices such as laptops and phones, including a single EFR-9116 or EFR-WF200 NCP mode device combination
  • WPA and WPA2 AP connection security modes

Not supported in this release:

  • Wi-Fi Network Diagnostics cluster (planned in a future release)
  • 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
  • Connection to AP's running in access point (AP) mode (planned in a future release)
  • Connection to AP's that have disabled IPv6 (planned in a future release)

Known Issues

General

  • This release focuses on the "Demo" use case in which pre-built images are flashed onto the EFR (and RaspberryPi in the case of Matter over Thread). Demo image artifacts are included in this release. As a result much of the documentation focuses on this "Demo" use case. The "Development" use case is more complex and will be documented thoroughly in an upcoming release.
  • Building images from scratch on Windows, while not required for the demo, requires the Windows Subsystem for Linux (WSL). This is because the build environment requires access to a command line to run many of the build tools. As a result, development on the Windows platform can be challenging at times. Silicon Labs is currently working on resolving these build issues for our Windows users.
  • 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/

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, ~11GB. 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

  • Our Wi-Fi solution works best if the controller (Mac or RPi) is connected to a 5GHz channel. This implies that we require an access point with both 2.4GHz and 5GHz capabilities. There is some interference on the controller when it is connected to a 2.4GHz channel. So in general, connect your controller to 5GHz network, but send the credentials (SSID and password) for the 2.4GHz channel to the end device.
  • 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
  • WLAN connection fails from WF200 in rare instances with an "access point not found" error. Commissioning should succeed on re-running.
  • 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.
  • WLAN connection fails from RS9116 during commissioning using the WPA3 security mode.
  • WLAN connection fails from RS9116 during commissioning when channel 13 is selected on the AP.
  • In the Network Commissioning cluster for RS9116, the Scan Networks command fails on specifying an SSID to filter the results on.
Assets 4
Loading