No Aqara Switch work with 2.23.X

[rweise]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

After updating to any version higher than 2.31.2 not one of my different Xiaomi switches works anymore. I try 2.32.0 /1 /2. I use Aqara single buttons, 1,2 and 4-button wall switches, and not one works with 2.32.0 and above.

Steps to reproduce the behavior

Install Version ...

Expected behavior

Deconz shows all switches as connected, but no signal goes to iobroker or back

Screenshots

No response

Environment

• Host system: (Raspberry Pi / PC / NAS / MAC)
• Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / deconz-docker container / Windows / Virtual Machine)
• Firmware version: (26xxyy00)
• deCONZ version (not Home assistant Addon version!): (2.xx.yy)
• Device: (ConBee I / ConBee II / ConBee III / RaspBee I / RaspBee II)
• Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II/III
• Is there any other USB or serial devices connected to the host system? If so: Which?

deCONZ Logs

No response

Additional context

No response

[Smanar]

Ha ?
This is something new. how are you using them ? in stand alone with third app and looking for state/buttonevent or using Phoscon stuff ? (with group)

Can you try to take a look in event when using them in Phoscon/help/API information/events ?

[MrSolo570]

Hello,

I think I have the same issue.
setup: RP4, conbee III, Home Assistant and deconz-addon.

I have two Aqara Wall Switches H1 with neutral Wire, this model: https://zigbee.blakadder.com/Aqara_WS-EUK01.html

One works like a charm for 3 years now, it is set to decoupled mode and spawns button events in Home Assistant.
The second one a visitor recently reset by mistake by pressing the button for too long. Now I wanted to re-pair it with my setup, but the pairing does not work anymore. I deleted the whole device multiple times and rebooted the system.
Issue:
starting to pair as a wall switch seems to work (a new switch shows up) but it also generates a new light (in section lights) that is not reachable. shortly after pairing the switch becomes unavailable for some minutes and shows up available again. Also the pairing on the wall switch never finishes, the blue light at the wall switch keeps flashing quickly for ever despite phoson/deconz telling me that the pairing is finished. Via Rest API I set the device into decoupled mode (which works) but it does not spawn any button events in Home Assistant anymore. In wired mode there are not button events either. Despite that I can use Home Assistant to control the button (on off works) but decoupled mode is out of the question with that. Energymeter does not work either.

When I compare my identical working wall switch with my "broken" one the DDF file in deconz looks hughely different and there are different options available.. also with the working wall switch deconz manages to show a software-version, which is not the case for the not working wall switch (software version just empty).

I did not find the time yet to test this with an older software version of deconz... I think something is broken with the pairing process, as my other wall switch clearly still works.

edit:
another thing I noticed when pairing it for the 5th time today. sometimes the pairing inside deconz finishes and the new wall switch gets displayed, but when you click somewhere else and come back after a minute or so, the wall switch is just gone from the configuration. as if it never was there. this does not happen with every pairing process but it forces my suspicion that the pairing process is somewhat broken for that switch....

[Smanar]

When I compare my identical working wall switch with my "broken" one the DDF file in deconz looks hughely different and there are different options available.. also with the working wall switch deconz manages to show a software-version, which is not the case for the not working wall switch (software version just empty).

Hello, can you share the 2 json to compare ?

From the actual DDF for the "lumi.switch.l1aeu1" (and no update since 1 years ...), You need to have a "light" entry and a "sensor " entry (a ZHASwitch).

I m searching a recent change on the code that can impact thoses device, but I don't found something ....

So 2.31.0/1 is working but problem after 2.31.2 ? Perhaps the problem is not in the API code but direclty deconz one ?

[MrSolo570]

its true, for the working sensor it also created a light entity, so that was a mistake on my side. idk why, but copying from VNC doesnt work anymore with my setup (neither linux nor windows VNC client manages to copy) so this is what I get from using the rest API:

not working wall switch:

 "237": {
    "capabilities": {
      "sleeper": false
    },
    "config": {
      "clickmode": "coupled",
      "devicemode": "compatibility",
      "ledindication": true,
      "on": true,
      "reachable": true
    },
    "ep": 41,
    "etag": "d85a6dc92ecea77138aff21945646aee",
    "lastannounced": "2026-01-02T08:22:08Z",
    "lastseen": "2026-01-02T10:51Z",
    "manufacturername": "LUMI",
    "mode": 1,
    "modelid": "lumi.switch.n1aeu1",
    "name": "Wandschalter Zwei",
    "nwkaddress": "0xA14D",
    "state": {
      "buttonevent": 0,
      "lastupdated": "none"
    },
    "swversion": "",
    "type": "ZHASwitch",
    "uniqueid": "54:ef:44:10:00:76:f8:18-29-0012"
  },
  "238": {
    "capabilities": {
      "sleeper": false
    },
    "config": {
      "on": true,
      "reachable": true
    },
    "ep": 21,
    "etag": "859a47417ca8d09a5374b0df92880639",
    "lastannounced": "2026-01-02T08:22:08Z",
    "lastseen": "2026-01-02T10:51Z",
    "manufacturername": "LUMI",
    "modelid": "lumi.switch.n1aeu1",
    "name": "Power 238",
    "nwkaddress": "0xA14D",
    "state": {
      "lastupdated": "none",
      "power": 0
    },
    "swversion": "",
    "type": "ZHAPower",
    "uniqueid": "54:ef:44:10:00:76:f8:18-15-000c"
  },
  "239": {
    "capabilities": {
      "sleeper": false
    },
    "config": {
      "on": true,
      "reachable": true
    },
    "ep": 31,
    "etag": "ad95686cad75b7d259f6b551127c3331",
    "lastannounced": "2026-01-02T08:22:08Z",
    "lastseen": "2026-01-02T10:51Z",
    "manufacturername": "LUMI",
    "modelid": "lumi.switch.n1aeu1",
    "name": "Consumption 239",
    "nwkaddress": "0xA14D",
    "state": {
      "consumption": 0,
      "lastupdated": "none"
    },
    "swversion": "",
    "type": "ZHAConsumption",
    "uniqueid": "54:ef:44:10:00:76:f8:18-1f-000c"
  }
}

working wall switch:

"184": {
    "capabilities": {
      "sleeper": false
    },
    "config": {
      "clickmode": "decoupled",
      "devicemode": "compatibility",
      "ledindication": true,
      "on": true,
      "reachable": true
    },
    "ep": 41,
    "etag": "d62e42cbfa00983487698f203b20da16",
    "lastannounced": "2025-12-30T12:34:11Z",
    "lastseen": "2026-01-02T10:51Z",
    "manufacturername": "LUMI",
    "mode": 1,
    "modelid": "lumi.switch.n1aeu1",
    "name": "Wandschalter Eins",
    "nwkaddress": "0xA5DE",
    "state": {
      "buttonevent": 1002,
      "lastupdated": "2026-01-02T04:34:56.097"
    },
    "swversion": "0.0.0_0023",
    "type": "ZHASwitch",
    "uniqueid": "54:ef:44:10:00:76:e7:27-29-0012"
  },
  "185": {
    "capabilities": {
      "sleeper": false
    },
    "config": {
      "on": true,
      "reachable": true
    },
    "ep": 21,
    "etag": "d215b744d931ef4070985d21121f82d0",
    "lastannounced": "2025-12-30T12:34:11Z",
    "lastseen": "2026-01-02T10:51Z",
    "manufacturername": "LUMI",
    "modelid": "lumi.switch.n1aeu1",
    "name": "Power 185",
    "nwkaddress": "0xA5DE",
    "state": {
      "lastupdated": "2026-01-02T10:51:46.438",
      "power": 0
    },
    "swversion": "0.0.0_0023",
    "type": "ZHAPower",
    "uniqueid": "54:ef:44:10:00:76:e7:27-15-000c"
  },
  "186": {
    "capabilities": {
      "sleeper": false
    },
    "config": {
      "on": true,
      "reachable": true
    },
    "ep": 31,
    "etag": "3e01737c3851d32cbd1d3ed9f862b226",
    "lastannounced": "2025-12-30T12:34:11Z",
    "lastseen": "2026-01-02T10:51Z",
    "manufacturername": "LUMI",
    "modelid": "lumi.switch.n1aeu1",
    "name": "Consumption 186",
    "nwkaddress": "0xA5DE",
    "state": {
      "consumption": 5635,
      "lastupdated": "2026-01-02T10:49:41.246"
    },
    "swversion": "0.0.0_0023",
    "type": "ZHAConsumption",
    "uniqueid": "54:ef:44:10:00:76:e7:27-1f-000c"
  },

What means working? Working means that decoupled mode works like charm and it spawns button events. Not Working means that even in decoupled mode there are no events passed to Home Assisstant, so basically its not usable in decoupled mode anymore...

[Smanar]

Ha yes, I can understand for ZHAswitch "lastupdated" was not updated in decoupled mode, but it's like the device don't receive return at all, all other sensors are empty too.
BTW you have the problem only on this device ?

It can be similar to #8428 (comment)

The device make report but deconz don't handle them.

[MrSolo570]

I have two identical wall switches Aqara H1 single button EU, one has the issue described the other one works flawlessly.
I have about 60 other zigbee devices from different manufacturers. Other ones work nice but tbh, none of them rely on deconz_events in home assistant but I use them with their entity abilities in home assistant like on, off etc.
Those two wall switches are the only devices that rely on events.
Do you have an idea what could be the background to this malfunction?

[Smanar]

But you haven't re-included yours devices recently, only the not working one.
IDK, I can't reproduce it on my side, and it's something rare, for the moment I m asking to other devs.

[rweise]

After one week, i lost the rest of my Hair. ;-). I try to build a test-system to reproduce the error. But with no luck. i get all times websocket errors. deconz-adapter in iobroker is yellow and make one fine round and then runs alltime in a websocket error. Ok, this is a other problem, and well known. ( Test system should be Debian Trixie with deconz-qt6 )
Now i think i will stay with my 5yo system on 2.31.2 and wait until all the bugs on the way to qt6 are past. I read a lot this weekend and it looks like that there are websocket problems around 2.32.x If i bring all together, there is a problem with sleepers and if im right, this is also my problem. I can't resolve it and i can't understand it, because i run the last year with an very instable configuration, because of a bug in the iobroker.toyota adapter that i found out 2 month ago. But with very slow connections (bcause of updating more then 80000 Objects from toyota :-( ) , I get never websocket errors from deconz.
And by the way, it is no fun, to switch back from 2.32.x to 2.31.2 because i must repair all my Eurotronic TRVs every time, because they lost there connections. I know, that all at dresden-elektronik do there best, but some times, i hate it. at an example, i can't load ddfs for an device. And if i read the problems from MrSolo570 here, he must have the same problems. Normaly, i would say, take the ddf from the working switch and load it for the other one. And then it should work. But equally what i do, if i try to do so, i get the message ddf can't be loaded ... So for me you can close this Thread. Sorry for any mistakes, but english is not my natural language and sorry for the frustration in this thread ...

[rweise]

deconz.0	2026-01-04 21:26:37.341	debug	Websocket connection closed
deconz.0	2026-01-04 21:26:37.338	warn	Could not connect to websocket instance of deConz/Phoscon. Error: socket hang up
deconz.0	2026-01-04 21:26:31.130	debug	Websocket connection closed
deconz.0	2026-01-04 21:26:31.129	warn	Could not connect to websocket instance of deConz/Phoscon. Error: socket hang up
deconz.0	2026-01-04 21:25:36.942	debug	Websocket connection closed
deconz.0	2026-01-04 21:25:36.941	warn	Could not connect to websocket instance of deConz/Phoscon. Error: socket hang up
deconz.0	2026-01-04 21:25:30.766	debug	Websocket connection closed
deconz.0	2026-01-04 21:25:30.763	warn	Could not connect to websocket instance of deConz/Phoscon. Error: socket hang up
deconz.0	2026-01-04 21:25:30.735	debug	Code 200: Request succeded get group attributes 1: {"action":{"alert":"none","bri":127,"colormode":"hs","ct":0,"effect":"none","hue":0,"on":false,"sat":127,"scene":"","xy":[0,0]},"devicemembership":[],"etag":"59c75257d7b478e162ce8d10c99d3be1","id":"1","lights":[],"name":"Phoscon_All_Off","scenes":[],"state":{"all_on":false,"any_on":false},"type":"LightGroup"}
deconz.0	2026-01-04 21:25:30.685	debug	Code 200: Request succeded get all groups: {"1":{"action":{"alert":"none","bri":127,"colormode":"hs","ct":0,"effect":"none","hue":0,"on":false,"sat":127,"scene":"","xy":[0,0]},"devicemembership":[],"etag":"59c75257d7b478e162ce8d10c99d3be1","id":"1","lights":[],"name":"Phoscon_All_Off","scenes":[],"state":{"all_on":false,"any_on":false},"type":"LightGroup"}}
deconz.0	2026-01-04 21:25:30.669	debug	Code 200: Request succeded get all sensors: {"1":{"config":{"configured":true,"on":true,"sunriseoffset":30,"sunsetoffset":-30},"etag":"d32ef4fe452f0108a320971be778f217","manufacturername":"Philips","modelid":"PHDL00","name":"Daylight","state":{"dark":true,"daylight":false,"lastupdated":"2026-01-04T19:23:53.178","status":230,"sunrise":"2026-01-04T07:18:49","sunset":"2026-01-04T15:17:52"},"swversion":"1.0","type":"Daylight","uniqueid":"00:21:2e:ff:ff:03:b5:33-01"},"2":{"capabilities":{"sleeper":true},"config":{"battery":100,"on":true,"reachable":true},"ep":1,"etag":"51f1ef85c8682510b3175c9e396cfd7e","lastannounced":"2026-01-04T17:00:11Z","lastseen":"2026-01-04T20:09Z","manufacturername":"LUMI","mode":1,"modelid":"lumi.remote.b1acn01","name":"Schalter 1","nwkaddress":"0x923C","state":{"buttonevent":1002,"lastupdated":"2026-01-04T20:09:32.758"},"swversion":"0.0.0_0002","type":"ZHASwitch","uniqueid":"00:15:8d:00:06:36:de:20-01-0012"},"3":{"capabilities":{"sleeper":true},"config":{"battery":100,"on":true,"reachable":true,"temperature":3300},"ep":1,"etag":"31960550646a7cec2a8b0e44845818bd","lastannounced":"2026-01-04T18:19:32Z","lastseen":"2026-01-04T20:09Z","manufacturername":"LUMI","mode":1,"modelid":"lumi.remote.b186acn01","name":"Schalter 2","nwkaddress":"0x8CC4","state":{"buttonevent":1004,"lastupdated":"2026-01-04T20:09:31.798"},"swversion":"20180809","type":"ZHASwitch","uniqueid":"00:15:8d:00:03:6d:54:df-01-0012"}}
deconz.0	2026-01-04 21:25:30.656	debug	Code 200: Request succeded get all lights: {}
deconz.0	2026-01-04 21:25:30.619	info	deConz Version: 2.32.2; API version: 1.16.0
deconz.0	2026-01-04 21:25:30.611	debug	Code 200: Request succeded get config: {"UTC":"2026-01-04T20:25:30","apiversion":"1.16.0","backup":{"errorcode":0,"status":"idle"},"bridgeid":"00212EFFFF03B533","datastoreversion":"93","devicename":"ConBee","dhcp":true,"disablePermitJoinAutoOff":false,"factorynew":false,"fwversion":"0x260b0500","gateway":"192.168.2.1","internetservices":{"internet":"connected","remoteaccess":"disconnected","swupdate":"connected","time":"connected"},"ipaddress":"192.168.2.152","lightlastseeninterval":60,"linkbutton":false,"localtime":"2026-01-04T21:25:30","mac":"50:a7:32:1c:74:4a","modelid":"deCONZ","name":"Trixie","netmask":"255.255.255.0","networkopenduration":60,"panid":7851,"portalconnection":"disconnected","portalservices":false,"portalstate":{"communication":"disconnected","incoming":false,"outgoing":false,"signedon":false},"proxyaddress":"none","proxyport":0,"replacesbridgeid":null,"rfconnected":true,"starterkitid":"","swupdate":{"checkforupdate":false,"devicetypes":{"bridge":false,"lights":[],"sensors":[]},"notify":false,"text":"","updatestate":0,"url":""},"swupdate2":{"autoinstall":{"on":false,"updatetime":""},"bridge":{"lastinstall":"2025-12-03T01:28:20","state":"noupdates"},"checkforupdate":false,"lastchange":"","state":"noupdates"},"swversion":"2.32.2","timeformat":"24h","timezone":"Europe/Berlin","uuid":"53d0998c-6ca1-41d3-9c9c-d2c12abc71ca","websocketnotifyall":true,"websocketport":80,"websocketport_wss":443,"whitelist":{"170C1F1339":{"create date":"2026-01-04T17:23:01","last use date":"2026-01-04T17:26:58","name":"Phoscon#B1898x890"},"2824F353B5":{"create date":"2026-01-04T17:23:39","last use date":"2026-01-04T18:20:58","name":"ioBroker"},"2B315F4786":{"create date":"2026-01-04T19:24:26","last use date":"2026-01-04T20:10:47","name":"Phoscon#B1898x890"},"6C20DCEEEC":{"create date":"2026-01-04T20:08:33","last use date":"2026-01-04T20:25:30","name":"ioBroker"},"AA0D085F4A":{"create date":"2026-01-04T19:26:10","last use date":"2026-01-04T20:07:21","name":"Phoscon#B1898x890"},"E921E40F28":{"create date":"2026-01-04T20:07:52","last use date":"2026-01-04T20:07:52","name":"Phoscon#B1898x890"},"F9082744B5":{"create date":"2026-01-04T17:59:36","last use date":"2026-01-04T19:04:52","name":"Phoscon#B935x898"}},"zigbeechannel":15}
deconz.0	2026-01-04 21:25:30.251	info	starting. Version 1.6.4 in /opt/iobroker/node_modules/iobroker.deconz, node: v22.21.0, js-controller: 7.1.0

Only for last demonstration, One round fine, all objects are createted and then nothing any more ...

[MrSolo570]

I just bought another new wall switch and will report if it works out of the box as soon as it arrives

[rweise]

This morning i made a last try. i take a pi400 install clean Trixie a raspbee II with deconz-qt6 and a clean Iobroker. It is always the same. the deconz adapter failed with: Could not connect to websocket instance of deConz/Phoscon. Error: socket hang up

And by the way, all the wall switches are only the first time easy to pair, because they have no real reset. when i will bring one to a new zigbee-network i must switch all aktive endpoints from the old network off, if i does not do so, it will instantly connect with the old network.

[rweise]

I know it is a little bit out of the initial post. But at the end, I made a last try this morning.
Clean install of a 64bit Bookworm edition on my Pi400. After installation of Deconz-Stable (2.31.2) all works fine.
Then I changed to beta and made the update to Deconz 2.32.2 (QT5) with the well-known result. No update in iobroker for the switches, and WebSocket errors :-( . I made this not as fun, only to see if there is a problem in my network. After all, this must be a problem with the beta 2.32.x. And by the way, the adapter in iobroker is now changed to yellow with No connetion to Hardware or Service.
chers

[rweise]

If someone needs logs, please tell me, what you want and where i can get it. I let the system like it is, because i do not need it ( better the sd-cards)

[Smanar]

Yes, avoid the 2.32.2, there is an issue on websocket
#8427