-
Notifications
You must be signed in to change notification settings - Fork 97
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
HA 0.110.2: Extra badge does not show up #187
Comments
extra_badge is long gone, and was designed for HA States, not for Lovelace. for your extra badge, you can have a look at https://github.com/benct/lovelace-multiple-entity-row as for your setup, you should only use this:
or:
and take out all other mentions of state-card in the bits you posted above. I suggest not using customizer though, because it does nothing more than the frontend option now that the other functionality is no longer use, and it causes a warning in the log you are using an unsupported custom integration... |
Oh, I see... Gotcha.. You are using the multiple-entity-row here.. I am aware of that, just wanted something new, like badge, lol. So the documentation for custom-ui is not clear about the badge. Thank you very much for clarifying this. So you mean the only feature of the custom-ui left is colorizing the icons and probably text? Btw, which brand switches are you using here on your screenshot above? |
no, many other things can still be customized using the template functionality custom-ui offers. and yes, if you use the frontend method, you can completely remove customizer. the pull request isn't merged, and probably never will, because the complete repo isn't maintained any longer. Im am hoping we can have a modern custom-ui.js version anytime in the future, since both Bram and Thomas have been helping me using the legacy custom-ui work with ha 110, and I am sure they see the power ;-) My switches are Z-wave switches that are connected to HA via Mqtt. |
which version HA are you using? change some of the syntax below, you had some dangerous 'else' clauses, creating diffuculties when the state would be above 30. Ive added the new 'else' line as 3d line:
not sure tbh, maybe the theme takes precedence over icon_color, you can check that in line 27 (which is enormously long....) fyi, I had just finished this question to the main frontend dev Bram: home-assistant/frontend#6035 (comment) |
great, as we made it work! note you can replace all triple ='s for doubles. == works in all templates. makes it a bit snappier, and, if you have many, like I do, you customizations that much shorter ;-) |
@drew-kun Have you tried another browser? In case of severe caching issue? |
in anyway, dont use both theme, and icon_color. Ive updated the Pull request file, so it reflects the correct version: inspector: so you know its loaded alright ;-)
you should always and everywhere take care for errors or unexpected outcomes. That's what the else is for. A guard. |
Yeah, testing it on Chrome and Android app, which updates pretty good... Also, just updated to 0.110.2 but still the same issue. |
you should post this in the other thread really, as this is about the extra badge, and your question is on activating custom-ui. |
Do you have a link to that? |
|
Ok, guys, sorry. Closing this. Will open the new issue soon. Thank you. |
Checklist
Browser + Version:
Chrome 81.0.4044.138 (Official Build) (64-bit)
CustomUI version:
20190518
Home Assistant release (
hass --version
):0.110.2
Problem-relevant
configuration.yaml
entries:ui-lovelace.yaml
Expecting extra badge here:
Problem-relevant Home Assistant log entries:
Any errors from browser Javascript console:
The text was updated successfully, but these errors were encountered: