Best solution would be if you make a simple if/then condition within your automation. If you double press and the cover is in “moving” state then just stop it.
Adding this complexity is not possible with a blueprint since it most likely requires additional helpers (like in @jhol-byte response)
Sadly it is not possible in have multiple entity.filter in Home Assistant blueprint logic. So having the blueprint working for Matter and Zigbee would not be easily possible and I want to keep the Matter integration filter.
Additionally the Zigbee trigger are completely different. So it would need to be its own blueprint anyway. So I would recommend using what @wmaker posted 
Understood, and thanks for the reply. I thought there might be a way to identify a double-press-and-hold action that would keep the blinds moving until the button is released. I will have a play with this and see what works. Or else I may compromise and just close/open to 50%
Any chance you could add multiple: true to the event selectors? I have 2 remotes in each of 2 rooms, and if it allows me to select multiple events (both ups or both downs) I would only need a single automation for a given room instead of 2 automations.
For multiple remotes that operate in the same way I just duplicate the blueprint and name it accordingly “Ikea Living room 1” “Ikea Living room 2”. This ties 1 automation to 1 remote which IMO is cleanest way to deal with remotes.
Have you tried that?
That’s viable, but not as easy for long term maintenance. If/when I decide to add a double tap action, or a hold/release, I have to either add it to both, or delete/duplicate/edit each time. Since the actions and conditions are what make the automation unique it just makes sense to me to have a single automation but allow multiple remotes (which are mounted on each of the nightstands) to trigger it.
I see what you mean now, add multiple remotes with 1-to-1 pairing from within the setup. That is definitely on the list, it was in one of my first attempts but I was worried that it was over complicating the initial release.
Would you mind tossing it as a feature request on the github and I’ll work it back in?
Good news: I’ve just released version 2.0.0 which includes support for this!
Note on Upgrading: Unfortunately, Home Assistant does not currently support automatic migrations when a Blueprint field changes from multiple: false to multiple: true. This means your existing automations will show empty fields for the button selector until they are updated manually.
To get back up and running, you’ll need to wrap your existing entity IDs in brackets so Home Assistant recognizes them as a list:
input section.[ and ] around your event entities as shown below:Before:
input:
button1_event: event.schreibtisch_fernbedienung_taste_1
button2_event: event.schreibtisch_fernbedienung_taste_2
After:
input:
button1_event: [event.schreibtisch_fernbedienung_taste_1]
button2_event: [event.schreibtisch_fernbedienung_taste_2]
Once you save these changes, you can switch back to the Visual Editor, and your entities should appear correctly again.
Hi
Is there a way to set brightness with this blueprint for a group of lights that is made in home assistant (helper group)?
That would make this blueprint complete.
Else i need to make this blueprint a controller for another blueprint to do brightness for a group.
This is great. Thank you.
As someone else noted, the fade rate on hold is really slow. Is there a setting that will speed this up?
This must be the best IKEA Bilresa dual button blueprint I can find, good work!
I miss one thing tho. Minimum dim level.
When I want to set the lowest dim level i always go to far and turn lights off.
For on / off I use single press.
That said I would like to see a lowest setting, like 10%.
Very well done, thank you.
Not only it works perfectly, but also it’s a great Blueprint to learn from!
After some faff with my hardware, I’ve got this going and it’s fantastic. I can buy some more buttons for my other rooms, now!
Hoping that you manage to make one just as good for the scroll wheel!
Thanks for the blueprint.
I can make a lamp get brighter with Long Press (on press), but cant get it to dim the light. Do you have any suggestions how to do this?
First of all: thanks for this Blueprint, works like a charm! However one question which might not be related especially to this blueprint but to the Bilresa in general?
I want to trigger a script which powers a Sonos Device (if not already on) and starts playing a radio station. I have different scripts for different stations which are working fine switching between them using a Somrig remote and different button schemes (single click, double click, …)
Putting these scripts to a Bilresa remote (tried also another Bilresa Blueprint which behaves the same) will start these scripts also but sometime they just do not do anything. From the traces of the script I saw them running but in fact they did nothing. Funnily it always works the first time (when the Sonos device needs to be powered on before), but not reliably afterwards - means that sometimes it works, sometimes not.
Script looks like this:
alias: Radio Paradise Büro
sequence:
- sequence:
- if:
- condition: state
entity_id: switch.sonos_connect_buro
state: "off"
then:
- action: switch.turn_on
metadata: {}
data: {}
target:
entity_id: switch.sonos_connect_buro
- delay:
hours: 0
minutes: 0
seconds: 45
milliseconds: 0
- action: media_player.volume_set
metadata: {}
data:
volume_level: 0.21
target:
entity_id: media_player.buro
- action: media_player.play_media
data:
media:
media_content_id: FV:2/19
media_content_type: favorite_item_id
metadata:
title: Radio Paradise
thumbnail: >-
https://cdn-profiles.tunein.com/s13606/images/logoq.png?t=1678196660000
media_class: genre
children_media_class: null
navigateIds:
- {}
- media_content_type: favorites
media_content_id: ""
- media_content_type: favorites_folder
media_content_id: object.item.audioItem.audioBroadcast
target:
entity_id: media_player.buro
description: ""
config for the button from the blueprint is:
button2_double:
- action: script.radio_paradise_buro
metadata: {}
data: {}
as said - doing this with a Somrig works without issues…
Any hint greatly appreciated