Zigbee SDK action_handler does not have addressing information
Posted: Tue Apr 29, 2025 2:01 pm
Hi all,
When I send a command using esp_zb_zcl_read_attr_cmd_req, for instance, the response is received by the registered action handler. What happens if I call esp_zb_zcl_read_attr_cmd_req multiple times to read attributes from multiple devices in turn. Say I have a bunch of lights and I want to request from each of the them their current brightness setting. How would that be done? I would have expected that I would be able to issue a bunch of requests and have asynchronous replies from each light carrying the requested brightness attribute value as well as information indicating which device is replying.
The registered action handler does not include any parameter containing information about the source of the messages it receives. The underlying ZBOSS sdk does have this information so someone decided to not forward that information. Why? Is this not useful, important even?
Right now all I can do is wait after each call to esp_zb_zcl_read_attr_cmd_req until the reply comes back before I send the next request to the next device. If there are lots of lights in the network this will take far too long.
Any help is much appreciated.
/J
When I send a command using esp_zb_zcl_read_attr_cmd_req, for instance, the response is received by the registered action handler. What happens if I call esp_zb_zcl_read_attr_cmd_req multiple times to read attributes from multiple devices in turn. Say I have a bunch of lights and I want to request from each of the them their current brightness setting. How would that be done? I would have expected that I would be able to issue a bunch of requests and have asynchronous replies from each light carrying the requested brightness attribute value as well as information indicating which device is replying.
The registered action handler does not include any parameter containing information about the source of the messages it receives. The underlying ZBOSS sdk does have this information so someone decided to not forward that information. Why? Is this not useful, important even?
Right now all I can do is wait after each call to esp_zb_zcl_read_attr_cmd_req until the reply comes back before I send the next request to the next device. If there are lots of lights in the network this will take far too long.
Any help is much appreciated.
/J