Fix arbitrary value of target position and more #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lbossle
changed the title
lbossle
changed the title
|
I'm facing the same issue. |
jeremiehuchet
added a commit
to jeremiehuchet/home-assistant-custom-components-cover-time-based-synced
that referenced
this pull request
Aug 21, 2025
Fix arbitrary value of target position and more kotborealis#5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #3 and #4.
Furthermore during my testing I found another problem which should know be fixed:
Example: The cover is at 100% and the button to go up is still active (because someone forgot). If you now set a target position via HA the cover goes down to 0% because the state change of the buttons overwrites the target position. I added a helper variable to prevent this.