Re-add GenScenes cluster to Busch-Jaeger RM01

[asmolarczyk]

Hi, until now I'm using Deconz to manage my zigbee network, but I would like to use zigbee2mqtt instead.

I own a lot of Busch-Jaeger RM01 switches. These switches are working quite good in deconz and I tried to get the same experience in z2m. In my deconz setup, I bound the GenScenes cluster of all EPs to my groups and used the automatically created/recalled scenes (I removed all other bindings).
In z2m this is also working fine for the first row, but unfortunately for the other rows, the GenScenes cluster was removed intentionally:

zigbee-herdsman-converters/src/devices/busch_jaeger.ts

Line 95 in 44b8acb

// In order to be able to toggle groups, we need to remove the scenes cluster from RM01.

I wonder whether it is possible to re-add it with a custom converter js?! An hints? Thank you!

[asmolarczyk]

For testing purposes I cloned zigbee2mqtt and zigbee-herdsman-converters and removed the dropScenesCluster code.
I am now able to bind genScenes to of all endpoints to my zigbee groups (after removing bindings to the coordinator). The buttons recall scenes 1, 2, 3... and so on of the groups. I really like this solution, but of course modifying the existing code is rather ugly, therefore I would like to use a custom converter approach (alternatively you might remove the dropScenesCluster code?!?).
Thank you!

[klada]

AFAIR I did some testing with this a while ago and if I remember correctly I also could not see any downsides when keeping the cluster. Just like you I never fully understood why this was needed in the first place so I'd give this a try again.

I have access to all combinations of Busch-Jaeger devices. I'll be able to perform some more tests next week and report back.

The only thing we need to be careful about is the amount of bindings we create when configuring the device. Their memory is very limited and I'd like to not create bindings for the genScenes cluster by default.

[asmolarczyk]

not create bindings for the genScenes cluster by default

This makes perfect sense! The default bindings to the coordinator work just fine for a standard user. Having the possibility to bind to the GenScene cluster is an advanced scenario...

Altought setting/recalling scenes work just fine after the change, a warning is logged, when a button is pressed, e.g.: z2m: No converter available for '6735/6736/6737' with cluster 'genScenes' and type 'commandRecall' and data '{"groupid":1,"sceneid":3}'

Do you have any idea how to deal with this? I haven't found any sample code for custom converters handling this kind of messages.

[klada]

Do you have any idea how to deal with this? I haven't found any sample code for custom converters handling this kind of messages.

You would need to add the converter for this message to fromZigbee. I think what we need here should be fz.command_recall but I am on the phone right now and cannot verify this.

[klada]

I ran some tests without the dropScenes code and it still worked for me.

@asmolarczyk Could you please try this custom converver:

https://gist.github.com/klada/3dc7918299fd9d365c5fd2e72bd98400

Simply put it into external_converters in your zigbee2mqtt data directory, restart zigbee2mqtt and remove/repair a Busch-Jaeger device.

Does it work properly and did the "No converter available" message go away? Whenever you activate a scene you should also see this command through MQTT.

In my environment I am running into different issues now with these BJ devices (the infamous TABLE_FULL message comes too early), but this is unrelated to the changes I made to the converter.