Controller - IKEA E1766 TRÅDFRI Open/Close Remote
This blueprint is part of the Controllers-Hooks Ecosystem. You can read more about this topic here.
Description
This blueprint provides universal support for running any custom action when a button is pressed on the provided IKEA E1766 TRÅDFRI Open/Close 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.
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.
Requirements
deCONZ Integration
OptionalIf you plan to integrate the with deCONZ, you must have this integration set up. The deCONZ integration can be configured from the Home Assistant UI and requires an additional container to run deCONZ on. Head over to the documentation for full details on the required hardware and how to set up deCONZ on your system.
deCONZ Integration DocsZHA Integration
OptionalIf you plan to integrate the with ZHA, you must have this integration set up. The ZHA integration can be configured from the Home Assistant UI. Check the documentation for full details on the required hardware and how to set up ZHA on your system.
ZHA Integration DocsZigbee2MQTT Integration
OptionalIf you plan to integrate the with Zigbee2MQTT, you must have this integration set up. Installation methods differ between different installation types. Check out the documentation for full details on the required hardware and how to set up Zigbee2MQTT on your system.
Zigbee2MQTT DocsInput Text Integration
RequiredThis integration provides the entity which must be provided to the blueprint in the Helper - Last Controller Event input. Learn more about this helper by reading the dedicated section in the Additional Notes.
Inputs
Integration used for connecting the remote with Home Assistant. Select one of the available values.
The controller device to use for the automation. Choose a value only if the remote is integrated with deCONZ, ZHA.
The action sensor of the controller to use for the automation. Choose a value only if the remote is integrated with Zigbee2MQTT.
Input Text used to store the last event fired by the controller. You will need to manually create a text input entity for this, please read the blueprint Additional Notes for more info.
Action to run on short up button press.
Action to run on up button release after long press.
Action to run on double up button press.
Action to run on short down button press.
Action to run on down button release after long press.
Action to run on double down button press.
Choose whether or not to expose the virtual double press event for the up button. Turn this on if you are providing an action for the up button double press event.
Choose whether or not to expose the virtual double press event for the down button. Turn this on if you are providing an action for the down button double press event.
Max delay between the first and the second button press for the double press event. Provide a value only if you are using a double press action. Increase this value if you notice that the double press action is not triggered properly.
Delay used for debouncing RAW controller events, by default set to 0. A value of 0 disables the debouncing feature. Increase this value if you notice custom actions or linked Hooks running multiple times when interacting with the device. When the controller needs to be debounced, usually a value of 100 is enough to remove all duplicate events.
Available Hooks
Some of the following mappings might include actions for virtual double press events, which are disabled by default. If you are using a hook mapping which provides an action for a virtual double press event, please make sure to enable support for virtual double press on the corresponding buttons with the corresponding blueprint input.
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.
Default Mapping
- Up button short press -> Brightness up
- Up button double press -> Turn on
- Down button short press -> Brightness down
- Down button double press -> Turn off
Mapping #2
- Up button short press -> Brightness up
- Up button double press -> Color up
- Down button short press -> Brightness down
- Down button double press -> Color down
Media Player
This Hook blueprint allows to build a controller-based automation to control a media player. Supports volume setting, play/pause and track selection.
Default Mapping
- Up button short press -> Volume up
- Up button double press -> Next track
- Down button short press -> Volume down
- Down button double press -> Play/Pause
Cover
This Hook blueprint allows to build a controller-based automation to control a cover. Supports opening, closing and tilting the cover.
Default Mapping
- Up button short press -> Open cover
- Down button short press -> Close cover
- Down button double press -> Stop cover and cover tilt
Additional Notes
Helper - Last Controller Event
The helper_last_controller_event
(Helper - Last Controller Event) input serves as a permanent storage area for the automation. The stored info is used to implement the blueprint's core functionality. To learn more about the helper, how it's used and why it's required, you can read the dedicated section in the Controllers-Hooks Ecosystem documentation.
Virtual double press events
It's also important to note that the controller doesn't natively support double press events. Instead , this blueprint provides virtual double press events. You can read more about them in the general Controllers-Hooks Ecosystem documentation.
Hooks support and missing long press events
Due to the controller not exposing long press events but only short and release events, it's not possible to determine the nature of a button press. Therefore, to prevent an erroneous behaviour, Hooks only rely on short and virtual double press events to implement their functionality for this controller.
Changelog
- 2021-10-29: first blueprint version 🎉
- 2022-08-08: Optimize characters usage for the
helper_last_controller_event
text input.