Scene with knx covers not working properly

swenz · April 9, 2022, 12:11pm

Hi,

my scene

- id: "1649500199377"
  name: Büro Arbeiten
  entities:
    cover.buro_garage:
      current_position: 0
      current_tilt_position: 0
      device_class: blind
      friendly_name: Büro Garage
      supported_features: 255
      state: closed
    cover.buro_terrasse:
      current_position: 0
      current_tilt_position: 50
      device_class: blind
      friendly_name: Büro Terrasse
      supported_features: 255
      state: closed
    cover.buro_strasse:
      current_position: 0
      current_tilt_position: 0
      device_class: blind
      friendly_name: Büro Strasse
      supported_features: 255
      state: closed
  icon: mdi:chair-rolling

works only partially.
first time it seems to be ok. but if the covers tilt is changed afterwards, it needs several scene activations to move the covers in the right tilt state.
any ideas?

best regards,
Samuel

farmio · April 9, 2022, 1:23pm

Is the cover tilt recognized by HA when it was changed afterwards? Are telegrams sent? How are the covers configured?

swenz · April 9, 2022, 1:56pm

It seems it changes stepwise only one tilt step each klick
2nd click

3rd click

swenz · April 9, 2022, 1:57pm

  - name: "Büro Strasse"
    move_long_address: "8/0/7"
    move_short_address: "8/1/7"
    stop_address: "8/1/7"
    position_address: "8/2/7"
    position_state_address: "8/3/7"
    angle_address: "8/4/7"
    angle_state_address: "8/5/7"
    travelling_time_down: 60
    travelling_time_up: 60

  - name: "Büro Garage"
    move_long_address: "8/0/6"
    move_short_address: "8/1/6"
    stop_address: "8/1/6"
    position_address: "8/2/6"
    position_state_address: "8/3/6"
    angle_address: "8/4/6"
    angle_state_address: "8/5/6"
    travelling_time_down: 60
    travelling_time_up: 60

  - name: "Büro Terrasse"
    move_long_address: "8/0/5"
    move_short_address: "8/1/5"
    stop_address: "8/1/5"
    position_address: "8/2/5"
    position_state_address: "8/3/5"
    angle_address: "8/4/5"
    angle_state_address: "8/5/5"
    travelling_time_down: 60
    travelling_time_up: 60

swenz · April 9, 2022, 1:59pm

swenz · April 9, 2022, 2:01pm

this script works perfect and every time.
I dont understand why scene is not working properly

office_arbeiten:
  alias: Office Arbeiten
  sequence:
  - service: cover.set_cover_position
    data:
      position: 0
    target:
      entity_id:
      - cover.buro_terrasse
      - cover.buro_strasse
      - cover.buro_garage
  - service: cover.set_cover_tilt_position
    data:
      tilt_position: 50
    target:
      entity_id: cover.buro_terrasse
  - service: cover.set_cover_tilt_position
    data:
      tilt_position: 0
    target:
      entity_id:
      - cover.buro_strasse
      - cover.buro_garage
  mode: single

farmio · April 9, 2022, 2:41pm

Sorry, but these screenshots are like looking through a keyhole.

Maybe create a scene using only one cover to make it better readable and describe in detail what the initial position is, what telegrams were sent (from HA) and received after you activated the scene in a continuous log.

You can also get logs from the knx integration - see troubleshooting
xknx.telegram together with fired events from homeassistant.core logger would be quite informative. These look like this:

[homeassistant.core] Bus:Handling <Event call_service[L]: domain=cover, service=close_cover, service_data=entity_id=cover.bad_fensterladen>`
[xknx.telegram] <Telegram direction="Outgoing" source_address="1.0.241" destination_address="7/4/1" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />

swenz · April 9, 2022, 3:24pm

hm, thanx for your remarks.

 <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" Reserve="0" TotalLength="22" />
 body="<TunnellingRequest communication_channel_id="30" sequence_counter="227" cemi="<CEMIFrame SourceAddress="IndividualAddress("1.2.11")" DestinationAddress="GroupAddress("8/5/6")" Flags="1011110011010000" code="L_DATA_IND" payload="<GroupValueWrite value="<DPTArray value="[0x9f]" />" />" />" />" />
2022-04-09 17:03:59 DEBUG (MainThread) [xknx.knx] Sending to 192.168.178.20:3671 at 1649516639.5868418:
 <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" Reserve="0" TotalLength="10" />
 body="<TunnellingAck communication_channel_id="30" sequence_counter="227" status_code="ErrorCode.E_NO_ERROR" />" />
2022-04-09 17:03:59 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Incoming" source_address="1.2.11" destination_address="8/5/6" payload="<GroupValueWrite value="<DPTArray value="[0x9f]" />" />" />
2022-04-09 17:04:03 DEBUG (MainThread) [xknx.raw_socket] Received from ('192.168.178.20', 3671): 061004200019041ee4002900bce01135050505008043fa0000

swenz · April 9, 2022, 3:27pm

I only see incoming messages for this group address. It is strange

farmio · April 9, 2022, 4:03pm

🤷 sorry, I really can’t help you with the information you are providing. Would need very much more logs to get a glimpse of what is happening - called services, incoming and outgoing telegrams - possibly without missing lines in between.

paf · May 19, 2023, 9:49pm

I just faced this same issue. It looks the sent messages on the knx bus are fine, but they would need to be sent as a sequence to have the wanted effect.

alas currently it sends them all at the same time more or less, so that the “close” datagram barely gets the motors to start until the “adjust the blinds” datagram comes and tells it to just change the angle.

I just removed the blinds angle from the automation (editing the yaml directly) and it works.

that also explains why swenz’s script works, as it is written as a sequence. Not sure if such a script can be bound to a scene though (I’d like to combine it with lights and multimedia too).

farmio · May 20, 2023, 4:12am

Hi !
Which blind actuator are you using?

If you like to set the blinds to a fixed position, you could look into plain knx scenes and trigger that from your HA scene.

stephanschuster · May 23, 2023, 10:21pm

Hi. I am facing very similar issues when trying to fully close my KNX shutters (in german: “Jalousie außen am Fenster”) within a HA scene. When activating the HA scene, the shutter only seems to tilt a single step. Like @paf mentioned, this is probably due to the fact that the “close” datagram is immediately followed by the “tilt” datagram. In contrast to @paf, I do not see any difference when removing current_tilt_position line from the scenes.yaml. Please find below my reduced test setup.

Here is my KNX shutter config:

  cover:
    - name: "Arbeitszimmer Nordseite"
      move_short_address: "2/0/80"
      move_long_address: "2/0/81"
      position_address: "2/0/82"
      position_state_address: "2/0/83"
      angle_address: "2/0/84"
      angle_state_address: "2/0/85"
      travelling_time_up: 25
      travelling_time_down: 25
      device_class: "shutter"

Creating a HA scene to fully close above shutter via UI (settings > scenes > new) results in the following scenes.yaml:

- id: '1684872983297'
  name: Test
  entities:
    cover.arbeitszimmer_nordseite:
      current_position: 0
      current_tilt_position: 0
      device_class: shutter
      friendly_name: Arbeitszimmer Nordseite
      supported_features: 255
      state: closed
  metadata:
    cover.arbeitszimmer_nordseite:
      entity_only: true
  icon: mdi:test-tube

When activating this scene via UI (settings > scenes > click … menu behind “Test”) these are the KNX logs:

2023-05-23 22:36:21.132 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/81" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-05-23 22:36:21.132 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/81")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:36:21.134 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="24" cemi="1100bce011391051010081" />" />
2023-05-23 22:36:21.137 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04011800
2023-05-23 22:36:21.137 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="24" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:36:21.138 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100420001504016f002e00bce011391051010081
2023-05-23 22:36:21.138 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="111" cemi="2e00bce011391051010081" />" />
2023-05-23 22:36:21.138 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="111" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:36:21.150 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/81")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:36:21.198 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/80" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-05-23 22:36:21.199 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:36:21.200 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="25" cemi="1100bce011391050010081" />" />
2023-05-23 22:36:21.203 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04011900
2023-05-23 22:36:21.203 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="25" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:36:21.205 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 061004200015040170002e00bce011391050010081
2023-05-23 22:36:21.205 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="112" cemi="2e00bce011391050010081" />" />
2023-05-23 22:36:21.206 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="112" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:36:21.206 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:36:21.469 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 061004200016040171002900bcd0110310550200800b
2023-05-23 22:36:21.469 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="22" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="113" cemi="2900bcd0110310550200800b" />" />
2023-05-23 22:36:21.469 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="113" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:36:21.471 DEBUG (MainThread) [xknx.cemi] Incoming CEMI: <CEMIFrame code="L_DATA_IND" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.3")" dst_addr="GroupAddress("2/0/85")" flags="1011110011010000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xb]" />" />")" />
2023-05-23 22:36:21.472 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Incoming" source_address="1.1.3" destination_address="2/0/85" payload="<GroupValueWrite value="<DPTArray value="[0xb]" />" />" />

When I manually remove current_tilt_position: 0 in scences.yaml and save, I get the exact same result:

2023-05-23 22:45:09.463 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/81" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-05-23 22:45:09.464 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/81")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:45:09.468 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="29" cemi="1100bce011391051010081" />" />
2023-05-23 22:45:09.470 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04011d00
2023-05-23 22:45:09.470 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="29" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:45:09.470 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 061004200015040177002e00bce011391051010081
2023-05-23 22:45:09.470 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="119" cemi="2e00bce011391051010081" />" />
2023-05-23 22:45:09.471 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="119" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:45:09.476 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/81")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:45:09.522 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/80" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-05-23 22:45:09.523 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:45:09.525 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="30" cemi="1100bce011391050010081" />" />
2023-05-23 22:45:09.527 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04011e00
2023-05-23 22:45:09.527 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="30" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:45:09.528 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 061004200015040178002e00bce011391050010081
2023-05-23 22:45:09.528 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="120" cemi="2e00bce011391050010081" />" />
2023-05-23 22:45:09.528 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="120" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:45:09.532 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-23 22:45:09.800 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 061004200016040179002900bcd0110310550200801e
2023-05-23 22:45:09.800 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="22" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="121" cemi="2900bcd0110310550200801e" />" />
2023-05-23 22:45:09.801 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="121" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-23 22:45:09.802 DEBUG (MainThread) [xknx.cemi] Incoming CEMI: <CEMIFrame code="L_DATA_IND" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.3")" dst_addr="GroupAddress("2/0/85")" flags="1011110011010000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0x1e]" />" />")" />
2023-05-23 22:45:09.803 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Incoming" source_address="1.1.3" destination_address="2/0/85" payload="<GroupValueWrite value="<DPTArray value="[0x1e]" />" />" />

It was about 2 years ago when I configured all my KNX devices for HA. So far everything worked as expected in HA. This is the first time I use HA scenes.

I wonder if the group addresses used by the HA scene - first 2/0/81 (move_long_address = move to end) and second 2/0/80 (move_short_address = tilt one step) are correct?

I also wonder if device_class: shutter is correct for “Jalousien”. Should it be device_class: blind? The docs about “device class” are not clear to me. Does it make a difference at all, for scenes and in general? In fact, all my “Jalousien” are configured exactly like “Arbeitszimmer”. And even all my “Rollladen” are configured with device_class: shutter like below. Is this a problem?

    - name: "Schlafzimmer Südseite"
      move_short_address: "2/1/88"
      move_long_address: "2/1/89"
      position_address: "2/1/90"
      position_state_address: "2/1/91"
      travelling_time_up: 19
      travelling_time_down: 18
      device_class: "shutter"

Last but not least, I noticed another strange behavior: Whenever I enter or exit the settings > scenes > “Test” UI, my shutter is tilting one step. Basically as if I activated the scene which I did not do.

This is the log when entering the “Test” scene UI:

2023-05-24 00:03:45.985 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/81" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-05-24 00:03:45.985 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/81")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-24 00:03:45.990 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="100" cemi="1100bce011391051010081" />" />
2023-05-24 00:03:45.993 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04016400
2023-05-24 00:03:45.993 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="100" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:03:45.994 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100420001504014a002e00bce011391051010081
2023-05-24 00:03:45.994 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="74" cemi="2e00bce011391051010081" />" />
2023-05-24 00:03:45.994 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="74" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:03:46.012 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/81")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-24 00:03:46.060 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/80" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-05-24 00:03:46.060 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-24 00:03:46.063 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="101" cemi="1100bce011391050010081" />" />
2023-05-24 00:03:46.066 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04016500
2023-05-24 00:03:46.066 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="101" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:03:46.067 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100420001504014b002e00bce011391050010081
2023-05-24 00:03:46.067 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="75" cemi="2e00bce011391050010081" />" />
2023-05-24 00:03:46.067 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="75" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:03:46.081 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />")" />
2023-05-24 00:03:46.347 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100420001604014c002900bcd0110310550200800d
2023-05-24 00:03:46.348 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="22" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="76" cemi="2900bcd0110310550200800d" />" />
2023-05-24 00:03:46.348 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="76" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:03:46.350 DEBUG (MainThread) [xknx.cemi] Incoming CEMI: <CEMIFrame code="L_DATA_IND" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.3")" dst_addr="GroupAddress("2/0/85")" flags="1011110011010000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xd]" />" />")" />
2023-05-24 00:03:46.351 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Incoming" source_address="1.1.3" destination_address="2/0/85" payload="<GroupValueWrite value="<DPTArray value="[0xd]" />" />" />

This is the log when exiting the “Test” scene UI:

2023-05-24 00:04:28.967 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.57" destination_address="2/0/80" payload="<GroupValueWrite value="<DPTBinary value="0" />" />" />
2023-05-24 00:04:28.968 DEBUG (MainThread) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="0" />" />")" />
2023-05-24 00:04:28.970 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="102" cemi="1100bce011391050010080" />" />
2023-05-24 00:04:28.975 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100421000a04016600
2023-05-24 00:04:28.975 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="102" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:04:28.975 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100420001504014d002e00bce011391050010080
2023-05-24 00:04:28.975 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="77" cemi="2e00bce011391050010080" />" />
2023-05-24 00:04:28.976 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="77" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:04:28.978 DEBUG (MainThread) [xknx.cemi] Incoming CEMI confirmation: <CEMIFrame code="L_DATA_CON" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.57")" dst_addr="GroupAddress("2/0/80")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="0" />" />")" />
2023-05-24 00:04:29.314 DEBUG (KNX Interface) [xknx.raw_socket] Received from ('192.168.178.8', 3671): 06100420001604014e002900bcd01103105502008000
2023-05-24 00:04:29.314 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" TotalLength="22" /> body="<TunnellingRequest communication_channel_id="1" sequence_counter="78" cemi="2900bcd01103105502008000" />" />
2023-05-24 00:04:29.314 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.178.8:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" TotalLength="10" /> body="<TunnellingAck communication_channel_id="1" sequence_counter="78" status_code="ErrorCode.E_NO_ERROR" />" />
2023-05-24 00:04:29.319 DEBUG (MainThread) [xknx.cemi] Incoming CEMI: <CEMIFrame code="L_DATA_IND" info="CEMIInfo("")" data="CEMILData(src_addr="IndividualAddress("1.1.3")" dst_addr="GroupAddress("2/0/85")" flags="1011110011010000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0x0]" />" />")" />
2023-05-24 00:04:29.324 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Incoming" source_address="1.1.3" destination_address="2/0/85" payload="<GroupValueWrite value="<DPTArray value="[0x0]" />" />" />

Calling a script from a scene as mentioned by @paf is not possible (different concept). Using a KNX scene triggered from a HA scene as mentioned by @farmio might be an option but seems double effort to me.

I still hope to get the HA scenes via UI working with all my “Jalousien” and “Rolladen”. Any help would be appreciated.

Thanks.