Amigo muchas gracias por tu configuracion, despues de dias buscando un ```
blueprint para mi Moes he conseguido dar con tu automatizacion y me ha funcionado a la primera, cambiando un par de cosas.
de verdad mil gracias por tu aporte¡¡¡¡¡
un saludo
1 Like
Thank you so much for sharing (:
it worked like a charm <3
as a suggestion is it possible to add the command mode set so command mode is set every time to ensure its on?
with kind regards
Hi. Thanks for sharing your automation. I could not get the blueprints to work so far as I cannot find my bulb in the list of available entities. However, only the toggle action works for me. When I go into z2m I get the following error:
Works like a charm. Thank a lot!
One thing though. It dig go off when I turn it all the way down. What do I need to change?
Happy to hear!
If you want to dim to 0 (and therefore effectively turn off the light) just change min_brightness: 1 in the variables block to 0.
BR
So I took the time, transferred the basic idea of this automation into an blueprint and added a couple more feature including keeping the knob in command-mode automatically:
Feel free to check it out.
1 Like
I tried several blueprints to make this controller work reliably and with lower latency.
I couldn’t find one that worked for me.
But then I a reddit commentor proposed using ControllerX, available for AppDeamon via HACS. And it works. Reliable and swift reaction to my input, including holding and rotating.
Once you set up ControllerX according to their guide1, you can try my config after disabling all automations for your controller.
Here’s my current config for the controller:
<your_appdaemon_appname>:
module: controllerx
class: TuYaERS10TZBVKAALightController
integration:
name: z2m
listen_to: mqtt
controller: <friendly name in z2m>
light: <light entity, can be single or group>
release_delay: 0.001 # helped me to avoid a toggle event by releasing after holding
mapping:
# Command mode
brightness_step_up: click_brightness_up
brightness_step_down: click_brightness_down
toggle: toggle
hue_move: hold_brightness_toggle
hue_stop: release
color_temperature_step_up: click_color_down
color_temperature_step_down: click_color_up
1 You also need to activate the mqtt plugin and add username and password to your broker.
I’ve imported the @pbergman blueprint as suggested by @rdeangel in the OP.
When trying to use it, it only allows me to choose select entities in the state step, but the knob doesn’t expose any to HA. The action sensor is just a normal sensor, not a select. In my case sensor.living_room_knob_action.
Is this correct?
What am I missing?
Edit: nvm. I saw the original post and noticed it says it should be the select entity that changes event to command mode. Still I took charge of the automation and adapted it to my needs.
Hi,
maybe look at my post if you need a smoother dimming experience. I’ve done some work to make it work better with zigbee2mqtt directly:
Tuya smart knob improved blueprint for Zigbee2Mqtt - Blueprints Exchange - Home Assistant Community
Nice work, will try have look! Currently i have some good result when leveraging the step size state to increase/decrease the brightness instead of letting ha increase/decrease the lights.
data_template:
brightness: >
{% set current = state_attr('light.some_light', 'brightness')|int(0) %}
{% set step_size = states('sensor.rotate_switch_action_step_size')|int(0) %}
{{ current + step_size if current + step_size < 255 else 255 }}
entity_id: light.some_light
action: light.turn_on
for command brightness up and
data_template:
brightness: >
{% set current = state_attr('light.some_light', 'brightness')|int(0) %}
{% set step_size = states('sensor.rotate_switch_action_step_size')|int(0) %}
{{ current - step_size if current - step_size > 0 else 0 }}
entity_id: light.some_light
action: light.turn_on
brightness down. The rotate_switch_action_step_size is the Action step size sensor of the device
Do you have the new (white) rotary button by any chance? Like this one: https://a.aliexpress.com/_EQayxwC
And would you mind sharing your full automation?
i don`t have that particular model. The ones i use are similar to this one and show up as Tuya ERS-10TZBVK-AA
i use my blue print for setting up the devices
1 Like
I decided to use switch manager. I should’ve known about this tool earlier! It’s really great and available on HACS.
I use your blueprint for months and works perfect!.
With the new zigbee2mqtt version 2.x do you will migrate the blueprint or create new for the new mqtt events system?
Hello, good to hear that its working perfect!.
I haven’t had time to upgrade to new version but reading change list i don`t see anything that could break this blueprint.
This because the blueprint uses the mqtt platform for detecting changes and as long the topics or state entitie don`t change it should just work.
But don`t know for sure unless i have tested this 
1 Like
I’m switching my stuff to the entity events If I can pull it off…
Ok. My automation stop working and I think is for the zigbee2mqtt changes.
I will test better
Edit:
Yes, its my fault.
Works fine
1 Like
Hello Pbergman,
I used the blueprint for an automation and commands on/off and dim work fine. Many thanks for that
The Command | Color Temperature Up and Command | Color Temperature Down I can’t get to work. I want to control RGB Led when I work at the table to cool white and in the evening to warm white by pressing the button and rotating.
How do I do that?
Wilfried
Hello Wilfred,
make sure you are in command mode and then you should be able press + turn to activate that command.
perhaps you should go to your device and check logs to see if it picks up the command.
