Press and long_press actions #344
Replies: 4 comments 11 replies
-
|
Hi, thanks for the feedback!
It's easy to do in HomeAssistant, but I don't have NodeRed to guide you. I'll think of making this easier to use, like other remotes in Z2M |
Beta Was this translation helpful? Give feedback.
-
|
It's easy to manage this in NodeRed as well as directly by HA, so never mind :) The small disadvantage is that in this case the reaction is on the releasing than pushing the button, but that's not the issue at all in my case. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
This is exactly why we give you the option..
It's impossible to have both, without triggering both events If you don't want long press, the single press trigger becomes 'when action changes from released to press' Double press will add an additional delay. So when we add it, it will be optional |
Beta Was this translation helpful? Give feedback.
-
|
can you roughly describe how to distinguish between the short press and the long press in an automation? |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
First of all, after flashing my first OXT T262 device I haven't been this happy with something new in the Home Assistant world since I launched my first automation :) Congratulations, really appreciate your work! I think after adding double_press action which was asked by some user, your firmware meets 100% of most users expectations.
I tried to prepare an automation in NodeRed that acts different way for press and long_press actions. What I found is that when I long press the momentary configured button, sensor gives my firstly "press" action" and then additional "long_press". Is this intensional? How can I separate that? I think I can programmatically check what event occurred immediately before "released", but IMHO it complicates things a bit.
Beta Was this translation helpful? Give feedback.
All reactions