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

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

Jody P Ono — Mon, 07 Mar 2022 14:29:40 GMT

Hi, Marte:

Thank you very much for all of the excellent help. I think that we can consider this issue closed!

Best regards,

Jody

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

Marte Myrvold — Mon, 07 Mar 2022 14:26:47 GMT

Hi Jody,

[quote user="MC_PlusPlus"]Should I get a report every time that the subscribed attribute changes? I'm only seeing one report after I subscribe.[/quote]

If you create a binding between the two endpoints (for example using zdo bind on) you will receive periodic attribute reports.

Best regards,

Marte

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

Marte Myrvold — Mon, 07 Mar 2022 14:20:40 GMT

Hi Jody,

Edit: I did not reload the page before publishing this response, so I did not see see that you already figured it out yourself.

I figured out what the issue was. You must use the decimal value for the attr_type in the subscribe on command, and not the hexadecimal value:

zcl subscribe on h:addr d:ep h:cluster h:profile h:attr_id d:attr_type [d:min interval (s)] [d:max interval (s)]

When you send the command with attr_type set to 20, you actually send that the data type of the attribute is 0x14, which is the value for 56-bit data type:

For current hue you should instead use 32 as attr_type:

zcl subscribe on 3e2d 11 0x0300 0x0104 0x00 32 2 5

This will send the command with 8-bit unsigned int as data type, which is the correct one for current hue:

This picture is from a sniffer log I captured where I successfully subscribed on the current hue attribute.

I can understand where the confusion comes from, because zcl attr read shows the hexadecimal value, and not the decimal.

Best regards,

Marte

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

Jody P Ono — Mon, 07 Mar 2022 14:04:20 GMT

Hi, Marte:

I found the problem in my "zcl subscribe on" command. I was not specifying the correct type. I did not realize that the response to my earlier attribute queries included the attribute type in hexadecimal while the "subscribe on" command wants the attribute type in DECIMAL. Anyway, it looks like it's working, sort of. Should I get a report every time that the subscribed attribute changes? I'm only seeing one report after I subscribe.

Best regards,

Jody

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

Jody P Ono — Mon, 07 Mar 2022 13:33:00 GMT

Hi, Marte:

The network key is: 41a30653e935ab6f531655f4c4c841d0.

Best regards,

Jody

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

Jody P Ono — Mon, 07 Mar 2022 12:19:31 GMT

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

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

Marte Myrvold — Mon, 07 Mar 2022 12:16:28 GMT

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

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

Jody P Ono — Mon, 07 Mar 2022 11:00:51 GMT

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

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

Marte Myrvold — Mon, 07 Mar 2022 09:37:55 GMT

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

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

Jody P Ono — Mon, 07 Mar 2022 08:38:06 GMT

Hi, Marte:

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

Best regards,

Jody

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

Marte Myrvold — Mon, 07 Mar 2022 08:02:51 GMT

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

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

Jody P Ono — Sat, 05 Mar 2022 05:04:30 GMT

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

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

Jody P Ono — Fri, 04 Mar 2022 12:04:38 GMT

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

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

Marte Myrvold — Fri, 04 Mar 2022 11:55:59 GMT

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

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

Jody P Ono — Fri, 04 Mar 2022 08:59:44 GMT

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

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

Marte Myrvold — Fri, 04 Mar 2022 08:01:29 GMT

Hi Jody,

Yes, I used our 802.15.4 sniffer and Wireshark. I suspect that there might be a bug or something missing in the actual SDK. I tested with unmodified versions of the network coordinator and light bulb samples from the SDK on a nRF52840 DK as well, only adding CONFIG_ZIGBEE_SHELL=y to configure Zigbee shell, and I saw the same there.

After some more digging I have found out what happens, but not exactly why. The CLI endpoint does not get registered, causing the endpoint handler, cli_agent_ep_handler_attr, to never be called. This seems to be true for all the CLI handlers in Zigbee shell (attr, generic_cmd, report, ping), and not just the one for attribute read/write. This handler is used to intercept incoming frames, so the way it is supposed to work is that when the read attr command is constructed and sent an alarm is scheduled. When the device receives a response, e.g. read attributes response, the endpoint handler should be called, and the alarm is cancelled inside the endpoint handler. Since the handler is never called the alarm is not cancelled, and it says that it times out even though the response was actually received.

In the Zigbee shell sample the CLI endpoint was registered and the endpoint handler worked as expected. I have not been able to figure out why it works in this example and not when configuring Zigbee shell in the other examples yet, as the latter worked in earlier versions of nRF Connect SDK. I have asked the developers about this, whether it is a bug somewhere, or if there is just some additional configuration or code that is needed in order to enable Zigbee shell in v1.9.0. I will update you when I get a response or if I find something else.

Best regards,

Marte

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

Jody P Ono — Thu, 03 Mar 2022 11:34:38 GMT

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

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

Jody P Ono — Thu, 03 Mar 2022 08:09:14 GMT

Hi, Marte:

I just finished setting up my system with the sniffer and Wireshark. I'll fire-up everything and see if my results match yours.

Best regards,

Jody

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

Marte Myrvold — Thu, 03 Mar 2022 07:23:40 GMT

Hi Jody,

I just wanted to update you on what I have found so far. After getting a sniffer log of the behavior myself, I see that the commands are sent correctly:

So the dongle does send the Read Attributes command, and you can see that it successfully receives the Read Attribute response command as well, as it sends an ACK in return. So the error is not with sending and receiving the command, but something else. I will keep looking into this and inform you or your colleagues when I find out more.

Best regards,

Marte

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

Jody P Ono — Wed, 02 Mar 2022 19:45:50 GMT

Hi, Marte:

One of my colleagues will likely be picking-up this issue in the coming days to get a sniffer log to you. Thanks for all of your help!

Best regards,

Jody

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

Marte Myrvold — Wed, 02 Mar 2022 15:02:11 GMT

Hi Jody,

It is hard giving suggestions without knowing what is causing the issue, and a sniffer log would greatly help in figuring this out. I was able to reproduce the issue on my side, but I am not able to get a sniffer log of it today. I will look more into this and get a sniffer log of it tomorrow.

Best regards,

Marte

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

Jody P Ono — Wed, 02 Mar 2022 09:51:08 GMT

Hi, Marte:

I've tried sending the "zcl attr read" command to each of five different devices: Three Philips Hue bulbs and two DK boards running as Zigbee light bulbs. I've tried cluster 0x0000, attribute 0x00. The command times-out without any response every time. Probably will take me a day or two to fire-up a sniffer as I have other deadlines. Any other suggestions in the meantime would be greatly appreciated.

Best regards,

Jody

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

Marte Myrvold — Wed, 02 Mar 2022 09:05:33 GMT

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