Thanks a lot for the template, is that possible to control more than 1 light by the same remote? I have now create 2 same automation to achieve this. If it could be combined into one blueprint that will be perfect
I think you mean a Light Group and not a standard Group.
Lights in a standard group can only be turned on/off (you can’t control their brightness). In addition, the blueprint uses an Entity Selector filtered for light entities only, so it won’t display a Group for selection.
Aaah, that’s why Alexa refuses to change brightness of my group. Other then that everything works (weird enough). I mean I can change brightness from Lovelace, and use the group in my blueprint. But (thanks to shitty Yeelight) I need to use this group via template
Thank you, Yuri! I love these blueprints. Is there any chance you can add the possibility to change the color temperature with the Dimmer Switch like the default behavior of the Switch?
That is, if you continue to press the “On” button, you circulate between 4 different color temperatures.
@yvolchkov is it possible to update the description with a button from this integration ? it’s about something like that because I don’t know how to implement it
I absolutely love this blueprint. However, after using it a couple times I noticed that sometimes lights would not go on in the right color or the right brightness and I was also missing an option to set transition times. So I just dove straight into your code and added some stuff and it seems to work fine ;-).
Things I have added/ changed:
Set default brightness (to switch on from off-value) in % of maximum brightness (100%)
Set color_temperature in Mired for switching on from an off-state
Selector for transition time for off > on transitions (also used for the dimming transitions)
Selector for on > off transition time
Below is the blueprint you wrote with the changes I made to it included, so if you like you can incorporate them into the official one and call it a version 2.0 ;-). (Ain’t opensource great?)
blueprint:
name: MQTT - Philips Hue Dimmer
description: 'Control lights with a Philips Hue Dimmer Switch.
The top "on" button will turn the lights on to the last set brightness.
Dim up/down buttons will change the brightness using predefined step and can be
pressed and hold until the brightness is satisfactory.
The bottom "off" button will turn the lights off.
Long Off or On press will set brightness to the maximum or to the minimum. '
domain: automation
input:
dimmer:
name: Philips Hue dimmer action sensor
description:
'This must be an "action" sensor provided by zigbee2mqtt. For example
"sensors.living_dimmer_action" '
selector:
entity:
domain: sensor
light:
name: Target light
selector:
entity:
domain: light
step:
name: Dimming step in percent
default: 25
selector:
number:
min: 0.0
max: 50.0
mode: slider
step: 1.0
unit_of_measurement: "%"
default_brightness:
name: Default brightness level
description: Set this brightness level for switching on from off state
default: 80
selector:
number:
min: 1.0
max: 100.0
mode: slider
step: 1.0
unit_of_measurement: "%"
lowest_brightness:
name: Lowest brightness level
description: Set this brightness level on long "Off" button press
default: 3
selector:
number:
min: 1.0
max: 50.0
mode: slider
step: 1.0
unit_of_measurement: "%"
color_tmp:
name: Color temp (in Mired)
default: 320
selector:
number:
min: 150.0
max: 500.0
mode: slider
step: 1.0
unit_of_measurement: "Mired"
trans-on:
name: transition for switching on as well as dimming
default: 0
selector:
number:
min: 0.0
max: 5.0
mode: slider
step: 0.5
unit_of_measurement: "s"
trans-off:
name: transition for switching off
default: 1
selector:
number:
min: 0.0
max: 5.0
mode: slider
step: 0.5
unit_of_measurement: "s"
source_url: https://community.home-assistant.io/t/mqtt-philips-hue-dimmer/257551
trigger:
platform: state
entity_id: !input "dimmer"
action:
- variables:
command: "{{ trigger.to_state.attributes.action }}"
step: !input "step"
negative_step: "{{ -1 * (step | int) }}"
- choose:
- conditions: "{{ command == 'on-press' }}"
sequence:
- service: light.turn_on
data_template:
entity_id: !input "light"
transition: !input "trans-on"
color_temp: !input "color_tmp"
brightness_pct: !input default_brightness
- conditions: "{{ command == 'off-press' }}"
sequence:
- service: light.turn_off
data_template:
entity_id: !input "light"
transition: !input "trans-off"
- conditions: "{{ command == 'down-press' or command == 'down-hold' }}"
sequence:
- service: light.turn_on
data_template:
entity_id: !input "light"
brightness_step_pct: "{{ negative_step }}"
transition: !input "trans-on"
- conditions: "{{ command == 'up-press' or command == 'up-hold' }}"
sequence:
- service: light.turn_on
data_template:
entity_id: !input "light"
brightness_step_pct: "{{ step }}"
transition: !input "trans-on"
- conditions: "{{ command == 'on-hold' }}"
sequence:
- service: light.turn_on
data_template:
entity_id: !input "light"
brightness: 255
transition: !input "trans-on"
- conditions: "{{ command == 'off-hold' }}"
sequence:
- service: light.turn_on
data_template:
entity_id: !input "light"
brightness_pct: !input "lowest_brightness"
transition: !input "trans-on"
As far as I understand it, I believe that would be easy to fix (famous last words). If you look into the code of the blueprint there are these snippets like
I believe (said the fool) that the easiest way to make the blueprint work with both the old and the new dimmers would be to change that snippet (and others like it) into something like:
So basically testing for both possibilities. But I am sure that there are readers here with a lot more experience and knowledge that might know a smarter way to do it. (maybe with a wildcard?)
It should be simple to test though if it works or not.
Hm, i´m getting the error below - any idea why this happens?
Trace:
Triggered by the state of sensor.dimmerschlafzimmerbett_action at 16. November 2021, 10:33:45
Stopped because only a single execution is allowed at 16. November 2021, 10:33:45 (runtime: 0.00 seconds)
@yvolchkov I think this is broke. I’m getting this message when trying to run an automation from the script, "Stopped because only a single execution is allowed ".
Can you confirm if it’s still working or not?
