📝 100% Templatable Lovelace Configurations

Share your Projects! Dashboards & Frontend
,
662

I never took notice of the decluttering card. But would that also work if the parent has to be remove also?

And does it always replace or can it append.

Imagine the decluttering card does not supply a color_threshold. Then the config would be

my_graph_card:
  default:
    ...
    - COLOR_THRESHOLDS: []
  card:
    ...
    color_thresholds: ''

That would break the card if an empty string or null were not permitted (which is often the case for options).

So you would need to add the parent key plus the child_keys using declutterin card.
e.g.

- entity_id: test
  option1: bla
  option2: bla
   '[[decluttering card]]`

Otherwise it is the same as card-mod, which supplies the value to an existing key and does not supply the key itself (at least not the top level key).

663

Maybe a more simple task :slight_smile:
I noticed, that when I have an entities card with input_datetime and input_select they are shown differently in Panel mode.

image
image1070×213 4.06 KB

Is there a way to make them all be the same width (preferrably not full width but without downsizing them in e.g. Masonry mode) and also center them?

664

Is there a way to use templating in the entities selection already?
I am facing the problem that two entities (input_datetime) keep making my card reload because the value changes every minute. The card itself should be ignoring this change as it is part of an if statement that is not ‘true’.

So I think the problem is, that the config-template-card is monitoring the input_datetime and causes a reload of the card with the new state.

I would like to prevent this, if the input_booleans are both true.

type: custom:config-template-card
entities:
  - input_select.dropdown_wildcards
  - input_select.dropdown_entities
  - input_select.dropdown_areas
  - input_select.dropdown_types
  - input_boolean.end_datetime_now
  - input_boolean.start_datetime_24h
  - input_datetime.start_datetime          # only if input_boolean.start_datetime_24h returns 'true'
  - input_datetime.end_datetime          # only if input_boolean.end_datetime_now returns 'true'

If that were possible somehow, it would prevent the regular reloading.

665

I’m having an issue where my card stopped showing at all. No errors. Just black, not taking up any space.

cards:
  - type: custom:config-template-card
    variables:
      - '''input_number.piek_afname_'''
      - if ((new Date()).getMonth()+1 < 10) { "0" }
      - String((new Date()).getMonth()+1)
      - states[vars[0] + vars[1] + vars[2]]
    entities:
      - ${vars[3].entity_id}
      - sensor.fluvius_verbruik_energy_kwartier_piek
    card:
      type: entities
      entities:
        - entity: ${vars[3].entity_id}     # replace with input_number.piek_afname_12
          name: Hoogste piek deze maand
          type: custom:multiple-entity-row
          format: precision2
          unit: kWh
          icon: mdi:transmission-tower
          entities:
            - entity: sensor.fluvius_verbruik_energy_kwartier_piek
              name: Huidige piek
              format: precision2
              unit: kWh

When I replace the actual entity by (what the result should be) input_number.piek_afname_12, and the card is showing.
So something is going wrong when creating the entity from the variables.
This has been working for half a year or so, and (when I remember correct) stopped working about 2 months ago.

What can be wrong ?

666

Probably because you have an undefined var.

Change it to (untested):

  ...
  - String((new Date()).getMonth()+1)
  - if (Number(vars[1]) <= 10) { "0" } else {""}
  - states[vars[0] + vars[2] + vars[1]]
  ...
1 Like
667

It’s working now.
That also explains why it “stopped working about 2 months ago”. month 10 doesn’t need the “0” at the beginning.

Thank you so much !

Edit: I think I have to replace ‘<=’ with ‘<’ otherwise we get month ‘010’ in october.

1 Like
668

Note that you may use “vars[x]” to define a “var[y]” - it saves some amount of a code.
This trick is also possible when using “named vars”.

669

This is indeed pretty cool.
This means that, the moment you define a var, it can be used in the next var.

670

and may be before, have not tested yet…

671

have you solved this problem yet?

i feel like we need url param support

672

I see no problems with generating urls:

type: vertical-stack
cards:
  - type: entities
    entities:
      - entity: input_text.test_text
  - type: custom:config-template-card
    entities:
      - input_text.test_text
    variables:
      URL: '"https://" + states["input_text.test_text"].state + ".com"'
    card:
      type: entities
      entities:
        - type: weblink
          url: ${URL}

image

What the person could not manage to achieve is accessing that “window.location.href” data - but which custom card do have an access? ))

1 Like
673

how to get iframe card to take up whole screen in panel mode?

looks like its a bug.

674

  1. It is possible w/o any additional efforts:

    image
    image1883×968 117 KB

  2. How is this question related to config-template-card?

675

yea but now put it in config-template-card… now it doesnt take up the whole screen if its narrow.
Resize your browser and see.

676

put it in a vertical or horizontal stack. I’m sure there’s way’s to get around it.

677

Do you man this?

image
image621×875 84.2 KB

But try playing with “aspect_ratio”:

image
image632×867 74.9 KB

678

yes this is what i mean, how do you put aspect_ratio in config-template-card?

679

This is an option of “iframe” card:

image
image995×420 39.5 KB

1 Like
680

oh my god i need some sleep… thank you so much , i cant believe this slipped by me

1 Like
681

I am stuck with templated entities

My variables are a list of entities. How can I inject them into my entities?
Here’s what I have now but without luck.

variables:
  - entity: sensor.socket_wireless_power_watt
  - entity: sensor.socket_christmass_tree_power
entities: ${vars.map(v => v.entity)}
1 Like