Thingy:53: Matter weather station
This Matter weather station application demonstrates the usage of the Matter application layer to build a weather station device using the Nordic Thingy:53. Such a device lets you remotely gather different kinds of data using the device sensors, such as temperature, air pressure, and relative humidity. The device works as a Matter accessory device, meaning it can be paired and controlled remotely over a Matter network built on top of a low-power, 802.15.4 Thread or 802.11ax (Wi-Fi 6) network. You can use this application as a reference for creating your own application.
The Matter weather station application from the v2.1.1 nRF Connect SDK release participated in Matter Specification Validation Event (SVE) and successfully passed all required test cases to be considered as a device compliant with Matter 1.0. You can use the nRF Connect SDK v2.1.1 release to see the application configuration and the files that were originally used in Matter 1.0 certification.
The application supports the following development kits:
To commission the weather station device and control it remotely through a Thread or Wi-Fi network, you also need a Matter controller device configured on PC or smartphone. This requires additional hardware depending on your setup. The recommended way of getting measurement values is using the mobile Matter controller application that comes with a graphical interface, performs measurements automatically and visualizes the data.
To program a Thingy:53 device where the preprogrammed MCUboot bootloader has been erased, you need the external J-Link programmer. If you have an nRF5340 DK that has an onboard J-Link programmer, you can also use it for this purpose.
If the Thingy:53 is programmed with Thingy:53-compatible sample or application, you can also update the firmware using MCUboot’s serial recovery or DFU over Bluetooth® Low Energy (LE). See Thingy:53 application guide for details.
Matter requires the GN tool. If you are updating from the nRF Connect SDK version earlier than v1.5.0, see the GN installation instructions.
The development kits for this sample offer the following IPv6 network support for Matter:
Matter over Thread is supported for
Matter over Wi-Fi is supported for
nrf7002expansion board attached, for the
prj_release.confbuild type only. See Building for the nRF7002 Wi-Fi expansion board for more information.
The application uses a single button for controlling the device state. The weather station device is periodically performing temperature, air pressure, and relative humidity measurements. The measurement results are stored in the device memory and can be read using the Matter controller. The controller communicates with the weather station device over the Matter protocol using Zigbee Cluster Library (ZCL). The library describes data measurements within the proper clusters that correspond to the measurement type.
The application supports over-the-air (OTA) device firmware upgrade (DFU) using one of the two following protocols:
Matter OTA update protocol that uses the Matter operational network for querying and downloading a new firmware image.
Simple Management Protocol (SMP) over Bluetooth LE. In this case, the DFU can be done either using a smartphone application or a PC command line tool. Note that this protocol is not part of the Matter specification.
In both cases, MCUboot secure bootloader is used to apply the new firmware image. For information about how to upgrade the device firmware using a PC or a mobile, see the Updating the device firmware section.
By default, the Matter accessory device has no IPv6 network configured. You must pair it with the Matter controller over Bluetooth LE to get the configuration from the controller to use the device within a Thread or Wi-Fi network.
The Bluetooth LE advertising starts automatically upon the device startup, but only for a predefined period of time (15 minutes by default). If the Bluetooth LE advertising times out, you can re-enable it manually using Button (SW3).
The Matter weather station application does not use a single
Configuration files are provided for different build types and they are located in the
prj.conf file represents a
debug build type.
Other build types are covered by dedicated files with the build type added as a suffix to the
prj part, as per the following list.
For example, the
release build type file name is
If a board has other configuration files, for example associated with partition layout or child image configuration, these follow the same pattern.
CONF_FILE variable contains a single file and this file follows the naming pattern
prj_<buildtype>.conf, then the build type will be inferred to be <buildtype>.
The build type cannot be set explicitly.
The <buildtype> can be any string, but it is common to use
For information about how to set variables, see Important Build System Variables in the Zephyr documentation.
The Partition Manager’s static configuration can also be made dependent on the build type.
When the build type has been inferred, the file
pm_static_<buildtype>.yml will have precedence over
The child image Kconfig configuration can also be made dependent on the build type.
The child image Kconfig overlay file is named
child_image/<child_image_name>.conf instead of
prj.conf, but otherwise follows the same pattern as the parent Kconfig.
Alternatively, the child image Kconfig configuration file can be introduced as
child_image/<child_image_name>/prj.conf and follow the same pattern as the parent Kconfig.
child_image/mcuboot/prj_release.conf can be used to define
release build type for
mcuboot child image.
Before you start testing the application, you can select one of the build types supported by Matter weather station application, depending on the building method. This application supports the following build types:
debug- Debug version of the application. You can use this version to enable additional features for verifying the application behavior, such as logs or command-line shell.
release- Release version of the application. You can use this version to enable only the necessary application functionalities to optimize its performance.
Currently, this application supports only the
releasebuild type when Building for the nRF7002 Wi-Fi expansion board.
factory_data- Release version of the application that has factory data storage enabled. You can use this version to enable reading factory data necessary from a separate partition in the device non-volatile memory. This way, you can read information such as product information, keys, and certificates, useful for example for Matter certification. See Generating factory data to learn how to put factory data into device’s storage. To learn more about factory data, read the Configuring factory data for the nRF Connect examples page in the Matter documentation.
Selecting a build type is optional.
debug build type is used by default if no build type is explicitly selected.
- LED (LD1):
Shows the overall state of the device and its connectivity. The following states are possible:
Short flash on (green color, 50 ms on/950 ms off) - The device is in the unprovisioned (unpaired) state and is not advertising over Bluetooth LE.
Short flash on (blue color, 50 ms on/950 ms off) - The device is in the unprovisioned (unpaired) state, but is advertising over Bluetooth LE.
Rapid even flashing (blue color, 100 ms on/100 ms off) - The device is in the unprovisioned state and a commissioning application is connected through Bluetooth LE.
Short flash on (purple color, 50 ms on/950 ms off) - The device is fully provisioned and has Thread enabled or has Wi-Fi connection established.
Rapid even flashing after commissioning (blue color, 100 ms on/100 ms off) - The device lost connection to Wi-Fi network (only in Wi-Fi mode).
Thingy:53 allows to control RGB components of its single LED independently. This means that the listed color components can overlap, creating additional color effects.
- Button (SW3):
Used during the commissioning procedure. Depending on how long you press the button:
If pressed for 6 seconds, it initiates the factory reset of the device. Releasing the button within the 6-second window cancels the factory reset procedure.
If pressed for less than 3 seconds, it starts the NFC tag emulation, enables Bluetooth LE advertising for the predefined period of time (15 minutes by default), and makes the device discoverable over Bluetooth LE.
- USB port:
Used for getting logs from the device or communicating with it through the command-line interface. It is enabled only for the debug configuration of an application. See the Selecting a build type section to learn how to select the debug configuration.
- NFC port with antenna attached:
Used for obtaining the Onboarding information from the Matter accessory device to start the commissioning procedure.
See Configuring your application for information about how to permanently or temporarily change the configuration.
This sample can be found under
applications/matter_weather_station in the nRF Connect SDK folder structure.
To build the sample with Visual Studio Code, follow the steps listed on the How to build an application page in the nRF Connect for VS Code extension documentation. See Building and programming an application for other building and programming scenarios and Testing and debugging an application for general information about testing and debugging in the nRF Connect SDK.
Before you start testing the application, you can select one of the Matter weather station build types, depending on your building method.
Selecting a build type in Visual Studio Code
To select the build type in the nRF Connect for VS Code extension:
When building an application as described in the nRF Connect for VS Code extension documentation, follow the steps for setting up the build configuration.
In the Add Build Configuration screen, select the desired
.conffile from the Configuration drop-down menu.
Fill in other configuration options, if applicable, and click Build Configuration.
Selecting a build type from command line
To select the build type when building the application from command line, specify the build type by adding the following parameter to the
west buildcommand:-- -DCONF_FILE=prj_selected_build_type.conf
For example, you can replace the selected_build_type variable to build the
release firmware for
thingy53_nrf5340_cpuapp by running the following command in the project directory:
west build -b thingy53_nrf5340_cpuapp -d build_thingy53_nrf5340_cpuapp -- -DCONF_FILE=prj_release.conf
build_thingy53_nrf5340_cpuapp parameter specifies the output directory for the build files.
If the selected board does not support the selected build type, the build is interrupted.
For example, if the
shell build type is not supported by the selected board, the following notification appears:
File not found: ./ncs/nrf/applications/matter_weather_station/configuration/thingy53_nrf5340_cpuapp/prj_shell.conf
To build this application to work with the nRF7002 Wi-Fi expansion board:
Connect the nRF7002 EB to the P9 connector on Thingy:53.
Build the application:
To build the application in the nRF Connect for VS Code IDE for Thingy:53 with the nRF7002 EB attached, add the expansion board and the build type variables in the build configuration’s Extra CMake arguments and rebuild the build configuration. For example:
-- -DSHIELD=nrf7002eb -DCONF_FILE=prj_release.conf.
To build the sample from the command line for Thingy:53 with the nRF7002 EB attached, use the following command within the sample directory:
west build -b thingy53_nrf5340_cpuapp -- -DSHIELD=nrf7002eb -DCONF_FILE=prj_release.conf
To enable factory data support, you need to select the
factory_data build type from the available application build types.
You can generate new factory data set when building for the target board by invoking the following command:
west build -b thingy53_nrf5340_cpuapp -- -DOVERLAY_CONFIG=overlay-factory_data.conf
This command builds the application with default certificates.
After building the target, the generated
factory_data.hex file will be merged with the application target HEX file, so you can use the regular command to flash it to the device:
west flash --erase
If you want to use Vendor ID, Product ID or other data that is not reserved for tests, you need custom test certificates. To build with custom certificates, you need to install CHIP Certificate Tool.
The testing procedure assumes you are using the CHIP Tool for Android Matter controller application. You can also obtain the measurement values using the PC-based CHIP Tool for Linux and iOS Matter controller and invoking the read commands manually. Compared with the PC Matter controller, the mobile Matter controller only gives access to a subset of clusters supported by the Matter weather station application. If you want to access all the supported clusters, including Descriptor, Identify, and Power Source clusters, use the PC Matter controller. To see how to send commands from the PC Matter controller, read the Working with the CHIP Tool page in the Matter documentation.
After programming the application, perform the following steps to test the Matter weather station application on the Thingy:53 with the mobile Matter controller application:
Turn on the Thingy:53. The application starts in an unprovisioned state. The advertising over Bluetooth LE and DFU start automatically, and LED (LD1) starts blinking blue (short flash on).
Commission the device to the network of your choice:
For Thread network, follow the steps in Matter over Thread: Configuring Border Router and Linux/macOS controller on separate devices.
For Wi-Fi network, follow the steps in Matter over Wi-Fi: Configuring CHIP Tool for Linux or macOS.
During the commissioning procedure, LED (LD1) of the Matter device starts blinking blue (rapid even flashing). This indicates that the device is connected over Bluetooth LE, but does not yet have full Thread network connectivity.
To start commissioning, the controller must get the Onboarding information from the Matter accessory device.
Once the commissioning is complete and the device has full Thread or Wi-Fi connectivity, LED (LD1) starts blinking purple (short flash on).
Request to read sensor measurements in CHIP Tool for Linux or macOS:
Choose one of the following measurement type and invoke the command using CHIP Tool for Linux or macOS (Fill the Device ID argument with the same as was used to commissioning):
To read temperature:
chip-tool temperaturemeasurement read measured-value <Device ID> 1
To read relative humidity:
chip-tool relativehumiditymeasurement read measured-value <Device ID> 2
To read air pressure:
chip-tool pressuremeasurement read measured-value <Device ID> 3
After invoking the chosen command, search the CHIP Tool for Linux or macOS console logs and look for the measurement value:
Example of the temperature measurement value log:
[1675846190.922905][72877:72879] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0402 Attribute 0x0000_0000 DataVersion: 1236968801 [1675846190.922946][72877:72879] CHIP:TOO: MeasuredValue: 2348
This means that the current temperature value is equal to 23.48°C.
Example of the relative humidity measurement value log:
[1675849697.750923][164859:164861] CHIP:TOO: Endpoint: 2 Cluster: 0x0000_0405 Attribute 0x0000_0000 DataVersion: 385127250 [1675849697.750953][164859:164861] CHIP:TOO: measured value: 2526
This means that the current relative humidity value is equal to 25.26%.
Example of the air pressure measurement value log:
[1675849714.536985][164896:164898] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0403 Attribute 0x0000_0000 DataVersion: 3096547 [1675849714.537008][164896:164898] CHIP:TOO: MeasuredValue: 1015
This means that the current current air pressure value is equal to 1015 hPa.
When you start the commissioning procedure, the controller must get the onboarding information from the Matter accessory device. The onboarding information representation depends on your commissioner setup.
For this application, the data payload, which includes the device discriminator and setup PIN code, is encoded and shared using an NFC tag. When using the debug configuration, you can also get this type of information from the USB interface logs.
Alternatively, depending on your build type, you can also use one of the following onboarding information formats to provide the commissioner with the data required:
For the debug and release build types:
QR Code Payload
Manual pairing code
Scan the following QR code with the app for your ecosystem:
For the factory data build type:
QR Code Payload
Manual pairing code
Scan the following QR code with the app for your ecosystem:
This data payload also includes test Device Attestation, with test Certification Declaration, Product ID, and Vendor ID. These are used for Device Attestation within commissioning, and you can generate your own test Certification Declaration when you work on Matter end product.
To update the device firmware, complete the steps listed for the selected method in the Performing Device Firmware Upgrade in the nRF Connect examples tutorial in the Matter documentation.
This application uses the Matter library, which includes the nRF Connect SDK platform integration layer:
In addition, the application uses the following nRF Connect SDK components:
The application depends on the following Zephyr libraries: