This blueprint provides universal support for running any custom action when a button is pressed on the provided IKEA E1743 TRĆ DFRI On/Off Switch & Dimmer. Supports controllers integrated with deCONZ, ZHA, Zigbee2MQTT. Just specify the integration used to connect the remote to Home Assistant when setting up the automation, and the blueprint will take care of all the rest.
In addition of being able to provide custom actions for every kind of button press supported by the remote, the blueprint allows to loop the long press actions while the corresponding button is being held. Once released, the loop stops. This is useful when holding down a button should result in a continuous action (such as lowering the volume of a media player, or controlling a light brightness).
The blueprint also adds support for virtual double button press events, which are not exposed by the controller itself.
Automations created with this blueprint can be connected with one or more Hooks supported by this controller.
Hooks allow to easily create controller-based automations for interacting with media players, lights, covers and more. See the list of Hooks available for this controller for additional details.
Full Documentation
Full documentation regarding requirements, inputs and more is available here.
Docs provide all the information you need to properly configure this blueprint on your instance.
Available Hooks
Light
This Hook blueprint allows to build a controller-based automation to control a light. Supports brightness and color control both for white temperature and rgb lights.
Hi @koconut,
youāre welcome, thank you for your feedback!
Sure, in the next days Iāll apply the latest updates which were deployed for the 5-button remote blueprint, so that the double click feature will be available also for this controller.
Iāll let you know as soon as the feature is implemented.
News for @koconut and anyone interested in the double clicks feature, Iāve just pushed an update which adds the support for this functionality, plus a few optimizations inherited from the Ikea 5-button remote blueprint. 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.
My tests suggest that this controller, in contrast with the E1524/E1810 5-button remote, is able to handle clicks which are pretty close in time. If you have issues with triggering the double press actions, try to wait a few moments before pressing the button. If even after clicking the button a little slower youāre still getting the short press action triggered instead of the double press one, 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 you notice that something is not working as it should with this update, please reach out here, Iād be glad to help.
Iām happy to inform you that Iāve just updated the Awesome HA Blueprints project with two new blueprint categories: Controllers and Hooks.
Controllers are blueprints which allow to easily integrate a wide range of controllers (wall switches, remotes, dimmers, etc.) and use them to run a set of actions when interacting with them. They consist of a practical abstraction layer for easily building controlled-based automations without worrying about the handling of raw controller events, and the integration used to connect controllers to Home Assistant (Zigbee2MQTT, ZHA, deCONZ, ZWave, proprietary hubs, etc.).
Most importantly, beside providing action sequences to Controller blueprints to build a custom controller-based automation, you can connect Controllers with Hooks .
Hooks are blueprints which seamlessly integrate with Controllers to enable control of lights, media players and much more, without you ever writing a single line of code.
For further details please read this annoucement post on the Awesome HA Blueprints project thread.
To reflect these changes, this blueprint has now been moved to the Controllers category. The original post on this thread has been updated with new links to docs and blueprint code. Examples have been removed since the functionality can now be implemented with the Light Hook.
first of all thanks for creating these awesome blueprints. I have just tried to add the blueprint into my HA instance, but it did not work with the following error:
Invalid blueprint: Unknown selector type select found for dictionary value @ data['blueprint']['input']['integration']['selector']. Got OrderedDict([('select', OrderedDict([('options', ['Zigbee2MQTT', 'deCONZ', 'ZHA'])]))])
Could you please look into this or give me a pointer into what Iām doing wrong?
iām trying to use ālong pressā functionality with āloop until releaseā flag activated.
Without loop itās ok, just decrease the brightness with each long press correctly.
With loop itās too fast so a long press of about 3 seconds is enough to turn off light (with a rapid sequence of decreases in brightness).
Is it possible to add a āloop delayā in order to decrease the brightness every X second while still controlling the ālong pressā?
I tried to edit by myself but iām not able to implement the ādelayā part in this sequence (and the other one):
- repeat:
sequence: !input action_up_long
until: '{{ not button_up_long_loop }}'
Also adding a new input to select the delay would be appreciated.
In this Controller blueprint, delay control for custom actions is left to users: in the provided custom action sequence, users can add a delay action at the end, e.g.:
sorry for my late response, youāre welcome, Iām happy to hear that everything runs great.
By the way, Iād suggest you using the Light Hook for controlling your lights, since it already includes all the features for controlling light brightness and color:
The only thing currently missing, which for you might be relevant, is the ability to indicate the number of steps to control brightness from 0% to 100%, which would allow a finer and more precise brightness control for the connected light.
Iāll add this useful functionality to the Light Hook in the next days. Iāll let you know as soon as the feature gets implemented so you could give it a try if youāre interested in it.
Here i am again!
I have a problem when I activate āExpose up button double press eventā: the controller stops working.
In order to use the Light Hook with the function of restoring the brightness of the light after switching off, I wanted to put that the double pressure of the keys sets the light to maximum / minimum.
However, if the option ādouble press eventā is activated, nothing works anymore.
I was wondering if I need to activate it or if I just map the double press on the controller without activating the option.
if you want to expose a double press event, you should also provide a valid text input for the helper_last_controller_event input. This is used to store the last controller event and check if the same button has been pressed twice in a row.
Yeah, itās required when using ZHA or Zigbee2MQTT or a double press action.
Maybe thatās a little confusing, we should find a way to better state that the helper is required with any integration, when using virtual double press events.
I have configured the text input and I see it changing value when I press the button, so that is ok.
However, if I press the button twice, with a delay of 1000ms, I get the result as if it were a single press.
Increasing to 2500ms is the same, it performs single action after 2.5s.
In the Light Hook I read that the double pressure corresponds to the change of color so it is not explained why instead it turns the light on / off.
Maybe I have to set the action in the controller instead? Or would I conflict with the hook again?
Please try to wait a few moments before pressing the button for the second time, since the controller does not fire the second press event when clicks are too close to each other. If even after clicking the button a little slower youāre still getting the short press action triggered instead of the double press one, increase the value for the Helper - Double Press delay input.
Get Started
Blueprint URL
Description
Full Documentation
Available Hooks
Light
Media Player
Cover
Changelog
