Aqara water leak sensor reports false leakage after update to latest version

[groenmarsmannetje]

What happened?

I have 3 of these Aqare water leak sensors and after updating to version 1.25.0 they all give false leakage reports because it is still totally dry.

What did you expect to happen?

The state of these water leak sensors should be unaffected after update.

How to reproduce it (minimal and precise)

I only updated to new version of the Home Assistant zigbee2mqtt addon.

Zigbee2MQTT version

1.25.0

Adapter firmware version

20211217

Adapter

zzh

Debug log

No response

[xekil]

Hello,

I had exactly the same problem and after several hours looking for a solution I found a very simple solution to solve this problem, just soak the detector in water so that it sends a leak alert, then just dry it and the status becomes dry in home assistant.

Hoping to have helped you ;)

[groenmarsmannetje]

@xekil thanks for sharing. I will try this out. Probably connecting the two metal pins with a paperclip will already do the trick.

[xekil]

@groenmarsmannetje with pleasure

[groenmarsmannetje]

I can confirm that this workaround also worked for me. I will leave the issue open for a while so that others who also experience this, can read this.

[groenmarsmannetje]

Very annoying … after a couple of restarts the sensors are giving false reports again.

[Koenkk]

@groenmarsmannetje could you provide the debug log when the incorrect reports are being send?

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging.

[groenmarsmannetje]

At the moment the sensors are acting normally again. But will do this next time when it occurs again.

[njordan77]

Having the same problem immediately after updating to 1.25
the workarround does fix it, but the issue comes back again after a while.
battery removal does not help, but this was mentioned before as the issue already came up in 2019.

@Koenkk any idea why this issue now is present @1.25? I'm using z2m for years and having the waterleak sensors at least 2 years but never had this behaviour. Cheers and thanks, Norbert

[Koenkk]

@McGiverGim I expect this is is caused by https://github.com/Koenkk/zigbee-herdsman-converters/blob/2351faa29151a1d4ef34a1012bd5159f57454537/lib/xiaomi.js#L215 , before Koenkk/zigbee-herdsman-converters#3994 we didn't parse any message from the basic Xiaomi cluster: https://github.com/Koenkk/zigbee-herdsman-converters/blob/6f422d10d1d10e41cdc5dae22f584c5a4a9d2345/devices/xiaomi.js#L904

[McGiverGim]

I will look into it. I've one Aqara water leak so I can try to reproduce.

[McGiverGim]

Some of you, with the problem, can put the logs in debug mode and look for something like:

debug 2022-04-02 20:49:35: Received Zigbee message from 'fuga_agua_ac', type 'attributeReport', cluster 'genBasic', data '{"65281":{"1":3125,"10":41058,"100":0,"3":24,"4":13224,"5":43,"6":[0,1],"8":516}}' from endpoint 1 with groupID 0

with the name of the Aqara device?
If it does not appear (this messages is sent by the device in a periodic manner), push the "button" on the device and it will send one of them.

[McGiverGim]

Nobody can publish some log with the problem? In my case, I can't reproduce the problem.

This is a log without water:

debug 2022-04-03 09:36:28: Received Zigbee message from 'fuga_agua_ac', type 'attributeReport', cluster 'genBasic', data '{"65281":{"1":3125,"10":41058,"100":0,"3":24,"4":13224,"5":43,"6":[0,0],"8":516},"modelId":"lumi.sensor_wleak.aq1"}' from endpoint 1 with groupID 0

This is a log with water:

debug 2022-04-03 09:39:56: Received Zigbee message from 'fuga_agua_ac', type 'attributeReport', cluster 'genBasic', data '{"65281":{"1":3125,"10":41058,"100":1,"3":25,"4":13224,"5":43,"6":[0,1],"8":516},"modelId":"lumi.sensor_wleak.aq1"}' from endpoint 1 with groupID 0

As you can see, the attribute 100 shows 0 and 1 that is what the code expects. We suppose that you are getting something different here and only want to be sure before doing a blind revert.