Aqara Wall switch QBKG04LM - How to enable decoupled mode (disconnect button from relay) #1816

am1ter · 2019-09-03T13:40:37Z

Hello everyone!

Could anybody please help me with disconnecting button from relay for switch Aqara QBKG04LM (1 line, no neutral)?

In other thread realted to 2 line switch Aqara QBKG12LM #1420 (comment) @ebaauw clarified that Aqara switches can work in decoupled mode and all you need to do is write new values (0xFE) in attributes 0xFF22 and 0xFF23. Unfortunatelly, deconz don't show this parameters for my switch QBKG04LM with default general.xml, despite in this files there is relevant lines.

<attribute id="0xFF22" name="Xiaomi Disconnect 1" type="u8" showas="hex" access="rw" required="o" mfcode="0x115F">
<description>Set to 0x12 (0xFE) to connect (disconnect) the left button to (from) the relay.</description>
</attribute>

From this topic #1487 (comment) I discovered that my switch QBKG04LM uses another manufacturing code - 0x1037 instead of 0x115F. When I changed mfcode to 0x137 in the file general.xml to correct value I discovered that disconnecting parameters appeared in deconz interface with a 0x00 value. But when I try to read or write a new value, for example 0xFE, I get an error:

failed UNSUP_MANUF_GENERAL_COMMAND

I read as many topics realted to my case as I could, but didn't find anything what could help me. Moreover I use Conbee II so I can't use ZSHARK for sniffing my xiaomi zigbee gateway and can't look out a command that disconnect switch button from relay.

I would really appreciate if anyone can give me advice how I can try to fix my problem.

==========
== UPDATE ==

TEMPORARY SOLUTION by @KapJI: #1816 (comment)

The text was updated successfully, but these errors were encountered:

ebaauw · 2019-09-03T17:39:03Z

@ebaauw clarified that Aqara switches can work in decoupled mode

All I clarified is that one particular model Aqara switch can work in decoupled mode. There’s no such thing as “Aqara switches”: every model works differently, and they seem to be using the same commercial model name for different technical models.

am1ter · 2019-09-03T21:08:57Z

@ebaauw clarified that Aqara switches can work in decoupled mode

All I clarified is that one particular model Aqara switch can work in decoupled mode. There’s no such thing as “Aqara switches”: every model works differently, and they seem to be using the same commercial model name for different technical models.

Thank you for your reply. In fact this Aqara switch can work in decoupled mode when it is connected to Xiaomi Aqara Gateway. This option works fine. But I can't find out a way to do the same thing using Deconz and Conbee II gateway.

ebaauw · 2019-09-03T21:26:49Z

Just a long shot: Did you try the attribute definition without a manufacturer code?

am1ter · 2019-09-03T21:29:35Z

Just a long shot: Did you try the attribute definition without a manufacturer code?

Yes, I did. In a such case there is another error:

writing failed

ArkadiuszNiemiec · 2019-09-24T17:48:33Z

I have the same problem. My switches ID is 0x1037 and I cannot find a way to enable decoupled mode...

ArkadiuszNiemiec · 2019-10-02T14:54:33Z

I have bought a CC2531 dongle to snif a network. Can I connect a switch do Xiaomi HUB and sniff what it sends when I enable a decoupled mode?

am1ter · 2019-10-04T14:36:49Z

I have bought a CC2531 dongle to snif a network. Can I connect a switch do Xiaomi HUB and sniff what it sends when I enable a decoupled mode?

I think you could. I would really appreciate if you would upload your sniffed data.

ArkadiuszNiemiec · 2019-10-07T09:40:56Z

I have bought a CC2531 dongle to snif a network. Can I connect a switch do Xiaomi HUB and sniff what it sends when I enable a decoupled mode?

I think you could. I would really appreciate if you would upload your sniffed data.

I will post it as soon as I have the hardware.

KapJI · 2019-10-20T12:03:59Z

I have the same problem. I can confirm that this switch support decoupled mode by sending 0xFE to 0xFF22 and 0xFF23. I added support of this feature to zigbee2mqtt few months ago and it works fine: Koenkk/zigbee-herdsman-converters#287
But deCONZ with Conbee 2 can't write this attribute for some reason.

KapJI · 2019-10-22T22:41:16Z

After sniffing traffic and comparing with what zigbee2mqtt does I found that manufacturer code 0x115F should be used (it's part of request). Deconz detects it incorrectly and then uses it to match with extra attributes from general.xml
@manup can you clarify how deconz detects mfcode?

KapJI · 2019-10-23T08:44:35Z

zigbee2mqtt for example just has it hardcoded: https://github.com/KapJI/zigbee-shepherd-converters/blob/be0c869339da485842b2b56bf5cd370f22ba2b89/converters/toZigbee.js#L15

KapJI · 2019-10-23T22:26:13Z

@am1ter @ArkadiuszNiemiec if you're still interested I created custom endpoint for rest plugin: https://github.com/KapJI/deconz-rest-plugin/tree/set-mfcode
It can write attribute with correct manufacturer code. Compile plugin, replace existing one.
Then you can use it like:

curl -X POST http://127.0.0.1:8090/api/<api_key>/attributes/<id> -d '{"key": 65314, "value": 254}'

Use <id> from /api/<api_key>/sensors.
65314 for left button, 65315 for right button.
254 for decoupled mode, 18 or 34 for enabling relay control back.

ArkadiuszNiemiec · 2019-10-24T10:04:43Z

@KapJI great job, thank you! I will be back in my flat in two weeks. I will update you here after I test it 👍

am1ter · 2019-10-24T23:12:52Z

@KapJI Thank you very much for your solution! I would really appreciate if you could give me some additional details. I compiled plugin and replaced existing, but I am not sure that I did it correctly.
A couple of questions:

I got an api key. When I send GET request to <api_key>/sensors I get a correct answer. But I am not sure what part of answer I should use as . Below an example of answer:

 "2": {
        "config": {
            "on": true,
            "reachable": false,
            "temperature": 2400
        },
        "ep": 4,
        "etag": "26ed2d6fa261328a18f2deb36c289794",
        "manufacturername": "LUMI",
        "mode": 1,
        "modelid": "lumi.ctrl_neutral1",
        "name": "lumi.ctrl_neutral1",
        "state": {
            "buttonevent": 1002,
            "lastupdated": "2019-08-26T19:45:33"
        },
        "swversion": "11-25-2017",
        "type": "ZHASwitch",
        "uniqueid": "00:15:8d:00:02:4d:4f:cb-04-0006"
    }

Is my id for POST request is "2" or "00:15:8d:00:02:4d:4f:cb-04-0006"?

When I try to send a POST command

curl -X POST http://192.168.0.115:40850/api/XXXXXXXXXXX/attributes/2 -d '{"key": 65314, "value": 254}'

I get an error:

[
{"error":
{"address":"/attributes/2","description":"method, POST, not available for resource, attributes/2","type":4}
}
]

So I suppose that I made a mistake while compiling plugin.
I would be grateful for any advice!

KapJI · 2019-10-25T14:44:10Z

@am1ter

Yes, "2" is correct id.
It looks like you don't have my changes. Check if you have this commit in your checkout: KapJI@8749dc7
Did you checkout correct branch in my fork? Did you restart deconz after replacing the plugin?

am1ter · 2019-10-29T15:07:48Z

@KapJI, Thank you very much for your solution. Everything works perfect. My mistake was moving copiled plugin to incorrect docker container. When I copied it in the correct I got an opportunity to write attributes.

I updated first post with link to this solution.

KapJI · 2019-10-29T16:28:22Z

@am1ter Great to hear!

ArkadiuszNiemiec · 2019-11-06T16:29:01Z

@ebaauw you are the only contributor here, what do we need to do to merge @KapJI work to master?

ebaauw · 2019-11-06T16:51:47Z

Technically, a pull request.

Not sure if it should be merged, though. I think it should be a PUT instead of a POST. Also, I don't like the hardcoded endpoint and mfcode.

You should be able to write the attribute using the CLI plugin (https://github.com/ma-ca/deconz-cli-plugin).

KapJI · 2019-11-13T18:12:56Z

@ebaauw I think the proper fix will be using the correct mfcode for Xiaomi devices in deConz itself. But as sources are closed, I can't submit pull request there :(
I believe there's hardcoded mapping somewhere between model id and mfcode.

ebaauw · 2019-11-13T19:35:55Z

The deCONZ core programme is closed source, but the Cluster Info panel is configurable through general.xml, which is part of this repository. That's how I added support for decoupled mode for the other Xiaomi switch.

I believe there's hardcoded mapping somewhere between model id and mfcode.

No. Per the ZigBee standard, the deCONZ core programme uses the Manufacturer Code from the Device Descriptor to determine which manufacturer-specific attributes (from general.xml) to show in the GUI.

The issue with this Xiaomi switch is that it uses a different codes in the descriptor vs the Basic cluster. Working around this mutilation of the standard seems way beyond the current design and function of the core programme. The values of the Basic cluster attributes are used only by the REST API plugin, not by the core programme.

The "proper" fix would be for Xiaomi to release firmware that adheres to the standard. I don't think that's likely to happen, so, unfortunately, we're stuck with "improper" workarounds. Which, imho, is still preferable over not supporting devices that don't adhere to the standard.

ArkadiuszNiemiec · 2019-11-15T10:08:55Z

Which, imho, is still preferable over not supporting devices that don't adhere to the standard.

Yes, please! I have equipped my whole house with these switches with the intention to use some of them as wireless switches for smart lamps or bulbs. That's the reason why I have bought the ConBeeII and set up Deconz 😄

Ccan you suggest or help to develop the improper but acceptable workaround for this? I have found your PR with decoupled mode for another switch (#1444) and tried to follow it but it's still too hard for me to grasp.

ebaauw · 2019-11-15T10:27:57Z

I don't see a workaround using the deCONZ GUI. For the more technical people: send the Write Attributes command using the deconz-cli-plugin (there you can specify mfcode yourself).

For the non-technical people, proper support by the REST API (and by its clients, like Phoscon) would be needed. As you only set this once when commissioning the switch, I see no urge to do this. Also, without access to a switch, development and testing would be very hard.

I suppose adding a config.detached REST attribute would be the proper way. Then we run into the same issue as with config.group: different switch endpoints have different settings, but are combined in a single REST resource. Best left to API v2.

ArkadiuszNiemiec · 2019-11-15T23:57:39Z

For the more technical people: send the Write Attributes command using the deconz-cli-plugin (there you can specify mfcode yourself).

I have prepared a docker with deconz-cli-plugin and I am currently trying to write the attribute. I am not quite sure what is wrong so maybe you can help.
I am typing:
zclattrmanu 0x6341 1 0x0000 0x115F 02FF2320FE
where: 0x6341 is NWK (address), 1 is the ep, 0x0000 is the cluster, 0x115Fis manufacturer code and then there is a command:02to write,FF23attribute identifier (16 bits according to docs),20is data type (u8) andFE` is data to write.

Is that right? What is wrong? Thank you in advance!

ebaauw · 2019-11-16T12:02:46Z

I think you need to specify the payload in Big Endian? So 0223FF20FE.

ArkadiuszNiemiec · 2019-11-16T12:09:25Z

I think you need to specify the payload in Big Endian? So 0223FF20FE.

You are right, it worked! I have a decoupled switch now. Thank you and thanks @KapJI

aleksandrdobrynin · 2019-11-21T00:45:31Z

Hello. I bought QBKG03LM switches and ran into the problem of adding. More precisely, a switch is added. At first it is added as 4 devices, but after restarting the gui, only two remain. But the sleepy problem is not that. How to implement a logic switch. One of the buttons should control the smart lamp. I tried to compile the plugin and set the parameter through it, succession reported, but at the same time, as the relay clicked, it continued to click.

SAOPP · 2020-03-06T22:57:04Z

Guys, when Deconz start work fine with all the features of these switches? Why is it impossible to include the decoupled mode in the phoscon functionality? Why is it possible in s**t Z2M and not in Deconz?

SilverFire · 2020-04-11T09:55:52Z

It works fine, check out the following post: #1420 (comment)

Mimiix · 2020-06-06T14:51:17Z

It seems this issue is resolved or otherwise inactive. If it is not, please re-open!

ReX1983 · 2023-02-13T17:31:08Z

This part only appear if the manufacture code is 0x1037, Can you check wich one you have ? your device can just don't support it.

I have just paired few more switches (until now connected to to the Xiaomi Gateway). These are all no neutral switches, some 1 rocket and some 2 rockets, they are all 0x1037, but none of them has the disconnect options.

Ideas?

Smanar · 2023-02-14T17:39:49Z

There is something bad, the manufacture code is checked and valided because we can see the title "Man,ufacture specific" and "Xiaomi Specific" but all is empty ?

        <attribute-set id="0x4000" description="Manufacturer specific" mfcode="0x1037">
          <attribute id="0x4001" name="128-Bit security key" type="seckey" access="r" required="m" mfcode="0x1037"></attribute>
          <attribute id="0x4002" name="IEEE address" type="uid" access="rw" required="m" mfcode="0x1037"></attribute>
        </attribute-set>
        <attribute-set id="0xFF00" description="Xiaomi specific" mfcode="0x1037">
          <attribute id="0xFF0D" name="Xiaomi Sensitivity" type="u8" access="rw" required="o" mfcode="0x115f"></attribute>
          <attribute id="0xFF22" name="Xiaomi Disconnect 1" type="u8" showas="hex" access="rw" required="o" mfcode="0x115f">
            <description>Set to 0x12 (0xFE) to connect (disconnect) the left button to (from) the relay.</description>
          </attribute>

What is your deconz version ?

I m seing something strange, it's not the same manufacture code for the title (mfcode="0x1037") and the attribute (mfcode="0x115f") probably because the request need to use the second one, But why it's not working too for the "Manufacturer specific" line.

ReX1983 · 2023-02-14T19:42:10Z

I am on Deconz v.2.20.1.

Is it possible that my local deconz database / configuration is compromised?

These are devices that I paired years ago, when I was on a much older deconz version. Deconz at the time didn't work so well with these devices, so I had to remove them from deconz and repair to the Xiaomi hub.

Few days ago I tried to pair them back to deconz and to my surprise the friendly name I gave them is still there. So it seems that the deconz config/database hasn't been properly cleaned when I removed them years ago.

Smanar · 2023-02-14T20:25:35Z

Is it possible that my local deconz database / configuration is compromised?

No I don't think this feature just work with deconz itself and the xml file (updated at every deconz update), nothing to see with the database.
I will ask in dev channel, realy no idea from my side.

ReX1983 · 2023-02-14T20:51:27Z

Is it possible that my local deconz database / configuration is compromised?

No I don't think this feature just work with deconz itself and the xml file (updated at every deconz update), nothing to see with the database. I will ask in dev channel, realy no idea from my side.

Is this logic hardcoded or in an xml file? If it is a file, could you give me the full path and filename so I check mine?

Smanar · 2023-02-15T17:29:04Z

it's an XML file, on classic OS it's /usr/share/deCONZ/zcl/general.xml

ReX1983 · 2023-02-15T23:29:10Z

it's an XML file, on classic OS it's /usr/share/deCONZ/zcl/general.xml

I can see the same path under preferences, but unfortunately, I don't have access to it, as the installation is managed by Home Assistant in a docker container.

Is there a way to re-pair the node and ensure that deCONZ doesn't reuse settings previously used?

As I mentioned earlier, I think I might have brought older settings when I restored an old installation using the backup/restore feature in Phoscon.

Something else to mention is that after pairing one of these switches, I see the same device listed as LUMI light under Lights and as Xiaomi transmitter under Switches (in Phoscon). Is this expected?

ReX1983 · 2023-02-16T11:47:48Z

Further update...

I did a "Reset Node" (F5) on each one of these switches and now the Xiaomi Disconnect attributes are displayed under the Basic Cluster.

I was able to read and set the values and I can confirm that the buttons are now in "disconnected" mode.

In Home Assistant I can still control the relay but there is no event when the buttons are pressed.

Following Home Assistant instructions, I tried to listen to "deconz_event" but nothing is captured there.

When I press the button I see the following the deCONZ container log:

ZCL attribute report 0x00158D0001F4864F for cluster: 0x0006, ep: 0x05, frame control: 0x18, mfcode: 0x0000

This is the right button of a double rocker no neutral switch.

Any idea on how to capture the event?

Should I see these disconnected buttons reported as sensors in Phoscon (I don't)?

Smanar · 2023-02-16T17:21:17Z

In disconnect mode, you need to have 2 devices, the "light" one and a "sensor" one the ZHASwitch.
You haven't a value in the state/buttonevent field ?

(If you can see it in HA, you have access to the API in phoscon/help/API Information/sensor/.. )

ReX1983 · 2023-02-16T17:40:20Z

I don't see any sensor in Phoscon, under API information. The only sensors are the one from other devices, not these switches.

For each two rockets Aqara switch, I still see two lights (LUMI) and one switch (Xiaomi), under the API.

Is there any sort of re-pair/refresh I should do in deCONZ so Phoscon updates the way the devices are exposed?

For the above device (00158D0001F4864F) I see:

        "31": {
            "capabilities": {
                "alerts": [
                    "none",
                    "select",
                    "lselect"
                ]
            },
            "config": {
                "groups": []
            },
            "etag": "9d408903658978b97e92657a66e60782",
            "hascolor": false,
            "lastannounced": null,
            "lastseen": "2023-02-16T17:43Z",
            "manufacturername": "LUMI",
            "modelid": "lumi.ctrl_neutral2",
            "name": "Ground Stairs Light Switch",
            "state": {
                "alert": "none",
                "on": false,
                "reachable": true
            },
            "swversion": null,
            "type": "On/Off light",
            "uniqueid": "00:15:8d:00:01:f4:86:4f-02"
        },
        "32": {
            "capabilities": {
                "alerts": [
                    "none",
                    "select",
                    "lselect"
                ]
            },
            "config": {
                "groups": []
            },
            "etag": "e30111509092e78f8ca9ccf20b24194f",
            "hascolor": false,
            "lastannounced": null,
            "lastseen": "2023-02-16T17:43Z",
            "manufacturername": "LUMI",
            "modelid": "lumi.ctrl_neutral2",
            "name": "Hallway Slave (Ground Stairs)",
            "state": {
                "alert": "none",
                "on": false,
                "reachable": true
            },
            "swversion": null,
            "type": "On/Off light",
            "uniqueid": "00:15:8d:00:01:f4:86:4f-03"
        },
       "84": {
            "config": {
                "on": true,
                "reachable": true,
                "temperature": null
            },
            "ep": 4,
            "etag": "bb85d6e0a8d214b31c3f9801d1840f16",
            "lastannounced": null,
            "lastseen": "2023-02-16T17:43Z",
            "manufacturername": "LUMI",
            "mode": 1,
            "modelid": "lumi.ctrl_neutral2",
            "name": "Switch 84",
            "state": {
                "buttonevent": null,
                "lastupdated": "none"
            },
            "type": "ZHASwitch",
            "uniqueid": "00:15:8d:00:01:f4:86:4f-04-0006"
        }

For another switch (in coupled mode) with one rocket I see instead:

        "27": {
            "capabilities": {
                "alerts": [
                    "none",
                    "select",
                    "lselect"
                ]
            },
            "config": {
                "groups": []
            },
            "etag": "55345ed2309c10bfe5904ac361abd3ae",
            "hascolor": false,
            "lastannounced": null,
            "lastseen": "2023-02-16T17:44Z",
            "manufacturername": "LUMI",
            "modelid": "lumi.ctrl_neutral1",
            "name": "Hallway Light Switch",
            "state": {
                "alert": "none",
                "on": false,
                "reachable": true
            },
            "swversion": null,
            "type": "On/Off light",
            "uniqueid": "00:15:8d:00:01:83:b4:14-02"
        }
        "83": {
            "config": {
                "clickmode": "coupled",
                "on": true,
                "reachable": true,
                "temperature": null
            },
            "ep": 4,
            "etag": "e973f4a03538623653f57c884b6cdbb6",
            "lastannounced": null,
            "lastseen": "2023-02-16T17:44Z",
            "manufacturername": "LUMI",
            "mode": 1,
            "modelid": "lumi.ctrl_neutral1",
            "name": "Switch 83",
            "state": {
                "buttonevent": null,
                "lastupdated": "none"
            },
            "type": "ZHASwitch",
            "uniqueid": "00:15:8d:00:01:83:b4:14-04-0006"
        },

What makes things interesting is that the device above has clickmode: coupled under options, while the device I have put in decoupled mode doesn't show the same attribute.

Smanar · 2023-02-16T18:10:38Z

There is a DDF now for thoses device https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/devices/xiaomi/xiaomi_qbkg04lm_switch.json

One can have be included before the DDF was here, so with legacy code.

            "name": "Switch 84",
            "state": {
                "buttonevent": null,
                "lastupdated": "none"
            },
            "type": "ZHASwitch",
            "uniqueid": "00:15:8d:00:01:f4:86:4f-04-0006"

But they are not working buttonevent=none.
This value need to be updated whe using it, else you need to see in logs with "info_l2" some information about a button map.

ReX1983 · 2023-02-16T18:18:56Z

I am not sure I follow. What should I do?

Smanar · 2023-02-16T18:25:26Z

Only on the problematic device.
Can try to re-include it, the new inclusion will use the DDF, so you will have the config/coupled field for exemple.
And if the button press don't work try to take a look in deconz log (deconz/help/debug view) with the flag "info _l2" when pressing a button.

ReX1983 · 2023-02-16T18:38:11Z

Only on the problematic device. Can try to re-include it, the new inclusion will use the DDF, so you will have the config/coupled field for exemple.

What is the best procedure to reinclude to ensure any trace of them is removed from deconz?

ReX1983 · 2023-02-16T19:27:23Z

New finding: the double rocker is xiaomi_qbkg03lm_switch.json while the single rocker is xiaomi_qbkg04lm_switch.json.
Looking at the json, there is no mention of decoupled mode for qbkg03lm.

Any idea how to add support for decoule mode to qbkg03lm?

Smanar · 2023-02-17T17:49:13Z

What is the best procedure to reinclude to ensure any trace of them is removed from deconz?

Just deleting it in phoscon is fine.

Any idea how to add support for decoule mode to qbkg03lm?

It have probably same zigbee request.

        {
          "name": "config/clickmode",
          "refresh.interval": 86400,
          "read": {
            "at": "0xFF22",
            "cl": "0x0000",
            "ep": 1,
            "fn": "zcl",
            "mf": "0x115f"
          },
          "parse": {
            "at": "0xFF22",
            "cl": "0x0000",
            "ep": 1,
            "eval": "if (Attr.val == 0xFE) { Item.val = 'decoupled' } else if (Attr.val == 0x12) { Item.val = 'coupled' } else { Item.val = 'unknown' }",
            "fn": "zcl",
            "mf": "0x115f"
          },
          "write": {
            "at": "0xFF22",
            "cl": "0x0000",
            "dt": "0x20",
            "ep": 1,
            "eval": "if (Item.val == 'decoupled') { 0xFE } else if (Item.val == 'coupled') { 0x12 } else { 'unknown' }",
            "fn": "zcl",
            "mf": "0x115f"
          },
          "values": [
            ["\"decoupled\"", "Decoupled Mode"],
            ["\"coupled\"", "Coupled Mode"] 
          ],
          "default": "coupled"
        },

But ATM the problem is more having buttonevent when pressing a button if the device is decoupled ^^.

ReX1983 · 2023-02-17T19:38:44Z

Any idea how to get this event?

I have removed and repaired the switch but still no luck.

Buttonpress shows null.

What can I do?

Smanar · 2023-02-18T13:31:34Z

Take a look in deconz log (deconz/help/debug view) with flag "info_l2", and press a button you will see an error message about button map.

ReX1983 · 2023-02-20T19:05:59Z

No error message, just the following when I press the button:

ReX1983 · 2023-02-21T09:37:55Z

FYI, created an issue for this: #6758

MrSolo570 · 2023-09-27T12:36:29Z

Hello guys as the thread is quite long and some comments are older: currently what is the easiest way to set the Aqara Smart Wall Switch H1 into decoupled mode? (Home Assistant, deconz-addon). Thank you

Smanar · 2023-09-27T14:10:21Z

With "config/clickmode" ? But I m seeing an issue on it.

MrSolo570 · 2023-09-27T17:09:08Z

Could you elaborate on what issue?
Ok I went to deconz, right Clicked on the device, edited DDF, saved and clicked hot reload, but it didn't work. When I press the switch it still works as a common switch...

ReX1983 · 2023-09-27T17:16:31Z

I managed set the device in decoupled mode and I could see the messages in the log (see above), but the event was not reported by deconz to HA.

In the other thread (link above) there are all the info on the what to do and what is the issue. Eventually there was no response / help and I just gave up.

MrSolo570 · 2023-09-27T17:24:28Z

Did you buy a different devices or how did you solve your use case? Sad, because the device looks excellent...
Btw I have the switch with neutral wire.

ReX1983 · 2023-09-27T19:10:33Z

I stopped using deconz with the aqara switches. They are now connected to the aqara hub and integrated with Home Assistant directly.

Smanar · 2023-09-28T10:51:35Z

Could you elaborate on what issue? Ok I went to deconz, right Clicked on the device, edited DDF, saved and clicked hot reload, but it didn't work. When I press the switch it still works as a common switch...

Just use the API to change the value in "config/clickmode", idk if HA permit that. (You have value decoupled/coupled).

The issue > #6758

MrSolo570 · 2023-09-28T13:30:24Z

Please don't mind my asking because I never did that, how can I access the API? I stumbled upon this guide https://dresden-elektronik.github.io/deconz-rest-doc/about_rest/ but it left me rather clueless on how to get it going.
Would like to find out if my switch with neutral wire suffers the same bug or if it reports the event correctly..

Mimiix · 2023-09-28T13:32:35Z

Im locking this issue as we are offtopic.

Please use the above issue.

dresden-elektronik locked and limited conversation to collaborators Sep 28, 2023

Aqara Wall switch QBKG04LM - How to enable decoupled mode (disconnect button from relay) #1816

Aqara Wall switch QBKG04LM - How to enable decoupled mode (disconnect button from relay) #1816

Comments

am1ter commented Sep 3, 2019 • edited Loading

ebaauw commented Sep 3, 2019

am1ter commented Sep 3, 2019

ebaauw commented Sep 3, 2019

am1ter commented Sep 3, 2019

ArkadiuszNiemiec commented Sep 24, 2019

ArkadiuszNiemiec commented Oct 2, 2019

am1ter commented Oct 4, 2019

ArkadiuszNiemiec commented Oct 7, 2019

KapJI commented Oct 20, 2019

KapJI commented Oct 22, 2019 • edited Loading

KapJI commented Oct 23, 2019

KapJI commented Oct 23, 2019

ArkadiuszNiemiec commented Oct 24, 2019

am1ter commented Oct 24, 2019

KapJI commented Oct 25, 2019

am1ter commented Oct 29, 2019

KapJI commented Oct 29, 2019

ArkadiuszNiemiec commented Nov 6, 2019

ebaauw commented Nov 6, 2019

KapJI commented Nov 13, 2019 • edited Loading

ebaauw commented Nov 13, 2019

ArkadiuszNiemiec commented Nov 15, 2019

ebaauw commented Nov 15, 2019

ArkadiuszNiemiec commented Nov 15, 2019

ebaauw commented Nov 16, 2019

ArkadiuszNiemiec commented Nov 16, 2019

aleksandrdobrynin commented Nov 21, 2019

SAOPP commented Mar 6, 2020

SilverFire commented Apr 11, 2020

Mimiix commented Jun 6, 2020

ReX1983 commented Feb 13, 2023

Smanar commented Feb 14, 2023 • edited Loading

ReX1983 commented Feb 14, 2023

Smanar commented Feb 14, 2023

ReX1983 commented Feb 14, 2023

Smanar commented Feb 15, 2023

ReX1983 commented Feb 15, 2023 • edited Loading

ReX1983 commented Feb 16, 2023

Smanar commented Feb 16, 2023

ReX1983 commented Feb 16, 2023 • edited Loading

Smanar commented Feb 16, 2023

ReX1983 commented Feb 16, 2023

Smanar commented Feb 16, 2023

ReX1983 commented Feb 16, 2023

ReX1983 commented Feb 16, 2023

Smanar commented Feb 17, 2023

ReX1983 commented Feb 17, 2023

Smanar commented Feb 18, 2023

ReX1983 commented Feb 20, 2023

ReX1983 commented Feb 21, 2023

MrSolo570 commented Sep 27, 2023

Smanar commented Sep 27, 2023 • edited Loading

MrSolo570 commented Sep 27, 2023

ReX1983 commented Sep 27, 2023

MrSolo570 commented Sep 27, 2023 • edited Loading

ReX1983 commented Sep 27, 2023

Smanar commented Sep 28, 2023

MrSolo570 commented Sep 28, 2023

Mimiix commented Sep 28, 2023

am1ter commented Sep 3, 2019 •

edited

Loading

KapJI commented Oct 22, 2019 •

edited

Loading

KapJI commented Nov 13, 2019 •

edited

Loading

Smanar commented Feb 14, 2023 •

edited

Loading

ReX1983 commented Feb 15, 2023 •

edited

Loading

ReX1983 commented Feb 16, 2023 •

edited

Loading

Smanar commented Sep 27, 2023 •

edited

Loading

MrSolo570 commented Sep 27, 2023 •

edited

Loading