You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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
AttributeDefsof a ZHA cluster, as the IDs are used as dict keys. To circumvent this, I tried to rewrite the IDs inside_read_attributesand_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
Beta Was this translation helpful? Give feedback.
All reactions