-
Notifications
You must be signed in to change notification settings - Fork 279
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
Load additional manufacturer-specific clusters from device converter #933
Comments
Been wanting this for a while too, it would be great to move those non ZCL ones to the device definitions. @Koenkk I wonder if can somehow leverage some of the extend stuff to inject (and also share some between devices) Although thinking about it some more that won't work as all the code to resolve these lives in zh. 🤔 |
@sjorge it needs to be injected somehow into ZH during startup, can be done in |
@Koenkk Yeah I'm really waiting for this one too, it would open a world of possibilities for makers! |
@Koenkk |
Hi, with new zigbee chips like Espressif ESP32-C6, more and more personal/hobby projects using the Zigbee protocol are starting to appear.
Problem is that manufacturer-specific clusters (and attributes) are hardcoded in zigbee-herdsman and there are no ways to extend them without modifing the source code.
It's would be great to add a new "cluster" option to the device converter and load it in zigbee-herdsman when parsing messages.
The text was updated successfully, but these errors were encountered: