-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to actively report attributes? (TZ-57) #5
Comments
Currently the |
Hi, before I add new API to next round, I'd like to understand little bit more. What scenario you'd like to use this actively send report command, does configure reporting method not meet your case? For example, you'd like to send report to certain remote device when local device power back online by your action? Or you'd like to send report without binding and configure report command action? Or you'd like to send report command triggered by your switch button or timer? |
You have given an example of the usage scenario of the report command here. However, the Configure Reporting Command cannot report properties whose data types are arrays, structures, collections, or packages. |
But as far as I read from the ZCL specs, I didn't see most common cluster's reportable attribute have types of structure packages or array. Is there any special type attribute you'd like to send(not like 8bit, 16bit, 32bit size of attribute)? Also, if we don't have new API implemented, does current configure report command could partly meet you need? For example you set the max_interval time to 1 second, do you accept 1 second delay to report a attribute to the remote device? |
@lbuque The actively send the report attribute command API has been provided in the latest commit. Please take a look to see if it is fixed |
Closing the issue, @lbuque Let us know if any other issues. |
I want to actively report some attributes to the protocol controller after the device is connected to the network, but I can't find the relevant API, what should I do?
I'm currently using examples/esp_zigbee_customized_devices/customized_client .
The text was updated successfully, but these errors were encountered: