Zigbee - can't use xiaomi aquara wireless mini switch

Setup, Configuration and Use Beginners
,
1

Hi community!

I’m new to home automation and OpenHab and got stuck at adding a zigbee xiaomi aquara wireless mini switch.
I’m currently running a brand new openHabian on a raspberry pi 4 (4GB Ram version). Open Hab is on version 2.5.5-1 (Release build).

I managed to install the zigbee binding and adding my Qivicon (Telegesis) Zigbee usb stick. This also seems to work fine as a hue lamp and a aqara door sensor were found immediately and are responsive.

Now I’m trying to add my wireless mini switch but got stuck there: When I reset the switch and search for things it mostly finds only a “Unknown ZigBee Device 00158D00028F5821”. After a few seconds (if I’m lucky) it tends to recognize it as a “LUMI lumi.remote.b1acn01” which I can add as a thing. But now its status is OFFLINE - HANDLER_INITIALIZING_ERROR No supported clusters found. It doesn’t have any channels so I’m now rather stuck.

I found some people with problems regarding the xiaomi mini switch but no conclusion how to fix it:
here
here

Some sources say you have to prevent it from going to sleep during initialisation by continually short pressing the button. I tried this with both the small reset button and the actual big button but to no avail yet.

The log also doesn’t seem to help a lot:

2020-06-20 20:36:20.454 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D000450E871: Starting ZigBee device discovery
2020-06-20 20:36:20.459 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zigbee:device:05000770:00158d000450e871' to inbox.

2020-06-20 20:36:20.460 [home.event.InboxAddedEvent] - Discovery Result with UID 'zigbee:device:05000770:00158d000450e871' has been added.
2020-06-20 20:36:22.292 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_telegesis:05000770' has been updated.


2020-06-20 20:36:26.517 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D000450E871: Starting ZigBee device discovery
2020-06-20 20:36:39.567 [WARN ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D000450E871: No supported clusters found

2020-06-20 20:36:39.487 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zigbee:device:05000770:00158d000450e871' has been removed.
2020-06-20 20:36:39.521 [hingStatusInfoChangedEvent] - 'zigbee:device:05000770:00158d000450e871' changed from UNINITIALIZED to INITIALIZING
2020-06-20 20:36:39.543 [hingStatusInfoChangedEvent] - 'zigbee:device:05000770:00158d000450e871' changed from INITIALIZING to UNKNOWN
2020-06-20 20:36:39.572 [hingStatusInfoChangedEvent] - 'zigbee:device:05000770:00158d000450e871' changed from UNKNOWN to OFFLINE (HANDLER_INITIALIZING_ERROR): No supported clusters found
2020-06-20 20:36:39.578 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:05000770:00158d000450e871 changed to UNKNOWN.

Is there meanwhile anyone who managed to use those switches? How did you do it?

Thank you very much in advance!

2

I get the same. This one is not currently supported.
There is two versions of this button. I belive it is the older one that is supported.

3

I suspect that you have not enabled debug logging? That may help to know what services this device reports.

4

hmm, all I can get from the button is: Unknown ZigBee Device 00158D00028F4669

Relevant Wireshark filter:
zbee_nwk.src == 0xd392 || zbee_nwk.dst == 0xd392

logfile: https://srv-file18.gofile.io/download/aiXTed/openhab-aqarabutton.log
pcap: https://srv-file18.gofile.io/download/aiXTed/aqara-button.pcapng

5

Thank you for your replies!

I now enabled following debug logging and it generated a huge pile of log entries:

log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee

You can find the corresponding log file here https://gofile.io/d/kBIhBP (as a new member I can’t upload files therefore i had to host it on an external hoster)

I appreciate your help although I start to believe that it is a lost cause

EDIT: Meanwhile I upgraded my test system to the newest build (openHAB 2.5.6~S150-1 (Build #150)) to see if support of the switch has been added recently but it is still the same.