💡 Awesome HA Blueprints: A curated list of blueprints + easily create controller-based automations (remotes, switches,...) for controlling lights, media players, and more

epmatt · May 18, 2021, 8:14pm

I’d like to inform you that I’ve published an update for the E1744 Controller blueprint which adds support for debouncing.

Debouncing allows to filter duplicate events which might be fired by this controller. This unexpected behaviour was reported for devices connected with the ZHA integration.

If you plan to update this blueprint, please read carefully the changelog and documentation, which also provides guidance on how to enable debouncing.

This update might solve the issue you were experiencing with this blueprint as well. If something is still not working as intended after the update, please let me know.

Thank you for your patience, and happy automating!

maskfaen · May 18, 2021, 8:49pm

@epmatt : my model number says: 324131137411

epmatt · May 18, 2021, 9:17pm

Hi @maskfaen,

Thank you. Unfortunately the current blueprint doesn’t support your controller.

If you’re available and have some time, we should check the ZHA events your controller is firing when interacting with it.
Please navigate to Developer Tools → Events, then in the Listen for events form type zha_event and click on Start Listening. Press the button on the remote, then you should instantly see the event fired by your remote.

Repeat the operation for the four buttons and for all the possible actions (short press/long press/release after long press). Then, post the events you received here.

I wasn’t able to find much information regarding this remote online. In any case given the action mappings we should be able to implement a blueprint specifically for your device integrated with ZHA.

Thank you!

maskfaen · May 19, 2021, 6:55am

@epmatt Everything I can do to achive this function

Here is short press events:

Long press (2-3seconds):

Double press:

epmatt · May 19, 2021, 8:48am

Hi @maskfaen,

thanks for your feedback, I’ve just opened an issue on the project’s GitHub repository to track your feature request.

I’ll let you know as soon as the new blueprint is ready.

AndrewF6 · May 19, 2021, 8:49am

Hi @epmatt thanks for taking the time to respond. I’ve tried the latest version of your controller and it works! Great times ahead! thanks again!

epmatt · May 19, 2021, 8:50am

Hi @AndrewF6,

great! I’m happy to hear that everything works as expected.
Happy automating, and enjoy the blueprints!

ferryhel · May 19, 2021, 9:22am

hi @epmatt ,
I’ve been working with this with the Cover hook for my ikea 2 button dimmer in combination with shelly rolling shutters.
I’d like to manipulate the Hook - Cover so that when I click on one of the buttons when it’s opening or closing, the cover stops moving.

action:
- variables:
    action: '{{ trigger.event.data.action }}'
- choose:
  - conditions: '{{ action == open_cover }}'
    sequence:
    - service: >
       {% if is_state('input.cover', 'closing' or 'opening')%}
         cover.stop_cover
       {% else %}
         cover.open_cover
       {% endif %} 
      entity_id: !input 'cover'
  - conditions: '{{ action == close_cover }}'
    sequence:
    - service: >
       {% if is_state('input.cover', 'closing' or 'opening')%}
         cover.stop_cover
       {% else %}
         cover.close_cover
       {% endif %} 
      entity_id: !input 'cover'

Should the above work or am I doing something wrong?

jolau · June 13, 2021, 8:28pm

Thanks for your great work! Your blueprint make HA automations work in a way I’ve expected they should.
I would like to update a blueprint (and all automations which use it) - what is the best way to do it?

vehsen · June 14, 2021, 5:16pm

The description of every hook blueprint ist written for a light, even if its for a media player or cover.
The controller device which will control the light.

The center button of my IKEA E1810 TRADFRI doesn’t work. The other buttons do work smoothly.
Smooth power off doesn’t work, too.

epmatt · July 7, 2021, 4:45pm

Hi @jolau, thank you for your nice feedback! I’m glad you find these blueprints useful.

As far as I know, currently the best way to update a blueprint is to delete it from the Home Assistant UI, then import it again in the same way you did when you first installed it on your system.

epmatt · July 7, 2021, 4:50pm

Hi @vehsen,

The description of every hook blueprint ist written for a light, even if its for a media player or cover.
The controller device which will control the light.

Thank you for spotting it, I’ll push an update to fix the description issue.

The center button of my IKEA E1810 TRADFRI doesn’t work. The other buttons do work smoothly.
Smooth power off doesn’t work, too.

I’m sorry to hear you’re having issues with the blueprints. Can you please share the YAML config for both the E1524/E1810 Controller and Light Hook automations?

Thank you!

tumtumsback · August 6, 2021, 1:17pm

Having an issue with this blueprint. When I press the double-tap up or double-tap down on my E1743, I can see that the automation’s “Last Triggered” timestamp DOES in fact update, so the double-tap trigger is kicking off the automation itself, but the action isn’t working.

The action is quite simple. For double-tap up, I want two different light entities to turn on @ 100% brightness. For double-tap down, I wan those two different light entities to turn off.

Any help would be greatly appreciated.

epmatt · August 11, 2021, 9:42pm

Hi @tumtumsback,
thank you for reporting here.

I guess you’re setting up the E1743 controller blueprint. Could you please share the YAML configuration for the automation you’re setting up with this blueprint?

Thank you!

tumtumsback · August 11, 2021, 10:23pm

- id: '1628254720620'
  alias: Controller - IKEA E1743 On/Off Switch & Dimmer
  description: ''
  use_blueprint:
    path: EPMatt/ikea_e1743.yaml
    input:
      helper_last_controller_event: input_text.text1
      integration: deCONZ
      controller_device: 7e2912eb650d47d5b96ab06fe4a2a582
      action_button_up_double:
      - service: light.turn_on
        target:
          entity_id:
          - light.lamps
          - light.office_lights
        data:
          brightness: 255
      action_button_down_double:
      - service: light.turn_off
        target:
          entity_id:
          - light.lamps
          - light.office_lights
      button_up_double_press: true
      button_down_double_press: true

epmatt · August 11, 2021, 10:25pm

Hi @tumtumsback, thank you for your quick reply.

At first sight the config looks good to me. Do you notice any entries in the Home Assistant logs related to this blueprint?

Thanks!

tumtumsback · August 11, 2021, 11:03pm

Logs are free of anything pertaining to this Blueprint – that’s what’s throwing me for a loop!

epmatt · August 12, 2021, 10:37am

Hi @tumtumstack,

I’d like to point out that the double press feature is not embedded in the controller itself. Instead, the blueprint implements it by capturing two subsequent short presses. That’s why the feature is considered a virtual double press. For this reason, a too fast double press of the button might not be identified as the correct event - the blueprint might only catch the first short press and not the second one, wrongly identifying the “virtual double press” as a “single short press”.

Please try to increase the value of the Helper - Double Press delay input to 1+ seconds. When double pressing the button on the device, wait a little bit more between the first and second short press.

Let me know if you’re able to solve the issue. If not, we might be facing a bug in the blueprint.
Thank you!

tumtumsback · August 13, 2021, 12:22pm

Ah! Before even changing the input to 1000ms, I wanted to see if I could figure out the perfect timing @ 500ms – and I was able to, but it was very tempermental.

So, I changed it to 1000ms – now it works like a charm every time. Thanks for the heads up on this! It’s possible you might want to bump the default from 500ms → 1000ms

PaNiCo · September 4, 2021, 8:19pm

Hi @epmatt , I would like to +1 for the new Hue Dimmer Switch (9290023986).
I have it connected via Zigbee2mqtt. If you need additional info, please let me know