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.
Thats a shame. Did you ever happen to get the double press working again on remotes?
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
Go into Zigbee2mqtt web ui. select your hue dimmer device. then settings (specific). set Legacy to True.
Hi every one,
Iād like to control 2 switches (on/off) with rwl021 hue remote. I have following setup:
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 }}
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!
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?
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
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.
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.
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.
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?
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.