Fix visualization by inverting open/closed state of patio awnings #128079
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.
Breaking change
The open/closed state of awnings will be inverted, so that the UI visualization and positioning matches reality. This means open (100%) now refers to the awning being completely retracted and closed (0%) now means the awning is fully expanded. This is not in line with industry terminology, but HA does not yet natively support awnings of type patio.
Proposed change
Until the referenced architectural discussion is solved and support for new types of covers has been implemented natively, invert the reported state of patio awnings to match the expections of the UI visualizations based on the cover platform and solve representation of virtical awnings until those can be handled more differentiated.
Details including screenshots without this change: home-assistant/architecture#979 (reply in thread)
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
.To help with the load of incoming pull requests: