Zigbee2Mqtt 2.0 - IKEA five button remote

The Zigbee2MQTT team lead has just confirmed that the reaction from the users have made him postpone the removal for a very long time. Especially the Node Red users are in trouble.

If you want an example of the 5 button remote here is mine using the new actions

alias: Tradfri PH Dimmer
triggers:
  - trigger: state
    entity_id: event.ph_dimmer_action
    not_from: unavailable
actions:
  - choose:
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.attributes.event_type == 'toggle'}}"
          - condition: state
            entity_id: light.ph
            state: "off"
        sequence:
          - data:
              entity_id:
                - light.ph
              brightness_pct: 80
            action: light.turn_on
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.attributes.event_type == 'toggle'}}"
          - condition: state
            entity_id: light.ph
            state: "on"
        sequence:
          - data:
              entity_id:
                - light.ph
            action: light.turn_off
      - conditions:
          - "{{trigger.to_state.attributes.event_type == 'brightness_up_hold'}}"
        sequence:
          - action: mqtt.publish
            metadata: {}
            data:
              topic: zigbee2mqtt/PH/set
              payload: "{\"brightness_move\": 50 }"
      - conditions:
          - "{{trigger.to_state.attributes.event_type == 'brightness_down_hold'}}"
        sequence:
          - action: mqtt.publish
            metadata: {}
            data:
              topic: zigbee2mqtt/PH/set
              payload: "{\"brightness_move\": -50 }"
      - conditions:
          - >-
            {{trigger.to_state.attributes.event_type in
            ('brightness_up_release', 'brightness_down_release')}}
        sequence:
          - action: mqtt.publish
            metadata: {}
            data:
              topic: zigbee2mqtt/PH/set
              payload: "{\"brightness_move\": 0 }"
      - conditions:
          - "{{trigger.to_state.attributes.event_type == 'arrow_right_click'}}"
        sequence:
          - data:
              topic: blinds/step/left
              payload: "10"
            action: mqtt.publish
          - data:
              topic: blinds/step/right
              payload: "10"
            action: mqtt.publish
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.attributes.event_type == 'arrow_left_click'}}"
        sequence:
          - data:
              topic: blinds/step/left
              payload: "-10"
            action: mqtt.publish
          - data:
              topic: blinds/step/right
              payload: "-10"
            action: mqtt.publish
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.attributes.event_type == 'arrow_right_hold'}}"
        sequence:
          - data:
              topic: blinds/set/left
              payload: "50"
            action: mqtt.publish
          - data:
              topic: blinds/set/right
              payload: "50"
            action: mqtt.publish
      - conditions:
          - condition: template
            value_template: "{{trigger.to_state.attributes.event_type == 'arrow_left_hold'}}"
        sequence:
          - data:
              topic: blinds/set/left
              payload: "0"
            action: mqtt.publish
          - data:
              topic: blinds/set/right
              payload: "0"
            action: mqtt.publish
initial_state: "on"
mode: queued
max_exceeded: silent
1 Like

Just to be clear, the updated blueprint does not use legacy triggers

2 Likes

z2m 2.0.0.2 and latest HA with blueprint “Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote” there is no entity ((Zigbee2MQTT) Controller Entity) for Ikea remote. My z2m does not use legacy option. Am I doing something wrong?

Download blueprint again, there’s been a update few days ago.

1 Like

Same here, removed and repaired the contrroller and it is i NOT in HA

image

I think you’re using the old blueprint. It should say “Device” not “Entity”

this is what I use, imported it today

it shows device for ZHA… but not for Zigbee2MQTT

it is a BP from here

Sorry, that’s a different blueprint than mine. I suppose they have not updated to use Device Entities yet. Feel free to import my blueprint with the forum link:

1 Like

in your BP, the lights entiuty is neccessary? I use the button to switch random stuff.

Remember

If you are happy with things from before 2.0 and your old blueprint or automation works fine. Just reenable the Home Assistant legacy sensors

The Zigbee2MQTT team has admitted the new event actions are not ready and the deprecation of the old is postponed with no known deadline.

In the screenshot I have enabled both the new and the old legacy sensors. It is easier to set in the UI than editing the config.

1 Like

it worked, seems I had to add some light although I`m not using the button to control light , but buttons now work to trigger switches I need to

Yes, that’s the primary use for this blueprint. Setting the lights entity (or entities) enables the brightness up and down buttons to work as brightness up/down on the lights. I actually used the blueprint you referenced with another remote a while ago.

thanks starbuck93, works fine.
Although I do miss the default option to change from warm white to cool white (color temp, which should also be adjusted to use color temp kelvin).

Maybe that is a different blueprint? Don’t know.