Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.14k stars 1.68k forks source link

WL-19DWZ Wrong message #24613

Open albertinizao opened 1 week ago

albertinizao commented 1 week ago

What happened?

After the 1.41.0, the contact sensor now detected as WL-19DWZ (previous version was detected as SNZB-04) works wrong.

Arbitrarily these devices are sending me incorrect messages with “contact=true” without the actual state of the device having changed. In this case, at 23:10:03 the device did not change his real status, without any movement, but sent these messages.

[2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":false,"linkquality":102,"tamper":false,"voltage":3000}' [2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":false,"linkquality":99,"tamper":false,"voltage":3000}' [2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":false,"linkquality":96,"tamper":false,"voltage":3000}' [2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":true,"linkquality":99,"tamper":false,"voltage":3000}'

What did you expect to happen?

The WL-19DWZ should not send any message with "contact=true" when the door is open

How to reproduce it (minimal and precise)

Version 1.41.0. Put a device WL-19DWZ close and then open it. Review the status is now opened (concact=false). Wait until a message with contact=true is sent, . Sometimes it happens a few minutes later, sometimes a hour later.

Zigbee2MQTT version

1.41.0

Adapter firmware version

20241002

Adapter

Sonoff_Zigbee_3.0_USB_Dongle_Plus

Setup

Add-on on home assistant at raspbery pi

Debug log

[2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":false,"linkquality":102,"tamper":false,"voltage":3000}' [2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":false,"linkquality":99,"tamper":false,"voltage":3000}' [2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":false,"linkquality":96,"tamper":false,"voltage":3000}' [2024-11-02 23:10:03] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Silla Bailey', payload '{"battery":100,"battery_low":false,"contact":true,"linkquality":99,"tamper":false,"voltage":3000}'

Oliohly commented 1 week ago

I got the same problem with any of these devices: they suddenly set 'contact' to 'true' - after long or short duration of time

Koenkk commented 6 days ago

Should be fixed in the latest dev branch