-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
IKEA Badring E2202 not reporting water leak correctly #21794
Comments
I’ll look into that. Also, could you please share the entry from database.db? I think it can do a little bit more than the current converter is exposing. |
Here it is
|
What it is reporting on my side: (Looks the same) The converter that works on my side: `// Add the lines below const {batteryPercentage, identify} = require('zigbee-herdsman-converters/lib/modernExtend'); const definition = { module.exports = definition;` It was updated in Koenkk/zigbee-herdsman-converters#7196 after my commit. Maybe something went wrong there? |
I've double checked the converter, extend and even the boolean math. I can't find anything out of the ordinary. That is so strange |
I've found the bug. When the alarms have the same name, the returning object has the same property name twice. Which is impossible and the second one ( |
@MiAutomations make a new seperate issue. Make sure you have z2m updated. |
Done https://github.com/Koenkk/zigbee2mqtt/issues/22616 Yes I'm using the last Z2M version |
What happened?
I've noticed that water leak is not reported correctly. When I simulate the leak, device beeps and red light is blinking, the MQTT messages are generated, but
water_leak
is alwaysfalse
MQTT publish: topic 'zigbee2mqtt/0x38398ffffe0axxxx/water_leak', payload 'false'
What did you expect to happen?
Payload should contain
true
forwater_leak
when device is reporting leak visuallyHow to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.36.0-dev commit: 720fc49
Adapter firmware version
20211217
Adapter
zzh!
Setup
Pi 3B+
Debug log
The text was updated successfully, but these errors were encountered: