Conflicting IDs for vendor-specific attributes on ubisys H1

[barnslig]

Hello!

I am currently trying to build a quirk for the vendor-specific features of the ubisys H1 thermostatic radiator valve.

The main quirk of the device is that it is re-using attributes on the Thermostat cluster. For example, attribute ID 0x0012 is the OccupiedHeatingSetpoint, as specified by ZCL. However, when reading/writing the same attribute with manufacturer ID 0x10F2, 0x0012 becomes the VacationMode - a complete different, vendor-specific attribute.

Is there a good way to implement such behavior? I found out that attribute IDs need to be unique inside the AttributeDefs of a ZHA cluster, as the IDs are used as dict keys. To circumvent this, I tried to rewrite the IDs inside _read_attributes and _write_attributes, but this seems rather tedious.

Furthermore, the vendor-specific attributes seem to support no reporting. So when I set an attribute via the Home Assistant UI, the UI is resetting the control after a few seconds. Is there anything I missed so that attributes are read after write?

There is a complete documentation for the Zigbee interface of ubisys H1 here: ubisys H1 Reference Manual.

Thank you so much for the great software! I am looking forward for your ideas

[TheJulianJES]

Zigpy will be refactored to properly support this soon: zigpy/zigpy#1719

There's also a related quirks PR here: #4658

There's already a workaround in place for some Frient devices, but it's a workaround and doesn't properly support everything. See this for reference: #4421
But it's not needed anymore soon.

[barnslig]

Very good to know! So probably I can rework my PR in the future: #4595