Aqara Opple 6 button switch in deconz 2.05.88

[ruabo]

Describe the question or issue you are having

Hi, I'm not able to receive events in HA after successful pairing in Phoscon. In developer tools deconz_event are not detected

Screenshots

Environment

Deconz 2.05.88

• Host system: Raspberry Pi 3
• Running method: Home Assistant 0.117.6 deCONZ Add-on 6.5.0 HassOS 4.16 Supervisor 2020.11.0
• Firmware version: 26390500
• deCONZ version: (2.05.88)
• Device: RaspBee I
• Is there any other USB or serial devices connected to the host system? Yes, Cyberpower UPS

deCONZ Logs

Additional context

While pressing opple button, other zigbee lights get activated. I tried to remove opple, stop deconz, remove from HA the device by calling service deconz.remove_orphaned_entries, reboot host but nothing. No entity are created for opple.

[Mimiix]

Probably pairing issues. I had this too on mine, after pairing it a few times it worked fine.

[arnvre]

Same problem here with Aqara Opple Switch 4 button. Similar issue as described in 2.05.85 (two buttons turn on or off all the lights and smart plugs connected) and is found in the Phoscon App. I'm not able to change the behavior of the buttons in Phoscon App nor in HAS. I tried resets, reconnects, reboot etc. Problem occurred after update deCONZ and firmware Conbee II.

Host system: Ubuntu 20.04
Running method: Home Assistant Container 0.117.6, deCONZ container
deCONZ version: 2.05.88
Device: Conbee II
Firmware: 26660700

[Maxtropos]

I‘m having the same issue in x.88 and x.85
New paired Aqara-Switches are controlling all lights paired to the Raspbee II, following the „standard“ Aqara-Opple Button Layout for direct light control. They do not trigger events anymore.
I re-paired 4 Switches ~10 Times to verify this behaviour.
I think, that deCONZ sets the switches from event-mode to command-mode and pairs them with every light this way. I don‘t know, how to reset this.

My home automation setup is broken by now, let‘s hope for a hotfix soon.

[BTCanada]

Same issue here with a WXCJKG13LM 6 button Aqara Opple switch. The device pairs successfully in Phoscon and it shows up as a device in Home Assistant. Pressing a button successfully updates the "Last Seen" time in deCONZ, but nothing is received by HA. The deCONZ addon log indicates that none of the buttons have handlers, and prints this when all six buttons are pressed in sequence:

12:08:07:051 [INFO] - No button handler for: lumi.remote.b686opcn01 endpoint: 0x01 cluster: ONOFF (0x0006) command: ON (0x01) payload[0]: 000
12:08:23:497 [INFO] - No button handler for: lumi.remote.b686opcn01 endpoint: 0x01 cluster: ONOFF (0x0006) command: OFF (0x00) payload[0]: 000
12:08:26:343 [INFO] - No button handler for: lumi.remote.b686opcn01 endpoint: 0x01 cluster: LEVEL_CONTROL (0x0008) command: STEP (0x02) payload[0]: 001
12:08:27:673 [INFO] - No button handler for: lumi.remote.b686opcn01 endpoint: 0x01 cluster: LEVEL_CONTROL (0x0008) command: STEP (0x02) payload[0]: 000
12:08:28:876 [INFO] - No button handler for: lumi.remote.b686opcn01 endpoint: 0x01 cluster: COLOR_CONTROL (0x0300) command: STEP_COLOR_TEMPERATURE (0x4C) payload[0]: 001
12:08:30:167 [INFO] - No button handler for: lumi.remote.b686opcn01 endpoint: 0x01 cluster: COLOR_CONTROL (0x0300) command: STEP_COLOR_TEMPERATURE (0x4C) payload[0]: 003

Host system: Windows 10
Running method: HassOS 4.17 in VM (Home Assistant 0.117.6, Supervisor 2020.11.0, deCONZ add-on 6.5.0)
deCONZ version: 2.05.88
Device: Conbee II
Firmware: 26670700

[SwoopX]

@BTCanada In you case, a file from deconz appears to be missing or cannot be found. Can you please share some log containingdeconz' start? 15-20 secs should be enough

[MarcelMertens]

Same issue here. After Updating to 2.06.xx from an older version (april/may 2020) most of my aqara switches are broken.
Some events are sent two times, reconnecting is close to impossible or same problems as Maxtropos

[BTCanada]

@BTCanada In you case, a file from deconz appears to be missing or cannot be found. Can you please share some log containingdeconz' start? 15-20 secs should be enough

@SwoopX Here's my deCONZ log during startup. Please let me know if you want the debugging log as well. Note that I have 9 Aqara temperature/humidity/pressure sensors and 2 Aqara water sensors connected that seem to work fine, though I seem to be getting No button handler for: lumi.weather messages now as well, which I don't recall seeing before.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] firmware.sh: executing... 
[10:01:51] INFO: GCFFlasher V3_16 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0     | 0x1CF1 | 0x0030  |            | ConBee II 
[cont-init.d] firmware.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] novnc.sh: executing... 
[cont-init.d] novnc.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[17:01:51] INFO: Running the deCONZ OTA updater...
[17:01:51] INFO: Starting udevd...
[10:01:51] INFO: Websockify waiting for VNC to start
[17:01:51] INFO: Running the IKEA OTA updater...
[17:01:51] INFO: Running the OSRAM LEdvance OTA updater...
[10:01:51] INFO: Waiting for device...
[10:01:55] INFO: Starting VNC server (local/yes)...
[10:01:56] INFO: Starting websockify...
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Flash security policy server
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900
  [10:01:58] INFO: deCONZ waiting for VNC to start
[10:01:58] INFO: Starting the deCONZ gateway...
QCoreApplication::arguments: Please instantiate the QApplication object first
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
10:01:59:287 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
10:01:59:289 CTRL. 3.27.210:01:59:296 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2217191-if00
[17:01:59] INFO: Starting Nginx...
2020/11/20 17:01:59 [notice] 321#321: using the "epoll" event method
2020/11/20 17:01:59 [notice] 321#321: nginx/1.14.2
2020/11/20 17:01:59 [notice] 321#321: OS: Linux 5.4.77
2020/11/20 17:01:59 [notice] 321#321: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2020/11/20 17:01:59 [notice] 321#321: start worker processes
2020/11/20 17:01:59 [notice] 321#321: start worker process 1475
10:01:59:305 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2217191-if00 / serialno: DE2217191, ConBee II
10:01:59:305 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
10:01:59:325 parent process s6-supervise
10:01:59:326 gw run mode: docker/hassio
10:01:59:326 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
10:01:59:326 DB sqlite version 3.27.2
10:01:59:326 DB PRAGMA page_count: 39
10:01:59:326 DB PRAGMA page_size: 4096
10:01:59:327 DB PRAGMA freelist_count: 0
10:01:59:327 DB file size 159744 bytes, free pages 0
10:01:59:327 DB PRAGMA user_version: 7
10:01:59:327 DB cleanup
10:01:59:327 DB create temporary views
10:01:59:330 started websocket server at port 8081
10:01:59:330 [INFO] - Found file containing button maps. Parsing data...
10:01:59:331 [ERROR] - Button map 'sunricherCCTMap' in JSON file has no assigned ModelIDs. Skip loading button map...
10:01:59:332 [INFO] - Button maps loaded.
10:01:59:332 dlg action: Read binding table
10:01:59:332 found node plugin: libde_rest_plugin.so - REST API Plugin
10:01:59:333 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
10:02:00:563 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
10:02:00:568 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2217191-if00 / serialno: DE2217191, ConBee II
10:02:01:574 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2217191-if00 / serialno: DE2217191, ConBee II
10:02:01:595 COM check bootloader
QObject::connect: Cannot queue arguments of type 'QTextBlock'
(Make sure 'QTextBlock' is registered using qRegisterMetaType().)
QObject::connect: Cannot queue arguments of type 'QTextCursor'
(Make sure 'QTextCursor' is registered using qRegisterMetaType().)
10:02:02:093 New websocket 172.30.32.1:35342 (state: 3) 
10:02:03:607 COM timout query bootloader, assume application
10:02:03:619 Device firmware version 0x26670700 ConBee II
10:02:03:625 unlocked max nodes: 200
10:02:03:742 Device protocol version: 0x010D
10:02:03:749 new node - ext: 0x00212effff05de74, nwk: 0x0000
10:02:03:756 SensorNode 2 set node 0x00158d000549af7b
10:02:03:756 SensorNode 3 set node 0x00158d000549af7b
10:02:03:756 SensorNode 4 set node 0x00158d000549af7b
10:02:03:757 SensorNode 7 set node 0x00158d00057912c9
10:02:03:757 SensorNode 6 set node 0x00158d00057912c9
10:02:03:757 SensorNode 5 set node 0x00158d00057912c9
10:02:03:757 SensorNode 8 set node 0x00158d000548a4ab
10:02:03:757 SensorNode 9 set node 0x00158d000548a4ab
10:02:03:757 SensorNode 10 set node 0x00158d000548a4ab
10:02:03:758 SensorNode 11 set node 0x00158d00049db043
10:02:03:759 SensorNode 12 set node 0x00158d00049e798a
10:02:03:759 SensorNode 13 set node 0x00158d000578e328
10:02:03:759 SensorNode 14 set node 0x00158d000578e328
10:02:03:759 SensorNode 15 set node 0x00158d000578e328
10:02:03:760 SensorNode 25 set node 0x00158d000578a8de
10:02:03:760 SensorNode 26 set node 0x00158d000578a8de
10:02:03:760 SensorNode 27 set node 0x00158d000578a8de
10:02:03:760 SensorNode 16 set node 0x00158d00054c6801
10:02:03:760 SensorNode 17 set node 0x00158d00054c6801
10:02:03:760 SensorNode 18 set node 0x00158d00054c6801
10:02:03:761 SensorNode 19 set node 0x00158d00054c67e3
10:02:03:761 SensorNode 20 set node 0x00158d00054c67e3
10:02:03:761 SensorNode 21 set node 0x00158d00054c67e3
10:02:03:761 SensorNode 22 set node 0x00158d00054c6834
10:02:03:761 SensorNode 23 set node 0x00158d00054c6834
10:02:03:762 SensorNode 24 set node 0x00158d00054c6834
10:02:03:762 SensorNode 29 set node 0x00158d0005489bc2
10:02:03:762 SensorNode 30 set node 0x00158d0005489bc2
10:02:03:762 SensorNode 28 set node 0x00158d0005489bc2
10:02:03:762 SensorNode 32 set node 0x04cf8cdf3c7d35b3
10:02:03:835 Current channel 15
10:02:03:860 CTRL ANT_CTRL 0x03
10:02:03:896 Device protocol version: 0x010D
10:02:03:974 Current channel 15
10:02:04:001 CTRL ANT_CTRL 0x03
10:02:04:284 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
10:02:04:284 GW firmware version: 0x26670700
10:02:04:284 GW firmware version is up to date: 0x26670700
10:02:04:866 LightNode 1: Configuration tool 1 added
10:02:05:161 Announced to internet https://phoscon.de/discover
[10:02:09] INFO: Successfully send discovery information to Home Assistant.
10:02:13:303 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0402 command: 0x0A payload[0]: 000
10:02:13:304 ZCL attribute report 0x00158D00057912C9 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:13:317 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0405 command: 0x0A payload[0]: 000
10:02:13:318 ZCL attribute report 0x00158D00057912C9 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:13:323 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0403 command: 0x0A payload[0]: 000
10:02:13:323 ZCL attribute report 0x00158D00057912C9 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:20:403 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0402 command: 0x0A payload[0]: 000
10:02:20:404 ZCL attribute report 0x00158D000548A4AB for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:20:415 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0405 command: 0x0A payload[0]: 000
10:02:20:416 ZCL attribute report 0x00158D000548A4AB for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:20:420 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0403 command: 0x0A payload[0]: 000
10:02:20:421 ZCL attribute report 0x00158D000548A4AB for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:26:407 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0402 command: 0x0A payload[0]: 000
10:02:26:408 ZCL attribute report 0x00158D00054C6834 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:26:416 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0405 command: 0x0A payload[0]: 000
10:02:26:416 ZCL attribute report 0x00158D00054C6834 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:26:420 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0403 command: 0x0A payload[0]: 000
10:02:26:420 ZCL attribute report 0x00158D00054C6834 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:45:275 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0402 command: 0x0A payload[0]: 000
10:02:45:276 ZCL attribute report 0x00158D000578A8DE for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:45:287 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0405 command: 0x0A payload[0]: 000
10:02:45:287 ZCL attribute report 0x00158D000578A8DE for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:45:292 [INFO] - No button handler for: lumi.weather endpoint: 0x01 cluster: 0x0403 command: 0x0A payload[0]: 000
10:02:45:292 ZCL attribute report 0x00158D000578A8DE for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
10:02:59:295 Current channel 15
10:02:59:307 Device TTL 1481 s flags: 0x7

[VoyteckPL]

Same here...

[Maxtropos]

Could we change the issue label to bug report then?

[ruabo]

@ Mimiix

Probably pairing issues. I had this too on mine, after pairing it a few times it worked fine.

no matter how many times I try, It ends the same way

[BTCanada]

I downgraded to 2.05.84 (HA add-on 6.4.1) and the switch now works properly. It looks like either something got lost when I upgraded to 2.05.88, or some bug was introduced.

[VoyteckPL]

How can I downgrade in HA? Any guides online? Thanks

[ruabo]

I need those instructions too ! Thanks

[MarcelMertens]

Also downgraded:

ConBee II Firmware 26660700 -> 26650700
Deconz 2.06.00 -> 2.05.84

Repairing now works, switch works.

Deconz downgrade for Ubunutu

wget http://deconz.dresden-elektronik.de/ubuntu/stable/deconz-2.05.84-qt5.deb
sudo systemctl stop deconz
sudo apt install /path/to/deconz-2.05.84-qt5.deb
sudo systemctl start deconz

[VoyteckPL]

Is that even possible on Hassos?

[BTCanada]

It is possible from HA, though unfortunately the only way I know of doing it is by restoring an old HA snapshot, so you have to have a snapshot that includes that version. Fortunately, you can just restore deCONZ from the snapshot rather than restoring the whole thing:

[VoyteckPL]

Nice. Unfortunately I don't have any backups... Any chance you could upload it do I could restore deconz only from your snapshot?

[VoyteckPL]

Or perhaps make a backup with deconz only for your privacy? I would be trully grateful!

[BTCanada]

There are quite a few files in the deCONZ snapshot. Any idea what's core vs configuration? I don't particularly want to stick my deCONZ database online.

[VoyteckPL]

Understand. Maybe you could mail it?

[BTCanada]

Not without anonymizing it, if we can figure out how. Better yet would be for whatever is causing this to get fixed in a deCONZ update, since it looks like numerous people are affected.

[VoyteckPL]

Sure

[VoyteckPL]

How often are Deconz update released? Is there any chance for a quick hotfix from this company?

[SwoopX]

Tough week. Releases are usually done on a monthly basis (check the repo readme). However, we can ofc shoot out hotfixes way faster if required. And for that, we first need to pinpoint the issue here.

I've seen things in @BTCanada's log data which doesn't really fit together. This comment here #3670 (comment) indicates the maps for the buttons are not loaded, so the zigbee commands cannot be translated. Here #3670 (comment) , deconz startup says it loaded the maps alright however (lines contain [INFO] after the timestamp).

The only reason for that I can think of is an older version of button_maps.json, which does not get updated due to whatever reason during the update. Can anybody having the issue with 2.06.00 search for the file withing the container and share it here to double check?

[BTCanada]

@SwoopX Ok, dumb question: how do I get button_maps.json out of the container so I can post it here? I found it and tried copying it directly from the addon_core_deconz container to the homeassistant container so I could access it though my HA samba share, but apparently docker doesn't support copying between containers. Trying to copy it first to a directory on the HassOS host tells me my file system is read-only. I tried apt-get install sftp and apt-get install smbclient in the deconz container and they both claimed the package was unable to be located.

[BTCanada]

Some progress here: I managed to grab button_maps.json from the container (for anyone else trying this, you can't write to /root when logged in as root on HassOS, apparently, but you can write to /tmp). After grabbing the 2.5.84 version of the file I re-updated to 2.5.88 and grabbed that one as well for comparison. However, the switch now works in HA with no modifications, and is no longer throwing No button handler events. It looks like something was messed up with my install, and downgrading to a previous snapshot and then re-upgrading to the latest fixed it.

[VoyteckPL]

Really weird...can we expect a hotfix soon?

[Mimiix]

@VoyteckPL I can arrange one, but i would need a good reason for it to push one ahead. I have one on the 30th this month, so i'd like to stick with that. But we need to have a PR done with a fix before that.

[VoyteckPL]

Good reason is that these buttons do not work :) I had to go with Z2M instead of Deconz because this switch is crucial for my house. It's in the kitchen and serves of the lights and my wife is not happy ;) Wife is a good reason :D Please, fix it, I also have Lonsonho 4 gang zigbee switch and it also doesn't work as expected....

[VoyteckPL]

I'd love to try 2.7.0 beta but how do I install it on Hassos?

[manup]

Ah ok, sorry I missed that part. Hassos uses the stable branch of deCONZ. The next stable version which includes these fixes will be released in roughly a week from now.

[VoyteckPL]

New version works perfect! Thanks!

[Mimiix]

@ruabo Can you let me know if its fixed :)?

[ruabo]

I'll try tomorrow when I'll be back home

[thkall]

Hi Guys, i have the same issue also with v2.7.1 after downgrade to 2.05.84 all works fine.

[thkall]

i have done some tests:

1. add new Opple 6 button Switch with deconz 2.05.84 = works
2. update to 2.7.1 = don't work
3. downgrade to 2.05.84 = don't work
4. Stop deconz instance, delete objects, start instance = works again

[manup]

Did you also press the setup button 'C' on the back?

[thkall]

only the first time for 5 s when i added the switch

[manup]

Can you please press it again, by doing so deCONZ should configure the switch to the correct mode so that button events are fired properly.

[thkall]

ok i've check that
from working 2.05.84:
update to 2.7.1 = don't work
press C Button for 5 s = don't work
Back to 2.05.84 = works again
I think that i stay at 2.05.84 for one or two month and then check it again. My wife needs that switch and that is a greater problem for me than an old Version ;-) Thanks manup

[SwoopX]

Would be interesting to see which value the device has for the marked attribute on the Lumi specific cluster (should have been set to 1, you might need to push a button prio to being able to read it)

[Jan1503]

@SwoopX So the mode should be 1, right?
I was finally able to add the switches before I did the update but I can't read the flags from the switch even if I push some buttons to wake it up.
But i think it must be 1 cause it works as expected. Mode 0 seems to be the one that switches all lights.

[SwoopX]

Yes, indeed. So what's then not working?

[Jan1503]

It's fine, just wanted to say I'm not able to read the config, but that seems to be another issue...
As I said last week, I was able to pair the switches after hammering F5 and pushing the C-Switch on the back in chaotic order ;)

[Mimiix]

ok i've check that
from working 2.05.84:
update to 2.7.1 = don't work
press C Button for 5 s = don't work
Back to 2.05.84 = works again
I think that i stay at 2.05.84 for one or two month and then check it again. My wife needs that switch and that is a greater problem for me than an old Version ;-) Thanks manup

Are you using iobroker?

[thkall]

oh sorry i forgot to mention that: I use iobroker with deconz on a headless pc running ubuntu server 20.04. But i thinks that is the same behavior.

[arnvre]

Thanks guys. Great work!

I had the same problem, see one of the first posts. I have Ubuntu and dockers. I got it working again by.

1. Updating to 2.7.1.
2. Udating to latest firmware of Conbee II 26680700
3. Pairing the switch in Phoscon by holding the C till connected
4. All lights and power plugs turned off by pressing one button (same problem since deCONZ version: 2.05.88)
5. Give the C button a short press. Lights stopt reacting to pressing a button.
6. Restart deCONZ docker
7. Home Assistant (118.5) integrations reload Phoscon
8. Aqara switch worked like before and is following my Home Assistant settings again

I think the short press C helped me to change a modus of the switch, which is needed after pairing.

[Mimiix]

oh sorry i forgot to mention that: I use iobroker with deconz on a headless pc running ubuntu server 20.04. But i thinks that is the same behavior.

Then that's your issue. There's issues with iobroker above 2.5.84.

[aleph37]

I think the short press C helped me to change a modus of the switch, which is needed after pairing.

Short press C after pairing did the Job! Thank you very much!

[ruabo]

@Mimiix Working for me ! Thanks
@arnvre from step 3 I followed the same path

[ruabo]

just a doubt: I only see in Devices

and nothing in entities:

Is this the exptected behaviour ?

[arnvre]

Is this the exptected behaviour ?

In my entities I've the sensor.opple_switch_2_gang_battery_level

Did you select all the deCONZ options in Home Assistant integrations?

[Mimiix]

Yes. You need to use the events for automations.

Anyway case closed :)

[rvsoftz]

I think the short press C helped me to change a modus of the switch, which is needed after pairing.

Short press C after pairing did the Job! Thank you very much!

This small step saved my day :) Working with latest version in Hassio