This makes me think about what I’ve read in the zigbee2mqtt docs some time ago about this button
and the configurable hold timeout:
-
hold_timeout
: The WXKG01LM only reports a button press and release.By default, a hold action is published when there is at least 1000 ms between both events. It could be that due to delays in the network the release message is received late. This causes a single click to be identified as a hold action. If you are experiencing this you can try experimenting with this option (e.g. set it to 2000) (value is in ms). The value must be a number with a minimum value of0
changelog of this blueprint:
- 2021-04-09: Changed Hold time default value (from 1s to 0.6s), along with the minimum hold time ( from 0 to 0.15s), max time (from 10s to 2.5s) and the step (from 1 to 0.05), to allow more granularity and flexibility. Kudos to @jant90
It could be that you have enough delay in the zigbee network that the release from a single press comes in too late and thats why It gets detected as a hold action. Try editing the blueprint to increase the hold time to a higher value again. Maybe this solves the issue