ubisys S1, S2 WIP

[FlorianBruckner]

Proposed change

Manufacturer specific cluster for ubisys devices for device configuration as requested in #3942

Additional information

see https://www.ubisys.de/wp-content/uploads/ubisys-s1-technical-reference.pdf and https://www.ubisys.de/downloads/ubisys-input-configuration-integrators-guide.pdf

Checklist

• The changes are tested and work correctly
• pre-commit checks pass / the code has been formatted using Black
• Tests have been added to verify that the new code works

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.00%. Comparing base (b87ac89) to head (e8bcd45).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #3959   +/-   ##
=======================================
  Coverage   91.00%   91.00%           
=======================================
  Files         328      328           
  Lines       10656    10656           
=======================================
  Hits         9698     9698           
  Misses        958      958           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[FlorianBruckner]

Dear @TheJulianJES, Dear @puddly

I have started with a device handler for my ubisys devices to allow for device configuration. Unfortunately I am stuck and hope to get some help from you.

The documentation (https://www.ubisys.de/wp-content/uploads/ubisys-s1-technical-reference.pdf) defines the attributes as

This attribute is an array (ZCL data type 0x48) of 8-bit data (ZCL data type 0x08).

and

This attribute is an array (ZCL data type 0x48) of raw binary data (ZCL data type 0x41).

How would I declare these attributes and what would be the format (in the UI) for input and output? Or is this approach unfit for this purpose anyway and you would suggest a different one?

[puddly]

The cluster commands and attributes need to be defined either way, regardless of how entities interface with them.

The ZCL array type define the data type dynamically so you can just specify the type as Array (there are other instances of this in the codebase).

Each array element seems to encompass two bits of configuration: disabling the input and inverting its logic level. I guess you can skip the input disabling part and just provide dropdowns to select the logic level? On the other hand, this can also easily be done in an automation.

I don't believe we have an API yet to process the value of an attribute bidirectionally, when creating a v2 quirk entity.