Light transition ignored by KNX/DALI entity

Configuration
1

I’ve read other similar topics, but found no solution for me. Now i’m trying to “debug” the situation.
My situation…

KNX entity in configuration.yaml:

    - name: 'spots_vz3'
      address: '0/1/20'
      state_address: '0/4/7'
      brightness_address:  '0/3/20'
      brightness_state_address:  '0/5/7'

transition ignoring services:
1

service: light.turn_on
entity_id: light.spots_sz1
data:
  transition: 10
  brightness: 100

2

service: light.turn_on
entity_id: light.spots_sz1
data:
  transition: 20
  brightness_pct: 100

Transition works fine, when starting a scene over the DALI gateway.
No other troubles with the light control - any hints/advices?

Cheers

2

The KNX integration just doesn’t support transition for lights.

3

that’s good to know, thanks a lot! For other KNX users, this should be a workaround:

4

Let’s hope this runs in an executor, otherwise this time.sleep will just kill your Knx connection - amongst other things.

5

I want to understand Your concern better. Is it flooding the Bus with telegrams?

6

No. This is about possibly blocking the main asyncio loop. I have not tested, nor looked further into this - if it runs in an executor, that would be perfectly fine.

7

Thanks a lot!

BTW, for those seeking a more KNX-type of way to achieve this: Dimming actors by MDT (should work similar for e.g. Theben or others) allow to define a scene, which sets a specific absolute dimming value and defines the time to get there. So, here from HA one just needs to activate the scene and the rest is done by the bus / the dimming actuator.

8

There are even a DPTs that allows to define transition times and target xy-color or color_temp per telegram - without manufacturer specific scene logic :wink:
So if anyone is interested: DPT 243.600 and 249.600