-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overkiz "AwningValance" open/close is reversed #94952
Comments
Hey there @iMicknl, @vlebourl, @tetienne, @nyroDev, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) overkiz documentation |
Hi, this is the expected behavior. Awnings expose deploy (map to open) and undeploy (map to close) commands. So depending of the orientation of your device close and open does not behave as you can expect. I will recommend you to create a cover template so you can reverse the logic. |
@home-assistant close |
Thank you for your quick response and for pointing in the direction of the solution. It took me some time to find and understand how to create a cover template and get the syntax right. On the community forum I also had the suggestion not to reverse open/close, but to invert the position. Although I don't really understand the implications of differences between the two right now I tried them both. With this code I have two working screen entities in my dashboard, next to the original one with the, for me, wrong orientation.
|
The problem
We have “exterior vertical shades/blinds” with Somfy motors (I had to look up the english terms) and two of them, type “AwningValance”, have open and closed reversed in Home Assistant.
Home Assistant found them automatically with the Overkiz integration. In the device information they are
My issue is with the “AwningValance” shades. The control for “Open cover” closes it. However, when I click “Close cover” it opens and in the Logbook it says “… was opened triggered by service cover.close_cover”.
What version of Home Assistant Core has the issue?
core-2023.6.2
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
home-assistant_overkiz_2023-06-21T07-15-25.601Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
The cover is open in this screenshot although the controls let you think it is closed:
I created an Entities Card with position as secondary information. When both covers are open, the PositionalbeScreen shows a position of 100 and it shows correctly as open. The open AwningValance shows incorrectly as closed with a position of 0. See screenshot:
In the Android app “Tahoma” by Somfy these shades work well. Open is open, and closed is closed, with correct positions. This lead me to believe the problem might be in the Home Assistant integration.
This exact question was posted here https://community.home-assistant.io/t/overkiz-api-and-somfy-api/61448/1969?u=mirjam and as replies suggested reported as an issue. Thank you.
The text was updated successfully, but these errors were encountered: