[FR] weather state is now exposed raw and untranslated #2910
Conversation
This file contains 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
As it goes for every exposed entity of any domain from now on. This concludes uncertainty about the content of "state.state", and will have the nice side effect of putting the development environment on par with the production behaviour. Fixes home-assistant#2899
bors-ltd
commented
Jan 24, 2025
| 'windy': 'Venteux', | ||
| 'windy-variant': 'Venteux et nuageux', | ||
| } %} | ||
| {{ weather_condition.get(state.state | string, "") }} |
There was a problem hiding this comment.
I assumed the future behaviour already, so I don't "lower" like most weather intents do today.
Edit: But I kept their behaviour of having no fallback when the value is unknown/unavailable.
|
FYI, I've got two experimental features in a core branch to help reduce the clutter of that template:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As it goes for every exposed entity of any domain from now on.
This concludes uncertainty about the content of "state.state", and will have the nice side effect of putting the development environment on par with the production behaviour.
Fixes #2899