I am trying since a while to get all four rows of the 4-gang Busch Jaeger switch 6737-84 working in Home Assistant with a SkyConnect Zigbee dongle and ZHA.
ZHA pairs with the switch and it appears as device RB01.
But most often only the top row gets connected to ZHA and emits on/off events when I press the upper left/right buttons.
I reset the switch to factory settings, paired again and sometimes two or three rows are recognized, but never all four.
I tried to follow section ‘Bottom row of 4-gang device not bound’ of https://www.zigbee2mqtt.io/devices/6735_6736_6737.html: I.e.: unbinding the device from the ZHA controller ‘Silicon Labs EZSB’ and binding the four rows to four groups I created in ZHA.
I manage to unbind and subsequently bind to the groups but events do not get emitted when I press the buttons.
I noticed that the binding to the groups worked since the switch is not showing errors by blinking LEDs anymore after successful binding to the groups.
Did anyone get the 4-gang Busch Jaeger switch working with all four rows in HA with ZHA?
Zigbee devices that do not only use standard configuration and parameters (default ZCL clusters and attributes) but instead also implement custom manufacturer clusters and attributes (also known as “quirks”) will need a custom handler/converter/parser/translator as Python script code in the upstream “ZHA Device Handlers” library repository to extend custom manufacturer device “quirk” support for specific non-standard ZCL clusters and attributes (which Zigbee gateway implementations that depends on zigpy and the ZHA Device Handlers library, like Home Assistant s ZHA integration, then can make use of).
If you can not code that Python script code yourself to write the needed custom handler/converter/parser/translator for adding that specific device to the “ZHA Device Handlers” repository/library then suggest submitting a “device support request” (with device signature and diagnostic information) as new issues → https://github.com/zigpy/zha-device-handlers/issues
Without a “device support request” as a new issue posted to the “ZHA Device Handlers” repository/library requesting support for an unsupported device or device feature with Device signature and Diagnostic information the ZHA integration developers will not even know about the device unless they by random chance happened to have bought it themselves.
It might if you can read TypeScript/JavaScript and write Python code, but if you can not code that Python script code yourself to write the needed custom handler/converter/parser/translator for adding that specific device to the “ZHA Device Handlers” repository/library then suggest submitting a “device support request” (with device signature and diagnostic information) as new issues → https://www.home-assistant.io/integrations/zha#how-to-add-support-for-new-and-unsupported-devices