News for @maxwood and anyone interested in the double clicks feature, I’ve just pushed an update which adds the support for this functionality, plus an optimization which significantly reduces automation runs, which where triggered under the hood for empty and repeated button events. Docs have been updated too to reflect the additional blueprint inputs.
Please notice that we’re really pushing the limits of this controller here, by implementing virtual double press events. Under the hood, the blueprint relies on the previous button press and a delay.
This means that if you provide an action for a double click event, when a button is pressed the automation will first wait for the second short press event, then, if none is received within the provided delay, the action for the single short press will be executed. This will result in a slight delay between the short press and the action execution.
Moreover, my tests suggest that the controller doesn’t fire the two button press events if the clicks are too close in time. This behaviour happens for all buttons, but it’s more noticeable for the left and right ones. To make sure the double press event is triggered properly, please wait a few moments before clicking the button for the second time. If you still have issues try to increase the value for the Helper - Double Press delay input.
I’d also like to point out that this is not a breaking change: anyone who is currently using the blueprint can safely update it without having to reconfigure the related automations. No performance reductions to existing automations will be caused by these new features.
If you have any suggestions or something is not working as it should with this update, please reach out here, I’d be glad to help.