Hi both.
Well thatās not ideal(!)
Could you check the input helper and see what events are coming through?
If you have the history, maybe we could compare the messages from before the upgrade?
Hi both.
Well thatās not ideal(!)
Could you check the input helper and see what events are coming through?
If you have the history, maybe we could compare the messages from before the upgrade?
Thanks for the quick reply. After further research, sounds like a Z2MQTT issue that will be resolved in the next stable update.
Phew! Thatās good news
I have these two entries in my logbook, which is probably the best I can conjure up at the moment.
After firmware update:
fenjas_remote_last_controller_event changed to {"a":"brightness_move_down","t":1717842132.865108} triggered by automation Controller - Fenjas loftlys remote triggered by event 'state_changed'
Before firmware update:
fenjas_remote_last_controller_event changed to {"a":"off","t":1717779706.343913} triggered by automation Controller - Fenjas loftlys remote triggered by event 'state_changed'
So it seems to me that Z2MQTT thinks a button_down_short action is a button_down_long action instead.
I have the same issue. Has the problem been resolved now?
Updated z2m to 1.39.01 and was able to bind again , and everything worked againā¦firmware 1.0.024 and 2.4.11 havenāt been able to update to latest 2.4.15.
Hi all.
A new version of the Light Hook has been released.
It adds a new feature.
In its current version the light hook allows the color temperature to be changed to values that are not support by the light bulbs. Reaching values far outside this range will require the user to press the opposite button, potentially overshooting in the other direction.
I added a clamping mechanism similar to the brightness minimum and maximum. Additionally, I added a feature toggle that is deactivated by default, in order to prevent any breaking changes.
It has been tested by them and myself with no issues.
Enjoy and thanks to Botastic for the contribution
Fixed for me!
Now long press up/down doesnāt work. Still troubleshooting why.
I have successfully installed the Blueprint and Light Hook which I connected to a Helper Group containing my 6 Table lights. Everything works except for the dimming. When I hold Dim down or up it just dims the lights all the way down until they turn off, even if I let go of the button. Or it dims them all the way back up.
Any ideas?
Thank you, I checked it but it says it is no longer supported
I think you made an issue on the Github, we can continue there.
I would like to give two styrbars the exact same automation. Is ist possible to select two or more styrbars to mirror their controll?
Hello and Welcome.
Maybe you could create a template input helper that takes the input from either?
Iām not sure how that would effect the āController Deviceā if you are using ZHA/deCONZ.
Otherwise, best iāve got is to duplicate the automation.
Hi @LewisSpring,
For some reason doublepress buttons stopped working. And for the life of me, I have no clue how to troubleshoot. I played a bit with delays, didnāt seem to do much difference.
The things that have changed somewhere around that it stopped working is some updates of HA and Z2M. Also I changed from Eszp to Ember driver.
In the traces, the second press gets a āfalseā result. So it is registeredā¦ just doesnāt do anything anymore.
Could you help me troubleshoot? What would you like me to share?
Thanks
Hi
Please confirm you are using the latest blueprint from GitHub - lsismeiro/awesome-ha-blueprints: A curated collection of automation blueprints for Home Assistant.
This is what resolved it for Z2M previously: š ZHA, deCONZ, Zigbee2MQTT - IKEA E2001/E2002 STYRBAR Remote control Universal blueprint (Redux) - #10 by bmk
Should this work as a dimmer with a long press? I cannot get it working. It dims only one step and thats it. For the same button is also registered toggle light command. Enabling loop doesnāt make it any better.
Grab the Light Hook automation, itās designed alongside the Controller automation and provide dimming and such.
Hope that helps
Hey, thank you for the hook. The only problem is that if I long press up or down for about 1 second and then let go the light continues to increase/decrease brightness until it is fully on/off.
What am I doing wrong?
And what is the technical explanation for the automation not supporting continuous dimming? If I add an action to āDown button long pressā to step brightness by -10% and enable ā(Optional) Down button long press - loop until releaseā in the automation this should work, shouldnāt it?
You can do dimming in the Remote blueprint - I have done it before by adding a small delay after the dim action but the Hook is preferred.
Make sure your Remote blueprint does not have actions that conflict with the Light Hook. And make sure you are using the latest lsismeiro version as well as this is a bug that was fixed previously.
Welcome and hope that helps.