Mine just stopped working with z2m 2.0.
I think we need an update of the Blueprint.
Context:
Unfortunately due to the new Z2m 2.0.0 version, this blueprint doesnāt work anymore. The action entity is depracted and the device trigger should be used. Does anyone have an updated blueprint? See: Quote from āZigbee2MQTT 2.0.0 breaking changes Ā· Koenkk/zigbee2mqtt Ā· Discussion #24198ā
@tivoo @UsefulVid did you try to add
to the zigbee configuration.yaml? Curious if that would get things working before I try it.
This can also be done in the gui and it works again now
Heya -
Iāve never looked too far into the logic myself - Iām not much of a programmer.
From what youāve said that would make sense though.
By changing the conditions, what do we achieve?
If youād like to put it in a pull request Iād be happy to discuss if itās going to improve the UX.
Hi @RGx01, @UsefulVid, @tivoo
As per @RGx01 's message, I believe this is all that is needed.
If youād like to test the new V2 compatible blueprints, please see here: Update to support mqtt based triggers by yarafie Ā· Pull Request #33 Ā· lsismeiro/awesome-ha-blueprints Ā· GitHub
I havenāt had chance to post this around yet
Hi everyone,
thank you for keeping this blueprint up to date, It works (nearly) perfect! One thing I cant get to work: āDown-button-releaseā isnāt triggered.
After checking my log, the STYRBAR sends a āstop_0_0ā when releasing the button after a long press.
If I understand it correctly, the automation listens for
"button_down_release:
- stop
- stop_with_on_off"
Is there a way (for me as a newbie) to add the āstop_0_0ā here? Or maybe thatās not the problem at all and Iām not far enough in to see a solution?
Thank you for your help!
hrivex
Worked yes, but after enabling this couldnāt create z2m groups in z2m addon anymore. Old groups didnāt work any more after 2.0 update so deleted them and try to create new, but it succeeded only after legacy set to false. Dimming and creating light groups is so more easier in z2m than in HA.
Tell me, how can I use this drawing to switch between light sources? So that the arrows can change the specified bulbs in turn.
Thanks for the reply. Matt seems to be actively developing the blueprints again and we are in touch. Have written up the issue more clearly here.
Thanks! To solve the issue for now I have just restored the backup of the old Z2M version, maybe itās better to wait a while
I did that once. I used two helpers. In an input select I populated entity_id of the lamps I wanted to control then used an input number which was controlled by styrbar buttons, the numbers were tied to the input select, so min max had to match input select length. This way left/right decreased/increased number. Up/down used input number to fetch correct entity from input select and then did itās light actions
Hi all
I havenāt updated z2m mainly because I have 3 stybar buttons with this blueprint. Is it safe to update now? Will this blueprint work? Is there any other version that works with these buttons?
Thanks
@LewisSpring could you give some guidance on what is needed to get the BP to work after disabling z2m v2 backward compatibility? what do I need to set in the (Zigbee2MQTT) Controller Entity? I canāt seem to figure it out. Iām using Version 2025.01.03-EPMATT from the repo but as soon as I disable the Z2M backward compatibility I canāt get things to work. What am I missing?
Wrong version of the blueprint
I am also commenting here as I am not sure how to get this working with my IKEA E2001/E2002 STYRBAR remotes.
Is there a quick reference section anywhere that tells us which remotes are working with Z2M 2.0 ?
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.
@yarafie thanks for this, I thought I had the latest version when I asked @LewisSpring but seems like there lots of similar repos with varying version numbers. Iāve used your repo and migrated my first switch and it works perfectly. 12 more to go
I started working with @LewisSpring on @lsismeiro fork, but as we were going to release @epmatt contacted us. A few discussions and some code discussions I decided to start from scratch and target updating the original repo of EPMatt whom has gone silent again I hope all is well with him.
Since I had most everything ready to go and saw a lot of confusion between the different versions, I decided to just push to my fork and post here so we can have a baseline.
Brand spanking newb here. I just got my Styrbar up and running (Home Assistant is the BEST rabbit hole ever!). I donāt quite understand the link between the controller and the hooks. My initial idea was to use up and down for a light group (3 GU10 spotlight globes). One and off, etc. But I wanted to use left and right for another light which is not part of the light group. Can this be done? How do I link the up/down to Hook Spotlight and the left/right to Hook Youāre Stupid?
Is there any reading that a newb can do to understand the controller/hook principal?
(Oh and did I mention that the Home Assistant rabbit hole is freeking awesome?)
You can change the blueprint in Studio code.
There you can manage the behavior of the left and right buttons.
If you want to toggle between scenes or other devices, you can make a dropdown helper which selects the lights.
Or check this blueprint