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?
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?
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
Hi Jody,
Jody P Ono said:Should I get a report every time that the subscribed attribute changes? I'm only seeing one report after I subscribe.
If you create a binding between the two endpoints (for example using zdo bind on) you will receive periodic attribute reports.
Best regards,
Marte
Hi, Marte:
Thank you very much for all of the excellent help. I think that we can consider this issue closed!
Best regards,
Jody