Zigbee ZCL read attributes command always times-out without any response.

[Jody P Ono]

I'm using the nRF52840 dongle with nRF Connect 1.90 and the CLI.  I cannot get "zcl attr read" command to return anything.  It simply times-out.  What am I doing wrong?

[Marte Myrvold]

Hi,

What device are you sending the zcl attr read command to, and what cluster and attribute?

Are you able to get a sniffer log of this? If you have an additional nRF52840 Dongle or DK you can use our nRF Sniffer for 802.15.4. Please start the sniffer before the network is started, so the sniffer has the network key.

Best regards,

Marte

[Jody P Ono]

Hi, Marte:

My Wireshark capture looks the same as yours, i.e. I can see broadcast and response packets.  How did you manage to display the specific Zigbee ZCL details of each packet?  Did you use Wireshark?

Best regards,

Jody

[Jody P Ono]

Hi, Marte:

Thank you for all of your hard work!  I look forward to whatever you and the Nordic developers discover and hope that a fix is possible.

Regarding your Wireshark capture, are you using some special kind of interpreting plugin such that details of the ZCL command (like profile ID and endpoint) are shown in your capture?  When I do a capture, it does not display that kind of detail.

Best regards,

Jody

[Marte Myrvold]

Hi,

It seems to have been a misunderstanding on my part. I thought that the CLI endpoint is a different endpoint than the application endpoint, and that you could set it to whatever valid endpoint value you wanted. However, it is actually the same endpoint as the application endpoint. So to fix this, all you need to do is to set CONFIG_ZIGBEE_SHELL_ENDPOINT in prj.conf to the same as ZIGBEE_COORDINATOR_ENDPOINT, which should be 10 unless you have changed in your code.

I also realized that the prj.conf that I shared earlier does not enable logging on the dongle. I was able to fix this by removing the configuration CONFIG_NCS_SAMPLES_DEFAULTS and setting CONFIG_LOG=y.

Best regards,

Marte

[Jody P Ono]

Hi, Marte:

This is great news.  I will modify the firmware and test tomorrow (er, today, I guess?).  Anyway, it's really late (or early) here and I need to get some sleep.  Thanks again for your exemplary (and quick) problem solving!  I'll report back with my results.

Best regards,

Jody

[Jody P Ono]

Hi, Marte:

Your changes to the prj.conf file work very well!  I am finding another issue, though.  I am unable to subscribe to any reportable attributes with "zcl subscribe on".  I keep getting a "Status 141" error, which is "Invalid Type".  I am using the same type that is returned when I query the same attribute with "zcl attr read".  I have tried the CurrentHue and CurrentX attributes of the Color Control cluster (0x0300) on a Philips Hue bulb.  These are reportable attributes per the Zigbee specification.  Can you please assist?

Best regards,

Jody

[Marte Myrvold]

Hi Jody,

Can you try using 0xc05e as profile ID instead? This is the profile ID for Zigbee Link Link, which I know some Zigbee light bulbs use instead of Home Automation.

Best regards,

Marte

[Jody P Ono]

Hi, Marte:

I get the same error, "Unable to configure attribute 0 reporting. Status: 141".

Best regards,

Jody

[Marte Myrvold]

Hi Jody,

Can you show me what the command you are sending looks like? Are you able to get a sniffer log of this that you can upload here for me to look at?

Best regards,

Marte

[Jody P Ono]

Hi, Marte:

Here's my command window:

uart:~$ bdb start
Started router
Done
[00:00:11.535,461] <inf> zigbee_app_utils: Production configuration is not present or invalid (status: -1)
[00:00:11.536,193] <inf> zigbee_app_utils: Zigbee stack initialized
[00:00:11.572,082] <inf> zigbee_app_utils: Unimplemented signal (signal: 54, status: 0)
[00:00:11.576,141] <inf> app: Start network steering
[00:00:12.049,743] <inf> zigbee_app_utils: Unimplemented signal (signal: 54, status: 0)
[00:00:12.053,192] <inf> app: Network steering started
[00:01:00.393,127] <inf> zigbee_app_utils: Device authorization event received (short: 0x3e2d, long: 001788010b6dec20, authorization type: 1, authorization status: 0)
[00:01:04.344,482] <inf> app: New device commissioned or rejoined (short: 0x3e2d)
[00:01:04.344,543] <inf> app: Joining period extended.
[00:01:10.199,310] <inf> zigbee_app_utils: Unimplemented signal (signal: 50, status: 0)
[00:03:14.206,390] <inf> zigbee_app_utils: Unimplemented signal (signal: 54, status: 0)
[00:04:06.627,136] <inf> app: Network steering finished
uart:~$ zcl cmd 3e2d 11 0x0300 0x00 -l a9000000
Done
uart:~$ zcl cmd 3e2d 11 0x0300 0x00 -l 64000000
Done
uart:~$ zcl cmd 3e2d 11 0x0006 0x02
Done
uart:~$ zcl subscribe on 3e2d 11 0x0300 0x0104 0x00 20 2 5
Error: Unable to configure attribute 0 reporting. Status: 141

Error: One or more attributes reporting were not configured successfully[00:08:16.009,094] <inf> zigbee.eprxzcl: Received ZCL command (0): src_addr=0x3e2d(sho~
uart:~$

And here's my Wireshark capture.

Best regards,

Jody

[Marte Myrvold]

Hi Jody,

The packets in the sniffer are encrypted. Do you have the network key so that I can decrypt the packets? If not, can you capture a sniffer log where you start the sniffer before the coordinator starts the network so that the sniffer has the network key?

Best regards,

Marte

[Jody P Ono]

Hi, Marte:

Actually, I did start the sniffer before the coordinator and I've never been able to capture the network key,  Is there a way that I can get the network key from the coordinator?

Best regards,

Jody