Not working SJCGQ11LM (lumi.sensor_wleak.aq1)

[vladik1969]

Hello. Gateway ZNDMWG03LM. Checked versions 1.5.0_0102 and 1.5.4_0090. Zigbee is mode "Mi Home". After upgrade plugin to 3.3 not update binary sensor "moisture", only battery and zigbee.

On gateway in MQTT topic

1. gw/IEEE/MessageReceived {"sourceAddress":"0xA6F7","eui64":"0x00158D000484C1A0","destinationEndpoint":"0x01","clusterId":"0x0000","profileId":"0x0104","sourceEndpoint":"0x01","APSCounter":"0x22","APSPlayload":"0x1C5F119A0A01FF42220121F90B03281C0421A8430521400006240100000000082104020A21738A641000","rssi":-33,"linkQuality":255}
2. zigbee/send {"cmd":"heartbeat","id":2000000155,"time":1687870547735,"rssi":-33,"params":[{"did":"lumi.158d000484c1a0","time":1687870547735,"zseq":154,"res_list":[{"res_name":"8.0.2008","value":3065},{"res_name":"8.0.2001","value":100},{"res_name":"8.0.2006","value":28},{"res_name":"8.0.2011","value":4},{"res_name":"8.0.2010","value":3},{"res_name":"8.0.2012","value":10},{"res_name":"8.0.2013","value":1},{"res_name":"8.0.2002","value":64},{"res_name":"8.0.2003","value":1},{"res_name":"8.0.2004","value":0},{"res_name":"8.0.2005","value":0},{"res_name":"8.0.2033","value":0},{"res_name":"8.0.2022","value":4},{"res_name":"8.0.2023","value":2},{"res_name":"8.0.2036","value":"lumi.158d000572626d"},{"res_name":"8.0.2007","value":255}]}]}

Other devices (RTCGQ11LM, MCCGQ11LM, ZNLDP12LM) working right.

[AlexxIT]

There is no moisture info in your log. Integration can't show info if your device doesn't send it.

[vladik1969]

I known it. Before upgrade I saw the info (in HA). After upgrade - not. And I have not one device this type. All are to working wrong now. May be the problem because of new version of mio agent?

[AlexxIT]

Don't think so. I have a lot of those sensors.

[vladik1969]

in the mi home application, the state of the sensors is reflected correctly, in HA - no. And it started after the update to 3.3. Might be a coincidence, but I don't really believe in them.

[AlexxIT]

Have you wet your sensor?

[vladik1969]

No. I don't have direct access to the sensors. But I think that if the plugin received heartbeat information from the device and not alarm information, you can use the value "false" and not "unknown" for that sensor.

[AlexxIT]

If you get the sensor wet, you will see a message about it. You will also see a message if the sensor dries out. It is wrong to focus on the heartbeat.

[vladik1969]

Wetting the sensors after each reboot of the gateway is already overkill. I don't know how this sensor works. I can only assume that he should not send only a heartbeat when there is a leak. If this is the case, then the initial value may well be set based on receiving only the heartbeat without alarm report. And I repeat, this problem arose only now. Before the values of these sensors were displayed correctly in HA.

[dansh1n]

I confirm, I have a similar problem after updating to 3.3.x.

After humidity appears on the sensor, the status changes. After the sensor is drying the sensor, the status also changes, but then after some time it goes into "unknown" status.