Huh. I didn’t know the lovelace editor did that… neat I guess, but I should fix the plugin so that it doesn’t.
Expect an update soon.
Don’t worry, however. As long as head: is a group, whatever is in items: is actually ignored. It will always take what’s currently in the group. In fact, it will probably update the configuration too.
I just got a notice to update to 6ce5d0 so must have been a glitch yesterday…
@thomasloven i’m following your cards for a while. just wanted to say: awesome work you’re doing here. thanks a lot!
Thanks for checking into this. I will post when I get something figured out. Thanks!!
Hi @VDRainer
I’m trying to get something similar to your first Cover Test1, but I am not able to do it.
I don’t see where you define to use the custom:slider-entity-row in the first part.
This is my config
- type: entities
show_header_toggle: false
title: Tende e tapparelle
entities:
- entity: cover.tenda_sala
name: Tenda sala
icon: mdi:blinds
and this is what I get now
What should I have to do to get your first example?
Thanks
You have to use the cover entity twice, one for the buttons, one for the slider
- type: entities
show_header_toggle: false
title: Tende e tapparelle
entities:
- entity: cover.tenda_sala
name: Tenda sala
icon: mdi:blinds
- type: custom:slider-entity-row
entity: cover.tenda_sala
full_row: true
I’m getting this message on starting or reloading Firefox. (Latest on Ubuntu)
After that everything seems to work.
I’ll assume you have read the message and installed card-tools.
If so, this is an unfortunate side-effect of how resources are loaded.
The best advice I can give is to make sure card-tools is first in your list of resources and any plugins that use it are at the very end of the list.
I’m thinking hard of ways to fix it.
I just tried that to fix the custom dark-sky card… no joy unfortunately
EDIT: at first it didnt… then after further Ctrl+F5 I got rid of that error and got another one…
Sorry to cross-thread but I figured I would reply to the card-tools issue
Hi,
after upgrade to HA 0.85.1 and upgrade all useful modul (card-modder, fold-entity-row, etc.), I have problem with card-modder on gauge card.
My ui-lovelace config:
- type: horizontal-stack
cards:
- type: custom:card-modder
card:
type: gauge
name: Download
unit: 'Mb/s'
entity: sensor.speedtest_download
max: 100
severity:
red: 0
yellow: 15
green: 25
style:
background-image: url("/local/images/cardbackH.png")
background-repeat: no-repeat
background-color: rgba(50,50,50,0.3)
background-size: 100% 100%
border: solid 1px rgba(100,100,100,0.3)
color: "#dadada"
box-shadow: 2px 2px rgba(0,0,0,0.6)
font-family: Oswald
- type: custom:card-modder
card:
type: gauge
name: Upload
unit: 'Mb/s'
entity: sensor.speedtest_upload
max: 100
severity:
red: 0
yellow: 10
green: 20
style:
background-image: url("/local/images/cardbackH.png")
background-repeat: no-repeat
background-color: rgba(50,50,50,0.3)
background-size: 100% 100%
border: solid 1px rgba(100,100,100,0.3)
color: "#dadada"
box-shadow: 2px 2px rgba(0,0,0,0.6)
font-family: Oswald
- type: custom:card-modder
card:
type: gauge
name: Ping
unit: 'ms'
entity: sensor.speedtest_ping
max: 100
severity:
green: 15
yellow: 25
red: 40
style:
background-image: url("/local/images/cardbackH.png")
background-repeat: no-repeat
background-color: rgba(50,50,50,0.3)
background-size: 100% 100%
border: solid 1px rgba(100,100,100,0.3)
color: "#dadada"
box-shadow: 2px 2px rgba(0,0,0,0.6)
font-family: Oswald
- type: horizontal-stack
cards:
- type: gauge
name: Download
unit: 'Mb/s'
entity: sensor.speedtest_download
max: 100
severity:
red: 0
yellow: 15
green: 25
- type: gauge
name: Upload
unit: 'Mb/s'
entity: sensor.speedtest_upload
max: 100
severity:
red: 0
yellow: 10
green: 20
- type: gauge
name: Ping
unit: 'ms'
entity: sensor.speedtest_ping
max: 100
severity:
green: 15
yellow: 25
red: 40
Before upgrade was everythinks ok.
Log is clear.
Browser cache and history I cleared.
Many thanks for all answers and ideas.
This is a know problem with some cards right now. Might affect light and thermostat as well.
Me and the frontend dev team are working on it!
Oh, ok thanks for your answer, I’ll follow the changes.
I’m trying to use the trick with the custom:hui-xxx-card in an entities card.
Seems like it’s the only way to show/hide gauges conditional and it works.
- type: conditional
conditions:
- entity: binary_sensor.e3dc_battery_power_pos
state: 'on'
card:
type: entities
entities:
- type: custom:hui-horizontal-stack-card
cards:
- type: gauge
entity: sensor.e3dc_battery_power
- type: gauge
entity: sensor.e3dc_net_power
- type: conditional
conditions:
- entity: binary_sensor.e3dc_battery_power_pos
state: 'off'
card:
type: entities
entities:
- type: custom:hui-horizontal-stack-card
cards:
- type: gauge
entity: sensor.e3dc_battery_power_pos
- type: gauge
entity: sensor.e3dc_net_power_pos
The only problem is the ‘dark’ background behind the gauges.
I assume it’s the entities card?
Any hints to avoid this?
Thanx!
You could try making the two guage cards both in their own card-modder card and style the box-shadow: none and border: none. See if that works. I had a lot of headachs with guage cards and horizontal stacks that I just gave up and went with something else.
Also, just an FYI, the custom:vertical-stack-in-card is a handy card as it removes a lot of the space around the inside cards.
Just noticed I have this ugly red thing showing it’s face. 
Seems to be a problem when using slider-entity-row inside fold-entity-row. This only just started happening in the last day.
If I change the 2 slider-entity-rows to just normal - entity: light.dining_front it all springs back to life.
Has something changed @thomasloven?? Maybe I applied a card update and didn’t notice.
I think I noticed that fold entity row updated today or yesterday. might wanna check for updates. don’t use slider so I can’t speak to that
Got the exact same thing after updating fold-entity-row, so you have probably updated as well.
Should be fixed now. Thanks!
The gauge card is a bit of an odd one… It’ll probably see an overhaul in the near future.
@Skeletorjus glad it wasn’t just me.
@thomasloven what was wrong? Is this why I was seeing the red box of horrer?