Sensor PIR#
The Z-Wave certified Sensor PIR application shows a presence/movement detector implementation for controlling other devices and for sending notifications.
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 |
Sensor PIR transmits the following notification types/events:
Home Security
Motion detection (unknown location)
Sensor PIR supports the "push mode" only of Notification CC.
Supported Command Classes#
Sensor PIR 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 |
Battery | 1 | 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 |
Notification | 8 | 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 |
Basic Command Class mapping#
Basic Command Class is not mapped to any of the supported command classes
Association Group configuration#
Application Association Group configuration
ID | Name | Node Count | Description |
|---|---|---|---|
1 | Lifeline | X | Supports the following command classes:
|
2 | Basic Set | Y | Upon a movement detection (simulated by button BTN2), nodes associated in this group will first receive a Basic Set with 0xFF (turn on) and after a while receive a Basic Set with 0x00 (turn off). |
X: For Z-Wave node count is equal to 5 and for Z-Wave Long Range it is 1. Y: For Z-Wave node count is equal to 5 and for Z-Wave Long Range it is 0.
Usage of Buttons and LED Status
Button | Action | Description | |
|---|---|---|---|
Radio Board 1 | Thunderboard 1 | ||
RST | Press | Resets the firmware of an application (like losing power). All volatile memory will be cleared. Sends Wake Up Notification. | |
BTN02 | Press | Sends Battery Report (only if the device is not sleeping) | |
BTN12 | 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 1 second and release | Simulates a "Motion detected" event. | ||
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. | ||
BTN2 | Hold for at least 1 second and release | Simulates a "Motion detected" event. |
LED | Description |
|---|---|
LED1 | Blinks with 1 Hz when learn mode is active. Used for Indicator Command Class. |
1: A Radio Board is plug-in board for the Wireless Pro Kit Mainboard. A Thunderboard is a stand-alone kit with a direct USB Type-C connection.
2: 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 Switch On/Off application from one SDK to a newer version.
CLI Support#
In case CLI support is needed pelase 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.
Command | Arguments | Description |
|---|---|---|
set_learn_mode | It can be start or stop | Starting or stopping the learn mode |
factory_reset | - | Executing factory reset |
get_dsk | - | Printing out the generated DSK of the device |
get_region | - | Printing out the set region of the application |
battery_report | - | Sending a battery report |
motion_detected | - | Triggering a motion detected event |
enable_sleeping | - | Lets the application go into sleep mode. After this command the CLI won't work until the next reset |