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

[FelixKa (Felix Kaechele)]

What is everyone using these days for their IKEA buttons, dimmers and controllers?

It seems the original author is no longer maintaining the repository, possibly due to other commitments in life (as indicated by the status message on the GitHub profile). I respect that.

Given that there have been some changes to ZHA and HA that make changes to the blueprints necessary and pull requests not being merged I am looking for either a maintained fork or some simpler blueprints that are easier to keep up to date myself.

[Slalamander (Engi-here)]

I only use two remotes, so I’m not sure how well it works for more extensive setups, but so far I like the switch manager integration a lot.

Switch Manager - New refined switch integration to manage your switches

[demo-3][demo-2] If you’re like me and have OCD it might feel like your automations is just getting too cluttered or your Node-Red is just getting too squiggly. Firstly, an introduction, I started using Home Assistant to manage my switch buttons but I could not stand them being in automations and theretically a button push isn’t even an automation. It was also cluttering the automations and making my list unnecessary longer. It was also counter productive to have a single automation for eac…

If you use ZHA, the IKEA strybar remote isn’t set up for that integration yet, however it did not take me long to write a functioning blueprint for it. It stills needs some finetuning though, but for that’s more on the way events are passed down in ZHA for the remotes.

[LewisSpring]

Can you share your STYRBAR blueprint for Switch Manager please?

[Slalamander (Engi-here)]

Switch Manager - New refined switch integration to manage your switches

I’m trying to set up a hold action for the Ikea Strybar in ZHA, however for some reason it seems to always get stuck in an endless loop. It could be due to the fact that, as far as I’ve found, the hold_release event for the top and bottom button is the same. The blueprint currently is the following: name: Ikea Styrbar ZHA service: ZHA event_type: zha_event identifier_key: device_id buttons: ## Not sure why the buttons are back to front and illogical by their numbers?? - x: 247 y: 61 …

name: Ikea Styrbar ZHA
service: ZHA
event_type: zha_event
identifier_key: device_id
buttons:
  ## Not sure why the buttons are back to front and illogical by their numbers??
  - x: 247
    y: 61
    width: 50
    actions:
      - title: press
        conditions:
          - key: command
            value: 'on'
      - title: hold
        conditions:
          - key: command
            value: move_with_on_off
      - title: hold_release
        conditions:
          - key: command
            value: stop_with_on_off

  - x: 442
    y: 248
    width: 50
    actions:
      - title: press
        conditions:
          - key: command
            value: press
          - key: params.param1
            value: '256'
      - title: hold
        conditions:
          - key: command
            value: hold
          - key: params.param1
            value: '3328'
      - title: hold (released)
        conditions:
          - key: command
            value: release
          - key: params.param1
            value: '-7258'
  - x: 245
    y: 434
    width: 50
    actions:
      - title: press
        conditions:
          - key: command
            value: 'off'
      - title: hold
        conditions:
          - key: command
            value: move
      - title: hold_release
        conditions:
          - key: command
            value: stop_with_on_off
  - x: 52
    y: 248
    width: 50
    actions:
      - title: press
        conditions:
          - key: command
            value: press
          - key: params.param1
            value: '257'
      - title: hold
        conditions:
          - key: command
            value: hold
          - key: params.param1
            value: '3329'
      - title: hold (released)
        conditions:
          - key: command
            value: release
          - key: params.param1
            value: '1675'

[hazio]

Has updates to the website stopped? There is a minute amount of blueprints listed on the site.

[cedzop (Cedric)]

Hi!

I’m using the IKEA E2001/E2002 STYRBAR Remote control Controller Blueprint.
It looks like the double press is not longer working. Does anyone made this work?

  path: EPMatt/ikea_e2001_e2002.yaml
  input:
    integration: Zigbee2MQTT
    controller_entity: sensor.button_table_action
    helper_last_controller_event: input_text.helper_controller_button_table
    action_button_left_short:
      - service: light.toggle
        data: {}
        target:
          entity_id: light.diningtable
    action_button_left_double:
      - service: light.toggle
        data: {}
        target:
          device_id: 97abd439d9e1d98dab582da402ce840b
    action_button_right_double:
      - type: toggle
        device_id: 97abd439d9e1d98dab582da402ce840b
        entity_id: 10db7e0fb3826b63372f7d40cb48024a
        domain: light
    button_right_double_press: true
    button_left_double_press: false
    helper_double_press_delay: 500
    button_up_double_press: false

Looks like the double click is not working.

[FelixKa (Felix Kaechele)]

There’s a good handful of issues and pull requests addressing that issue in the authors’ repository. One example: remove spaces to match new helper format in 2023.5 by LordSushiPhoenix · Pull Request #545 · EPMatt/awesome-ha-blueprints · GitHub

Unfortunately the project is abandoned at this point, so no PRs are merged and no new releases are made right now.

[BeastHouse (Damien)]

Thats a shame. Did you ever happen to get the double press working again on remotes?

[el-Presi]

Hey folks!

Maybe I’m too stupid, but I’ve read the description up and down for a few times now and I guess, I’m missing something… I created 2 automations, 1 controller and 1 hook - I cannot relly “connect” them, as they should be connected just by using the same device/entity (of the hardware-controller).
The controller automation gets triggered and fired, fills the input helper, but the hook automation never gets fired, so my lights stay out…

hope for a quick tip

[Mathmxp]

Go into Zigbee2mqtt web ui. select your hue dimmer device. then settings (specific). set Legacy to True.

[Saorin]

Hi every one,

I’d like to control 2 switches (on/off) with rwl021 hue remote. I have following setup:

1. ha on a VM as haos.
2. MQTT as containeraized app outside od HAOS vm
3. Both switches work fine when toggled directly in ha.
4. Remote seems fine as well, I have tried toggling legacy on/off in z2m

I set-up the controller blueprint only with following settings and short/long ON press actions:

In the automation’s log I see it fails on 2nd step, can anyone help figuring out what’s the logic here?

condition: and
conditions:
  - >-
    {%- set trigger_action -%} {%- if integration_id == "zigbee2mqtt" -%} {{
    trigger.event.data.new_state.state }} {%- elif integration_id == "deconz"
    -%} {{ trigger.event.data.event }} {%- elif integration_id == "zha" -%} {{
    trigger.event.data.command }} {%- endif -%} {%- endset -%} {{ trigger_action
    not in ["","None"] }}
  - >-
    {{ integration_id != "zigbee2mqtt" or trigger.event.data.new_state.state !=
    trigger.event.data.old_state.state }}

[Saorin]

Nvm on above, issue rwaolved: I guess I simply had to post here and it got scared… legacy setting on the remote in z2m is true, I also dziś few ha restarts in between, so maybe that’s it.

Thanks for the blueprint!

[Dominik2109]

Hey there, I recently got a Hue Dimmer switch v2 and wanted to use your automation. I also used the light-hook, to control the minimum brightness, which works really good. However, it seems like I can’t change the default settings with the blueprint. If I say, for example, that the on switch should turn the light on but also off (if it’s already on) it just doesn’t change and still executes only the default settings. What am I doing wrong?

[FachKraft42]

I have created and properly configured automatons based on these blueprints:
Controller: Styrbar;
Hook: Light &
Hook: Mediaplayer.

Now I want to do the following:
assign

• button press left_long to media player: volume up
• button left_double to media player: previous track &
• up_long to light: brightness up

and so on.

I am also thinking about using custom actions for the short presses. I know I can put the custom actions into the responding button presses in the controller, but I can not figure out how to call a specific action within a specific hook.

I read the documentation several times but somehow I missed what I was searching for.

[FortranFour]

Your Awesome blue prints are… awesome. Could you add sunrise/sunset with offset (random offset option would be even better) to the start/stop times? Thanks for considering.

[KrzysztofHajdamowicz]

I have an impression that @epmatt abandoned his collection, but somebody else took over: GitHub - lsismeiro/awesome-ha-blueprints: A curated collection of automation blueprints for Home Assistant.

[LewisSpring]

Hi all,

I have created a new threads for support with the @lsismeiro blueprints:

ZHA, deCONZ, Zigbee2MQTT - IKEA E2001/E2002 STYRBAR Remote control Universal blueprint (Redux) - Blueprints Exchange - Home Assistant Community (home-assistant.io)
ZHA, deCONZ, Zigbee2MQTT - Ikea 5-button Remote Universal blueprint (Redux) - Blueprints Exchange - Home Assistant Community (home-assistant.io)
ZHA, deCONZ, Zigbee2MQTT - Ikea E1743 On/Off Switch & Dimmer Universal blueprint - all actions + double click events - control lights, media players and more with Hooks - Blueprints Exchange - Home Assistant Community (home-assistant.io)

For now I have only done the most popular blueprints, but I will keep an eye on the others for activity that would benefit a new thread.

[MarvinMynx]

Hey Everyone,

I need some help recreating my light automations using the Controller and Light Hook blueprints ^^"

I had to reinstall Home Assistant from scratch with a new coordinator (long story, but I had backups). Now, I’m struggling to set up my Hue Dimmer Switch automations.

I’ve imported the following blueprints:

• Light Hook Blueprint
• Philips Hue Dimmer Controller Blueprint

I configured two automations based on these blueprints:
Controller Automation:

alias: PC Lichtschalter
description: ""
use_blueprint:
  path: EPMatt/philips_324131092621.yaml
  input:
    integration: Zigbee2MQTT
    button_up_long_loop: true
    button_down_long_loop: true
    helper_last_controller_event: input_text.pc_lichtschalter_last_controll_event
    action_button_on_short: []
    action_button_off_short: []
    helper_debounce_delay: 100
    action_button_off_release: []
    action_button_off_long: []
    action_button_off_double: []
    controller_entity: sensor.pc_lichtschalter_action
    controller_device: 8f8022d5a4772b26d508d0238806f6f1

Hook Automation:

alias: PC Lichtschalter Hook
description: ""
use_blueprint:
  path: EPMatt/light.yaml
  input:
    controller_model: Philips 929002398602 Hue Dimmer switch v2
    light: light.0x0017880109626498
    controller_entity: sensor.pc_lichtschalter_action
    controller_device: 8f8022d5a4772b26d508d0238806f6f1

Here’s the data I retrieved from the Zigbee2MQTT page for the Hue Dimmer Switch (translated from German):

Device Name:        PC Lichtschalter
Description:
Last Seen:          N/A
Availability:       Disabled
Device Type:        EndDevice
Zigbee Model:       RWL022
Zigbee Manufacturer: Signify Netherlands B.V.
Description:        Hue Dimmer Switch
Support Status:     Supported
IEEE Address:       0x001788010bdc7d62
Network Address:    0x1950 / 6480
Firmware Date:      20210729
Firmware Version:   2.45.2_hF4400CA
Manufacturer:       Philips
Model:              929002398602
Power Supply:       Battery 44%
Interview Successful: Yes
Description:
Last Seen:          N/A
Availability:       Disabled
Device Type:        EndDevice
Zigbee Model:       RWL022
Zigbee Manufacturer: Signify Netherlands B.V.
Description:        Hue Dimmer Switch

However, I can’t get these automations to work. I’ve tried debugging with traces but haven’t made much progress. It seems like the button press packets from the Dimmer Switch are named differently since I reinstalled Home Assistant and paired everything with the new coordinator.

Here are some screenshots for reference:

I’d really appreciate it if someone could point me in the right direction ^^"

Kind regards,
MarvinMynx

[MarvinMynx]

well i fixed it, i used the Wrong Controller, and i switched to ️lsismeiro Updates Version’s for the Controller and the Hook. It’s working now.
Thanks @KrzysztofHajdamowicz for the Notice on that:

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

I have an impression that @epmatt abandoned his collection, but somebody else took over: GitHub - lsismeiro/awesome-ha-blueprints: A curated collection of automation blueprints for Home Assistant.

[pOpY]

Hi guys.

Are you aware of the removal of the legacy “action” payload in the upcoming Z2M 2.0.0?

See here: Z2M 2.0.0, legacy triggers, _action entity's and hue dimmer blueprints · Koenkk/zigbee2mqtt · Discussion #24997 · GitHub
I am using also this blueprints (slightly modified/fixed) and they will not work anymore.

What do you use now instead?