deconz-rest-plugin: Aqara Single Switch module not working since update to 2.19.01
Describe the bug
After updating from 2.18.2 to 2.19.1 my Aqara T1 Switch doesn’t work. https://www.aqara.com/en/single_switch_T1_no-neutral.html In 2.18.2, and before, the switch was recognised as a light, I think this is correct. But since the upgrade to 2.19.1, the switch appears as both a light and a switch, i.e. 2 entities are created. If you delete either one, the other is also removed. One of these entities is being exposed to home assistant, but it doesn’t work. When attempting to switch it on/off in home assistant, I get the error message: -
[545860309824] 3 /lights/3 resource, /lights/3, not available
Steps to reproduce the behavior
- Go to ‘Phoscon HTTP GUI’
- Click on ‘Lights’
- Scroll down to ‘MasterBedroom Light | LUMI | lumi.switch.l0agl1’
- Click on ‘Switches’
- Scroll down to ‘lumi.switch.l0agl1 | LUMI | lumi.switch.l0agl1’
Expected behavior
I would expect to only see this exposed as a light, I think with two entities available, there is a clash somewhere.
Screenshots


Environment
- Host system: Raspberry Pi 4 (8GB)
- Running method: Raspbian
- Firmware version: 26720700
- deCONZ version: 2.19.01
- Device: ConBee II
- Do you use an USB extension cable: yes
- Is there any other USB or serial devices connected to the host system? If so: Which? No
deCONZ Logs
API Info: - ` “8”: { “etag”: “a16e0dcf3996a01210406c742d36c5df”, “hascolor”: false, “lastannounced”: null, “lastseen”: “2022-10-25T10:57Z”, “manufacturername”: “LUMI”, “modelid”: “lumi.switch.l0agl1”, “name”: “MasterBedroom Light”, “state”: { “alert”: “none”, “on”: false, “reachable”: true }, “swversion”: “0.0.0_0022”, “type”: “On/Off light”, “uniqueid”: “54:ef:44:10:00:07:62:80-01” },
“ep”: 41, “etag”: “9dcdf4cc905be1ee02ff03f24af4ebdb”, “lastannounced”: null, “lastseen”: “2022-10-25T10:57Z”, “manufacturername”: “LUMI”, “mode”: 1, “modelid”: “lumi.switch.l0agl1”, “name”: “lumi.switch.l0agl1”, “state”: { “buttonevent”: null, “lastupdated”: “none” }, “swversion”: “0.0.0_0022”, “type”: “ZHASwitch”, “uniqueid”: “54:ef:44:10:00:07:62:80-29-0012” } `
Additional context
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 35
Yep, it’s from the Swoops’s DDF, probably because you can "decouple’ them.
From the comment the corrective is in the version 2.19.1 https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/v2.19.1