figured it out from playing around with itā¦leaving the solution here in case anyone else is interested and stumbles upon this thread.
basically, i had to tweak both the svg for the gauge as well as the text for the card itself. in order to get the gauge pct text into the middle further, i had to add the overflow: visible property, which then extended the left part of the gauge into the bottom of the cardā¦so to fix that, i added a white background on the card text and expanded it to cover the part of the now visible svg that i didnāt need (to basically cut off the bottom half of the gauge to make it look like it originally did, just smaller).
I found that I had an error in the javascript console saying: TypeError: Cannot read property 'then' of undefined
Searched in the project issues I found that this is fixed in a commit, but the next version ā3.0.13ā has not been released and therefore, people who have installed card-mod through HACS will not be able to use the CSS in the dialogs using the tag ācard-mod-more-info-yamlā.
In the end I added the card-mod.js file with the other installation method.
Once this was fixed, I found a way to hide the āPreload streamā checkbox:
Strange behaviour: On iOS and Windows the .card-header inside the hui-grid-card is respected and applied correctly. But on my Android devices (HA Companion app and browser) itĀ“s not, so my lovelace view looks different depending on the device - which is quite bad
To be more specific: only the text-align: center; is correctly applied, everything else seems like itĀ“s being ignored.
Is there an Android specific thing (bug) or the need to address the .card-header on another way
Hello
I could probably discuss it on general forum, or maybe even on github as issue of mentioned cards. But I can feel I will get more usefull help over here.
Iāve found, Weather card doesnāt play well with grid card set to square. It looks like weather card can force size of grid ignoring square size.
Is there a systematic way how to instruct weather card to not expand grid card? Likely I could change sizes of weather elements or hiding them, but this might (and ussually does) ends with some differences in presention on different devices.
BTW Example below shows a way of achieving colspan in built-in grid card (I hevenāt seen it yet on this forum. Maybe someone will find it useful)
If I embed all other entities into custom:button-card with aspect_ratio: 1 / 1 (which is my goal) then itās even more vissible that grid is being streached out.
Setting aspect_ratio to 2:1 for weather card doesnāt help in 100%. It results in some difference in height, probably because total horizontal size contain padding between cards, so calculated height is few pixels greater than needed (which is issue of button card rather than weather or grid)
Hi, Iām trying to style āmultiple rowsā icon with input select state: How could I make it less verbose?
Condition is made on nth-child. I tried to put the state directly in nth-child({{state}}) but it seems not to work.
Result should be like this:
Hi,
In a picture-element card I am trying to style a state-icon of a fan with card-mod.
I followed these examples but it only works when I apply the css for the whole card and it doesnāt when I do it just for one entity.
What am I doing wrong?
I used to get colors for the icons.
The arrow would be rgba(255, 155, 0)
The numbers in circles would be var(--accent-color) but only if Enabled.
Else the whole line was var(--secondary-text-color)
Iām looking to change the entity icon based on a template state change, but nothing changes. If I can get this working I wanted to add this to one of my swipe cards.
The idea is to have an indication of if the doors are closed then the icon will show one icon and if the doors are open the the icon will change and may place in some text as well displaying which door has opened
Tried this and it didnāt work either. As described above it was working till 20.10.x. Afterwards only with this curious additional $: And on card level, as in your recommendation, I didnāt get this work.
What changed with 2010.x. in the way it is working?
What happens with this additional $: on same level?
How would it work on card level as in your recommendation instead restriction card level?