-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update computeStateDisplay to support new translation_key #293
Conversation
@benct, can you please review this PR ? |
@mill1000 Is it possible to support translated attribute values as well? |
Yes it's possible but likely best for a separate PR. It would need to implement something like computeAttributeValueDisplay |
While waiting for an official update, I have tried to replace my local "multiple-entity-row.js" file with the one from this pull request. I've chosen "Reload Resources" from the menu, and cleared cache. Doesn't seem to change how things are displayed. Still says "off" and "on" instead of "Closed" and "Open". Is there something I'm missing to make this work? |
What if you gzip |
Interesting, I was wondering what was up with the .gz file. That worked! Makes sense now. Thank you! |
Any update on this? I’m unfamiliar with how long the role was takes for pull requests to become published updates but eager to have this fixed so that I can once again upgrade HA. |
Unfortunately it seems there is no activity from @benct on GitHub since Dec 22. |
Does anyone know how to take these files and use them? I saw the gzip comment @mill1000 and @iankaufmann made and confused by it. Not familiar with how to do that. Using Home Assistant IN Docker environment. |
@GRClark, replace/overwrite the .js file and delete the gzip from the directory - once you refresh your browser/cache, the updated values should show. for the mobile app, open the settings and select the reload frontend cache option. |
Those looking for an easier solution can add my fork (mill1000/lovelace-multiple-entity-row) as a custom repository under HACS. |
@benct Thanks Ben! |
Released in version 4.5.0. I'm not myself on HA 2023.4 or later yet, so please let me know if it works as expected. |
updated, works as expected on Home Assistant 2023.5.3, Frontend 20230503.3 - latest |
Close #292, #290, and maybe #289