-
Notifications
You must be signed in to change notification settings - Fork 168
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
--card-mod-icon stopped working in Entities card #176
Comments
I found that the With the default theme or any custom theme w/o card-mod-theme it works stable. Reopened the issue (( Update 13.02.22: Update 06.04.22: |
I'm seeing similar behaviors when using custom icons with card mod. This happens when using Simple Icons, FontAwesome, etc. I am using the default dark theme and have an entities card:
When using custom icons, the card loads, the icon shows for a split second, and then disappears. Only after toggling the switch does the icon show properly for its respective states. When using Material Design Icons, however, there is no such issue:
I've also never got |
After upgrade to 3.1.5: |
My Home Assistant version: 2022.2.0
My lovelace configuration method (GUI or yaml): yaml, storage
What I am doing:
Trying to change an icon using a
--card-mod-icon
variable.What I expected to happen:
The icon is changed.
What happened instead:
The icon is NOT changed.
Minimal steps to reproduce:
Error messages from the browser console:
none
By putting an X in the boxes ([]) below, I indicate that I:
Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
Have made sure I am using the latest version of the plugin.
Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
The text was updated successfully, but these errors were encountered: