Use entity component translations for update entity #18608
Merged
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.
Proposed change
Previously, all the state display logic for
update
entities was done with the state translation function.One of the issue was that
on
state was using the latest version number in the automation editor as state translation.This PR move the display logic into card components (e.g. tile, entity row, state content) so state translation can work in the automation editor.
After the fix, automation editor uses translations and card uses special display.
Needs home-assistant/core#103752
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: