It appears app-header has been deprecated when using the element inspector. Itās now split into two elements which are .header and .toolbar.
You could try renaming app-header in your card-mod-theme to .header e.g.
card-mod-root-yaml: |
.: |
@media only screen and (max-width: 480px) {
app-header {
display: none;
opacity: 0;
}
}
now becomes
card-mod-root-yaml: |
.: |
@media only screen and (max-width: 480px) {
.header {
display: none;
opacity: 0;
}
}
It semi-working for me using this method, but a consequence of it (at least in my config) is I am unable to actually get the header to fully display ānoneā - this just removes the action buttons but leaves the header there. It also seems to prevent the sidebar from being opened on mobile devices when swiping from left to right.
However for your application of just moving it, rather than hiding it, might work.
I was able to fix that, using above suggestion for replacing āapp-headerā with ā.headerā, āapp-toolbarā with ā.toolbarā, and some more adjustments.
Here is my full theme configuration, in case anyone want to compare.
ends up just blurring my whole homescreen and leaving the toolbar at the top of the page. Admittedly, Iām not amazing at CSS so I could be really borking this.
Sadly some card-mod stuff changed as well with 2023.4, in my case none of thesticky code works anymore. I used this to create a sticky header bar (horizontal-stack) with icons in it, but now the sticky part doesnāt work anymore:
Edit: sticky element was broken due to Kiosk Mode module. I always used to hide my header with card-mod theme. However, since that was broken I decided to try the new Kiosk Mode at teh same time as when I upgraded everything else. Disabling Kiosk Mode, fixes sticky cards again.
not sure if I see what that does, but why not simply use that stack without any card_mod? I have a horizontal stack as menu bar on all of my views as is
Yes, it sticks it at the top and stays there when your scroll the page. In my setup I have hidden the HA header bar completely (which thankfully works with new released Kiosk Mode module). And then I use my own statusbar that sticks to the top of my screen.
And at the bottom of my screen I created another horizontal stack with button-cards, to use as the navigation bar to each tab. Which uses bottom variable, making it stick at the bottom.
For that you need mod-card, otherwise you canāt make a stack card sticky as you know. This has worked for me since ever I used it like 2 years ago. But since the latest HA update, it doesnāt work anymore. Seeing as how sticky is just a CSS variable, I think we just need to use a different path in card-mod.
nice, I never had that, and it indeed seems very useful. I do still use the main view icons in the header bar, but have a dashboard menu stack, so I can always have a direct link to those, without having to slide I the menu from the left. We all have our use case
would be great if we could fine the correct element again.
As for the icon change, with has been broken since 3.1.5ā¦ or maybe I need another element for that too?
I wonder if the performance notice is just a bug that it says that, or it actually isnāt loaded properly as a front_end module anymore for better performance.
Edit: @Mariusthvdb sticky element was broken due to Kiosk Mode module. I always used to hide my header with card-mod theme. However, since that was broken I decided to try the new Kiosk Mode at teh same time as when I upgraded everything else. Disabling Kiosk Mode, fixes sticky cards again.
HA 2023.4 introduced Macros feature which may also be used for card-mod.
Consider this simple case:
ā some CO2 value is displayed in many places on cards of different types;
ā you want to colorize this info dependingly on the value (like āgreen if < 500 ppm, ā¦ā).
Note: a similar output for an icon may be achieved by Custom UI.
Earlier we had to repeat same logic for every card.
Now we can use a global macro like this simple one:
{% macro test_color_co2(input_COLOR_CO2) -%}
{%- if input_COLOR_CO2 | int <= 500 -%}
color: green !important;
{%- elif input_COLOR_CO2 | int <= ... -%}
color: orange !important;
{%- elif input_COLOR_CO2 | int <= ... -%}
color: red !important;
{%- else -%}
color: magenta !important;
{%- endif -%}
{%- endmacro %}
Been experimenting with that same feature yes! Very nice, thanks for the write up Ildar.
My main usage would be the power sensors coloring along with their wattage
I do have a worry though, since this is all Jinja templates. They are evaluated in the backend. Server side. First of all, that might not be good for the efficiency . Secondly, if used heavily , I wonder if this wonāt slowdown the Frontend.
Ofc it wonāt make a difference if you already had these templates in many cards, and now only change to this import.
However, adding this to a new dashboardā¦ I am truly worried/interestedā¦.
One specific ask: personally I would only have these macros spit out the color, and keep the key word color: inside the card_mod style. This way you can easily see what your are doing without going to the templates folder and check
Sure, but imagine a more complex case: you need to style more than one property. In the simplest case like described above - yes, your alternative seems to be more descriptive.
{% macro signal_strength_color(entity_id) %}
{% set state = states(entity_id) %}
{% if state >= -50) %} darkgreen
{% elif state >= -60) %} green
{% elif state >= -67) %} lightgreen
{% elif state >= -70) %} gold
{% elif state >= -80) %} orange
{% else %} red
{% endif %}
{% endmacro %}
have to test some further, but I feel the actual card would be better readable, and the same goes for the custom_template macro definition.
this would be a nice one too:
{% macro battery_color(entity_id) %}
{% set state = states(entity_id) %}
{% if state in ['unavailable','unknown'] %} steelblue
{% elif state > 75) %} green
{% elif state > 50) %} gold
{% elif state > 25) %} orange
{% elif state > 10) %} brown
{% else %} red
{% endif %}
{% endmacro %}
Probably we are talking about different things.
The alternative way ācolor: {{calling macro}}ā is absolutely good, but if you need to style like color and background - then you have to place both properties inside a macro.
And there is another case - assume you need to style several properties located on different paths, then these paths are defined inside a macro.
yes, that is correct. For both of these scenarios, I would personally prefer to take the customization out of the path and element. It just makes it much more readable.
the different paths scenario would even be more illustrative of that, because you could simply throw in the same macro in all of these different paths. As long as your card_mod itself describes these correctly (as they do now). It would benefit most!
of course, this is all not yet taking into account the impact this might have on the system/Frontend. Maybe it wont hurt, but I fear it does.
I say that because dumping the jinja templates in the new Profiler logs with
shows all of these jinja templates are registered there too. it might be interesting to see what happens with adding macros to the frontend. since we can not rate limit them like we can in the backend, they might go crazy
I stopped believing in āRaspberry Pi 4ā is enough for HA" more than 2 years ago(((.
We have to use powerful setups anyway, even w/o card-mod.
Or may be I am just a complete noob.
now I want that too, mine scroll away indeedā¦
