Correct! You also need to make sure the max value of your counter helper is increased (double press =4 now, so counter max needs to at least be that.
Let me know if you aren’t able to figure that part out and I will upload some yaml code you can reference. Might not be until next week though when I have a chance to sit down and strip out my personal information from the script.
It’s interesting that you’re having the same issue with me on this! Frustrating that I can’t find a fix, but at least it works now!
Hi, I just installed the Z2M blueprint, great work! For the rotations I am currently using increase_brightness and decrease_brightness. Increments are quite large and discontinuous. Anyone has a good solution to have a smooth increase and decrease of brightness? Thank you!
An upgrade request. Regardless of the last button press, I’d like to always use wheel to increase/decrease the brightness in the room.
It would be nice if there is an option for “rotation clockwise” and “rotation counter clockwise”, that is executed for all 4 buttons, together with specific button_x_rotate_counter_clockwise operation.
This way we can have actions dedicated to specific button (current implementation) and generic ones, that are always executed.
The only way to achieve this today is by copy-pasting the same code for all 4 buttons.
# tasks linked to button
switch (button_pressed):
case btn1: actions_rotate_btn_1();
case btn2: actions_rotate_btn_2();
case btn3: actions_rotate_btn_3();
case btn4: actions_rotate_btn_4();
# And finally actions regardless of the button
# these are always executed
actions_rotate_btn();
Ah, apologies, that is even another option compared to what I had in mind…
But this is a quite specific need, for which I don’t think it adds to put it in a generic blueprint.
My suggestion would still be that you convert the blueprint back into an automation.
Then, in the default actions section, between “call a service ‘counter: Reset’ on templated entities” and “Choose between 16 actions” add a new action which follows:
If-Then logic
Condition : triggered by ‘rotation’
Action: Whatever action you always want to happen
this way, the automation will process this before it will follow the button specific action. You can also put the action after the ‘Choose between 16 actions’ for it to execute after the rotary action of the specific button.
Be aware: You need to put this OUTSIDE of the choose, otherwise, it will not trigger both the generic rotation action and the button specific rotation action
I have just received my tap dial and i want to use this blueprint but i cant get it to work.
I have used the same names for the helpers en have tried in mqtt to turn of the legency attributes and the legency triggers but stil it doesnt work.
I dont now what i am doing wrong.
Can someone mayby help me?
In the picture is a screenshot of my bleuprint with only on the first button a test light near my pc
If you remove ‘sensor.’ from that field, the topic should be fixed.
If it still doesn’t work & you want to ensure you have the correct topic, you can get if from the Z2MQTT logs or HA events when pressing any button on the dial, or by using MQTT explorer.
i have it now fixed. i had to remove the sensor. and the _ between wandschakelaar and garage. maybe it is a idea to put a screenshot of this in the manual? i am still a noob so with that picture i had figured it out of my own.
MQTT topic technically comes from the Z2M ecosystem. You can open the device inside Home assistant, settings → Devices and Services → MQTT integration → your device. There is a MQTT log and shows device name inside MQTT.
No, that would just confuse people even more. Not only are people’s topics named differently because of the device name, they also have different formats.
Some people have spaces in the topic, others use dashes instead or don’t use spaces at all. Hell, some just leave the default Z2M naming so the topic looks like 0x123bda…
