[Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

RE: [Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

user97655 — Mon, 13 Jun 2022 09:40:59 GMT

Thank you for your answer and sorry for the late reply,

So this behavior can be easily seen by using CLI dongle and a NRF_dev board running example from the two light bulb example. You can just add some log in the zcl handler and using the cli dongle to send on/off command. You can tried to send 2-3 off command to see that only the first off command will trigger the callback

So if nothing you can do to change the SDK, is there any other way I can use to fix this behavior like changing to another command or something.

Best regards,

RE: [Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

user26071 — Tue, 07 Jun 2022 13:29:30 GMT

Is this seen in e.g. the light bulb examples in v4.1.0 and 4.2.0? It is still a bit vague to me. If not, can you zip and send some examples that I can use to replicate this on a few DKs?

Disclaimer:

If the behavior did actually change, I guess there isn't much we can do, since the nRF5 SDK for Thread and Zigbee is in maintenance mode (meaning there will not be any updates unless there are crucial security bugs that need patching). All future development is on the nRF Connect SDK (NCS).

[quote user="Tu Hoang"]But the problem is that after a reset, the value on/off in the cluster attribute is return to 0.[/quote]

So this was not the case in 4.1.0? If it was not, then I assume that this must have been stored in flash by the zboss stack (but I don't think it is).

Best regards,

Edvin

RE: [Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

user97655 — Mon, 06 Jun 2022 02:37:38 GMT

Hi Edvin,

Sorry for the late response and making the last reply unclear

I do not use binding and configure report but use API such as to create a report message and send.

So in my system I have a set of buttons; each goes with one endpoint and have an on/off cluster. If I press a button I want it to send an on/off to the coordinator and the coordinator will work as a gateway to send out the data through Ethernet to the server. I also have an app to control the button through the internet by using the data in the server. Because I form my own package report without configure (using marcro like ZB_ZCL_START_PACKET, ZB_ZCL_CONSTRUCT_GENERAL_COMMAND_REQ_FRAME_CONTROL, ZB_ZCL_CONSTRUCT_COMMAND_HEADER, ZB_ZCL_PACKET_PUT_DATA8 and ZB_SEND_SHORT_CMD) I usually just send the message without making changes in cluster attribute. This will make the data on the server and the attribute value in devices go un-sync. So there will be cases when the attribute is off/on and the command send to the device is also off/on. The call back was declared with ZB_ZCL_REGISTER_DEVICE_CB as usual. In 4.1.0, the callback register by that macro is always called whenever there are a on/off command. But from what I see, in 4.2.0, The callback will only called when the value in on/off command change the attribute in device cluster. If the value in that endpoint is off and I send an off command to it , it will not change anything thus the callback is not triggered. The same case goes with on. So what I did is to add ZB_ZCL_SET_ATTRIBUTE to everytime I press the buttons.

But the problem is that after a reset, the value on/off in the cluster attribute is return to 0. What I ask is that is there any way I can persist the value on every reset without initiate a new regions in Fds. Also, Is there any way I can get the callback to call every time.

Thank you and looking forward for your answer,

Best regards,

RE: [Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

user26071 — Wed, 01 Jun 2022 06:28:12 GMT

Hello Tu,

It is not clear to me what you used to do and what you have to do now. Can you explain in detail how you used to change the value, which doesn't work anymore. What API did you use?

[quote user="Tu Hoang"]In the last SDK version 4.1.0 I do not need to set the value in the cluster but looks like in 4.2.0 your developers have made some changes so now the on/off command is only callback when the value to change is different from the value in the command[/quote]

How did you do it before?

[quote user="Tu Hoang"]But I have one more problem, after reset does the value that I use ZB_ZCL_SET_ATTRIBUTE will persist since when I reset the device the issue happen again.[/quote]

Can you explain what you mean by this? This is not clear to me.

Best regards,

Edvin

RE: [Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

user97655 — Wed, 01 Jun 2022 02:12:58 GMT

Hi Edvin,

Well I have just figured it out that I need to use this marco ZB_ZCL_SET_ATTRIBUTE to set the cluster on/off value correspondingly whenever I change the state with the button so that when the on/off command is receive it will call the zcl callback function.

In the last SDK version 4.1.0 I do not need to set the value in the cluster but looks like in 4.2.0 your developers have made some changes so now the on/off command is only callback when the value to change is different from the value in the command. Now everything works as normal.

But I have one more problem, after reset does the value that I use ZB_ZCL_SET_ATTRIBUTE will persist since when I reset the device the issue happen again.

I am look forward to hearing from you.

Best regards,

RE: [Zigbee] Problem with Zcl callback handler in zigbee and thread 4.2.0

user26071 — Tue, 31 May 2022 13:57:50 GMT

Hello Tu,

This is not something that I have seen reported before. Do you have some application that I can use to replicate this behavior? Or did you just use one of the already existing examples?

Best regards,

Edvin