C8 latest - Using Tuya Zigbee Scene Switch Driver
My rules are failing because it looks like the driver for this holds TWO states to be true? Is there a way to clear them? The only option that looks like it would even possibly do this is “configure.” …and it doesn’t?
I JUST started this process…but it just seems really odd ANY controller would do this.
What driver are you using? Can you post a screen shot of the device page for this “scene switch”?
Use the HE inbuilt ‘Button Controller’ instead of RM5.
Or split your current rule into four RM5 rules.
Any button brand and any button driver will act like this.
Maybe?
I’ve had hand help remotes and Zooz 5 button switches and none of them have done this? I will try that driver…THANKS!!!
No, I meant to use the HE App ‘Button Controller’
Is this device presented as switches or as buttons?
The switches have on and off state attributes.
The buttons are stateless. You can use only the event generated in the RM5 rules as a trigger. Inside the rule you can not check the ‘pushed’ or ‘double tapped’ states, as there are not states for buttons. Only events.
For now…I just made two rules…
One for 4 buttons pushed
One for four buttons double click
It just I’ve never had to do that before…clueless why it won’t pass the most recent single state…imho…almost makes it useless.
l know it works …but I already have almost 100 rules…2 to do one thing is a bit frustrating…three when I add a couple long press options.
The Button Controller app is tailor-made for this sort of thing, and it has Rule Machine under its hood.
I think you are confusing states and events. In your rule, if it triggers off of doubleTapped as an event, you then check pushed state even for a doubleTapped event, not checking if that was the event that triggered the rule.
Nope…just not used to two thing being true after a change
Look at the rule …after button change TWO STATES SHOW AS TRUE IN THE RULE.
This is how the button devices work in Hubitat. The ‘pushed’ and ‘double tapped’ attributes are not states, you should not use these in conditions. The attributes are just used to fire events as triggers in HE automations.
THANKS!
Maybe I’m not following since they work well in IF statements just fine? 0
Anyway, if I wasn’t matching on them in if statements I need EIGHT rules to get this done?That’s totally ridiculous to a KISS fan. Add long presses to that and that number goes to 12 to run a single 4 button switch. I’m not thrilled even my way would take 3.
Have you tried the button controller app as suggested above?
I have not Mark …but will.
That’s probably the right long term answer…i’ve been rushing just a little bit to get it set up for my significant other… That isn’t always thrilled with Home automation to begin with to say the least
Or even needing to talk to Alexa
It’s probably the right short-term answer too 
.
Thanks…
So, I do like the fact that the app pulls all of these out of the general rule machine tab from an organizational perspective…and works just like rule machine. That’s awesome…
I do wish every button action didn’t create a whole entry.
So, I can do what I need for 12 different triggers in rule machine with only 3 rules. Someone said NOT to do it that way. Will this break or stop working? Why is this kind of considered “bad form.”
This is why:
You can trigger a rule based off a button push or double tap.
You cannot check, within the rule’s actions, “was button 1 just pushed or double tapped?”
You’ve said a couple times you want to keep things simple.
Rule Machine is the wrong tool for what you’re trying to do. And it’s more complicated to use.
Button Controller is the right tool. And it’s simpler to use.
Sorry, but I really do like to see as much of what any device does in a single entry/page. I understand you disagree. That said…is there any reason how I’ve done it doesn’t work?
