Basic Rule Triggering many times

🧰 Built-In Apps and Drivers Basic Rules
1

Basic rules have been pretty nice, thanks for adding it.

I have a basic rule for a HS-WD200+ double tap up turning on a scene device. It seems the HS-WD200+ driver is creating 8 to 10 events when the button is pushed, which causes the basic rule to trigger the same number of times. This manifests as the scene getting “stuck” on for for a few minutes. Turning off a light just has the light mysteriously turn on as the hub processes all the actions and turns on the scene multiple times.

Is there an easy way to debounce a button push? It’d be great if there was a check box in basic rules, “Only execute once in within 2 seconds” or something.

Alternatively, do you have any suggestions to overcome this problem of multiple events triggering the rules multiple times?

dev:712021-07-18 09:43:16.094 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:16.008 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:15.948 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:15.644 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:15.571 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:15.513 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:14.930 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:14.674 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:14.358 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:13.685 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:13.341 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:12.604 am infoScene Main Floor was turned on
dev:712021-07-18 09:43:12.196 am infoScene Main Floor was turned on
dev:712021-07-18 09:34:25.822 am infoScene Main Floor was turned on
dev:712021-07-18 09:26:11.445 am infoScene Main Floor was turned on
dev:712021-07-18 09:24:14.145 am infoScene Main Floor was turned on
2

This is really a device/driver problem. What driver are you using??

There is a simple app that can debounce it (see our public repo for contact debounce -- that could be modified). But really, the driver or device needs to be fixed.

3

I haven't actually tested one of these .. I just ordered one, will be in on tuesday..

4

The HS-WD200+ driver from here [Withdrawn] HomeSeer HS-WD200+ Dimmer Driver - #119 by mike.t.weaver resulted in duplicate events.

I switched over to Any Z-Wave Dimmer Driver v1.1.8 and single events for multi-tap are working as expected.

1 Like
5

Great. FYI, I'd use the System driver, but it doesn't support multi-tap 3,4,5 currently. I'm sure you're aware.

6

It's also missing a lot of other stuff:

  • Changing the remote & local ramp rate
  • Changing between normal mode and status mode
  • Changing all the LEDs in a single command
  • Ability to set the lowest dimming threshold

I'll also say I don't have an issue with multitap at all:

image
image705Ă—181 2.77 KB

image

Are you doing it with buttons?
Here are the button mappings posted in the driver you were using:
image

7

Yes, to be clear buttons 1-12 generate events with that driver, but the problem is they trigger 8-10 times creating lots of duplicate actions in RM.

8

That's weird! Mine don't trigger more than once at all.

Can you send me everything I need to know to replicate your setup? I'd like to get it reproducible and then we can see what needs to be fixed in the driver.