You missed the point.
It just a string - so you write whatever language you want there.
1 Like
yes, we can use
card-mod-view: &cam_background
|
horizontal-layout {
{% if is_state('input_boolean.weer_view_background','on') %}
background: repeat url({{state_attr('camera.buienradar','entity_picture')}});
{% endif %}
}
card-mod-subview: *cam_background
and ofc I have been (unsuccessfully thusfar) trying to find some syntax using that on the new view type.
Thomas, if you read this, got a hint for us? or at least an answer to whether this should be doable?
hope to reach either a theme-mod like
card-mod-view: |
hui-sections-view .title { #findthe$correct$Domwalk .here
color: red;
}
or a mod on the individual sections directly smthg like:
- type: grid
title: Eetkamer
card_mod:
style: |
.title { #findthe$correct$Domwalk .here > too
color: red;
}
did I ?
use-case:
Admin creates a Dashboard for a multi-lingual user-base.
Every User has his native language set in his profile.
The Dashboards includes several entities and templates, everything will be translated based on the user-setting.
Except the static text → section titles…
a possible solution could be - for example - a customized translation file.
Then, you would still need to maintain this file, but you could then use the translation file to create a dashboard, which is completely translated to the specific user-profile.
And yes, I would have a multi-language use case - where I could use such a translated section title… 
or is there any other solution / workaround for such a case?
1 Like
this would be just like any other card everywhere in HA.
dont use a title (should be a new option for that), and use a custom card (button-card stands out) and give that a template to display atop of the section.
use those allover, and, given they use javascript can be very useful in showing browser related details.
browser_mod might come in handy as that provides several useful templating options in Jinja, so maybe use a small markdown card in that case
here’s a grid as example using button-card templates:
btw, in next release we can have unnamed sections:
and (in yaml) include those buttons easy-peasy
- title: Sections
type: sections
icon: mdi:vector-intersection
sections:
- type: grid
cards:
- !include /config/dashboard/buttons/buttons_verlichting_binnen.yaml
- type: grid
title: Samenvatting
cards:
- !include /config/dashboard/buttons/buttons_huis_samenvatting.yaml
- type: grid
title: Oogopslag
cards:
- !include /config/dashboard/buttons/buttons_huis_oogopslag.yaml
can also do
- type: grid
title: This is an Empty grid
which could come in handy as some divider element
5 Likes
Sensor: section from configuration.yaml is not loaded. So I am missing a lot of sensor and some integrations like Bitcoin.
Yes, will be fixed in 2024.3.1. See SNMP device tracker broken in 2024.3.0 and Python 3.12 · Issue #112548 · home-assistant/core · GitHub for more information and a workaround when you use hass-core in a Python virtualenv.
2 Likes
Yeah, tried that out and worked like a charm. I actually discovered that my script hadn’t been assigned a random id number but was using my original entity id when I first wrote script months ago. I had forgotten I renamed it, and the renaming process must have failed.
I also found a couple other scripts that were assigned with random numbers and explains why they have given me grief before.
Do you have details on how to replicate vertical-stack-in-card with card-mod?
Has something changed with regards to casting dashboards in this release?
Since updating the release when casting a dashboard from an automation i just get the home assistant - connected display.
I can cast a dashboard fine from the UI, it just seems calling it from an automation is broken.
A new energy graph is very cool! It would be even cooler to get cost graphs next 
It would be so helpful for any kind of optimizations in case of multiple or changing tariffs. In our energy market very cheap price often means surplus production and more consumption helps to keep grid stable. Optimizing only for kWh consumption is a way wrong for the whole system.
Many users here have quite smart setups for car charges, heating and water boiler automation and so on based on energy price but HA still miss good built-in overview to visualize the final cost/saving.
2 Likes
Sure, what do you want to know.
There are many examples in this community so maybe check those? Card-mod thread holds many.
Probably mainly how to get rid of the stack-gap and how to delete box-shadow and widen margins.
That’s about it, here’s an example
1 Like
Is it possible to set the number of columns in a section? I see in the yaml its a grid but even with columns set to 3 or 4 it seems each section is still 2 columns max for me using buttons or vertical tiles. Surely I am missing something?
same here 
Cast problem for me too, Google hub stuck with Nabu Casa “connected” image with the latest version of home assistant.
1 Like
I downgraded to the last Stable version, and it all started working again.
So there is definitley something funny going on in this release with casting. I notice in the detailed release notes there are some changes to cast. Guessing one of these broke it.
Shame i was looking forward to this release
use
type: horizontal-stack
cards:
… And some card-mod
type: tile
entity: binary_sensor.asusr_wan
hold_action:
action: more-info
hide_state: true
name: []
icon_color: orange
card_mod:
style:
ha-tile-icon$: |
.shape {
border-radius: 10px !important;
height: 50px !important;
width: 50px !important;
margin-top: 10px !important;
margin-bottom: 5px !important;
margin-left: -5px;
margin-right: -5px;
}
.: |
ha-card: {
height: 50px;
width: 40px;
}
:host {
height: 50px;
width: 40px;
margin-left: 10px;
}
Another example ( I dont use )
So i don’t paste the whole code, i guess you can count
type: tile
entity: binary_sensor.ds2_door
hold_action:
action: more-info
hide_state: true
name: []
icon_color: orange
card_mod:
style:
ha-tile-icon$: |
.shape {
border-radius: 10px !important;
height: 40px !important;
width: 30px !important;
margin-top: 10px !important;
margin-bottom: 5px !important;
margin-left: -5px;
margin-right: -5px;
}
.: |
ha-card: {
height: 40px;
width: 40px;
}
2024.2.4 works again if you downgrade.
Raised an issue on GitHub for it
Possibly…what is at_date ? That may be what its complaining about.
Thanks for looking into this.
at_date is part of the suntime module, so it’s internal to python, not mine.
I’ve got a confirmation at stack overflow that this is a bug introduced into python 3 days ago. A bug report has been submitted already, so I’ll just wait for it to be solved in the next release.