KNX - relative dimming for lights

wisedatum · December 2, 2022, 2:12pm

Please add the function of absolute dimming to your blueprint

hansQ · December 31, 2022, 4:16pm

Hi wisedatum, I already did a workaround for an absolute dimming. You find the description here: Dim Hue Lights with KNX Push Button – Home Assistant Solutions

airmax · January 28, 2023, 8:47pm

Somehow I miss the part how to define the relative dimming address in the configuration.yaml. The entity KNX light supports only DPT5 not 3. Could you provide an example?

farmio · January 28, 2023, 8:51pm

This is a blueprint for controlling non-knx HA light entities from Knx buttons.
No Knx light entities should be involved.

airmax · January 28, 2023, 9:07pm

That’s what I’m trying to do, but there’s this relative dimming address that I’m assigning to a KNX button and that should be used in the template. So I don’t need to declare this address in the configuration file? Just use it in the automation?

farmio · January 28, 2023, 9:23pm

Yes, no yaml needed.

I must have misunderstood that sentence.

benschi11 · January 28, 2023, 10:48pm

Hi, I really like your blueprint and it is working great with my ikea tradfri light.
I use the MDT Glastaster 2 for controlling the light and would like to control the color too. The switch offers a way to change the color, but it uses HSV and the DPT 3.007 dimming step. Do you know a way to integrate this into your blueprint?
Thanks a lot

farmio · January 28, 2023, 11:20pm

Hi !
I think your best bet is to copy / fork the blueprint and extend it. I do not plan to add more features to it right now.
It was originally meant to be a showcase how the knx integrations services can be used

Gurkenflieger · March 8, 2023, 5:25am

For me this blueprint wont work. It only dims one or 2 percent and then aborts the dimming process like the others described. Im using MDT Tas55 and GT2. I think the problem is the feedback. If we can read out the brightness before dimming and count it up or down by ourself without waiting for the return state of the lights entity it should work, like the owner of the Hue integration suggested. I will try it but Yaml is totaly new to me. I think thats also the way how some other vendors implemented relative dimming.

farmio · March 8, 2023, 6:09am

Not sure what you mean by that. This blueprint doesn’t wait for any return.

I’m successfully using it with Hue, but not with the default step count - Hue seems to have problems processing too many service calls per second. (I use 5 sec 5 steps currently).

Where did marcelveldt say that? Do you have a link?

Gurkenflieger · March 8, 2023, 7:40am

github.com/home-assistant/core

Philips Hue Dim Sequence

opened 11:51AM - 15 Feb 22 UTC

closed 04:51PM - 18 Feb 22 UTC

kruzgix

integration: hue

### The problem I want to DIM UP or DOWN hue lights as long as a push button is… pressed. To achieve this I use an automation the sends repetitions of DIM UP or DOWN commands. In my test case I simplified it to: 1. Turn on the light 2. Wait 2s 3. Send DIM DOWN commands with a value of -10% 4. After 10 repetitions I expect the light to be OFF, but the light is still ON at a certain percentage, doing this with several lights cause different end status of the lights ### What version of Home Assistant Core has the issue? core-2022.2.3 ### What was the last working version of Home Assistant Core? never worked ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue Philips Hue ### Link to integration documentation on our website https://www.home-assistant.io/integrations/hue/ ### Diagnostics information Doing this with multiple hue lights (several entitity ID's) at the same time cause different states of the lights, even if they should be synchronized. ### Example YAML snippet ```yaml alias: Test Hue Wohnzimmer description: '' trigger: - platform: state entity_id: light.eg_wohnz_hue_on_off from: 'off' to: 'on' condition: [] action: - service: light.turn_on data: brightness_pct: 100 target: entity_id: light.hue_eg_wohnz_bodenlampe - delay: hours: 0 minutes: 0 seconds: 2 milliseconds: 0 - repeat: count: '10' sequence: - service: light.turn_on data: brightness_step_pct: -10 target: entity_id: light.hue_eg_wohnz_bodenlampe - delay: hours: 0 minutes: 0 seconds: 0 milliseconds: 200 mode: single ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

Dont know if i understand it correct but it seems that sending absolut percentage should be better or am i mistaken? But to do this, the start brightness should be read out first and after that al dimming steps (initial_brightness - step_pct) should be calculated with the initial value.

farmio · March 8, 2023, 9:25pm

You’ll need to test that.
I could imagine that the sent value drifts away from the actual value then. Eg. You start at 100% and dimm down. Each step -5%. If the light doesn’t dimm as fast as you send new values (eg. because it adds system dimm time) when you release the button after 15 steps, but the actual brightness is just 50%, it will still dimm all the way down to 25% - because that was the last received value.

dubtec · May 9, 2023, 3:42pm

Hi, am a fan of this blueprint and use it in a couple of places already. I would like to surpress that the dimming (up or down) powers on or powers off the light. In other words, when the lights are off, a long press of the button should not power on the light from. And, vice versa when the light is already on and dimmed all the way down, it should not power off the light. Which is what happens at the moment and makes the KNX / ZigBee combination behave different than the rest of the lights in my home.

Is there a chance for a flag that ignores dimming when light is otherwise off and when it’s about to be powered off? I hope I made myself clear…

Thanks in advance!

farmio · May 9, 2023, 4:19pm

Hi !
I don’t plan to add any features to this blueprint. Feel free to fork it and add things you need.
Maybe also have a look at one of the more recent forks here: Advanced control of any light entity from KNX (state,brightness,dim,color + states feedback)

kalhimeo · May 12, 2023, 3:38pm

I updated my code with an option to prevent the light to switch off when reaching the minimum dimming level. I am not at home at the moment so I was not able to test it, let me know in the dedicated subject if you face problems.

Phryx · December 29, 2023, 8:27pm

Hi there,

just one, maybe stupid, question:
I want to integrate my existing knx dim lights ( more accurate lights attached to mdt knx dim actuator) in home assitant.
All the lights have been setup using relative dimming.
Can I use this blueprint or better not?

farmio · December 29, 2023, 8:32pm

Any Knx dimming actuator I have seen supports not only relative, but also absolute dimming objects. You should use those.

This blueprint does not send Knx relative dimming commands. It only receives and acts on them.

Phryx · December 30, 2023, 11:20am

Hello farmio,

thank you for your explanation,
I will have a look into my knx programming and will have a Test whether I like the absolut dimming or not. Right now the relative dimming works quite smooth and I like that.
From what I‘ve gathered the knx ultimate for node red should be able to handle relative dimming both for knx and Hue lights.

farmio · December 30, 2023, 11:44am

You can always use both. Relative dimming is for holding push buttons on wall switches. Not for setting specific dim values.

sunstarfire · January 12, 2024, 8:26pm

Hey @farmio , I am using a modified version of your blueprint from another webpage here:

I have mdt switches and am addressing hue lights. Switching on works. Switching off works. Pressing the off button long will set the light to approximately 50%… do you by chance have any idea why this is happening?

Thanks