fix: del invalid custom cluster #10862
Conversation
|
Can you try with |
But in this case, the web interface has cluster genBasic, and when I request, for example, attribute powerSource, I get this error. [27.11.2025, 13:41:15] z2m: Publish 'set' 'read' to '0xbc026efffe372e6b' failed: 'Error: ZCL command 0xbc026efffe372e6b/1 genBasic.read(["powerSource"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":26214,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')' Custom attributes are not displayed in this cluster.
[27.11.2025, 13:47:29] zhc:tz: Read result of 'genBasic': {"powerSource":4}
, then cluster genBasic is available in the web interface with standard attributes (but no custom ones). However, the response to the request for attribute powerSource is: [27.11.2025, 15:02:19] zhc:tz: Read result of 'genBasic': {"powerSource":4}
|
|
If I add attributes to a standard cluster after cluster.ts like this: , the result is as expected – custom attributes are available in cluster genBasic in the web interface: and are readable normally: [27.11.2025, 15:53:42] zhc:tz: Read result of 'genBasic': {"deviceVersion":"4.34.1"} |
|
Would it be possible to use a non conflicting cluster ID for the device? If not, maybe you can help debugging https://github.com/Koenkk/zigbee-herdsman/blob/fe0d4a428a05002e248a52af0ed87cfde3828e36/src/controller/model/device.ts#L1268 ? |
|
Unfortunately, it's currently not possible to use another cluster for these attributes. Only in the near future. |
|
To start, I would add some |
|
After commit 7ef4099, adding custom attributes to the standard cluster works. |
|
Added logging to And I saw that the cluster was expanding with new custom attributes. |
|
The custom cluster are published as part of the |
|
I subscribed to the topic |
|
At the very end of the response I see custom cluster |
|
Will it be possible to backport these changes to 2.7.0? Because the changes in #10856 resulted in the standard cluster |
Can you add some debug logging to z2m to log the custom clusters when published? Seems they are missing there?
Fix will be included in the next version and dev branch once this is merged. |
|
I must have missed it last time. So, all 5 custom attributes ( |
|
@Nerivec could it be that windfront ignores the custom cluster because it conflicts with |
|
No WindFront picks custom cluster first, then standard if not available (2.7.0 includes a fix on this, previously was ZH first - old frontend has the bug also I believe). @BurchuMikhail can you check the state.json from Settings>Tools>Download state to see if the custom cluster attributes are present in the frontend's store? I did not read everything related to this, but I see some renaming, could it be it's trying to use an improper (outdated) key somewhere? |
|
@Nerivec I checked. I see that the custom attributes are in this file. |
|
This is what I get when adding one of the devices in that state.json as mock: Did you test this with latest Z2M version (as mentioned there was a related fix)? |
|
@Nerivec Thank you. |
|
I've added a mock device to the demo so we can have an example of this: https://nerivec.github.io/zigbee2mqtt-windfront/ |
|
@Koenkk, It's working as expected now. Would you like to accept the changes to the converter? |
|
Thanks! |
3 participants
An issue has arisen (commit: 50ea9ba) where when extending a standard cluster with custom attributes, the standard genBasic attributes become unavailable from the zigbee2mqtt web interface.
The mechanism for expanding a standard cluster via a converter file turned out to be unclear.
Expansion is only possible through cluster.ts?