Closed mojaki8286 closed 1 week ago
If you get the device to change state (either dry > wet or wet > dry), does it then display correctly?
It just doesn't change. It just stated NULL. However, overnight it somehow reverted to "Clear" so status changed by itself. The problem now is even if it gets in contact with water it doesn't change to "Leaking", it just stays "Clear".
I'll remove it again from the network and rejoin it and will report back. Until then I will have to manually kick off the sump pump
If you get the device to change state (either dry > wet or wet > dry), does it then display correctly?
Removed it from the network, rejoined. Water_Leak attribute value is NULL. This status does not change when the sensor gets in contact with water. So this is definitely something that worked prior to the update.
Looking in the state.json when restarting the add-on these attributes are not reported on:
"water_leak": false,
"tamper": false,
"battery_low": false,
Only the below: MQTT publish: topic 'zigbee2mqtt/Water Leak/Pump Mid', payload
{
"battery": 90,
"battery_low": null,
"device": {
"applicationVersion": 6,
"dateCode": "20200310",
"friendlyName": "Water Leak/Pump Mid",
"hardwareVersion": 2,
"ieeeAddr": "0x00158d0006e3a965",
"manufacturerID": 4151,
"manufacturerName": "LUMI",
"model": "SJCGQ11LM",
"networkAddress": 43197,
"powerSource": "Battery",
"softwareBuildID": "3000-0001",
"stackVersion": 2,
"type": "EndDevice",
"zclVersion": 1
},
"device_temperature": 24,
"last_seen": "2024-05-05T09:26:15+10:00",
"linkquality": 105,
"power_outage_count": 106,
"trigger_count": -1,
"voltage": 2985,
"water_leak": null
}
Not sure if this helps but also viewing the Home Assistant Core log, this comes up:
Log Details (ERROR): Logger: homeassistant.helpers.template Source: helpers/template.py:772 First occurred: 09:12:56 (2 occurrences) Last logged: 09:12:56
Error parsing value: 'value_json' is undefined (value: , template: {{ value_json.water_leak }}) Error parsing value: 'value_json' is undefined (value: , template: {{ value_json.battery_low }})
Hi so this is my summary,
After numerous testing.
Removing, rejoining, resetting the device (Aqara SJCGQ11LM), adding to different router (I have 3 routers + 1 coordinator in my house). Restoring to the previous zigbee2mqtt version 1.36.1-1. Restoring to hass core_2024.4.1.
I got this to work. The water_leak attribute initially stated NULL, and would not change at all even if dumped into water. All of a sudden it worked and changed from NULL to Leaking. Weird.
It took a day of testing but eventually came right.
Hi so this is my summary,
After numerous testing.
Removing, rejoining, resetting the device (Aqara SJCGQ11LM), adding to different router (I have 3 routers + 1 coordinator in my house). Restoring to the previous zigbee2mqtt version 1.36.1-1. Restoring to hass core_2024.4.1.
I got this to work. The water_leak attribute initially stated NULL, and would not change at all even if dumped into water. All of a sudden it worked and changed from NULL to Leaking. Weird.
It took a day of testing but eventually came right.
Do I understand you right that you got it working when you restored zigbee2mqtt to 1.36.1 and it is not working on 1.37.0?
I also had to revert to 1.36.1 as all four of my SJCGQ11LM sensors stopped working on my Multi Pan SkyConnect.
What happened?
After upgrading to 1.37.0-1 my Aqara SJCGQ11LM water leak sensors started reporting NULL in the water_leak attribute. I have removed, rejoined, removed, rejoined and still reports NULL.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.37.0-1
Adapter firmware version
20220219
Adapter
Sonoff Zigbee 3.0 Dongle Plus
Setup
Add-on P4
Debug log
No response