This blueprint provides universal support for running any custom action when a button is pressed on the provided IKEA ICTC-G-1 TRĆ DFRI wireless 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 optionally loop the rotate actions while the remote is rotating either left or right. Once the remote stops rotating, the loop stops as well. This is useful when rotating the controller should result in a continuous action (such as lowering the volume of a media player, or controlling a light brightness).
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.
this blueprint is specifically for the IKEA ICTC-G-1 controller, but good news, the same one is available for the SYMFONISK controller as well. Hereās the link to the related forum topic.
Moreover, you can always browse the full list of available Controller blueprints here.
Has anyone got this working with ZHA? Iāve tried setting it to just change the brightness of one lamp up and down when I turn left and right. Nothing seems to change on the lamp though (connected via the Hue integration). I think these IKEA devices are a bit weird staying connected to ZigBee networks but if I listen for ZHA events I can see them coming through when I turn the knob.
I think these IKEA devices are a bit weird staying connected to ZigBee networks but if I listen for ZHA events I can see them coming through when I turn the knob.
As far as my little experience with IKEA controllers goes, remotes usually donāt disconnect from the Zigbee network. The main problem is though they sometimes send duplicate events eg. when rotating the knob or pressing the button (especially the E1812 shortcut button, which fires 6 events in average when pressing the button once).
Iāve tried setting it to just change the brightness of one lamp up and down when I turn left and right.
Could you please post here the YAML for the automation youāve setup? You can grab it by navigating to Configuration->Automations->Edit Automation (the pencil icon part of the automation row), then clicking on the 3 dots on the top right->Edit as YAML.
Moreover, do you notice any entries in the Home Assistant log related to this blueprint?
Hi Matteo. Thanks so much for the prompt reply. Iāve attached the YAML. For testing I have changed this so it should (if I understand correctly) turn one of the downlights above me on or off. Idelly it will do brightness or something. I assuming for this type of basic functionality I donāt need to use hooks or set anything else up? There are some log errors. Iāve posted them as well.
Logger: homeassistant.components.automation.test_library_wireless_dimmer_knob
Source: helpers/script.py:1334
Integration: Automation (documentation, issues)
First occurred: 14:01:02 (586 occurrences)
Last logged: 20:40:13
Test Library Wireless Dimmer Knob: Choose at step 2: choice 3: Choose at step 1: choice 1: Error executing script. Invalid data for call_service at pos 1: not a valid value for dictionary value @ data['entity_id']
Test Library Wireless Dimmer Knob: Choose at step 2: choice 3: Error executing script. Invalid data for choose at pos 1: not a valid value for dictionary value @ data['entity_id']
Test Library Wireless Dimmer Knob: Error executing script. Invalid data for choose at pos 2: not a valid value for dictionary value @ data['entity_id']
Test Library Wireless Dimmer Knob: Choose at step 2: choice 1: Choose at step 1: choice 1: Error executing script. Invalid data for call_service at pos 1: not a valid value for dictionary value @ data['entity_id']
Test Library Wireless Dimmer Knob: Choose at step 2: choice 1: Error executing script. Invalid data for choose at pos 1: not a valid value for dictionary value @ data['entity_id']
Hi @Count.Zilch, thank you for your quick feedback.
Your configuration is missing a value fot the helper_last_controller_event input, which is required for the blueprint to work when the remote is integrated with either Zigbee2MQTT or ZHA, as stated here in the documentation. The reason why the input is required is described in the Additional Notes.
Please provide a valid text input for the helper_last_controller_event input, then try again and check if your issue is solved. You donāt need a particular text input, just create a brand new one in Configuration ā Helpers.
Iād also like to mention that if you have multiple controllers, youāll need to setup a separate text input for each Controller blueprint youāll configure. You donāt need to name the text input helper_last_controller_event explicitly: you just need to pass the text entity in the blueprint configuration, as described above.
Please let me know if adding the missing input solves your issue.
Iāll reply as well, I just switched over from deconz to zha and was hoping I could get those old remote working finally (picked up a handful on the clearance shelf a while back), and while before the problem was that I never received any events from it, now thatās working fine but itās still not doing anything. Basically the exact same as the poster above me, helper entity is configured and does update with the last event, but the actions do not get triggered.
Looks like this has been abandoned, as @epmatt wonāt reply anymore to this project. Weāll have to either find a solution ourselves or just move on. If I ever find something functional Iāll reply here.
Hi. Just dropping a comment to say that the Media Player Hook doesnāt work very well for this device with Google Home speakers, when it comes to controlling volume.
So, just using an automation based on this blueprint and using volume_set with a template instead, works much, much better.
When turning the device all the way to the left (off position) it lowerās the brightness of the light to the minimum possible value, but it never turns it off (with this controller and the related āHook - Lightā).
By default, when paired normally to an IKEA bulb, it turns it off when you continue turning the device after the minimum brightness value is reached.
Does any of you know if this can be replicated?
I had the same problem you and @pietdevries had and I managed to find the root cause for it: as it turns out, some zha_events associated with the actions of Ikea controllers have changed, not sure if itās related to a new version of the ZHA plugin or the firmware on the controllers itself, eitherway, the blueprint is using obsolete or incomplete actions sets when this happens.
I added the new actions to both the controller and hooks files and also took the opportunity to add the handling of quick rotation events (as when used with the Ikea gateway directly).
Thereās a pull request open where you can get the updated files, hoping that @epmatt will get back to this project.
No longer using these devices, but I still have some Symfonisk that are similar.
Full automation below.
Since HA reverted a change where the Google Home speaker volume was always exposed, and now only when itās not off, I had to add an if off else to still be able to control volume while itās off. When itās on, I can adjust the volume in 0.02 intervals (much more precise than the normal volume change that happens when off).