Busch Jäger Probleme

General
1

I don’t know if it’s better to write in German or English - that’s why I have chosen English :slight_smile:
I have following hardware from Busch-Jäger:
6711U Relay and the 8-way control panel 6737-84.
I was able to connect the devise to my Conbee III and I am also able to switch the light that has hard his on with key 2 and the off with key 1.
When tracing the reaction pressing any other key 3-8 I am getting following entries in the INFO Log:
16:37:29:977 [INFO] - Button 3002 - RM01, broadcast to: 0x0002, endpoint: 0x0B, cluster: SCENES (0x0005), action: Recall scene 3, payload: 020003, zclSeq: 53
16:37:31:191 [INFO] - Button 4002 - RM01, broadcast to: 0x0002, endpoint: 0x0B, cluster: SCENES (0x0005), action: Recall scene 4, payload: 020004, zclSeq: 54
16:37:32:355 [INFO] - Button 5002 - RM01, broadcast to: 0x0002, endpoint: 0x0C, cluster: SCENES (0x0005), action: Recall scene 5, payload: 020005, zclSeq: 55
16:37:33:461 [INFO] - Button 6002 - RM01, broadcast to: 0x0002, endpoint: 0x0C, cluster: SCENES (0x0005), action: Recall scene 6, payload: 020006, zclSeq: 56
16:37:34:473 [INFO] - Button 7002 - RM01, broadcast to: 0x0002, endpoint: 0x0D, cluster: SCENES (0x0005), action: Recall scene 7, payload: 020007, zclSeq: 57
16:37:35:507 [INFO] - Button 8002 - RM01, broadcast to: 0x0002, endpoint: 0x0D, cluster: SCENES (0x0005), action: Recall scene 8, payload: 020008, zclSeq: 58

But there lights/scenes that I have assigned to that key not reacting.

Is there something I did wrong?

Kind regards from a newbie…
Helmut

2

Hallo Helmut,
ich denke nicht das Du etwas falsch gemacht hast. Ich habe seit jahren 9 Busch Jäger Schalter mit dem Raspbee 2 in Benutzung. Bisher ohne Probleme. Zwischenzeitlich habe ich sowohl die Firmware als auch Phoscon aktualisiert.
Seitdem lassen sich keine Busch-Jäger schalter mehr in Phoscon konfigurieren. Weder die bestehenden, noch neue. Das scheint ein Fehler zu sein. Ich warte auch dringend auf eine Lösung.

PS. Das die oberste wippe des Schalters immer funktioniert ist normal. Diese sin nicht programmierbar.

Ich hoffe das bald das Problem gelöst wird.

Hier gab es schon ein ähnliches Problem:

Grüße Manuel

Hello Helmut,
I don’t think you did anything wrong. I have been using 9 Busch Jäger switches with the Raspbee 2 for years. So far no problems. In the meantime I have updated both the firmware and Phoscon.
Since then, Busch-Jäger switches can no longer be configured in Phoscon. Neither the existing ones nor new ones. This seems to be a mistake. I’m also urgently waiting for a solution.

P.S. It is normal that the top rocker of the switch always works. These are not programmable.

I hope that the problem will be solved soon.

3

Hello,
I have the exact same problem. Everything works fine, but I can not use any of the Busch Jaeger (BJ) RM01 (6736-8x) to control anything.
I can control the lights controlled by the 6 Busch Jäger via Zigbee/Phoscon, though. The top row switched the lights directly, this works as well. All additional Buttons are useless.

Setup:

What I did try to fix the problem and what is my understanding:

  1. Several remove (in phoscon) and pairing trials over several weeks. The pairing for the BJ failed most of the time
    … which did not help at all, so I tried to look into more detail

  2. I checked all the elements via the API for lights, groups, devices, sensors and it did not completely match what I saw in deCONZ and in phoscon
    e.g via http:///api//lights
    After trying to delete several via API I decided to …

  3. setup a complete new system and moved the conbee II to the new Raspi
    All already paired zigbee nodes came up - and everything except the BJ buttons did work.
    What was strange, they showed up incomplete, so some I got only a switch some only lights.
    So I tried to reconnect the BJ once again, it all seems to work. Pairing was immediate, and controlling the lights worked.
    I was able to connect a RB01 (4 Buttons, Two rows, Battery Controlled, no light attached) and the TOP ROW works, the SECOND ROW of buttons do not work.
    I repeated it with another RB01 → same result.
    → Now I have at least some buttons back to control lights.

Trying to use the SECOND ROW of buttons does not work for any of the 6 RM01.

What seems strange for all the RM01, in deCONZ I can see 2 Light Link Color Scene Controllers and the light Link Dimmable Light. In Phoscon I can assign 4 Button, instead of 2 Buttons (TOP ROW is direct light control via wire). I believe i used the correct type “QControl Unit 2-fold”

sample-RM01
sample-RM011920×1907 127 KB

4

Hi together
i have installed the recently released Firmware of the Zigbee stick and also the system update … but still nothing happens with my Busch Jäger … does anybody knows anything if it supposed to work again ? Any special treatment I might also need to do … thanks for any helping information.
BR Helmut

5

Hallo,

ich habe die gleichen Probleme mit den 6736 bzw 6737 und hatte mich deswegen auch an BJ Support gewandt, die Antwort lasse ich hier mal weg, weil war unterirdischen Nutzlos.
Deswegen habe ich mit Dresden Elektronik in Verbindung gesetzt und ihnen das Problem erklärt, nach einigem hin und her haben Sie mir heute mitgeteilt das dieses Problem vom Schaltereditor der Phoscon-app kommt und beim nächsten Update behoben werden soll.

Noch ein kleiner Tipp bis dahin, bei meinen 6737-84 kann ich die 3. Wippe im Schaltereditor frei zuweisen und es funktioniert;-)

Grüße Hoomi

Hello,

I have the same problems with the 6736 or 6737 and therefore had also contacted BJ Support, the answer I leave out here because was underground useless.
That’s why I contacted Dresden Elektronik and explained the problem to them, after some back and forth you told me today that this problem comes from the switch editor of the Phoscon app and should be fixed at the next update.

A little tip until then, with my 6737-84 I can freely assign the 3rd rocker in the switch editor and it works;-)

Greetings from Hoomi!

6

Can your please post in English?

7

That sounds good. I had also addressed the problem with Dresden Elektronik, but had not received any feedback. Where do we get the information if the problem has been solved?

8

Hi @Hoomer
i have installed the Version 2.25.3 that was released earlier this week but still not working ;-(
The BJ Switch was already paired and I have also removed the assignment to the scene and re-added it … still not working. Did you hear anything if 2.25.3 should solve the issue? I also not have seen any release note later than the one released for 2.25.1 on January 1st.
Any news are appreciated.
BR Helmut

9

Hallo,

Meine Versionen sind Gateway 2.24.2 Firmware 26780700 und App Version 1.8.52. (auf Android Handy)
Gestern habe ich die Belegungen der BJ’s im Schaltereditor nochmal gelöscht und danach so belegt wie ich es von Anfang an geplant hatte und Sie da es funktioniert:-).
Evtl. mal noch die App updaten und dann im Schaltereditor alles neu einstellen.
Als letztes Mittel würde ich evtl. noch probieren das gesamte System auf dem Raspi neu zu installieren.

@Brent
die Informationen kommen von Dresden Elektronik vom Software Developer Christian Haeseler.

Hier mal die Nachricht;

wir haben einen Fehler im Schaltereditor der Phoscon App gefunden, der dafür verantwortlich ist, dass die unteren Tasten des Busch Jaeger Schalters nicht korrekt mit Funktionen belegt werden können. Wir werden den Fehler in einer der nächsten deCONZ / Phoscon App Versionen beheben.

Mit freundlichen Grüßen / Best Regards

Christian Haeseler
Software Developer

Ich hoffe ich konnte Helfen

Hello,

My versions are Gateway 2.24.2 Firmware 26780700 and App Version 1.8.52. (on Android phone)
Yesterday I deleted the assignments of the BJ’s in the switch editor again and then assigned them the way I had planned from the beginning and you can see it works :-).
Maybe update the app and then reset everything in the switch editor.
As a last resort, I might try reinstalling the entire system on the Raspi.

@Brent
The information comes from Dresden Elektronik from software developer Christian Haeseler.

Here’s the message;

We have found an error in the switch editor of the Phoscon app, which is responsible for the fact that the lower buttons of the Busch Jaeger switch cannot be assigned functions correctly. We will fix the error in one of the next deCONZ / Phoscon app versions.

Sincerely / Best regards

Christian Haeseler
Software developers

I hope I could help

Hoomi

2 Likes
10

Any news on the release date, I’d also like to test (and of course use) it.

11

I installed the version 2.26.3 today. And I was finally able to assign the lower buttons again.
Thanks a lot for solving this issue.
Andreas

12

I seems that the change is only working for the RM devices and not for RB (with battery) devices. For the RM devices I am also able to assign the lower buttons. For the battery devices only the first row is working. The lower rows are not working. Can somebody confirm this?

13

I will check on the weekend, did not try it yet.

14

I can confirm RB lower row does not work.

I tried it with a 4 button Busch Jaeger battery switches (RB01). Assigning keys in the top row works. DeCONZ looks ok.
Top Row: Toggle / Next Scene
Lower Row: Scene Hell / Scene Ambiente

Top Row works. Even when assigning Scene Ambiente and Scene Hell.
No reaction on any keypress in lower row.

See screenshot attached.

image
image1920×1201 103 KB

15

it’s somehow frustrating… I am using Conbee III together with recent Firmware 26510900 and Gateway 2.26.3 - unfortunately non of the keys neither 2nd row, now 3rd row are reacting after I have done the programming.

image
image2660×646 77.6 KB

Could it be, that this has something to do with Conbee III ? My brother-in-law is also using BJ switches but he has Conbee II.

Is there a difference between 4-key and 8-key switches? My are all those without the batteries (power supply 230V)

Since December I a struggling here without any major step forward. … any further ideas???

BR Helmut

16

I believe you have battery powered switches (RB). I have 5 RBs. For me only the first row works on all of them, none of the others buttons work.

I also have the battery powered 8 button switch. For this one no button works for me. But I wanted to remove it and reconnect it first before I’m sure it is an actual problem.

Please check if your brother in law has battery powered (RB) or the “online” (RM) switches, so we can rule out it is related to the Conbee Version - I have a Rasbee II.

Andreas

PS: @Hoomer could you continue on your support thread with Dresden Electronik, that the problem still exists for battery powered switches.

17

The switch is “online” - means it get’s power from 230V cable. The one I have tested has on first row the hard connected switch to the light while row 2,3,4 supposed to be able to be programmed.
My brother-in-law has also those that are connected directly to 230V power - only need to check if he has the one with control hard with row 1 the connected lamp or if both rows freely programable - his switch only has 2 rows.

18

Sorry, I missed the 230V (online) information in your first post.

I setup in January a complete new system (see post above). Since I had some duplicates and missing configurations. But this did not solve the second row issue.

My current status - with Raspbee II:

  • The version 2.26.3 solved the second row issue for 230V connected switches only.
  • for my battery powered switches (4 Buttons) only the first row works.
  • my 8 button (battery) switch does not work at all (not sure if this is related)
19

Can you guys share the events of the switches on the api?

I want to know if this is a phoscon / rule engine issue or a zigbee issue.
In phoscon go to “help” and click " API information" . There’s one for “events”. If you click the buttons you should see responses.

Make sure to filter, because it can get a bit noisy if you have a lot of devices.

20

Doesn’t look like a zigbee problem to me - hope that helps.
Screenshot from deconz for the respective button attached as well.
I pressed the 4 buttons one after the other starting on the top left.

{
    "18:18:42:451": {
        "e": "changed",
        "id": "24",
        "r": "sensors",
        "state": {
            "buttonevent": 1002,
            "lastupdated": "2024-05-13T16:18:42.500"
        },
        "t": "event",
        "uniqueid": "d8:5d:ef:11:a1:00:2c:0d-0a-1000"
    },
    "18:18:44:70": {
        "e": "changed",
        "id": "24",
        "r": "sensors",
        "state": {
            "buttonevent": 1002,
            "lastupdated": "2024-05-13T16:18:44.120"
        },
        "t": "event",
        "uniqueid": "d8:5d:ef:11:a1:00:2c:0d-0a-1000"
    },
    "18:18:46:851": {
        "e": "changed",
        "id": "24",
        "r": "sensors",
        "state": {
            "buttonevent": 2002,
            "lastupdated": "2024-05-13T16:18:46.900"
        },
        "t": "event",
        "uniqueid": "d8:5d:ef:11:a1:00:2c:0d-0a-1000"
    },
    "18:18:49:702": {
        "e": "changed",
        "id": "25",
        "r": "sensors",
        "state": {
            "buttonevent": 3002,
            "lastupdated": "2024-05-13T16:18:49.750"
        },
        "t": "event",
        "uniqueid": "d8:5d:ef:11:a1:00:2c:0d-0b-1000"
    },
    "18:18:51:772": {
        "e": "changed",
        "id": "25",
        "r": "sensors",
        "state": {
            "buttonevent": 4002,
            "lastupdated": "2024-05-13T16:18:51.821"
        },
        "t": "event",
        "uniqueid": "d8:5d:ef:11:a1:00:2c:0d-0b-1000"
    },
    "18:18:57:893": {
        "e": "changed",
        "id": "24",
        "r": "sensors",
        "state": {
            "buttonevent": 1002,
            "lastupdated": "2024-05-13T16:18:57.940"
        },
        "t": "event",
        "uniqueid": "d8:5d:ef:11:a1:00:2c:0d-0a-1000"
    }
}

image
image960×1148 75.3 KB