@thomasloven || @petro since you both are the most prolific responders in this thread tagging you both for a solution to the issue in my post above.
Sorry about tagging you guys, but have spent hours trying to figure this one out, without any luck.
Any help would be much appreciated.
Thank you.
Is there any way to do a conditional based on an entities supported features? For example, I may want to format a card slightly differently based on whether a light supports brightness, color temp, etc.
I know itās pretty useless to be able to use state and attributes in general, but this is a static value, so Iām hoping thereās a chance?
I have a lovelace_gen configuration of ~2100 lines of code that gets expanded to >10000 lines of code - I use a lot of macros and for loops.
Is there a way to see the expanded code for debugging? I get an error on line 6798 but I donāt know what is really there.
you can just use j instead of i? if you want to add a name to an entity, they must be the same length lists, so not sure how j & i would ever be different.
I donāt know what happened but I just rebooted twice without lovelace trying to load before lovelace_gen 
I am currently trying to change my frontend a little bit. As I am now working a lot with custom cards where it is not possible to use the ui editor I am trying to switch to the yaml mode. I saw lovelace_gen allows me to use jinja2 templates for my lovelace configuration.
So I tried it out.
So it seems like with this I can do a lot stuff but for now I am not able to print now().
Or I need a different syntax.
This is my smallest example which does not work:
# lovelace_gen
- title: Home
cards:
- type: custom:mushroom-template-card
primary: '{{now()}}'
secondary: ''
icon: mdi:home
I am not sure if this does work with lovelace_gen. But how can I build a Dashboard with this values with lovelace_gen?
Is there also a safe way for other cards? I have one card where I want to include different cards in separated files:
quickinfo.yaml
quickinfo_licht.yaml
quickinfo_fenster.yaml
quickinfo.yaml:
# lovelace_gen
type: custom:swipe-card
card_width: auto
start_card: 1
reset_after: 10
cards:
!include 'quickinfo_licht.yaml'
!include 'quickinfo_fenster.yaml'
quickinfo_licht.yaml looks similar to this:
# lovelace_gen
- type: conditional
conditions:
- condition: screen
media_query: '(max-width: 600px)'
card:
type: custom:mushroom-template-card
tap_action:
action: navigate
navigation_path: licht
- type: conditional
conditions:
- condition: screen
media_query: '(max-width: 600px)'
card:
type: custom:mushroom-template-card
tap_action:
action: navigate
navigation_path: licht
And quickinfo_fenster.yaml as well. So I have multiple files with a list of elements and I want to include them.
Or isnāt this possible at all? So do I have to include either all cards in one file or define one yaml per type and then i am able to include multiple files?
Banging my head against a wall for day. Need input from experts!
I am trying to pass the state of climate.porch_ac_windfree_3_0e to the climate_device_state variable. But no-matter what I do, it doesnāt work. All works in the test markdown card shown below. But I canāt figure out a way of passing the result to the !include variable.
Please, pretty please, help! Iāve tried inline, indentation frenzies, filters ā all to no avail. It MUST be possible!
# lovelace_gen
{% set climate_entity = 'climate.porch_ac_windfree_3_0e' %}
{% set card_bg = card_bg or "var(--primary-background-color)" %}
{% set card_margin = card_margin or "12px auto 12px auto" %}
{% set ac_state_off = "off" %}
{%- macro offState() -%}
{%- raw -%}
{%- if (states({% endraw %}"{{climate_entity}}"){% raw %} == {% endraw %}"off"{% raw %}) -%}
{%- endraw -%}
{{"off"}}
{%- raw -%}
{%- else -%}
{%- endraw -%}
{{"on"}}
{%- raw -%}
{%- endif -%}
{%- endraw -%}
{%- endmacro -%}
type: custom:stack-in-card
group: true
card_mod:
style: |
ha-card {
max-width: 388px !important;
margin: {{card_margin}};
background: {{ card_bg }} !important;
padding: 8px;
}
cards:
- type: vertical-stack
cards:
- !include
- ../components/mini-climate.yaml
- entity: {{climate_entity}}
name: "Porch AC (Samsung)"
climate_device_state: "I AM STUCK"
buttons: ["cool", "heat", "auto"]
- type: markdown
title: "WTF"
content: |
"Hello from Markdown"
............
{% raw %}
So I can tell that my light is {{ states('climate.porch_ac_windfree_3_0e') }}!
{% endraw %}
.......
{{offState()}}
raw/endraw keywords in my lovelace code. {% macro lightswitch(entity, x, y) -%}
- entity: {{entity}}
style: { left: {{x}}%, top: {{y}}%, width: 4% }
type: image
tap_action: {# action: toggle #}
action: call-service
service: script.zwave_switches_toggle
service_data:
entity: {{entity}}
hold_action: { action: more-info }
state_image: { 'off': /local/images/BulbOff.png, 'on': /local/images/BulbOn.png }
{%- endmacro %}
Then, apply your macro as follows:
{{ lightswitch('switch.front_porch_sconces', 65.0, 20.3 ) }}
which will render the result of the macro in your dashboard.
Caution: # lovelace_gen causes the custom:state-switch card not to render and to return Unknown Error on the Dashboard.
Hi,
I did a super bad job of explaining my conundrum. Apologies. Your reply was educational though. Thank you.
Let me simplify with a different example.
I have included yaml file in my yaml dashboard for a climate-card that is fed by variables.
The !include, looks like this:
- !include
- ../components/mini-climate.yaml
- entity: {{govee_entity}}
name: "Porch Space Heater"
buttons: ["heat", "auto", "swing", "presets"]
hvac_show_buttons: ["auto", "heat", "fan", "swing_mode", "custom_1"]
hvac_mode: {{govee_hvac_modes}}
indicators: {{govee_indicators}}
secondary_info: {"type": "fan-mode-dropdown"}
{# override defaults #}
hvac_auto: {"icon": "mdi:sun-snowflake-variant", "is_active": "auto",
"hvac_mode": "auto", "activeColor": "var(--state-climate-auto-color) !important"}
hvac_custom_1: {"type": "dropdown", "icon": "mdi:lightbulb",
"active": "(value !== '' && entity.attributes.nightlight == 'on')",
"state": {"attribute": "selected_scene"}, "activeColor": "var(--state-light-active-color) !important",
"source": {"off":"Light Off", "Coffee": "Coffee", "Sleep":"Sleep", "Warm": "Warm"},
"action": {"domain": "mqtt", "service": "publish",
"options": "{ topic: 'gv2mqtt/DB2A6074F445163C/set-mode-scene', payload: selected }"
}
}
Inside the included yaml file, we use the hvac_custom_1.source variable like this:
source:
<<:
{{item.source}}
It works.
The rendered output (with the dropdown fed by hvac_custom_1.source) is:
Now, instead of hard-coding that hvac_cutom_1.source variable, I want to create the options, from an attribute of an entity:
I have an entity: climate.porch_spaceheater. It has an attribute that looks like this (abbreviated):
nightlight_scenes:
- name: Reading
value: 1
- name: Movie
value: 2
- name: Work
value: 3
- name: Night Light
value: 4
- name: Party
value: 5
- name: Sports
value: 6
- name: Music
value: 7
- name: Warm
value: 8
To test my jinja to get the data from that attribute, I have created a āDebug Markdown Cardā in the dashboard yaml that looks like this:
- type: markdown
title: "Debug Markdown Zone"
content: |
{% raw %}
{% set scenes = state_attr('climate.porch_spaceheater', 'nightlight_scenes') | map(attribute='name')|list %}
{% set source = '[' ~ (scenes | map('regex_replace', '^(.*)$', '{ "\\1": "\\1" }') | join(", ")) ~ ']' %}
{{ source }}
{% endraw %}
It works. And outputs this (I know thatās a hairy xform, but it works!):
So, my question is how the heck do I get that {%raw%}ā¦{%endraw%} block to feed the source prop in hvac_custom_1.source?
- !include:
- ../..etc...
- entity: ....
hvac_custom_1: {
...
"source": //STUFF FROM %RAW% %ENDRAW% GOES HERE!
}
I have tried everything. doing it inline, creating a source variable at the top of the file, creating a macro, but all to avail. I hope I explained this well enough, and hoping someone can teach me the way. If you need more info, please shout!
TIA.
Iām passing tap_action into a custom:button-card ātemplateā and it all works as expected.
(Note that it is not literally a button-card-template but something I use as a template for button-card using lovelace-gen)
Iād like it to use a default tap_action of toggle when none is provided.
An illustaration:
Here is how I include the button ātemplateāā¦
- !include
- ../templates/button_on_off.yaml
- entity: binary_sensor.ld2410_presence
name: mmWave
tap_action:
action: fire-dom-event
browser_mod:
service: browser_mod.popup
data:
content:
type: entities
entities:
- entity: binary_sensor.ld2410_status
name: Status
- more entities etc. etc....
And here is the (relevant parts of) button template itself (button_on_off.yaml)ā¦
type: custom:button-card
aspect_ratio: {{ aspect_ratio | default('1/1') }}
entity: {{ entity }}
name: {{ name }}
tap_action: {{ tap_action | default({'action': 'toggle'}) }}
Whatever I try with that tap_action I cannot get the editor to approve the default and nor will it work (I always tried, thinking it might just be a syntax format that the syntax checker couldnāt handle).
Just to be clear if I provide the tap_action it works.
Iāve tried several variations and even ended up guessing a few.
Is it possible?
Yes, you need to return valid JSON, not a yaml dictionary.
Thanks, can you expand a little?
If the yaml I want to be the default tap_action is
action: toggle
i.e.
tap_action:
action: toggle
the JSON for that is:
{
"action": "toggle"
}
So to pass that in I would use
tap_action: {{ tap_action | default({'action': 'toggle'}) }}
As in my original example.
Which is obviously wrong.
What am I missing?
tap_action: {{ tap_action | default({'action': 'toggle'} | to_json) }}
Iām afraid that doesnāt workā¦
I wonder if lovelace_gen can handle the colon?
Whatās the error in the logs?
it might be tojson
No you were right first time.
There are no log messages, itās a dashboard.
The VS Code editor complains too.
It works in the template tools
Iām fairly sure itās tojson, to_json is what HA built into jinja where tojson is whatās built into jinja.
https://jinja.palletsprojects.com/en/stable/templates/#jinja-filters.tojson
Thatās what you have to use.
tojson didnāt originally exist in jinja, so HA added to_json
Well thatās pretty confusing (to me at least! Or are you saying that the HA to-json is now obsolete because jinja does it natively, with tojson?)
Butā¦ it still isnāt solving it.
Interestingly VS Code still doesnāt like it but the dashboard will display correctly.
But no tap actions work.
