awesome-ha-blueprints
awesome-ha-blueprints copied to clipboard
Enhancement - Short Button Release
Blueprint name
philips_324131092621
Description
Currently if I have scene 1 bound to button press and scene 2 bound to long button press, on a long press both scene 1 and scene 2 are triggered in sequence.
I would like to instead bind scene 1 to short button release to avoid this situation.
Automation YAML config
No response
Implementation
No response
Additional Details
- [ ] I'd like to help developing this feature/improvement.
Useful resources
No response
Additional context
No response
Hi @sidequestboy,
thank you for reporting here! Which integration are you using to connect the controller to Home Assistant? (from your feedback, I guess it's ZHA)
If I understood correctly, these are the events sequences fired by this device when a certain interaction occur:
- Button long press: 1.Short press event 2.Long Press event 3.Long Release event
- Button short press: 1.Short press event 2.Short release event
Is that right? If this is the case, I think it would be a viable solution to simply use the short release events in place of short press ones in our blueprint. In my opinion exposing both short press and release events would create confusion among users who don't know about this issue with short press events fired when long pressing buttons; they might instead configure actions for short press events, which would result in the same unexpected behavior you experienced and were able to recognize. Moreover, using just short release events, only exposed by ZHA, would allow to have an uniform interface between all the supported integrations.
Please let me know what are your thoughts on this fix. :) Thanks!
oh, let's see if I understand the situation: ZHA is the only integration that exposes short release events, and your suggestion is to use that for ZHA while using short press events for the others in this blueprint?
I am actually using deconz, and I was assuming that it exposed the short release event as well. In fact, in a previous configuration I had the deconz dimmer switches added through diyhue, and was able to bind to short release through the Hue Essentials app - so it should be possible to get this event for deconz as well I guess.
my opinion is that the behaviour of a single field should be consistent between the integrations, I think having a disclaimer that a certain option only works on certain integrations would be clear, e.g.
"short release (ZHA and deconz only)"
what you suggested wouldn't be the worst, but imo is a bit more confusing and less flexible - maybe some people prefer binding to short press because it's faster, and don't use long press so won't encounter this issue.