This blueprint provides universal support for running any custom action when a button is pressed on the provided IKEA E1524/E1810 TRĂ DFRI Wireless 5-Button Remote. 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.
I wanted to give this a try, but I cannot get it working. I am testing with a 5-button IKEA remote and an IKEA Tradfri LED bulb E27 600lm, dimmable colour and white spectrum opal white. I create a new automation based on your blueprint and when I press SAVE, nothing happens: no message pops up but also no automation is being created.
Thank you for reporting here, Iâm sorry for what you experienced. Iâve just updated the blueprint, this issue should be fixed now.
The problem was on how triggers were defined. The state trigger which was used only for Zigbee2MQTT required a valid entity_id, but this is not provided when using ZHA or deCONZ. I moved this to an event trigger which targets state_changed events for the provided remote. Of course if the input is empty, no event will be caught. This is the best fix I came up with, but if anyone has a better solution Iâd be happy to hear your voice.
Please reload the blueprint into your HA installation, and let me know if everything runs smoothly.
Thank you. I saw you had just changed the code on github so I was already testing your new version. Now I can save my automation, but when I push buttons on the remote, the automation is never triggered.
I have another automation (frenck/zha-ikea-five-button-remote-for-lights.yaml). When I enable that automation, it is triggered by my IKEA remote. When I disable that automation and I enable the automation based on your blueprint, that automation never gets triggered by your blueprint.
thank you for the suggestion. In the beginning I thought that was the cause, but while I was trying to come up with a solution for the issue I tested a working config both with and without the line-continuation character with a similar action, and the automation seemed to work properly.
You need access to your raw configuration files and edit yaml, for example with the File Editor addon, but no need to do this just to test this blueprint. So donât worry, Iâve just updated the blueprint on GitHub with the fix, so you can try to reload it and see if it works.
Still not working. I am now editing the blueprint directly (/config/blueprints/automation/EPMatt/ikea_e1524_e1810_universal.yaml) and I get an exclamation mark in the editor:
unknown tag !<!input> at line 150, column 36:
integration: !input 'integration'
^
[edited]âŚbut maybe that is only a false positive.
@ribbonofblack and anyone interested in using this blueprint with ZHA,
@kks36 and I finally managed to find out what the issue was with ZHA. The blueprint has been updated, now it should be working fine.
Kudos to @kks36 for spending lots of time and energy into this! Without his help I would not have been able to understand where the problem was. Thanks!
Got everything working with zigbee2mqtt, remote and Ikea LED bulb, except color change. Zigbee2mqtt logs say âNo converter available for âcolor_tempâ (50)â. Any ideas?
Hi @Tomas_Kibirkstis, thank you for reporting here.
Which Ikea bulb are you using? If you can provide an identifier or model number, that could be helpful to try to solve this issue.