This blueprint provides universal support for running any custom action when a button is pressed on the provided IKEA E1812 TRĆ DFRI Shortcut button. 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.
thank you for your feedback, we have to implement some sort of debounce in this blueprint, for ZHA.
To help solving this issue, Itād be extremely helpful if you could post here the list of events fired by the controller when clicking the button.
In your Home Assistant UI, navigate to Developer Tools -> Events. At the bottom of the page, in the āListen to Eventsā form type zha_event, click on āStart Listeningā, then press the shortcut button only once. Copy the events which appear on the page and paste them here (or as PM).
I am posting only one event, but 6 are fired with one click. On the second button I have, only 3 are fired. Maybe, there is also off_delay setting in ZHA cluster, but I did not test that.
Could you please post all the 6 events which gets fired on the single button press? Iām particularly interested in the time_fired attribute, which weāll probably use for debouncing, but if you could post the whole list of events it would be great.
Maybe, there is also off_delay setting in ZHA cluster, but I did not test that.
Interesting, is there any documentation regarding this ZHA cluster? Maybe we can use it to implement debouncing without the need to alter the blueprint.
It looks like there is some battery issue too, with Sonoff gateway.
My battery was dead in couple of days.
Tried different ZHA settings, but doesnāt affect multiple event firing anyway.
We need to add timeout to automation
Hi @MattX,
thank you for testing the ZHA settings. Given the results, adding the debounce feature directly in the blueprint is probably the best solution.
Iāll work on it and let you know as soon as itās ready.
Hi @MattX,
Iām really sorry for not reaching out to you sooner. Thanks to the valuable contribution of another user, we currently have an open Pull Request on GitHub which implements debouncing for the E1812.
The process was not straightforward since the controller behaviour varies from installation to installation, and we also encountered an issue with the HA Core automation integration, which eventually got fixed in the 2021.4.6 release.
Iām currently in the process of reviewing the Pull Request, hopefully weāll be able to merge it and provide a fully working debounced version in the upcoming days.
To @MattX and anyone who might be interested in this feature, Iāve just pushed an update for the blueprint which adds support for debouncing.
Debouncing allows to filter duplicate events which might be fired by this controller. This unexpected behaviour was reported for devices connected with the ZHA integration.
If you plan to update this blueprint, please read carefully the changelog and documentation, which also provides guidance on how to enable debouncing.
This update should solve your issues with duplicate action runs. If something is not working as intended after the update, please let me know.
Thank you for your patience, and happy automating!
Hi,
I tried different ways, but always getting this errors:
Logger: homeassistant.components.automation.controller_ikea_e1812_shortcut_button_3
Source: components/automation/init.py:508
Integration: Automation (documentation, issues)
First occurred: 10:57:34 AM (5 occurrences)
Last logged: 11:07:31 AM
Error while executing automation automation.controller_ikea_e1812_shortcut_button_3: not a valid value for dictionary value @ data[āentity_idā]
Logger: homeassistant.components.automation.controller_ikea_e1812_shortcut_button_3
Source: helpers/script.py:1337
Integration: Automation (documentation, issues)
First occurred: 10:57:34 AM (5 occurrences)
Last logged: 11:07:31 AM
Controller - IKEA E1812 Shortcut button: Error executing script. Invalid data for call_service at pos 3: not a valid value for dictionary value @ data[āentity_idā]
You need to provide a valid input_text entity for the helper_last_controller_event input.
To learn more about the helper_last_controller_event , how itās used an why itās required, you can read this section in the official documentation.
Please let me know if adding the missing input solves your issue.
Thanks!
Hi, was working fine and all of a sudden my automation stopped working correctly. It is meant to toggle some lights to a certain RGB value and brightness, instead its gone back to just putting it on whatever the last state was. An error in the logs popped upā¦
Error while executing automation automation.bedroom_button_1: UndefinedError: 'dict object' has no attribute 'event'
The issue seems relative to the way the blueprint recognizes Zigbee2MQTT events.
Did you perform any modifications to your system before experiencing this issue? (eg. Zigbee2MQTT or HA update, Zigbee coordinator change etc.)