How to use the OnOff Switch Config cluster on a device acting as a Server 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 OnOff Switch Config cluster. Once the Zigbee mesh network is created, the user can send requests from the Client to the Server through push buttons SW1/SW2 in order to read or change attribute SWITCH ACTION.
Note: The OnOff Switch Config Server Cluster need always to be integrated in a device with a OnOff Client Cluster.
Connectivity, Zigbee, Zigbee protocol, 802.15.4 protocol, OnOff cluster, Switch Config cluster
For this application it is requested to have:
Coord. Router +--------+ +--------+ | | | | | OnOff | | OnOff | | SwCfg | | SwCfg | | Client | | Server | | | | | | OnOff | | OnOff | | Server | | Client | | | | | 'OnOff Switch Config' during init : default Switch Action Toggle(SW1) | | | | <= ZbZclAttrIntegerWrite(ZCL_ONOFF_SWCONFIG_ATTR_ACTIONS) | | | | | | ZbZclOnOffClientToggleReq | | Red LED Toggle <= | | <------------------------------------ | | <= PushB SW1 | | | | | | | | | | ZbZclWriteReq | | * Change Action Mode | | (ZCL_ONOFF_SWCONFIG_ATTR_ACTIONS) | | PushB SW2 => | | ------------------------------------> | | => Switch Action : from Toggle(SW1) to On(SW1)/Off(SW2) | | | | | | ZbZclOnOffClientOnReq | | Red LED ON <= | | <------------------------------------ | | <= PushB SW1 | | | | | | ZbZclOnOffClientOffReq | | Red LED OFF <= | | <------------------------------------ | | <= PushB SW2 | | | | | | | | | | ZbZclReadReq | | | | (ZCL_ONOFF_SWCONFIG_ATTR_ACTIONS) | | PushB SW1 => | | ------------------------------------> | | Display Setting <= | | <------------------------------------ | | | | | | | | | | | | ZbZclWriteReq | | * Change Action Mode | | (ZCL_ONOFF_SWCONFIG_ATTR_ACTIONS) | | PushB SW2 => | | ------------------------------------> | | => Switch Action : from On(SW1)/Off(SW2) to Off(SW1)/On(SW2) | | | | | | ZbZclOnOffClientOnReq | | Red LED ON <= | | <------------------------------------ | | <= PushB SW2 | | | | | | ZbZclOnOffClientOffReq | | Red LED OFF <= | | <------------------------------------ | | <= PushB SW1 | | | | | | | | | | ZbZclWriteReq | | * Change Action Mode | | (ZCL_ONOFF_SWCONFIG_ATTR_ACTIONS) | | PushB SW2 => | | ------------------------------------> | | => Switch Action : from Off(SW1)/On(SW2) to Toggle(SW1) | | | | | | ZbZclOnOffClientToggleReq | | Red LED Toggle <= | | <------------------------------------ | | <= PushB SW1 | | | | | | | | +--------+ +--------+
Start the first board. It must be the coordinator of the Zigbee network, so in this demo application it is the device running Zigbee_OnOff_Server_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 send OnOff Cluster commands from the Client to the Server in multicast mode by pressing on the SW1 or push button. You must see the Red LED state change on the Server side in function of Switch Action mode.
It’s possible to display the Switch Config of an OnOff Switch Config Server by pressing the SW1 button on OnOff Switch Config Client.
It’s possible to change (increment) the Switch Config of a OnOff Switch Config Server by pressing the SW2 button on OnOff Switch Config 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.