-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Shutters don't open or close fully #154
Comments
parts of the algorithm to stop the shutters to open/close are related to the data from ONYX about the transition time it calculates. i am adding a small additional delay to it to account for time skews, but in newer versions, a similar problem than you described never occurred. could you provide the following details:
|
Hey, sure, here are the details: LOG: Error doing job: Future exception was never retrieved Please let me know if this is the correct information. I'm not an expert. Thanks, |
hi, thank you for these lines. however, there must be some other logs as well if you have set the HA log level to debug. this is now an example for lights but you should see a lot of debug message similar to #89 (comment). |
Sorry for that.
|
this is an interesting one because your data is missing keyframe: if you check the however, the keyframes are sent by ONYX and should not affect what you trigger. what i am missing though are lines containing to give you a quick high-level overview of the entire process:
if ONYX doesn't send a keyframe in an animation, the background wait is not triggered but also no |
Thanks for your response. Greets |
I'm having the same issue, since about a few weeks or month (can't remember exactly). So i have to finaly open with the Onyx App. With HA i can open it to 70-80 percent, after that every new open or set position command opens the cover another 1-2%. My Setup: Here some lines from my debug log from an open event (set Position, as this seems more reliable in the past). Hope this helps, I'm not sure what happens there.
Does it help? Do you need more Information or Tests? By the way, i really appreciate your work, thank you for this integration, |
i have fixed the error i don't think this is going to be root cause of this issue but it would be great if you could test it again and provide new logs with the new release to filter out this error. |
Thanks. So far issue still there with 10.1.0. I will activate debug and provide logs, maybe tomorrow or on the weekend. |
Hello, thanks for the update. Unfortunately the issue still presists. Here some logs from the latest commands to the shutters via HA:
|
sorry for the silence. i finally found some time to look at your debug logs, and i believe the reason was that you had multiple keyframes in your movement command. i have published could you please try the new version and provide feedback on this issue? |
Thanks a lot, it seems to be fixed or at least nearly. I opened my shutter about 7 times with the new version, only 1 time it was not opened to 100%. I couldn't reproduce it since i activated debug logging. I will provide logs if it happens again. |
thank you for the feedback! if this happens again, please also let me know if this was off by quite some percent or just a few milliseconds until the shutter state had been reached. (see #220 as i am thinking about whether some timing issues could cause an early stop) |
That helped to understand the log entries, thanks. In my case 1 or 2 more seconds would help. See logs from today, it stopped at position 9.
|
btw, the |
Great, for me it is working perfectly now. Thank you very much. |
Hello all, i tested since a couple of days and its working perfectly fine now. Thank you very much! |
awesome, and sorry for the late attention to this bug. i'm going to close it - please re-open it if necessary. |
My automations or even manual control of the shutters via homeassistant don't open or close the shutters fully.
they start to move but they just stop randomly in between and I have to give the command multiple times until they are fully opened or closed. Any ideas?
thank you,
Daniel
The text was updated successfully, but these errors were encountered: