Skip to main content

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Maintainers

Loading maintainers…

Total Downloads
–

Loading versions…


tip

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 E1524/E1810 TRÅDFRI Wireless 5-Button Remote. Supports controllers integrated with Zigbee2MQTT, ZHA, deCONZ. 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.

tip

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​

Zigbee2MQTT Integration

Optional

If 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 Docs

ZHA Integration

Optional

If 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 Docs

deCONZ Integration

Optional

If 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 Docs

Input Text Integration

Required

This 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.

Input Text Integration Docs

Inputs​

Available Hooks​

Virtual double press actions

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 long press -> Brightness up (continuous, until release)
  • Down button short press -> Brightness down
  • Down button long press -> Brightness down (continuous, until release)
  • Left button short press -> Color down
  • Left button long press -> Color down (continuous, until release)
  • Right button short press -> Color up
  • Right button long press -> Color up (continuous, until release)
  • Center button short press -> Toggle

Light Hook docs

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 long press -> Volume up (continuous, until release)
  • Down button short press -> Volume down
  • Down button long press -> Volume down (continuous, until release)
  • Left button short press -> Previous track
  • Right button short press -> Next track
  • Center button short press -> Play/Pause
  • Center button long press -> Stop

Media Player Hook docs

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
  • Left button short press -> Close the cover tilt
  • Right button short press -> Open the cover tilt
  • Center button short press -> Stop cover and cover tilt

Cover Hook docs

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.

The helper is used to determine button release events when the controller is integrated with ZHA, because of the actions mapping for the controller with these integrations. Natively, the controller doesn't allow to distinguish between different button release events, so the blueprint must store the previous clicked button.

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.

Center button long press​

Please note that the long press on the center button behaves differently from the long press for other buttons, due to how the controller implements this feature: when long pressing the center button, the controller first fires the short press event, then after a couple of seconds it sends the long press event as well. This behaviour is due to the controller design and it's not relative to any integration or the blueprint itself.

Issues with the E1810 model firing bad events​

It has been reported that the newer IKEA E1810 controller, which looks identical to the E1524, might fire wrong events in certain situations when interacting with it. This is due to an issue with the controller design and is not relative to the blueprint itself.

If you notice your controller is not behaving as expected please remove the battery, wait about 2 minutes, insert it back and try again.

Changelog​

Loading changelog…