ZHA Debounce

I have a persistent issue that my Zigbee push buttons send multiple events if they have been idle for a period of time (only a few minutes) and then I press them. This happens with my Smartthings buttons that I brought over as part of my Smartthings Divorce as well as a my Sonoff SNZB-01 buttons and a recently purchased Sengled E1E-G7F.

As I use Node-Red for my automations I have solved this by using a Node-Red Throttle node to throw away these extra events although this does add a short delay, limiting how fast I can execute a single press, double-press or a press and hold action. Not a show stopper but it seems to be a clunky way to keep these wake up events from triggering any unnecessary downstream actions.

Has anyone else experienced this issue and if so, how did you solve it. I am using a HUSBZB-1 USB radio on a Pi 4 with 8G and an 128G SSD. An example of one of my use cases is using a Smartthings button to control the bedside light (toggle on/off with a single-press), ceiling lights (toggle on/off with a press and hold) and a reading light by a chair in the bedroom (toggle on/off with a double-press). Without the 2 second Throttle node I would experience multiple toggles if the button had been idle for a while. Once it “wakes up” there were no multi event issues but the initial action would turn the light on and then off.

As I mentioned, the Throttle node works and doesn’t cause any issues unless I try to do different button presses to quickly. Overall, a 99% satisfaction level - I am really trying to understand if there is a better solution.

Thanks

I’m having the same issue as you. Is this still the best solution that you have found?

If you mean am I still using the Throttle node, yes that has been the only consistent and minimal impact solution. I no longer even notice the need to wait a couple of seconds.

1 Like