-
Notifications
You must be signed in to change notification settings - Fork 20
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
Custom data package send (TZ-841) #334
Comments
This issue is similar to the one discussed in this GitHub link: #202. I recommend referring to it first for further insights. |
@LorenzoGrandi7 could you please provide the full code, I mean the .h file as well. I am trying convert the code to Arduino IDE and do some customized modification. |
|
@LorenzoGrandi7 Thanks for quick reply, I have seen that one and even convert it, but I want to make a single structure attribute contains all information I want to report from the EP, so basically looking for a way to create custom attribute and handle it. anyway thanks for your feedback. |
I have question but I don't want to initiate a thread, is it possible to make a packet (structure attribute) with multiple set of data like uint8_t, char, string and more, and then make it reportable ? like each time the EP send the full packet. I know I need to make a custom cluster with its own attribute. |
Question
Goodmorning, I'm trying to check the performance of the ESP32-C6, and in particular I'm studying the Zigbee protocol. The setup I'm working on are two controller, one acting as a coordinator and the other as an endpoint, that transfer a data package of 120kB from the endpoint to the coordinator (virtually as a generic sensor that sends its data to a coordinator). Looking to the examples I see that it's easy to send single values, but I haven't found a way to send a stream of data. I'm attepting to send the package using esp_zb_zcl_write_attr_cmd_req, but I'm not sure it's the correct way to proceed. Any suggestion?
Additional context.
End point code:
Coordinator code:
The text was updated successfully, but these errors were encountered: