How to use the Occupancy Sensing on a device acting as a Client within a Centralized Zigbee network.
The purpose of this application is to show how to create a Zigbee centralized network, and how to communicate from one node to another one using the Occupancy Sensing cluster. Once the Zigbee mesh network is created, the Server sends regularly the Occupancy to Client. The user can indicate if the Room is empty or not on Server by using push buttons SW1 and SW2.
Connectivity, Zigbee, Zigbee protocol, 802.15.4 protocol, Occupancy Sensing cluster
For this application it is requested to have:
The Occupancy Sensing Server updates regularly (500 ms) its ZCL_OCC_ATTR_OCCUPANCY attributes (via the measure of a sensor or by random).
The Occupancy Sensing Client sends a Report Request to obtain regularly the ZCL_OCC_ATTR_OCCUPANCY attributes.
The Occupancy Sensing Server sends regularly (5 s) a Report with the latest value of ZCL_OCC_ATTR_OCCUPANCY attributes.
Coord. Router +-----------+ +-----------+ | | | | | OccupSens | | OccupSens | [ Client | | Server | - Occupancy Sensing Server during Init | | | | launch a 500 ms Periodic Timer | | | | | | | | - Every 500 ms | | | | * Read the Occupancy Sensor (if exist) | | | | or simulate it with RNG. | | | | * <= ZbZclAttrIntegerWrite(ZCL_OCC_ATTR_OCCUPANCY) | | After a Router was connected : | | | | ZbZclAttrReportConfigReq(ZCL_OCC_ATTR_OCCUPANCY, 5sec) | | | | ------------------------------------------------------------> | | | | <------------------------------------------------------------ | | | | | | | | <-------------- Report (every 5 seconds) -------------------- | | | | | | | | | | <= PushB SW1 : Indicate Room Occupancy. | | | | -> ZbZclAttrIntegerWrite(ZCL_OCC_ATTR_OCCUPANCY) | | | | | | | | <= PushB SW2 : Indicate Room Empty. | | | | -> ZbZclAttrIntegerWrite(ZCL_OCC_ATTR_OCCUPANCY) | | | | +-----------+ +-----------+
Start the first board. It must be the coordinator of the Zigbee network, so in this demo application it is the device running Zigbee_OccupSensing_Client_Coord application.
Wait for the Blue LED ON.
Start the second board. This board is configured as Zigbee router and will be attached to the network created by the coordinator. Do the same for the other boards if applicable.
→ At this stage, Blue LED blinks indicating that the Zigbee network is being created. This usually takes about 15 seconds. It is important to wait until Blue LED becomes ON to start pushing buttons.
It is now possible to change Room Occupancy by pressing SW1 or SW2 on Server. This change is reported to Client.
Note: When LED Red, Green and Blue are toggling it is indicating an error has occurred on application.
This example runs on STM32WBA55xx devices.
This example has been tested with an STMicroelectronics STM32WBA55CGA_Nucleo board and can be easily tailored to any other supported device and development board.
On STM32WBA55CGA_Nucleo, the jumpers must be configured as described in this section. Starting from the top left position up to the bottom right position, the jumpers on the Board must be set as follows:
JP1: 1-2: [ON] 3-4: [OFF] 5-6: [OFF] 7-8: [OFF] 9-10: [OFF]
JP2: 1-2: [ON]
To get the traces you need to connect your Board to the Hyperterminal (through the STLink Virtual COM Port).
The UART must be configured as follows:
BaudRate = 115200 baud Word Length = 8 Bits Stop Bit = 1 bit Parity = none Flow control = none Terminal “Go to the Line” : <LF>
By default, this application runs with Zigbee PRO stack R23.
If you want to run this application using Zigbee PRO stack R22, you should replace ZigBeeProR23_FFD.a by ZigBeeProR22_FFD.a and ZigBeeProR23_RFD.a by ZigBeeProR22_RFD.a and ZigBeeClusters.a by ZigBeeClustersR22.a in the build environment.
Also, set in the project setup compilation flag CONFIG_ZB_REV=22.