Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xiaomi SJCGQ11LM Water Sensor - False Positives #1967

Closed
coolguymatt opened this issue Sep 13, 2019 · 24 comments
Closed

Xiaomi SJCGQ11LM Water Sensor - False Positives #1967

coolguymatt opened this issue Sep 13, 2019 · 24 comments

Comments

@coolguymatt
Copy link

Bug Report

What happened

After updating to zigbee2mqtt to 1.6, I have received two false positives on two of my Xiaomi water leak sensors. For the first one, I could not get it to go back to Dry (Off). Removing and rejoining the device did not fix the issue so I completely removed it from the database manually and rejoined it. This seems to have fixed the first one. After about another hour, the second device had a false positive. It has the same behaviour - it does not go back to Dry (Off) when the device is dry.

What did you expect to happen

Accurate water leak readings

How to reproduce it (minimal and precise)

Random

Debug Info

zigbee2mqtt version: 1.6
CC253X firmware version: CC2531_DEFAULT_20190608.zip

@mpuff
Copy link

mpuff commented Sep 13, 2019

i also get a false "true" notification yesterday from a Xiaomi water leak sensor, i am also on zigbee2mqtt 1.6

@groenmarsmannetje
Copy link

I also have experienced this today. Sensor is still reporting leakage, but is dry. Even after removing battery and reconnect. I updated to version 1.6 just before this sensor turned on.

@ptvoinfo
Copy link
Contributor

ptvoinfo commented Sep 14, 2019

I've added this update to the latest version but my sensors work well. It seems we should an option (disable or enable) interval reports for these sensors. @Koenkk, what do think?

Also, this problem was mentioned before in Koenkk/zigbee-herdsman-converters#109

@Koenkk
Copy link
Owner

Koenkk commented Sep 14, 2019

Im wondering if the converter is actually correct @ptvoinfo how do you know these are the correct values?

@ptvoinfo
Copy link
Contributor

@Koenkk I've tested it with the real device and simulate water leaks. I have 2 sensors, both works identically.

@groenmarsmannetje
Copy link

But why has it changed? It used to work without any problems. My sensor is still reporting leakage and has become totally useless now.

@docBliny
Copy link

I started having the exact same issue. I currently have ~15 sensors going off causing me to get alerts throughout the day. I'm using zigbee2mqtt on Home Assistant. I see lines similar to the following in the Docker log:

zigbee2mqtt:info 9/15/2019, 12:08:06 PM MQTT publish: topic 'zigbee2mqtt/water_leak_1', payload '{"water_leak":true,"linkquality":2,"battery":100,"voltage":3065}

This started immediately after updating to 1.6.

@ptvoinfo
Copy link
Contributor

ptvoinfo commented Sep 16, 2019

The quick temporary workaround is to edit the following file:
node_modules\zigbee-shepherd-converters\devices.js
Find

        zigbeeModel: ['lumi.sensor_wleak.aq1'],
        model: 'SJCGQ11LM',
        vendor: 'Xiaomi',
        description: 'Aqara water leak sensor',
        supports: 'water leak true/false',
        fromZigbee: [
            fz.xiaomi_battery_3v, fz.SJCGQ11LM_water_leak_iaszone,
            fz.SJCGQ11LM_water_leak_interval, fz.ignore_basic_change,
        ],
        toZigbee: [],
    },

and remove fz.SJCGQ11LM_water_leak_interval, .

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Sep 16, 2019
@Koenkk
Copy link
Owner

Koenkk commented Sep 16, 2019

Fixed in the dev branch (removed converter).

@Koenkk Koenkk closed this as completed Sep 16, 2019
@ptvoinfo
Copy link
Contributor

ptvoinfo commented Sep 17, 2019

@Koenkk Can I add this converter as a device option? Because it works for some devices?

@Koenkk
Copy link
Owner

Koenkk commented Sep 17, 2019

Yes

@gecata93
Copy link

gecata93 commented Oct 8, 2019

This issue is marked as fixed(closed) but i still experience this problem, is the new version deployed with this fix? And if yes? What i need to do, to get these changes?

I'm using: Zigbee2mqtt Hass.io Add-on
Aqara water leak sensor (SJCGQ11LM)
Firmware: Zigbee2mqtt 1.6.0

@Koenkk
Copy link
Owner

Koenkk commented Oct 9, 2019

@gecata93 it is not in zigbee2mqtt but in the latest dev (edge for hassio)

@gecata93
Copy link

gecata93 commented Oct 9, 2019

@Koenkk oh okay, thanks. When will be available for the stable(regular) version?

@Koenkk
Copy link
Owner

Koenkk commented Oct 9, 2019

@gecata93 in zigbee2mqtt 1.7.0 (no eta)

@VivantSenior
Copy link

In my case simple trick helped. @gecata93, just try to simulate leak (connect two screws at the bottom of sensor) using wire or just put it in the cup with water. After few seconds break the wire circuit / remove sensor from the cup. Now the sensor should detect real leakage.

@apeeters
Copy link

apeeters commented Feb 5, 2020

I still experience this in 1.9.0 :(

@docBliny
Copy link

docBliny commented Feb 5, 2020

I still experience this in 1.9.0 :(

I had that too on some sensors, but then found out that the battery was dead in those... Worth a check.

@groenmarsmannetje
Copy link

I only experience this after a restart of Home Assistant. I always have to restart Zigbee2Mqtt otherwise one water leak sensor will report that it detects water.

@apeeters
Copy link

apeeters commented Mar 5, 2020

I triggered a wet and dry cycle once and seems stable now. I will keep a close look at it for a few more days. Didn't replace the battery.

@apeeters
Copy link

As promised I report back: It is perfectly stable now: no more false positives.

@bbrendon
Copy link

bbrendon commented Apr 9, 2022

Apparently, my house is flooding right now. All 3 of my sensors are triggered. The place is dry.
It's broken again. version 1.25.0

@mpuff
Copy link

mpuff commented Apr 9, 2022

I had the same yesterday on 2 of 3 sensors, also on 1.25.0

@Koenkk
Copy link
Owner

Koenkk commented Apr 9, 2022

See #12018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants