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.
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.
3 Likes
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.
1 Like
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:
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
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:
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?
2 Likes
Blueprint does not work Zigbee2mqtt 2.x as mention above.
same here. the ikea e2001/e2002 is not working anymore.
IKEA Controller stopped working after update to Zigbee2MQTT 2.0.0
refer to
this concerns e.g.:
Controller - IKEA E2001/E2002 STYRBAR Remote control
Controller - IKEA E1743 TRĆ
DFRI On/Off Switch & Dimmer
Solution
but as far as I understand just temporary:
All action sensors are now disabled by default (sensor.*_action entities). Itās recommended to use the MQTT device trigger instead. In case you really need the action sensors, add the following to your [Zigbee2MQTT] configuration.yaml.
homeassistant: legacy_action_sensor: true
see /Zigbee2MQTT 2.0.0 breaking changes Ā· Koenkk/zigbee2mqtt Ā· Discussion #24198 Ā· GitHub
Just for reference/Notes:
also found so far:
sorry - even after using HA intensive - I have no idea, whatās going on there
Probably the solution is here:
- alias: Respond to button click
triggers:
- trigger: device
domain: mqtt
device_id: ad44cabee4c646f493814306aa6446e1
type: action
subtype: arrow_left_click
actions:
- action: light.toggle
target:
entity_id: light.bedroom
I put my eyes for 5 minutes in the blueprint - but this code is over my abilities ā¦
Itās because after update to 2.0 of z2m the actions sensors are not created by default they were replaced by event.xxxxx entities.
in the configuration you canenable the legacy configuration or just stop using this blueprint.
Everyone,
I finished updating all of EPMatts blueprints to work with zigbee2mqtt 2.x.
They are on my fork of his repo.
All links (website & docs) should work so no need to download manually unless you want to.
Blueprints largely remain untested (Controllers and Hooks) so would love some feedback.
As a bonus I added support for a new Controller
IKEA E2201 RODRET Dimmer
If you run into an issue I still would like you to open an issue on EPMattās Repo but mention if the blueprint or hook is from my fork.
Enjoy Ohh one last thing
**WARNING** **Breaking Change**:
The controller_entity input has been deprecated, and controller_device is now mandatory.
If you are a Zigbee2MQTT user and plan to update this blueprint, please make sure to remove the controller_entity input from your automation config and add the device ID of your controller to the controller_device input.
To obtain the device ID from your controller, configure the automation from the UI and use the device selector dropdown on the controller_device input to select your controller.
3 Likes
Iāve been watching your work over the last few weeks and have a lot of respect for it.
I already had parts of your revision and parts of lsismeiro in use.
You were probably thrown back a bit by the rebase to epmattās repository, werenāt you?
Itās certainly a good step for the community to upload everything back to the original repo. But I find it unfortunate that this has led to delays again.
The release of Z2M v2.0 is already too long ago. The forums were full of questions and you would have already had the answers. And the pull requests have still not been accepted.
Iām keeping my fingers crossed that everything can be finalized soon.
Thank you for your work. All of you!
Can anyone tell me why long presses on Styrbar E2001/E2002 are not looped correctly? Iād like to increase or decrease the brightness of lights continously, but holding the button longer has no effect.
1 Like
Iām having a similar issue with double clicks, not sure if it is related but it doesnāt seem to work with the button press. Itās one or the other but not both
I was able to update some blueprints, but when I try to import philips_324131092621.yaml I get an error āInvalid blueprint: extra keys not allowed @ data[āblueprintā][āinputā][ācontroller_deviceā][āselectorā][āfilterā][0][āmodel_idā]. Got Noneā
2025 Update: We are back! 
Hey everyone, 
after a bit of a break (because, wellā¦ life happens), Iām finally back contributing to Awesome HA Blueprints! 
For those wondering what Iāve been up to in the last few years, my LinkedIn says it all ā feel free to check it out and connect!
A Huge Thank You
I know it must have been frustrating to see this project slow down, and I canāt thank you all enough for keeping it alive while I was away. Looking at the time, effort, and dedication youāve put in - whether through forks, discussions, contributions, or just spreading the word - truly leaves me speechless.
Itās incredible to see how much this community cares about Awesome HA Blueprints, and itās exactly what motivates me to jump back in and bring my energy back to the project. You all rock!
Whatās Happening Now?
Weāre diving back into the project with a clear focus on improving and expanding Awesome HA Blueprints:
Reviewing open issues and PRs ā refining existing blueprints and ensuring they meet the high-quality standards we all strive for.
Addressing community feedback ā from this repo, the Home Assistant Forums, and the countless DMs Iāve received. Your input matters, and Iām making sure itās heard.
Planning for the future ā beyond just blueprints, Iāve been focusing on improving the entire ecosystem: better docs, a smoother contributor experience, and other quality-of-life enhancements to make this project even more accessible.
Our goal? To make this the go-to platform for high-quality, reliable automation blueprints for Home Assistant. 
Want to Get Involved?
This project is all about community, and weād love your help! Whether itās submitting blueprint ideas, reporting issues, or contributing with code, every little bit helps. Feel free to share your feedback on the announcement post on GitHub.
Thanks for being part of this journey, looking forward to catching up with all of you! Letās make Awesome HA Blueprints even better, together. 
Cheers to many more automations ahead!
2 Likes
For anyone facing bugs or challenges in setting up our blueprints, feel free to open a new Issue on GitHub - happy to help!
Thank you all again for your amazing support and kind patience!
Thanks for the great work!
I tried to use the Styrbar blueprint. I know my Styrbar works well, because a simple automation with it as a trigger does work. However, try as I might I cannot have the blueprint working. Iām reluctant to call this a ābugā and report it in Github, so I write here.
I have the Z2M integration, an HAOS install, an SLZB-06 concentrator. Z2M sees every button press.
The blueprint is installed, I refer to my Styrbar remote in the ā(deCONZ, ZHA) Controller Deviceā field since the documentation says the ā(Zigbee2MQTT) Controller Entityā field is deprecated. That field is left blank. I have a text helper dedicated to this blueprint and itās properly identified in the required field. I added an action for a single button press and didnāt change anything else (timings for long presses, etc). The blueprint gets saved but a button press does nothing.
I will welcome any help at all. Thanks!
EDIT:
Well, itās good to check the github issues first:-)
Hi,
I just tried these blueprints out for the first time trying to configure a Hue v2 dimmer to controll a hue light. However, the controller blueprint doesnt find the controller device for the v2 dimmer so I canāt configure it. Using ZHA. What am I missing?
