Hi danieldeni,
Many thanks for your blueprint (and to those you based it on) !
I am using this to control 4 lights - 2 Philips hue and 2 Tapo multi-coloured lights.
With your code the dimming on the tapo lights was changing the brightness by approximately 3% but I wanted to make this 1%. I noticed that each click of the dial increased the raw data by 8 so I adjusted the variables section in the code as follows:
This code now means every small step rotation is a step of 1.
(I am new to HA blueprinting and I couldn’t work out how to divide by 8 in one line!)
To dim the light in all the rotate left or right aliases I changed all references of:
brightness_step to brightness_step_pct
This means 1 click of the dial will change the brightness by 1% if the dial is moved slowly, and if the dial is moved quickly the brightness step will change accordingly. The dial automatically reports a larger step size which is great!
My Tapo lights change brightness from 1% to 100% in steps of 1% so I find this works best for these lights, particularly if you want to set it at the minimum setting as a night light. It also works well for the Philips lights, but they are less sensitive.
Feel free to integrate this in your blueprint if you or anyone else finds it useful!
I am only using Philips Hue lights and those have 255 steps of brightness as it doesn’t target the % of the light but the raw brightness values through the step command. For Zigbee lights this is common, but I guess Wifi based lights like Tapo only have 100 steps using this?
I’ll need to check when I have time to make the step size configurable for this use case, as it will be too slow for Zigbee lights with your changes.
Hi @danieldeni - I’ve been using your Blueprint for a while now but I think I have run into an issue with using a Schedule.
My Hue downlights are switched my Clipsal Wiser switches so I have an automation that keeps the light state and switch state in sync but also using different light settings (brightness, colour temp) depending on the time of day.
I replicated those time of day settings in a Schedule, created via the UI:
Check the example I have in the start post. The additional data should be with these names per field:
brightness_pct: 30
color_temp_kelvin: 3333
Where you can put your own numbers of course, per preference.
Do keep in mind the Blueprint doesn’t trigger the schedules automatically on changes, only if you press the button. I have a separate automation in place that triggers on schedule change, might integrate that later into the blueprint.
That’s an example for generic use yes. And might be updated in the future outside of my control.
color_temp was linked to mired in the past and was changed somewhere in 2024 to be based on kelvin. To avoid confusion I used color_temp_kelvin .
My start post has instructions for my blueprint specifically. You can use whichever names are set inside the blueprint, others are ignored as they are not put in the logic of the automations and variables.
