Added Zigbee2MQTT Busch-Jäger wallswitches

Ra72xx commented 9 months ago

Blueprint Checklist

[ ] You viewed the README and conformed to the naming conventions
[ ] You ordered the actions as stated in the README action order
[ ] All filenames are lowercase and uses '-' for spaces and not '_' while using {service-name}-{switch-name-or-type}.yaml format
[ ] Images are png
[ ] Image backgrounds are transparent and is cropped to the device boundries
[ ] Images has a maximum width of 800px and maximum height of 500px
[ ] There are no missing buttons or actions
[ ] Your integration/service is running on the latest version
[ ] You have tested your blueprints and made sure each button and action works

[ ] (older devices) You have ensured legacy is off/false for the device in the Z2M devices Settings (specific) page and that your actions matches those with legacy off?

This is my first pull request, so be patient if something is wrong.

This pull request adds support for the Busch Jäger 673x family of wall switches in Zigbee2MQTT

These switches are available as 1, 2 and 4 gang models. The blueprint assumes the 4 gang model, for the smaller models the additional rows are simply ignored.
The switches are available as battery- and mains-powered devices. Z2M does not make any difference here, so the blueprint does not, too.
If the switch is directly applied to Busch Jäger 6711U and 6715U in-wall relais/dimmer-elements, the top row is not programmable as it directly interacts with the device. The blueprint ignores this.
The "long press release" action is, at least in Zigbee2MQTT, the same for both sides of every rocker. As I don't know how to work around this limitation, this action is only editable for the left sides of the buttons.

Ra72xx commented 9 months ago

How would I get this change included?

Sian-Lee-SA commented 9 months ago

Everything seems fine and will be commited, thank you.