Xiaomi Aquara Water leak sensor (SJCGQ11LM) falsely reports trouble on deConz 2.22.2 (HA addon) #7061

bennydiamond · 2023-06-26T19:54:42Z

Describe the bug

I'm running deConz HA addon.
I updated addon to version 6.20.0 (which includes deConz 2.22.2). One of my water leak sensor SJCGQ11LM started reporting trouble right away.

I tried to delete and re-pair the device, device will behave normally for a couple of seconds and then will fall back to reporting trouble.

I tried replacing the battery in the device, same issue.

I downgraded deConz HA addon to previous version (6.19.0). The problem went away. SJCGQ11LM sensor behaves as intended.

Only 1 of my 5 * SJCGQ11LM sensor exhibited the problem but I suspect this is due to the fact the others might have been sleeping and thus did not report to deConz while I was witnessing the issue.

Steps to reproduce the behavior

Pair "SJCGQ11LM" with deConz HA addon 6.20.0
Once paired, press the button on SJCGQ11LM sensor to trigger sending its attributes
Device will report trouble/wet and will stay in that state indefinitely

Expected behavior

If no water is physically touching the sensor, the sensor should not report trouble/wet.

Environment

Host system: USFF PC, HP ProDesk Mini G3 400, running Debian 12.
Running method: Home Assistant deCONZ Add-on (6.20.0)
Firmware version: 26400500
deCONZ version: (2.22.2)
Device: ConBee I
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system? Aeotec Z-Wave stick Gen5, 2 * RTL-SDR receiver dongles

Additional context

I reverted to HA Addon 6.19.0 and did not save any logs. If necessary, I could update again to the faulty version and generate logs.

I highly suspect the issue originates from this change: #6919

Mimiix · 2023-06-27T02:24:03Z

@SwoopX can you check?

Larry0ua · 2023-06-27T05:26:14Z

Same here. 3 of 4 aquara water sensors started reporting water shortly after update to HA addon 6.20.0 yesterday (deCONZ 2.21.2->2.22.2) running with ConBee II

If additional logs are necessary I can extract them

ebaauw · 2023-06-27T05:51:36Z

We changed the DDF in #6919 to use the Xiaomi special attribute report next to the IAS Zone. This PR was merged in v2.22.1-beta. I’ve been running that version since it’s release. Haven’t upgraded to v2.22.2 yet, but I don’t think that version has additional changes for the water leak sensor.

Pressing the button causes a special attribute report to be sent. Could you turn on logging (I think it’s APS level 2) so deCONZ lists the payload of incoming messages on a separate line with asdu and list the Xiaomi special attribute payload? Also, what swversion does the sensor report? Is that the same of the sensors not reporting false positives?

I think I saw some false positives just after installing v2.22.1-beta, but these were caused by an almost empty battery in the sensor. The value of config.battery for these (and many other Xiaomi button cell powered) sensors is utterly useless for detecting this - I think we should expose the voltage as reported by the sensor in addition to the (wrongly) extrapolated level. Anyway, changing the battery solved my issue, and I haven’t seen any false positives since.

Make sure to test the new battery before installing it to the sensor - it should deliver at least 3.0V. I’ve seen new button cell batteries that already lost too much power during storage.

S474N · 2023-06-27T08:15:03Z

@bennydiamond same problem as me. but unfortunately I didn't manage to fill out the form, so it was closed to me. By the way, I first reported on Discord a month ago...

#7059

EDIT: the special thing is that there is always about 50 minutes between announcements

EDIT2: @ebaauw my battery has 2.92-2.90V in one sensor, but changed for new with 3.21 and will wait :)

EDIT3: testing new battery and it's same. I also tested restarting the container and then pressing the buttons on the sensor and it also declared an alarm.

Log:

2023-06-27T08:43:58.533958042Z 10:43:58:409 	asdu (length: 2): c607
2023-06-27T08:43:58.533971246Z 10:43:58:414 APS-DATA.indication srcAddr: 0x60d0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0000, lqi: 255, rssi: -57
2023-06-27T08:43:58.533985042Z 10:43:58:414 	asdu: 1c5f113b0a050042156c756d692e73656e736f725f776c65616b2e61713101ff42220121e50b03281a0421a84305211b0006240000000000082104020a21b3f4641001
2023-06-27T08:43:58.533999579Z 10:43:58:417 [INFO] - No button map for: lumi.sensor_wleak.aq1, unicast to: 0x0000, endpoint: 0x01, cluster: BASIC (0x0000), command: 0x0A, payload: 050042156C756D692E73656E736F725F776C65616B2E61713101FF42220121E50B03281A0421A84305211B0006240000000000082104020A21B3F4641001, zclSeq: 59
2023-06-27T08:43:58.534014838Z 10:43:58:418 ZCL attribute report 0x00158D00024BFCE7 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F 
2023-06-27T08:43:58.534049486Z 10:43:58:419 	payload: 050042156c756d692e73656e736f725f776c65616b2e61713101ff42220121e50b03281a0421a84305211b0006240000000000082104020a21b3f4641001
2023-06-27T08:43:58.534069912Z 10:43:58:421 Websocket 10.0.0.200:47634 send message: {"attr":{"id":"32","lastannounced":null,"lastseen":"2023-06-27T08:43Z","manufacturername":"LUMI","modelid":"lumi.sensor_wleak.aq1","name":"ZAPLAVA_sklep","swversion":"0.0.0_0004","type":"ZHAWater","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 338)
2023-06-27T08:43:58.534161966Z 10:43:58:422 Websocket 10.0.0.1:52445 send message: {"attr":{"id":"32","lastannounced":null,"lastseen":"2023-06-27T08:43Z","manufacturername":"LUMI","modelid":"lumi.sensor_wleak.aq1","name":"ZAPLAVA_sklep","swversion":"0.0.0_0004","type":"ZHAWater","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 338)
2023-06-27T08:43:58.534188985Z 10:43:58:424 Websocket 10.0.0.200:47634 send message: {"config":{"battery":100,"on":true,"reachable":true,"temperature":2600},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 167)
2023-06-27T08:43:58.534205744Z 10:43:58:425 Websocket 10.0.0.1:52445 send message: {"config":{"battery":100,"on":true,"reachable":true,"temperature":2600},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 167)
2023-06-27T08:43:58.534221855Z 10:43:58:427 Websocket 10.0.0.200:47634 send message: {"e":"changed","id":"32","r":"sensors","state":{"lastupdated":"2023-06-27T08:43:58.417","water":true},"t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 159)
2023-06-27T08:43:58.534238003Z 10:43:58:428 Websocket 10.0.0.1:52445 send message: {"e":"changed","id":"32","r":"sensors","state":{"lastupdated":"2023-06-27T08:43:58.417","water":true},"t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 159)
2023-06-27T08:43:58.534253780Z 10:43:58:429 APS-DATA.request id: 29, addrmode: 0x03, addr: 0x00158d00024bfce7, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04
2023-06-27T08:43:58.534268095Z 10:43:58:430 	asdu (length: 2): 2400
2023-06-27T08:43:58.534288317Z 10:43:58:437 APS-DATA.confirm id: 27, status: 0x00 SUCCESS
2023-06-27T08:43:58.534303539Z 10:43:58:439 APS-DATA.confirm request id: 27 -> confirmed, timeout 435122801
2023-06-27T08:43:58.534317335Z 10:43:58:452 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -57

EDIT4: already after replacing the battery:

ebaauw · 2023-06-27T13:12:21Z

The sensor reports Model Identifier (0x0005) and the special attribute (0xFF01) in one message, in response to pressing the button.

attr tp  l                           model identifier
---- -- -- ------------------------------------------
0500 42 15 6c756d692e73656e736f725f776c65616b2e617131
        21  l u m i . s e n s o r _ w l e a k . a q 1

                                   1                       2                       3
            1 2  3 4  5 6  7  8 9  0 1  2 3  4 5  6 7  8 9 0 1 2  3 4  5 6  7 8  9 0  1 2  3
attr tp  l   battery    temp         ?   RSSI dB             LQI  firmware    parent    leak
---- -- -- --------- ------- --------- --------- --------------- --------- --------- -------
01ff 42 22 0121 e50b 0328 1a 0421 a843 0521 1b00 0624 0000000000 0821 0402 0a21 b3f4 6410 01
        34    3.045V    26°C                                    0.0.0_0004              leak

deCONZ is working as expected; the sensor does actually report leak detected through the XIaomi special attribute. Battery should be OK at 3.045V, though. Note the older firmware (my newest sensor has 0.0.0_0006, however this model doesn't seem to support firmware updates, not even through the Aqara M2 hub). Also note that the reported length of the special attribute value is wrong (34 bytes reported vs 33 bytes sent), but that's the case on my sensors as well.

Did you try shorting the contacts for a while? Does the detection state change when you remove the shortcut? I vaguely remember messing with the sensor for a bit, after replacing its battery, but I haven't kept a log of what I did exactly. I might have done a factory reset and re-pair to deCONZ.

If everything else fails, you could delete the state/water_bis item from the DDF, so deCONZ ignores the leak state (tag 64) from the special attribute.

EDIT: the special thing is that there is always about 50 minutes between announcements

That's the interval of the regular special attribute reports.

S474N · 2023-06-27T13:24:07Z

Look at my closed bug report: #7059

I just wrote here that I have several water leakage sensors. Two of them have a different FW version than the other three (I also added screenshots there). Now older sensors are 0.0.0_0004, but were 20170721. Newest are now 0.0.0_0006, before upgrade 20200310.

As soon as I'm at the device, I'll try artificially shorting the sensor and send the log if there's any difference in it.

I'm sorry, but I don't know what DDF is and how I can delete the given parameter from it, I'm just a user ;)

EDIT: logs:

All time:

2023-06-27T14:35:17.093566348Z 16:35:17:024 APS-DATA.indication srcAddr: 0x60d0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0000, lqi: 255, rssi: -57
2023-06-27T14:35:17.093675069Z 16:35:17:024 	asdu: 1c5f11420a01ff42220121110d03281a0421a84305211b0006240100000000082104020a21b3f4641001
2023-06-27T14:35:17.093693810Z 16:35:17:026 [INFO] - No button map for: lumi.sensor_wleak.aq1, unicast to: 0x0000, endpoint: 0x01, cluster: BASIC (0x0000), command: 0x0A, payload: 01FF42220121110D03281A0421A84305211B0006240100000000082104020A21B3F4641001, zclSeq: 66
2023-06-27T14:35:17.093790624Z 16:35:17:027 ZCL attribute report 0x00158D00024BFCE7 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F 
2023-06-27T14:35:17.093829160Z 16:35:17:028 	payload: 01ff42220121110d03281a0421a84305211b0006240100000000082104020a21b3f4641001
2023-06-27T14:35:17.093843771Z 16:35:17:028 Websocket 10.0.0.200:55798 send message: {"attr":{"id":"32","lastannounced":null,"lastseen":"2023-06-27T14:35Z","manufacturername":"LUMI","modelid":"lumi.sensor_wleak.aq1","name":"ZAPLAVA_sklep","swversion":"0.0.0_0004","type":"ZHAWater","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 338)
2023-06-27T14:35:17.093862382Z 16:35:17:030 Websocket 10.0.0.200:55798 send message: {"config":{"battery":100,"on":true,"reachable":true,"temperature":2600},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 167)
2023-06-27T14:35:17.093878660Z 16:35:17:032 Websocket 10.0.0.200:55798 send message: {"e":"changed","id":"32","r":"sensors","state":{"lastupdated":"2023-06-27T14:35:17.026","water":true},"t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 159)
2023-06-27T14:35:17.253247266Z 16:35:17:109 rule event /config/localtime: 16:35:16.109 -> 16:35:17.109 (1000ms)

When sensors are connected:

2023-06-27T14:43:19.973941299Z 16:43:19:940 APS-DATA.indication srcAddr: 0x60d0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -57
2023-06-27T14:43:19.974032872Z 16:43:19:941 	asdu: 194300010000ff0000
2023-06-27T14:43:19.974049409Z 16:43:19:942 void DeRestPluginPrivate::handleIasZoneClusterIndication(const deCONZ::ApsDataIndication&, deCONZ::ZclFrame&),196: assertion 'itemIasState' failed
2023-06-27T14:43:19.974064983Z 16:43:19:943 void DeRestPluginPrivate::handleIasZoneClusterIndication(const deCONZ::ApsDataIndication&, deCONZ::ZclFrame&),197: assertion 'itemPending' failed
2023-06-27T14:43:19.974080149Z 16:43:19:943 [INFO] - No button map for: lumi.sensor_wleak.aq1, unicast to: 0x0000, endpoint: 0x01, cluster: IAS_ZONE (0x0500), command: STATUS_CHANGE (0x00), payload: 010000FF0000, zclSeq: 67
2023-06-27T14:43:19.974094945Z 16:43:19:944 Websocket 10.0.0.200:55798 send message: {"attr":{"id":"32","lastannounced":null,"lastseen":"2023-06-27T14:43Z","manufacturername":"LUMI","modelid":"lumi.sensor_wleak.aq1","name":"ZAPLAVA_sklep","swversion":"0.0.0_0004","type":"ZHAWater","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"},"e":"changed","id":"32","r":"sensors","t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 338)
2023-06-27T14:43:19.974113760Z 16:43:19:945 Websocket 10.0.0.200:55798 send message: {"e":"changed","id":"32","r":"sensors","state":{"lastupdated":"2023-06-27T14:43:19.942","water":true},"t":"event","uniqueid":"00:15:8d:00:02:4b:fc:e7-01-0500"} (ret = 159)
2023-06-27T14:43:20.134069018Z 16:43:20:109 Wait 1s till query finished
2023-06-27T14:43:20.134192461Z 16:43:20:110 rule event /config/localtime: 16:43:19.109 -> 16:43:20.109 (1000ms)

bcutter · 2023-07-02T16:15:10Z

Please see https://forum.phoscon.de/t/aqara-leak-sensor-new-firmware-unavailable-entities-in-ha/3702/14.

Summary: since updating to 2.22.2 (deCONZ addon for Home Assistant) and restarting the container, two entities are missing:

Where's the old DDF? I'd like to use that.

Oh wait: why has this been removed?!?

Remove the non-functional config/enrolled, config/pending, state/lowbattery, and state/tampered that the legacy code exposed. (#6919)

Guys I spent hours trying to bring things back and now I read "ah, well, it has been removed" - which is NOT listed as "breaking change" but as "ENHANCEMENT" (Refactor Xiaomi special attribute handling in DDF https://github.com/dresden-elektronik/deconz-rest-plugin/pull/6919) in https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/v2.22.1-beta. Explanation please. 😠

SwoopX · 2023-07-02T18:21:12Z

Well, imho, it's not a breaking change as the PR doesn't break the two items from the screenshot above. You cannot break what non-existent on the device.

bcutter · 2023-07-02T20:08:51Z

Well, imho, it's not a breaking change as the PR doesn't break the two items from the screenshot above. You cannot break what non-existent on the device.

So there's never been e. g. a low battery feature? What I see is:

before the update: all entities available and working
after the update: two entities unavailable

So technically something broke. If it never was provided from the hardware side so why was it provided in the past... than the PR would be a correction which is good - but the communication is not sufficient, that's the point.

SwoopX · 2023-07-02T22:10:55Z

I'm sorry, but again: you cannot break what's not there. Of course, the question is valid to ask why it was included in the first place but you probably will never get a (satisfying) answer: it was added by an inexperienced user just expecting the feature to be available, items were added as defaults to a certain device category automatically, features were assumed based on the relevant cluster and the device following zigbee standards, accidentally, etc... we're all humans in the end. Corrections/updates on devices happen all the time, similarly to other projects.

They way of communication or level of detail, respectively, is certainly always debatable. In my view, this is also not given for other projects, but I might be wrong here. Not sure if mentioning more details in the release notes would be a silver bullet as they are not frequently checked in my experience.

Anyway, we're drifting away from the topic of this issue, so we should keep it focussed.

andys73 · 2023-07-03T07:02:22Z

The problem is not the tampered and low battery entities, is the most important one which is leak detected! :)
Like I have detailed in https://forum.phoscon.de/t/aqara-leak-sensor-new-firmware-unavailable-entities-in-ha/3702/14 the newer firmware 0.0.0_0006 leak sensor have this problem. The sensors with 0.0.0_0004 firmware are fine.

mirml · 2023-07-03T08:19:21Z

I've got same problem.

bennydiamond · 2023-07-03T11:40:57Z

The problem is not the tampered and low battery entities, is the most important one which is leak detected! :) Like I have detailed in https://forum.phoscon.de/t/aqara-leak-sensor-new-firmware-unavailable-entities-in-ha/3702/14 the newer firmware 0.0.0_0006 leak sensor have this problem. The sensors with 0.0.0_0004 firmware are fine.

I only have sensors with version 0.0.0_0004 firmware and they exhibit the issue.

pergolafabio · 2023-07-04T03:07:51Z

Is it possible this issue is also present on Xiaomi motion sensors, seeing same thing here, I'm not home, and it gives detected state every 2 hours...

mirml · 2023-07-04T03:16:09Z

The problem is not the tampered and low battery entities, is the most important one which is leak detected! :) Like I have detailed in https://forum.phoscon.de/t/aqara-leak-sensor-new-firmware-unavailable-entities-in-ha/3702/14 the newer firmware 0.0.0_0006 leak sensor have this problem. The sensors with 0.0.0_0004 firmware are fine.

I have sensor with version 0.0.0_0003 and that problem.

pergolafabio · 2023-07-04T15:33:32Z

I have 4 Xiaomi motion sensors, they all give me now false detections, one almost every hour, the other one like every 6 hours... Seems all happening after the last update (using ha addon )

SwoopX · 2023-07-04T15:42:06Z

@pergolafabio please do not highjack this issue, however, feel free to create new one. Thanks!

pergolafabio · 2023-07-04T15:44:06Z

@pergolafabio please do not highjack this issue, however, feel free to create new one. Thanks!

I thought it's maybe related to Xiaomi detection in general?

Mimiix · 2023-07-04T15:59:55Z

@pergolafabio please do not highjack this issue, however, feel free to create new one. Thanks!

I thought it's maybe related to Xiaomi detection in general?

Its not. We recommend opening a new one.

ebaauw · 2023-07-04T16:07:01Z

Got a (presumably false) notification from my 0.0.0_0004 sensor today.

Looking at the legacy code, we used to ignore the Xiaomi special attribute for this sensor. So it shouldn't have been added it to the DDF - my bad.

deconz-rest-plugin/xiaomi.cpp

Line 888 in 2f021e0

    
           // item = item ? item : sensor.item(RStateWater);  // lumi.sensor_wleak.aq1, ignore, value is not reliable

I'll prep a PR. In the meantime, as workaround, you can remove the state/water_bis item from the DDF.

S474N · 2023-07-07T17:44:23Z

I tested on all affected sensors to trigger an artificial alarm by connecting both sensors. Since then, I have had peace and no flood has been reported.

Unfortunately, now I started constantly reporting a problem with the Aqara vibration sensor.

Mimiix · 2023-07-08T15:22:58Z

I tested on all affected sensors to trigger an artificial alarm by connecting both sensors. Since then, I have had peace and no flood has been reported.

Unfortunately, now I started constantly reporting a problem with the Aqara vibration sensor.

Please open another report, following the template, for the vibration.

S474N · 2023-07-09T08:11:49Z

...until restart docker. Now is it back.

How can I edit DDF please? Right click, Edit DDF and Remove water_bis isn't work.

Tested also Save, but...:

EDIT: OK, edited directly in shell.

docker exec -it deconz bash
apt update
apt upgrade
apt install mcedit
mcedit  /usr/share/deCONZ/devices/xiaomi/lumi_sensor_wleak_aq1.json

and deleted water_bis section, save, quit, restart container and voila.

martind1983 · 2023-07-20T05:17:46Z

I only have sensors with version 0.0.0_0004 firmware and the same issue since upgrade....

S474N · 2023-07-20T08:39:19Z

martind1983: it's only two months from first report :)

I finally solved it by switching to another HW and Zigbee2MQTT.

mirml · 2023-08-04T11:46:27Z

deConz 2.22.2 (HA addon)

I don't have this location:
/usr/share/deCONZ/devices/xiaomi/lumi_sensor_wleak_aq1.json

dxa13 · 2023-08-31T20:07:31Z

Got a (presumably false) notification from my 0.0.0_0004 sensor today.

Looking at the legacy code, we used to ignore the Xiaomi special attribute for this sensor. So it shouldn't have been added it to the DDF - my bad.

deconz-rest-plugin/xiaomi.cpp

Line 888 in 2f021e0

// item = item ? item : sensor.item(RStateWater); // lumi.sensor_wleak.aq1, ignore, value is not reliable

I'll prep a PR. In the meantime, as workaround, you can remove the state/water_bis item from the DDF.

Hi, I tried using your fix with the 2.23.0 beta branch, and my one leak sensor with firmware 0.0.0_0004 (all other 9 I have have firmware 6) is still reporting a false leak. Is that expected after the fix? Is there a way to make the false leak go away without physical interaction of the sensor (i.e. shorting the leads, or re-pair it)?

andys73 · 2023-09-19T11:20:40Z

Just to mention the Aqara leak sensor does not have a firmware version issue. The issue with missing entities for leak and door sensors is caused by the bad ddf in the Lidl watering system see https://forum.phoscon.de/t/aqara-door-sensors-entities-not-available-in-ha/3949/16
You will have to remove the LIDL watering system and re-add it after the next release where it has been fixed.

SwoopX · 2023-09-19T11:46:13Z

Hi and thanks for mentioning. However, we should highlight that a missing property of a different device does not affect the Xiaomi leak sensor and therefore, deconz REST API in any way. If a REST API clients gets confused based on that, it's unfortunate.

martind1983 · 2023-10-25T22:23:13Z

Any news on this topic? I did a complete new system installation, but still having the issue with my water leak sensors (both with firmare 0004) reporting a false leak. Initially I thought they are working now, but after a reboot of the system, since more than 1 hour false leak reported.
My Gateway 2.24.1 / Firmware 26780700
According to the release notes, this was / should be already included in my 2.24.1 version? or am I wrong?

andys73 · 2023-10-26T11:20:40Z

I have 10 leak sensors and none of them received any fake alert.
I am running the stable release
version 2.22.02 / firmware 26780700

bennydiamond added the Bug report label Jun 26, 2023

Mimiix added the Confirmed Bug label Jul 4, 2023

ebaauw mentioned this issue Jul 7, 2023

Bug fix: false water detection for lumi_sensor_wleak_aq1 #7091

Merged

ebaauw linked a pull request Jul 7, 2023 that will close this issue

Bug fix: false water detection for lumi_sensor_wleak_aq1 #7091

Merged

manup closed this as completed in #7091 Jul 20, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Xiaomi Aquara Water leak sensor (SJCGQ11LM) falsely reports trouble on deConz 2.22.2 (HA addon) #7061

Xiaomi Aquara Water leak sensor (SJCGQ11LM) falsely reports trouble on deConz 2.22.2 (HA addon) #7061

bennydiamond commented Jun 26, 2023 •

edited

Mimiix commented Jun 27, 2023

Larry0ua commented Jun 27, 2023

ebaauw commented Jun 27, 2023

S474N commented Jun 27, 2023 •

edited

ebaauw commented Jun 27, 2023 •

edited

S474N commented Jun 27, 2023 •

edited

bcutter commented Jul 2, 2023

SwoopX commented Jul 2, 2023

bcutter commented Jul 2, 2023

SwoopX commented Jul 2, 2023

andys73 commented Jul 3, 2023

mirml commented Jul 3, 2023

bennydiamond commented Jul 3, 2023

pergolafabio commented Jul 4, 2023 •

edited

mirml commented Jul 4, 2023

pergolafabio commented Jul 4, 2023

SwoopX commented Jul 4, 2023

pergolafabio commented Jul 4, 2023

Mimiix commented Jul 4, 2023

ebaauw commented Jul 4, 2023

S474N commented Jul 7, 2023

Mimiix commented Jul 8, 2023

S474N commented Jul 9, 2023 •

edited

martind1983 commented Jul 20, 2023

S474N commented Jul 20, 2023 •

edited

mirml commented Aug 4, 2023

dxa13 commented Aug 31, 2023

andys73 commented Sep 19, 2023

SwoopX commented Sep 19, 2023

martind1983 commented Oct 25, 2023

andys73 commented Oct 26, 2023

Xiaomi Aquara Water leak sensor (SJCGQ11LM) falsely reports trouble on deConz 2.22.2 (HA addon) #7061

Xiaomi Aquara Water leak sensor (SJCGQ11LM) falsely reports trouble on deConz 2.22.2 (HA addon) #7061

Comments

bennydiamond commented Jun 26, 2023 • edited

Describe the bug

Steps to reproduce the behavior

Expected behavior

Environment

Additional context

Mimiix commented Jun 27, 2023

Larry0ua commented Jun 27, 2023

ebaauw commented Jun 27, 2023

S474N commented Jun 27, 2023 • edited

ebaauw commented Jun 27, 2023 • edited

S474N commented Jun 27, 2023 • edited

bcutter commented Jul 2, 2023

SwoopX commented Jul 2, 2023

bcutter commented Jul 2, 2023

SwoopX commented Jul 2, 2023

andys73 commented Jul 3, 2023

mirml commented Jul 3, 2023

bennydiamond commented Jul 3, 2023

pergolafabio commented Jul 4, 2023 • edited

mirml commented Jul 4, 2023

pergolafabio commented Jul 4, 2023

SwoopX commented Jul 4, 2023

pergolafabio commented Jul 4, 2023

Mimiix commented Jul 4, 2023

ebaauw commented Jul 4, 2023

S474N commented Jul 7, 2023

Mimiix commented Jul 8, 2023

S474N commented Jul 9, 2023 • edited

martind1983 commented Jul 20, 2023

S474N commented Jul 20, 2023 • edited

mirml commented Aug 4, 2023

dxa13 commented Aug 31, 2023

andys73 commented Sep 19, 2023

SwoopX commented Sep 19, 2023

martind1983 commented Oct 25, 2023

andys73 commented Oct 26, 2023

bennydiamond commented Jun 26, 2023 •

edited

S474N commented Jun 27, 2023 •

edited

ebaauw commented Jun 27, 2023 •

edited

S474N commented Jun 27, 2023 •

edited

pergolafabio commented Jul 4, 2023 •

edited

S474N commented Jul 9, 2023 •

edited

S474N commented Jul 20, 2023 •

edited