Skip to content
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

Closed
rgiordano30 opened this issue Feb 25, 2024 · 4 comments
Closed

Comments

@rgiordano30
Copy link

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.

@sjorge
Copy link
Sponsor Contributor

sjorge commented Mar 5, 2024

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. 🤔

@Koenkk
Copy link
Owner

Koenkk commented Mar 5, 2024

@sjorge it needs to be injected somehow into ZH during startup, can be done in onEvent but didn't had the time to look at this yet.

@Suxsem
Copy link

Suxsem commented Mar 7, 2024

@Koenkk Yeah I'm really waiting for this one too, it would open a world of possibilities for makers!
If you are willing to provide me some insights in how you would implement this I'm happy to try making a PR!

@Suxsem
Copy link

Suxsem commented Mar 11, 2024

@Koenkk
I see that in https://github.com/Koenkk/zigbee2mqtt/blob/2a53b8e59b457e0805318bdb38d2c74de651724d/lib/zigbee.ts#L61
ZH is initialized with an herdsmanSettings object, do you think this could be a good place to inject manufacturer-specific clusters?
Or this settings should only contain global (aka adapter) settings?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants