[Reactor] Variables not updating correctly in latest-25201-2aa18550

[Pabla]

Hello all, I recently installed a Zooz ZEN 32 scene controller and was looking for some guidance on how I could use a button press as a trigger in MSR. The scene controller has a total of 5 buttons that can activate scenes based on single press, double press, triple till 5 presses and also a press and hold. Currently in MSR I see an entity for the scene controller itself and separate entities for each button.

Using the MSR native Z wave controller I can see the button.state (shows if it was pressed single double...) and button.since which shows the last time the button was pressed. The issue with the button.state is that say I press the scene controller button once its state is single but it never "resets" it's state will remain single. So if I press the button again the trigger won't work (pulse action won't work here because the state never changes).

Going through HA similar issue but instead the x_hass.state is used and the number pertains to how many presses 0 means one press, 3 means 2 presses and so on. But again the x_hass.state never resets to an "off" state so retriggering the rule will not work if you press the button again.

Before I tackle this in other ways using separate rules, input booleans and expressions is there any other way I can go about this? To me I need to trigger that is something like button_pressed.single but I don't see that option.

No logs since there is technically no issues and no real examples since I am stuck at the triggers part lol.

MSR 23302
Z Wave 0.1.23194
HA 2023.11.2

[Snowman]

If I understand you correcltly, I had the same issue when I first setup this device. Here's what I did to ensure the button state gets reset after a button is pressed two times in my case.

I am using the ZwaveJS controller provided by @togglebit.

Triggers

Controller Scene 001.button.state (primary) == double

Set Reaction

Controller Scene 001.button.release

The "button.release" action ensures the button state resets.

Give it a try.

[Pabla]

@Snowman this is exactly what I needed!! Thanks

[toggledbits]

The "correct" way is to check both the button state and the timestamp (button.since changes each time the button is pressed).

Using the button.release action is not recommended.

[Snowman]

@togglebits Thanks for the recommendation. I do have to ask though.

I am by no means an expert so how am I supposed to know this? The documentation does not mention anything about this. And based on your recommendation, I will have to review all my rules/logics using this device.

Thanks in advance.

[toggledbits]

The question has been asked and answered in prior forum posts.

[Andr]

@Snowman
I think my old thread could be helpful for you.
Good luck
Adding remotes, scene controllers as entities to MSR

[Snowman]

Thank you both @togglebits and @Andr. I got it now.