Busch-Jaeger once more

[afoeder]

There is still some unadressed issues with the Busch-Jager 6735/6736/6737; to get a gist check this archived discourse thread that adresses #879.

The double-row items so far work as intended on a 6710 U, 6711 U and 6715 U (i.e. the power supply device, the relais device and the dimmer device; in the meantime I own all of them).
However, when trying to use the four-row control panel on a 6710, I can observe the actions for the top three rows (i.e.
row_1_off, row_1_down, row_1_stop, row_1_on, row_1_up etc).
The fourth row doesn't emit and their LED indicator blink when pressing, while the first three who do emit actions just briefly light a single time to indicate acknowledgement.

It feels like the fourth row is still in some scene thingie mode.

Is there some swarm knowledge here in the meantime who got any further information? Unfortunately the main contributor of the Busch-Jaeger devices @docbobo seems to be not available anymore :( // edit: thanks @docbobo!

[docbobo]

The blinking means that the row is not bound to anything. In that mode, you should be able to store a particular scene on the button, as described in the manual. Luckily for you, I just had the same problem when I was looking into what you were just describing.

The problem with the Busch Jaeger devices is that they have very limited memory. With the two or one row versions that hardly an issue, but with the 4 row version it's a problem.

Anyway, I had the same problem and the zigbee2mqtt UI was showing correct bindings. I removed the binding for Source EP 13 (row 4), and then created a new one binding Source EP 13 to Coordinator/LevelCtrl. Blinking stopped. I also see row_4_on and row_4_off events in HA.

BTW: You should be able to also unbind any other row to get into the "scene programming" mode. If you unbind e.g. EP 11 (2nd row), it should be possible to store a scene as described in the switches manual.

[afoeder]

oh thanks a lot! I've mentioned you here and there in other issues without luck, therefore I assumed you were "lost" :)

I gotta admit that I don't fully understand what you're saying yet, I seem to lack some basic (protocol) knowledge. Could you please elaborate on particularly

• zigbee2mqtt UI was showing correct bindings

  where can I see those bindings? I checked the doc page but I cannot find anything related in the UI

• Source EP […] Coordingator/Level Ctrl

  what's EP? and what's Coordinator/Level Ctrl?

Thanks for taking the time to explain it to me (feel free to add some screenshots, that'd be highly appreciated); and I commit on adding this information to the respective Doc page (like a new chapter "common issues" for the Busch-Jaeger items).

[docbobo]

I am definitely not gone for good but the time required for things like this has been lost to other important stuff. That said, @Koenkk is probably much better suited to explain all the details of zigbee, so I'll limit my response to what I believe is need to help you out.

Every zigbee device exposes its capabilities through a set of endpoints (EP). The capabilities themselves are grouped into clusters and each device indicates the clusters that are acceptable as either input or output of a particular endpoint. For example, a 6737 running on an in-wall power adapter expose endpoints 10, 11, 12, 13 which represent the individual rows on that switch.

Binding sets up a relation ship between two different endpoints on different devices or groups. For example, you could bind the OnOff cluster of ep 10 (on a 6737) to the OnOff cluster of endpoint 11 of a hue bulb. As a result, you can use the first row of the 6737 to turn the hue bulb on and off, even if Home Assistant is not running.

Now back to your problem. When you click on the Busch Jaeger device in the zigbee2mqtt UI, you'll get something similar to this:

Clicking on the "Bind" tab will lead to this:

There is a row for Source EP 13, which corresponds to the fourth row on the switch.

• Click on unbind to remove the binding - the row should disappear.
• Afterwards, select 13 in the Source EP field at the bottom, select Coordinator as Destination. Keep the Destination EP at 1 but select LevelCtrl as Cluster.
• Press the blue bind button.

If binding is successful a new row with the binding should appear. Theoretically, things should work at this point.

BTW: Some of the things I described in the beginning are nicely visualized under the Cluster tab.

[afoeder]

I skipped your ideas with reversing the loop and repairing the device and directly tried recreating all the bindings manually one after another via the GUI and this worked! 🥳 Now all four rows are emitted!
Having said this, do you think it would help to add a 300ms-ish delay in the binding code when pairing the devices?

For the background, is there some doc/literature on what the "Coordinator" is and what the Clusters refer to? Are the clusters defined by zigbee (protocol) or is it an z2m "invention"?

(I hope this doesn't sound like an excuse)

don't you dare to excuse for what you did in your free-time and what helps other guys who gave an arm and a leg to unleash capabilities of these overpriced Busch-Jaeger devices! :)

[afoeder]

btw it's "funny" (weird?) that Busch-Jager decided to not emit the actions of the top row when there's a Dimmer or Relais attached: just why not doing it anyways, it won't hurt if it's not listened to…

[docbobo]

First of all: glad to hear that it's working.

Having thought about this further, I believe that this is related to the comment that you can also see in the code:

// The total number of bindings seems to be severely limited with these devices.
// In order to be able to toggle groups, we need to remove the scenes cluster
const index = endpoint.outputClusters.indexOf(5);
if (index > -1) {
    endpoint.outputClusters.splice(index, 1);
}

I have this nagging feeling that this was added specifically to address the issue with the fourth row not being configured properly. However, it stopped to work exactly the way it's supposed to work since then, but once you recreate the binding it takes effect. Not sure if this timing related to just due to internal code changes.

And yes, it's completely annoying that dimmers and relays don't emit events on the first row. That's why I replaced almost all of my relais...

[Joe3n]

@docbobo Could you post a picture of your binding of a 6711U, preferable with a 6735 (if you have it). I have some problems with it like descripted in Ticket #7077

[blib-blub]

Sorry for necroing a nearly 4 year old thread, but it seems I somehow managed to get my BJ 6737 (4 rockers) to emit zigbee events on the first row despite being on a 6711U Relais and no longer causing Relais switching on the 6711U. I am currently using them in Deconz managed by HA and I am in the process of migrating to Z2M.

At some point I rewired some of the Relais outputs to be no longer connected and hardwired the lights to be permanently supplied. (Son likes to push the wrong buttons... ;)). It does not work on all of the rewired switches, so I am not sure if the order of rewiring / pairing or some other thing caused them to behave that way. But there seems to be some mode that the switches can enter to be "fully Zigbee" even on a 6711 Relais. Do you maybe know anything about this?

[FloW990]

Hi there,

I have the same problem that afoeder had. (the buttons in row four do not work).
Unfortunately, I am not very knowledgeable about programming.
I would like to use z2m in combination with node-red.
Now I have already tried the z2mAssistant in use with Docker, unfortunately the server is displayed there as not connected. (although the top three buttons go into node-red at the same time?).
I would be very happy if the exact procedure for the new binding of the buttons would be explained here again. (gladly for dummies) :)
Thank you for the fantastic work everyone has done here since then
Greetings Flo