-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cover issue when adjusting range via Alexa #74
Comments
I’ll have a look at the code for Alexa but what I don’t understand is why it does that ridiculous dance with the delta position. Aren’t you just trying to set it to a specified percentage. Of course the current position is reported but it could be yet another property of the cover entity that is undocumented. |
I understand that the delta position is sent when the command used with Alexa is something like "raise the cover by 10%" or "lower it a little". It would be easier if Amazon did the calculations themselves and just sent the target position, but that would not be the case. |
It looks like the Alexa component does not use the property decorator for the current lift or tilt position. I will have something for you to try shortly. |
Try the release I just released. While I do not use Alexa I traced through the code to find where the position data is coming from and made changes to set that value. |
Hey! |
Hey!
First of all, thanks for creating this awesome integration.
I added covers to Home Assistant without an issue. I can see the entities, open/close them, set them to a position, etc.
What happened is that I added the Alexa integration and exposed the covers to it. The absolute commands, like opening and setting to a position work fine. But the adjustRange command is failing. This is a link to the link that is failing in the home assistant integration code. The log error is:
It appeas to be failing because it cannot determine the current position to adjust it correctly. Is it possible that that value is not being exposed in your integration code? Or could this be a home assistant issue?
Thanks!
The text was updated successfully, but these errors were encountered: