IKEA Blinds Not Working with Remote

[jmason9836]

I was able to successfully add my IKEA blinds to my Zigbee2MQTT instance without issue. During the process my blinds lost their connection to the remote that came with them.

I paired the remote back to the blinds but then lost the blinds in Home Assistant. It’s seeming like I can only have one or the other paired.

I wasn’t expecting that to be the case and it doesn’t make sense to me why it would be like that.

I wanted to ask if anyone else had this experience and if there’s anything I’m not aware of on why only one can be paired at a time?

[jchh (my username is my initials (and my first name isn't John))]

Yes, that happened to me as well.

However, you can also add the remote to MQTT and a simple automation will bring the functionality back.

Here are 2 of mine as examples:

automation: 

- alias: "Shades - livingroom remote"
  id: shades_livingroom_remote
  mode: queued
  trigger:
    - platform: state
      entity_id: sensor.livingroom_tradfri_remote_action
      to:
        - "open"
        - "close"
  action:
    - choose:
        - conditions:
            - "{{ trigger.to_state.state == 'open' }}"
          sequence:
            - service: cover.open_cover
              target:
                entity_id: cover.livingroom_shade
        - conditions:
            - "{{ trigger.to_state.state == 'close' }}"
          sequence:
            - service: cover.close_cover
              target:
                entity_id: cover.livingroom_shade

- alias: "Shades - orangery remote"
  id: shades_orangery_remote
  mode: queued
  trigger:
    - platform: state
      entity_id: sensor.orangery_tradfri_remote_action
      to:
        - "open"
        - "close"
  action:
    - choose:
        - conditions:
            - "{{ trigger.to_state.state == 'open' }}"
          sequence:
            - service: cover.open_cover
              target:
                entity_id:
                  - cover.orangery_lh_shade
                  - cover.orangery_ctr_shade
                  - cover.orangery_rh_shade
        - conditions:
            - "{{ trigger.to_state.state == 'close' }}"
          sequence:
            - service: cover.close_cover
              target:
                entity_id:
                  - cover.orangery_lh_shade
                  - cover.orangery_ctr_shade
                  - cover.orangery_rh_shade

[ShadowFist]

Another option is to use the binding functionality within Z2MQTT which was designed for this very purpose.

That way your remote will always control your blind even if Z2MQTT is down, and you don’t need to set up a separate automation.

[jchh (my username is my initials (and my first name isn't John))]

@ShadowFist

Another option is to use the binding functionality within Z2MQTT which was designed for this very purpose.

I’ve never fully understood how to do that as I don’t really understand what an endpoint is/means and how to send the setup commends from within the Z2M interface.

Do you know if a simple guide to explain these things?

edit: If my remote screen looked like this:

Would I do this:?

I appreciate I can just try it, but I am also trying to understand.

…if an endpoint is only a number (and there is more than one), how do you know what is what?

Also, if I do this, is the remote still available to use in automations as well?

[ShadowFist]

Sorry mate, my knowledge of binding is limited to the fact that it exists and what it’s supposed to do.

Hopefully someone more knowledgeable than me will show up to answer your questions. In the meantime, there’s a couple of threads in this forum on binding. Try looking them up and seeing if what you’re looking for is already explained.

[francisp (Francis)]

I have it like this (and yes, still controllable from HA)

but you need to look up what cluster is for up/down, and tick that too

[jchh (my username is my initials (and my first name isn't John))]

@ShadowFist

Sorry mate, my knowledge of binding is limited to the fact that it exists and what it’s supposed to do.

Cheers. We’re in the same position!

[jchh (my username is my initials (and my first name isn't John))]

Brilliant - much appreciated.

I’ll give that try.

Cheers!