Shutters and Scene with KNX

Configuration
,
1

Hi there,

just ried to set up a scene to group and operate the shutters / covers.

If I activate the scene HA sends the following to the KNX bus:

“Langzeitbetrieb (long-term movement)” followed immedialtely by a “Kurzzeitbetrieb (short-time movement)”

The KNX Aktor immediately replys with a movement (Antriebsbewegung) and no movement status.

This happens so quick that there is no movement at the end.

@Farmio: Any idea with this?

2

YAML Code looks like this:

name: Rollo - AB
entities:
cover.rollo_1:
current_position: 0
device_class: shutter
friendly_name: Rollo 1
supported_features: 127
state: closed
icon: mdi:window-shutter
metadata:
cover.rollo_1:
entity_only: true

name: Rollo - AUF
entities:
cover.rollo_1:
current_position: 100
device_class: shutter
friendly_name: Rollo 1
supported_features: 127
state: open
icon: mdi:window-shutter
metadata:
cover.rollo_1:
entity_only: true

3

Just tried to set up a new scene with the cover and having the same effect.

HA always sends two actions. Long movement / Langzeitbetrieb followed by a Stop command.

4

Same problem here.

5

I had the same problem. My config for the covers was:

  - name: "EG AZ Rollo"
    move_long_address: "13/0/0"
    move_short_address: "13/1/0"
    position_address: "13/2/0"
    position_state_address: "13/3/0"

It seemed that when activating a scene, a move_long_address was activated but shortly after that, the move_short_address also.

I changed it now to:

  - name: "EG AZ Rollo"
    move_long_address: "13/0/0"
    stop_address: "13/1/0"
    position_address: "13/2/0"
    position_state_address: "13/3/0"

So the key was to set the stop_address instead of move_short_address. My actor (MDT JAL-0810M.02) uses the same address for short movement and stop.

Everything works as now before.

2 Likes
6

That solved it for me too!
Herzlichen Dank! :wink:

7

Great this is a solutions that solves the issue for the UP / DOWN covers.

Just wondering why it was possible in previous relases to use the move_short_address to operate the covers via a scene. Seams that sth. has been changed in the background.

8

@farmio

Do you have an idea why this happens?

9

No. I never looked into HA scenes.

Have a look at How to help us help you - or How to ask a good question to learn how to format yaml output properly here.
Also, please avoid tagging people for attention.

10

Don’t wanted to be unpolite with tagging you but hought this might be an issue with the KNX integration and with all this topics in the forum you will never see it. Didn’t know this a a “no go”.

Thanks for the hint with the yaml output, updated the code with the right format.

1 Like
11

But what about covers with UP / DOWN / TILT?

- name: "Tuere 1"
    move_long_address: "10/1/0"
    move_short_address: "10/1/1"
    position_address: "10/1/5"
    position_state_address: "10/1/2"
    angle_address: "10/1/6"
    angle_state_address: "10/1/3"
    travelling_time_down: 60
    travelling_time_up: 61

As far as I understand the KNX documentation move-short is used for the tilt function.

12

Hi! I’m having the same issue.

My HA scenes with KNX-controlled covers were working until at least mid-April, something seems to have changed to create this new behavior and, from the symptoms, it does not seem to me to be in the KNX integration.

In relation to this answer above, as per the the KNX integration docs in here, all 3 move_long_address, move_short_address and stop_address should be defined and all have specific functions. Example from the docs:

# Example configuration.yaml entry
knx:
  cover:
    - name: "Kitchen shutter"
      move_long_address: "3/0/0"
      move_short_address: "3/0/1"
      stop_address: "3/0/4"
      position_address: "3/0/3"
      position_state_address: "3/0/2"
      travelling_time_down: 51
      travelling_time_up: 61

In my case, both move_short_address and stop_address have the same group address value (this should be true, I believe, for many KNX cover control devices). Example of one of my current cover definitions:

    - name: "Andar-Quarto Visitas-Blackout"
      move_short_address: "1/0/22"
      move_long_address: "1/1/22"
      stop_address: "1/0/22"
      position_address: "1/3/22"
      position_state_address: "1/2/22"
      travelling_time_down: 23
      travelling_time_up: 24

As I said, my scenes have been working for years with this configuration and, after one of these last updates (I had a few on the pipeline), it stopped working…

It seems to me the 2 calls to the 2 different group addresses is the problem. Moreover, the call should be to the position_address has the scene is defined with a final position and not only fully closed or fully open.

Question: can anyone point me to where should I register and issue with the team managing the updates?

13

There are already two on Github regarding this issue:

1 Like
14

Hi all,
I can confirm that blinds are now working again when the stop_address is used instead of move_short_address.
Interestingly that problem only occurs with scenes. The manual control of the blind was possible without any problems.

I’m using ha 2025.4.3 and ABB blind actors