FR: Dynamic (template) graph_span

[Mariusthvdb]

originally posted FR here #344 (comment) but it was closed, and Repo seemed quiet.

Now we have active support again, please let me re-FR here

we can currently only hard_code the graph span.

In configs like below, it would be awesome if we could do that with an input_select, and have the chart re-rendered.

Currently we can only do that with a set of conditional cards repeating the same card (yaml anchor), or add extra custom with config-temlpate-card.

Neither are optimal.

Pleas consider doing

graph_span: input_select.graph_span

and be done with it.

type: vertical-stack
cards:
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '15m'
    card:
      graph_span: 15m
      update_interval: 1min
      <<: &apex_config
        type: custom:apexcharts-card
        series:
          - entity: sensor.zp_actuele_opbrengst
            color: var(--power-color)
            type: area
            name: Zon
            stroke_width: 3
            opacity: 0.5
          - entity: sensor.bruto_stroom_verbruik #sensor.calculated_bruto_verbruik
            color: darkblue
            name: Verbruik
            group_by:
              func: avg
              duration: 2min
            stroke_width: 1
          - entity: sensor.netto_verbruik
            color: lightblue
            type: area
            name: Vermogen
            group_by:
              func: avg
              duration: 2min
            stroke_width: 3
            opacity: 0.5
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '30m'
    card:
      graph_span: 30m
      update_interval: 1min
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '1h'
    card:
      graph_span: 1h
      update_interval: 15min
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '2h'
    card:
      graph_span: 2h
      update_interval: 30min
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '6h'
    card:
      graph_span: 6h
      update_interval: 1h
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '12h'
    card:
      graph_span: 12h
      update_interval: 1h
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '16h'
    card:
      graph_span: 16h
      update_interval: 1h
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '24h'
    card:
      graph_span: 24h
      update_interval: 1d
      <<: *apex_config
  - type: conditional
    conditions:
      - condition: state
        entity: input_select.apex_span
        state: '2d'
    card:
      graph_span: 2d
      update_interval: 1d
      <<: *apex_config

[glirnder]

FWIW, I suppose if my approach to #463 is going to get merged, this should be checked as one of the use cases ('tis been a while since I looked at that code, but I think it should Just Work, provided you figure out the JS/TS side of whatever you want to use to control it).

[RomRider]

This can currently be achieved using config-template-card, no need for multiple conditions.
But yes, I'll think about implementing a native span picker

[Mariusthvdb]

yes, we have been using the config-template-card for long.

its not optimal though, and very inefficient at times, so I did away with that, replaced it with the conditional config above.

But yes, I'll think about implementing a native span picker

that would be awesome! no need for templates, just the entity in that options field would me all that we need ;-)

[glirnder]

@RomRider I ended up with setSpanDates() that'd be called by whatever external control, and various things adapt to it (e.g. statistics period chosen based on span; config-wise it's set up as multiple values with thresholds on span). See here.

[mgunther68]

I would like to have the graph_span adapt dynamically to the length of daylight. I'm comparing actual solar production with forecast data and I don't need the graph_span to extend into the night before and after sunrise/sunset. I already have a sensor and number for the daytime length in hours. It would be great if that can be utilised to set the graph_span dynamically.