Good day.
I am currently developing with two NRF52840 DK boards, and I also have two NRF Dongles. On a dongle a sniffer for ZigBee. I am working with SDK 3.2. This is my first project with ZigBee, so I don't have much know-how yet.
My goal is to implement the coordinator as like CLI agent. So that it subscribes to the multi-sensor and receives data. Is so to speak an A to B communication.
With "zb_zdo_match_desc_req()" I get the short address and the endpoint of the sensor. Then with "zb_zdo_ieee_addr_req()" I get the long address (EUI64) of the sensor. After that the "zb_zdo_bind_req()" request starts (Between coordinator and sensor) and in the callback function ("p_resp->status") this is confirmed successfully with ZB_ZDP_STATUS_SUCCESS. However, I only connect to the ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT cluster.
My questions:
1) Is it necessary to connect both clusters (temperature/pressure) to subscribe to the multisensor? If so, is the bind request simply done again with the ZB_ZCL_CLUSTER_ID_PRESSURE_MEASUREMENT?
2) Is subscribing the sensor in the first step as below, correct?
3) Does it even need "cmd_zb_subscribe_unsubscribe_cb" and what is that unsubscribe for?
My problems:
1) The "ep_handler_report" is not called, but I see in Wireshark that a Report Attributes has been sent?
Is there still something to change at the sensor, because there I have left everything as is.
My ep_handler_report Handler:
The other functions as well as the output of the data I took from the CLI as well as from other discussions.
With the function "print_attr()" the data is output (Same function as with CLI), what am I doing wrong here with subscribe?
2) After a while the network crashes, any idea what this is? The Connected LED on the sensor goes out.
I would also be glad if you could give me a quick rundown on the process for subscribing to devices. If you want the whole code, I can share it with pleasure.
Thanks in advance.
With kind regards
Jonas T