Zigbee CLI example can't interact with some clusters and Sleepy End Devices

Question

Hello all, 
 I'm interacting with some nodes in a test network: 
 setup: 10x nrf52840 DK (PCA10056) boards loaded with the following software. 
 1x Coordinator ( Zigbee CLI Agent example ) 
 3x Routers ( Zigbee Light Bulb Example ) 
 6x End Devices ( Zigbee Light Switch ) 
 
 I've made it on the End devices so, that if a certain attribute gets written that the node's LED2 will go on for a few seconds. 
 ( Zigbee CLI Reference --> zcl attr write & zcl attr read) 
 
 However I face 2 problems. 
 1) Certain commands aren't working using the CLI. 
 
 Routers accept "zcl attr write" & "zcl attr read" functions targeting all in_clusters 
 Routers accept "zcl cmd" commands targeting cluster 0x0006 
 Routers don't accept "zcl cmd" commands targeting cluster 0x0003 and 0x0004 
 
 2) Sleepy End Devices can't be interacted with. 
 
 Non-sleeping End Devices can be interacted with. But i'd like to use the sleepy behaviour to save power. 
 
 Is there a way that I can interact with Sleepy End devices using the CLI example? 
 Can I make my Routers accept "zcl cmd" commands targeting at least the 0x0003 and 0x0004 clusters?

Marte Myrvold · Accepted Answer

Hi Sam, SamTheMan said: None of the ZCL CMD commands from 0x0003 and 0x0004 sended to my nodes return a message in the logging. This does not necessarily mean that the commands are not received or handled by the router, but it could simply mean that there is no logging for the command in the example. The CLI agent did not print logs when I sent the commands to the router, but I could see in the sniffer log that the router did receive and respond to the commands. Can you get a sniffer log of the network traffic when you are sending the packets? If you have a nRF52840 Dongle or DK you can use nRF Sniffer for 802.15.4 . Please share the log as a pcap file so I can look at it. SamTheMan said: Also the command to put a node in identifying mode doesn't increase the identifying time. What does the command you are sending look like? Are you sending it to the correct address and endpoint? You should be able to change the IdentifyTime attribute using the Identify command. It should not be necessary to use the generic write attributes command. I tested with all commands in the Identify cluster, and I was able to change IdentifyTime, and verify that it was changed with the Identify Query command and read attributes command. This is the command I used to put the device in Identify mode for 120 seconds: zcl cmd 0b010e1585785ce7 10 3 0 -l 0x78 Where the arguments were as follows: zcl cmd -l Best regards, Marte

Zigbee CLI example can't interact with some clusters and Sleepy End Devices

Top Replies