[NL] Fix HassGetWeather #2901
Merged
[NL] Fix HassGetWeather #2901
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
frenck
approved these changes
Jan 22, 2025
|
@andreasbrett so, if I understand correctly, I should revert this change? |
|
Yes, the linked PR will bring us untranslated states finally. |
frenck
pushed a commit
that referenced
this pull request
Jan 27, 2025
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.
After getting some reports that HassGetWeather didn't return the current state, I did some testing on my local instance.
Apparantly
state.statealready returns the translated weather state for the weather entity, so the template using the mapping didn't return anything (as it expects the original untranslated entity state).This way it will return a weather condition, and not only the temperature.