Yeah I saw that documentation part, but read it as if I was using either ZHA, Z2MQTT or wanted to use Double press actions, which i didnāt use any of. Seems that it could be improved in the docs a bit
Iām glad to hear that you managed to configure this blueprint.
With the feedback from you and other users here in the forum I recently fixed and improved docs for both controllers and hooks. Some of those info were outdated and referred to a previous blueprint version, so they needed to be updated.
Anyway, with the updated docs it should now be clearer which inputs are required, their role and how to set them up.
iām just getting started with HA and really struggling to get this to work. when running the blueprint automation i keep getting an error UndefinedError: ādict objectā has no attribute āeventā
iāve been all over the config files, instructions, and interwebs and just canāt figure out whatās missing here. any ideas?
Hi, have you created āHelper - Last Controller Eventā, itās required.
Check the additional notes of the button bleuprint.
In the configuration menu of HA there is a āHelpersā section.
More info on: Controllers-Hooks Ecosystem | Awesome HA Blueprints
@epmatt what a nice blueprint! Love it - especially the volume increase with long press!
But, when i Play/Pause my Sonos speaker with a SINGLE push, it also increases the volume but 1 unit - how come?
thank you for reporting here. Iām sorry for the delay.
Could you please provide the full YAML for the automation youāre trying to configure with this blueprint?
Thank you for your nice feedback! Iām glad that my work has proven useful to you!
But, when i Play/Pause my Sonos speaker with a SINGLE push, it also increases the volume but 1 unit - how come?
This behaviour is not expected. Could you please provide the full YAML for the automation you configured with this blueprint? Moreover, are you also using the Media Player hook for the same device?
I somehow worked around it when I disabled ālong pressā as volume up/down.
I can still somehow turn volume up/down by ālong pressā but now it sometimes lags/hangs, resulting in the volume being turned up all crazy to 100%!
Thanks for making this blue print. itās exactly what I need for these E1743 buttons that I have. I created a automation using this blue print. I used all the clicking triggers and all of them work, but I donāt know why double press triggers both short press and double press actions. I set double press delay from 500ms to 2000ms and it still triggers 2 actions. Here is the code and trace timeline:
Hi, @epmatt
Great blueprint.
Short press work fine with turning on/off.
But LongPress doesnāt seem to do much :-/
Questionā¦
Is the ā(Optional) Up button long press - loop until releaseā required when using long press?
If so, what is a feasible value for ānumber of repeatsā ?
How often does it loop per second (if that is how it works?)
(Optional) Up button long press - Maximum loop repeats
Maximum number of repeats for the custom action, when looping is enabled. Use it as a safety limit to prevent an endless loop in case the corresponding stop event is not received.
Hey @epmatt, Iām experiencing the same issue as @aceindy. With zigbee2mqtt and the latest version of home assistant (2022.3.8) / this blueprint (2021.10.26), only the short presses work. The E1743 switch itself is on firmware (2.2.010). It seems like one of the automation conditions are failing for some reason on a long or double press. Attached is the automation trace in case itās useful.
Looking at long press up/down as well,ā¦ Trying to configure the blueprint by remote (on my brothers HA instance - he lives 300km away)ā¦
How would one con figure the long press up/down to dim the the selected entities up/down ?