Reverse KNX Cover (awning) mixes states and works incorrect

[pos-ei-don]

The problem

When i configure a Device like this

- name: "Markise"
  move_long_address: "5/4/205"
  stop_address: "5/4/206"
  position_address: "5/4/207"
  position_state_address: "5/4/208"
  travelling_time_down: 46
  travelling_time_up: 46
  device_class: blind    #https://www.home-assistant.io/integrations/cover/#device-class
  #entity_category:
  invert_updown: true

there is an error! When the Cover is "open", so it is not providing a shadow, I see it like this in the UI. When i want to close it, i need to first push the "down" button, only to get the "up" button clickable. So i have to push two buttons to get it closed.

It it the same when i change the configuration to device_class: awning

I have tho puth the right button before i can puth the left one.

What version of Home Assistant Core has the issue?

v24.7.3

What was the last working version of Home Assistant Core?

-

What type of installation are you running?

Home Assistant OS

Integration causing the issue

knx

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

- name: "Markise"
      move_long_address: "5/4/205"
      stop_address: "5/4/206"
      position_address: "5/4/207"
      position_state_address: "5/4/208"
      travelling_time_down: 46
      travelling_time_up: 46
      device_class: blind    #https://www.home-assistant.io/integrations/cover/#device-class
      #entity_category:
      invert_updown: true

Anything in the logs that might be useful for us?

No response

Additional information

Hey there @Julius2342, @farmio, @marvin-w, mind taking a look at this issue as it has been labeled with an integration (knx) you are listed as a code owner for? Thanks!

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (cover) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `cover` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign cover` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

cover documentation cover source _{^{(message by IssueLinks)}}

[farmio]

Hi 👋! device_class doesn't change any entity behaviour - it is just a hint for UI. It seems to send the wrong command to the move_long_address. Why don't you try to remove invert_updown: true?

[home-assistant[bot]]

Hey there @julius2342, @marvin-w, mind taking a look at this issue as it has been labeled with an integration (knx) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `knx` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign knx` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

knx documentation knx source _{^{(message by IssueLinks)}}

[pos-ei-don]

Hi 👋! device_class doesn't change any entity behaviour - it is just a hint for UI. It seems to send the wrong command to the move_long_address. Why don't you try to remove invert_updown: true?

Because "closed" is the wrong state, when it is truly "open". My Wife has no chance to know, which state is correct. And in Automations there is the easy chance to set thw wrong command aswell....

[farmio]

invert_position: true then maybe. It somehow gets the state / position wrong. I can't know how your actuator is configured - you'll have to provide some details or try a bunch of config options yourself 🤷

[pos-ei-don]

The actuator from my example is an older gira. it has only 6 GAs. ( but i have the same issue with other and newer devices. i have to use cover in HA-knx for valves as knx currently does not support the valve class)

Long, Short, position-set, position-get (state), currently moving and lock.

position-get (state)=0 (dpt5.001) when it is open (no shade) and 100% when it is closed (providing shade).

This all is reported correctly in HA, but when the awning is open, th button to close it is disabled. the same happens when it is closed and i want to open it with the opening button. i always have to puth the opposit button to be able to push the correct button

[farmio]

A standard Knx cover should move DOWN (close, towards 100% Knx / 0% HA) when the move_long address receives a 1. Does it behave that way?

when the awning is open, th button to close it is disabled.

In the screenshots above the state is "open" and the "close" button is not disabled. The one right to "stop" is close. Clicking this should emit a 1 to the move_long_address (unless you have invert_updown: true set - which of course inverts this.

Does the position slider in HA work correctly? As in, if you slide it to 0, it should close (Knx 100%).

[pos-ei-don]

Thank you for your response.

I can confirm this! As you see, sending 0 to the actor starts "moving" and responds with 0% state

But, maybe i misunderstood invert_updown: true. Does this only send 0 instead of 1 to "long"? T thought, this also changes 100% to 0% and vice versa, but reading the documentation again let me think that this is invert_position for. I had problems with this aswell, but i will retest this setting.

[pos-ei-don]

Ok, closing it.