Multilevel Sensor#
Shows the ability to advertise numerical sensor readings, such as temperature, and humidity. Multiple parameters can be set for the minimum and maximum values.
The Multilevel Sensor application is based on:
Role Type | Reporting Sleeping End Device (RSS) |
Supporting Device Type | Data reporting |
Device Type | Notification sensor |
Generic Type | Sensor Notification |
Specific Type | Notification Sensor |
Requested security keys | S2_UNAUTHENTICATED and S2_AUTHENTICATED |
Multilevel Sensor transmits the following events:
Environment monitoring
Temperature, and humidity measure
Supported Command Classes#
Multilevel Sensor implements mandatory and some optional command classes. The table below lists the supported Command Classes, their version, and their required Security class, if any.
Command Class | Version | Required Security Class |
---|---|---|
Association | 2 | Highest granted Security Class |
Association Group Info | 3 | Highest granted Security Class |
Device Reset Locally | 1 | Highest granted Security Class |
Firmware Update Meta Data | 5 | Highest granted Security Class |
Indicator | 3 | Highest granted Security Class |
Manufacturer Specific | 2 | Highest Granted Security Class |
Multi-Channel Association | 3 | Highest granted Security Class |
Powerlevel | 1 | Highest granted Security Class |
Security 2 | 1 | None |
Supervision | 1 | None |
Transport Service | 2 | None |
Version | 3 | Highest granted Security Class |
Wake Up | 2 | Highest granted Security Class |
Z-Wave Plus Info | 2 | None |
Configuration | 4 | Highest granted Security Class |
Multilevel-Sensor | 11 | Highest granted Security Class |
Basic Command Class Mapping#
Basic Command Class is not mapped to any of the supported command classes.
Association Groups#
The following table shows the available association groups.
ID | Name | Node Count | Description |
---|---|---|---|
1 | Lifeline | 5 | Supports the following command classes:
|
Usage of Buttons and LED Status
To use the sample app, the BRD8029A Button and LEDs Expansion Board must be used. BTN0-BTN3 and LED0-LED3 refer to the buttons and LEDs on the Expansion Board.
The following LEDs and buttons shown in the next table below are used.
Button | Action | Description |
---|---|---|
RST | Press | Resets the firmware of an application (like losing power). All volatile memory will be cleared. |
BTN01</sup | Press | Sends Battery Report, temperature, and humidity data (only if the device is not sleeping) |
BTN11</sup | Press | Enter "learn mode" (sending node info frame) to add/remove the device. Removing the device from a network will reset it. |
Hold for at least 5 seconds and release | Perform a reset to factory default operation of the device, and a Device Reset Locally Notification Command is sent via Lifeline. |
1: The application needs to be woken up for these operations. It is not possible to wake up the BRD4400C and BRD4401C radio boards using BTN0 and BTN1, and the BRD2603A Thunderboard using BTN1.\ To support these functionalities, the affected buttons must be remapped to pins that support waking up the chip from EM4 sleep mode. Please refer to your hardware's documentation for further information.
Firmware Update#
This section will describe backward compatibility when upgrading the MultilevelSensor application from one SDK to a newer version.
CLI Support#
In case CLI support is needed please install zw_cli_common component to the project. Please note the zw_cli_common component will modify the power consumption in case of sleeping applications. Like door lock keypad, sensor pir or multilevel sensor. CLI cannot work with sleep mode, after a reset the application stays awake until the user issues the enable_sleeping command. From that point CLI won't work and sleep mode will be reached until the next reset.