My Position configuration does not match position of recalling My Position

[mvdwetering]

The problem

I am using the Overkiz integration with a Tahoma Switch box.
My Somfy shutter shows a "My Position" configuration entity with a slider. That slider shows 85.
When activating My Position by pressing the button entity (or through the Tahoma App) the position goes to 15 which is the expected position (shutter almost fully closed).

The My Position configuration value seems to be flipped (100 - 85 == 15)

What version of Home Assistant Core has the issue?

core-2022.2.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz/

Diagnostics information

config_entry-overkiz-2910f402e809161e4e71c45ac5509c66.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

My Position configuration as shown in UI

Position of shutter after activating My Position

[probot-home-assistant]

Hey there @iMicknl, @vlebourl, @tetienne, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

---

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

[tetienne]

Hi, I was able to reproduce with own covers too. Didn't know why I didn't notice this behavior before.

For the awning, the feature is correct. Only vertical covers are impacted.

[mvdwetering]

FYI I just discovered the "Target Closure" sensor which seems to have the same issue. I could not find documentation on this sensor, but I assume that on changing the postion (or activating the My button) it shows the position where the shutter will eventually end.

When setting the position to 15%, the Target Closure sensor shows 85% instead of 15%, so also seems to be "flipped".

[tetienne]

About the TargetClosure if your device is stateful your are not suppose to use it. It's why we disabled it by default. This state is useful for RTS cover. Indeed, the value of this state is equal to the last position asked by the user. We directly expose the value returned.

[mvdwetering]

Ah, my covers are using IO so they are stateful.
However I am using the TargetClosure to check if the shutter got to the target position within 1 minute. If not I send a notification that the cover did not close/move properly and I need to check it (I could have left a window open which is blocking it)

[tetienne]

About this use case, I can backport a still missing part of the custom component.
We raise an event when the cover is stuck. You can normally see it by yourself with the official application. Move your cover using an app (not from a physical switch) and block your cover with something. You will see a warning. That's what we catch.

[mvdwetering]

It would be great to have the same errors as in the Tahoma app directly in HA.

However I worked my way around it for now so no hurry from my side as I see that the to-port-to-HA list is still quite long and this topic seems to be near the bottom (assuming it is this one " Raise Overkiz events in DataUpdateCoordinator (on failure etc.)")

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[tetienne]

Still valid

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[tetienne]

Still valid

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[tetienne]

Still valid

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[iMicknl]

Still valid.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mvdwetering]

Still the case on HA 2023.7.2

[mvdwetering]

Still the case on Home Assistant 2023.10.2

[QinX]

For what it's worth, this is still valid and I'm experiencing this "issue" as well.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mvdwetering]

Still the case on Home Assistant 2024.2.3

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mvdwetering]

Still exists in HA 2024.5.5

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mvdwetering]

Still in 2024.8.3

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mvdwetering]

Still in 2024.11.3