I looked a bit into the commands that the controlller sends, and besides the double clicks I mentioned in my previous post, there is a problem with this blueprint and long presses too. When you do a short press, it sends a âshort_releasedâ and a âshort_pressedâ command (in that order!). When you do a long press, it first sends a âshort_pressedâ, then a series of âlong_pressedâ (about 1 per second) , and finally a âlong_releasedâ. So if you want to use both long and short presses of the same button, and the long press is not just a repeat of the short press action, the event you should listen too for the short press action, is the short release.
So, in short, this blueprint collection is very nice for the IKEA buttons, but to work for the Philips dimmers it needs some adaptation.
This blueprint stopped working for me last night. Possibly after a HACS update of something (maybe the zha toolkit?) I can see the remote is still firing events. Any suggestions on how I should debug? Iâm still on 2023.1.6 since 2023.2.x has screwed up ZHA Sonoff integration and I havenât been brave enough to try 2023.3.1 yet
So I think I did what youâre describe, moving the short press action over to release, but Iâm still not able to trigger thing with short press when I have double press turned on. Any other hints you can give as to how you fixed this? Thanks!
for my part is not working. really weird because I can see the integration in the device. The commands are ok in the log of z2mqtt and even the scripts is with the same commands. Any idea?
I love this blueprint.
Actually, one thing is missing for me.
It would be great to have a time or sun based condition in there.
For example, in my bath, when I press âonâ I would like to have the light at 100% when the sun is up, but only 20% when the sun is down.
In the room of my childs, the light should be at 100% between 7 am and 7 pm, and 20% between 7 pm and 7 am.
I would have one automation for each time slot.
Do you think it would be possible to add this?
Maybe you should not be using this blueprint, and instead crafting your own automation. Just a thought. Looks like you have defined your scenarios and parameters already.
This blueprint is for using a switch as a switch, not for creating routines.or automations based on other events. You press a button on the switch to perform a set function, like a light switch would do.
Youâd need to create your own spearate automations for conditions like that, or look for a different blueprint to do what you need to do. A light switch doesnât create routines like that. Itâs a switch.
You can use the Events generated by the switch integrated to your own automation to achieve what you want to achieve.
does this blueprint still work?
iâm trying to use it with my 324131092621 switch (just as a basic on/off switch), but when i press a button nothing happens.
Anyone having problems with double press? I want to have a double press of the off button turn off all my lights (by activating a scene) but it always just chooses the default option (which is what a single press of the off button does - turns off one specific light).
It seems the condition which checks if previous event was a short press does not work.