Correct, but the dim up/down button has no config options other than the action which it increase or decrease brightness
Well, of course to use the light.turn_on service, you need to configure it to use the light.turn_on service instead of a device trigger.
That button isn’t the light on button, it’s the dim button
There is a separate button solely for turning the light on, as I said it’s a 4 button switch
1 button solely for turning the light on
1 button for dim up
1 button for dim down
1 button for turning the light off
When I press dim up or down (once the light is already on) the brightness steps are too harsh
Yes, I know what the Philips Hue Dimmer Switch looks like. And we have been telling you that you need to use light.turn_on with the brightness_step parameter adjust the brightness of your lights by, well, the given step (with a negative value for the Down button of course).
I am using the light.turn_on parameter set on the “on” button, as that’s the only button that I require to turn the light on
The dim up/down should only adjust the brightness if the light is on, thus having the light.turn_on parameter against those burns would be inappropriate, however there is no brightness step parameter to set against those buttons
Well, if you want to adjust the brightness step, you will have to use the service. If you don’t want it to operate on lights that are not currently switched on, you will have to add some conditions around the service call. Fortunately, you can easily do that.
Edit: You might even get around the conditions with some clever templating, see Add action to update light state without turning on - #12 by 123 for inspiration.
I’m not 100% convinced you’re fully understanding the use case and how the switch is configured, maybe it’s me being the idiot in explaining it
All I want is that, whilst the light is on, pressing the dim up or down button results in a less harsh brightness step. At a guess I’d say that each press results in a 20% change
Yes, I do understand. You use the light.turn_on service with the parameter brightness_step for that. If you do not want that call to turn on lights that currently off, you have to filter light group in the entity template (or add some more elaborate conditions around the service call). There is no magic “change all brightness steps” setting to make that work with device triggers.
where do i find the yaml file to post?
i’ve had a look thru various yaml files and can’t see anything that has the switch config in it.
You can change the view to YAML while editing the switch. But it does not matter anymore, what we needed to know was visible on your previous screenshot. You just don’t like the answer.
I just tryed to add a blueprint for the eglo 99099 remote, but for some reason it does not show up in switch manager
Anyone able to help out here?
I have an issue which I can’t figure out. I use a HUE Dimmer V2 via Z2M.
On the press event I have this yaml code configured. But somehow the input select triggers two next’s. In the logbook most of the time there are two entries see below
Logbook
Woonkamer Scenes changed to Woonkamer Romantisch triggered by service Input Select: Next
20:25:11 - 29 minutes ago
Woonkamer Scenes changed to Woonkamer Overdag triggered by service Input Select: Next
20:25:11 - 29 minutes ago
YAML
- service: input_select.select_next
data:
cycle: true
target:
entity_id: input_select.woonkamer_scenes
- service: scene.turn_on
target:
entity_id: >-
{{'scene.' + states('input_select.woonkamer_scenes').replace("
","_").lower()}}
Hey @Sian (or anyone else),
I’d love to get my Inovelli 2-1 dimmer switch to dim/brighten when holding the button, and then stop dimming/brightening upon release. Could anyone explain to me how to do this within switch manger?
Does anyone have any examples for how to set up conditions and triggers for a philips hue switch v2 running on zigbee2mqtt?
I can make it do something simple like “activate scene 2” no problem. But if I want it to cycle through multiple scenes, I need to do some kind of conditional if/then statement (it seems) but none of the available options seem to be able to read the current scene or current brightness of a bulb, and so it doesn’t function.
I assume I need to do it via yaml code or something, but there seems to be zero guidance on how to actually do this (common issue with home assistant haha).
I use something like this on the Press event:
- service: scene.turn_on
target:
entity_id:
- scene.my_first_scene
- wait_for_trigger:
- platform: device
domain: mqtt
device_id: <device_id of the switch>
type: action
subtype: off_press_release
discovery_id: <discovery ID> action_off_press_release
timeout:
hours: 0
minutes: 0
seconds: 10
milliseconds: 0
continue_on_timeout: false
- service: scene.turn_on
target:
entity_id:
- scene.my_second_scene
- wait_for_trigger:
- platform: device
domain: mqtt
device_id: <device_id of the switch>
type: action
subtype: off_press_release
discovery_id: <discovery ID> action_off_press_release
timeout:
hours: 0
minutes: 0
seconds: 10
milliseconds: 0
continue_on_timeout: false
- service: scene.turn_on
target:
entity_id:
- scene.my_third_scene
Not sure what the discovery_id is for, that part is auto-generated, I made the automation in visual mode and edited parts afterwards in YAML. (My actual automation contains some additional stuff that’s not relevant to your question.)
Hello, thank you for this app !
I have an ikea sonos E1744 rotate controller. I’ve set up it. It works for press buttons, but not for rotates right or left :
Nothing happens when I rotate… Any idea ? Thank you
I just want to say; this is amazing. After messing about for ages with scripts and automations across HA and Z2M trying to get my Philips Hue remote’s “hue” button to cycle through scenes in the way it does with the native app, I chanced across this and IT DOES EVERYTHING I NEED.
Fantastic work indeed! More people should use this - it solves so many problems and can simplify many setups, I’m sure. Thank you to the developer of this.
Hi Sian, thanks a lot for switch manager! it’s great!
@all
I am trying to create a blueprint and I followed the advices given in the docs, especially regarding naming conventions.
I placed the yaml and the png in
/config/custom_components/switch_manager/blueprints
and called
switch_manager.reload
via developer tools to activate/see it in switch manager.
Meanwhile I restarted HA, but the blueprint is still not shown in the UI
But: my blueprint is not showing up - what could I have done wrong?
Sian pointed me to the section in the docs that I didn’t read carefully: custom blueprints should be stored in the config/blueprints/switch_manager folder and not in the custom_components folder.
Thank you Sian!