ApexCharts card - A highly customizable graph card

[scotta]

I am trying to display electricity forecasts from Amber Electricity (Australia). However it is not displaying the forecast datetimes correctly.
Looking for some help. I’m sure it is something simple I am missing but cannot figure it out.
I am a noob wrt ApexCharts and JavaScript.

This is the sensor data;

sensor.amberelectricity_general_forecast
yaml

state_class: measurement
forecasts:
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T15:30:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.1
    start_time: '2022-02-14T05:00:01+00:00'
    end_time: '2022-02-14T05:30:00+00:00'
    renewables: 35
    spike_status: none
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T16:00:00+10:00'
    per_kwh: 0.26
    spot_per_kwh: 0.11
    start_time: '2022-02-14T05:30:01+00:00'
    end_time: '2022-02-14T06:00:00+00:00'
    renewables: 34
    spike_status: none
    range_min: 0.08
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T16:30:00+10:00'
    per_kwh: 0.27
    spot_per_kwh: 0.12
    start_time: '2022-02-14T06:00:01+00:00'
    end_time: '2022-02-14T06:30:00+00:00'
    renewables: 32
    spike_status: none
    range_min: 0.08
    range_max: 0.35
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T17:00:00+10:00'
    per_kwh: 0.26
    spot_per_kwh: 0.11
    start_time: '2022-02-14T06:30:01+00:00'
    end_time: '2022-02-14T07:00:00+00:00'
    renewables: 30
    spike_status: none
    range_min: 0.08
    range_max: 0.25
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T17:30:00+10:00'
    per_kwh: 0.27
    spot_per_kwh: 0.12
    start_time: '2022-02-14T07:00:01+00:00'
    end_time: '2022-02-14T07:30:00+00:00'
    renewables: 28
    spike_status: none
    range_min: 0.08
    range_max: 0.24
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T18:00:00+10:00'
    per_kwh: 0.27
    spot_per_kwh: 0.12
    start_time: '2022-02-14T07:30:01+00:00'
    end_time: '2022-02-14T08:00:00+00:00'
    renewables: 26
    spike_status: none
    range_min: 0.09
    range_max: 0.23
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T18:30:00+10:00'
    per_kwh: 0.29
    spot_per_kwh: 0.15
    start_time: '2022-02-14T08:00:01+00:00'
    end_time: '2022-02-14T08:30:00+00:00'
    renewables: 23
    spike_status: none
    range_min: 0.11
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T19:00:00+10:00'
    per_kwh: 0.29
    spot_per_kwh: 0.15
    start_time: '2022-02-14T08:30:01+00:00'
    end_time: '2022-02-14T09:00:00+00:00'
    renewables: 20
    spike_status: none
    range_min: 0.1
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T19:30:00+10:00'
    per_kwh: 0.34
    spot_per_kwh: 0.19
    start_time: '2022-02-14T09:00:01+00:00'
    end_time: '2022-02-14T09:30:00+00:00'
    renewables: 19
    spike_status: none
    range_min: 0.11
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T20:00:00+10:00'
    per_kwh: 0.35
    spot_per_kwh: 0.2
    start_time: '2022-02-14T09:30:01+00:00'
    end_time: '2022-02-14T10:00:00+00:00'
    renewables: 19
    spike_status: none
    range_min: 0.11
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T20:30:00+10:00'
    per_kwh: 0.28
    spot_per_kwh: 0.13
    start_time: '2022-02-14T10:00:01+00:00'
    end_time: '2022-02-14T10:30:00+00:00'
    renewables: 19
    spike_status: none
    range_min: 0.1
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T21:00:00+10:00'
    per_kwh: 0.27
    spot_per_kwh: 0.12
    start_time: '2022-02-14T10:30:01+00:00'
    end_time: '2022-02-14T11:00:00+00:00'
    renewables: 20
    spike_status: none
    range_min: 0.09
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T21:30:00+10:00'
    per_kwh: 0.26
    spot_per_kwh: 0.11
    start_time: '2022-02-14T11:00:01+00:00'
    end_time: '2022-02-14T11:30:00+00:00'
    renewables: 19
    spike_status: none
    range_min: 0.08
    range_max: 0.3
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T22:00:00+10:00'
    per_kwh: 0.26
    spot_per_kwh: 0.11
    start_time: '2022-02-14T11:30:01+00:00'
    end_time: '2022-02-14T12:00:00+00:00'
    renewables: 19
    spike_status: none
    range_min: 0.08
    range_max: 0.26
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T22:30:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.11
    start_time: '2022-02-14T12:00:01+00:00'
    end_time: '2022-02-14T12:30:00+00:00'
    renewables: 19
    spike_status: none
    range_min: 0.08
    range_max: 0.26
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T23:00:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.1
    start_time: '2022-02-14T12:30:01+00:00'
    end_time: '2022-02-14T13:00:00+00:00'
    renewables: 18
    spike_status: none
    range_min: 0.08
    range_max: 0.14
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-14T23:30:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.1
    start_time: '2022-02-14T13:00:01+00:00'
    end_time: '2022-02-14T13:30:00+00:00'
    renewables: 16
    spike_status: none
    range_min: 0.08
    range_max: 0.15
  - duration: 30
    date: '2022-02-14'
    nem_date: '2022-02-15T00:00:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.11
    start_time: '2022-02-14T13:30:01+00:00'
    end_time: '2022-02-14T14:00:00+00:00'
    renewables: 15
    spike_status: none
    range_min: 0.08
    range_max: 0.18
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T00:30:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.1
    start_time: '2022-02-14T14:00:01+00:00'
    end_time: '2022-02-14T14:30:00+00:00'
    renewables: 14
    spike_status: none
    range_min: 0.08
    range_max: 0.13
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T01:00:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.1
    start_time: '2022-02-14T14:30:01+00:00'
    end_time: '2022-02-14T15:00:00+00:00'
    renewables: 14
    spike_status: none
    range_min: 0.08
    range_max: 0.13
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T01:30:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.09
    start_time: '2022-02-14T15:00:01+00:00'
    end_time: '2022-02-14T15:30:00+00:00'
    renewables: 14
    spike_status: none
    range_min: 0.07
    range_max: 0.11
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T02:00:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.09
    start_time: '2022-02-14T15:30:01+00:00'
    end_time: '2022-02-14T16:00:00+00:00'
    renewables: 14
    spike_status: none
    range_min: 0.05
    range_max: 0.1
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T02:30:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T16:00:01+00:00'
    end_time: '2022-02-14T16:30:00+00:00'
    renewables: 15
    spike_status: none
    range_min: 0.05
    range_max: 0.11
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T03:00:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T16:30:01+00:00'
    end_time: '2022-02-14T17:00:00+00:00'
    renewables: 15
    spike_status: none
    range_min: 0.02
    range_max: 0.1
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T03:30:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T17:00:01+00:00'
    end_time: '2022-02-14T17:30:00+00:00'
    renewables: 15
    spike_status: none
    range_min: 0.02
    range_max: 0.1
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T04:00:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T17:30:01+00:00'
    end_time: '2022-02-14T18:00:00+00:00'
    renewables: 15
    spike_status: none
    range_min: 0.02
    range_max: 0.11
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T04:30:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T18:00:01+00:00'
    end_time: '2022-02-14T18:30:00+00:00'
    renewables: 14
    spike_status: none
    range_min: 0.02
    range_max: 0.1
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T05:00:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T18:30:01+00:00'
    end_time: '2022-02-14T19:00:00+00:00'
    renewables: 14
    spike_status: none
    range_min: 0.04
    range_max: 0.11
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T05:30:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.1
    start_time: '2022-02-14T19:00:01+00:00'
    end_time: '2022-02-14T19:30:00+00:00'
    renewables: 13
    spike_status: none
    range_min: 0.07
    range_max: 0.13
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T06:00:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.11
    start_time: '2022-02-14T19:30:01+00:00'
    end_time: '2022-02-14T20:00:00+00:00'
    renewables: 12
    spike_status: none
    range_min: 0.08
    range_max: 0.16
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T06:30:00+10:00'
    per_kwh: 0.28
    spot_per_kwh: 0.13
    start_time: '2022-02-14T20:00:01+00:00'
    end_time: '2022-02-14T20:30:00+00:00'
    renewables: 12
    spike_status: none
    range_min: 0.09
    range_max: 0.3
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T07:00:00+10:00'
    per_kwh: 0.27
    spot_per_kwh: 0.12
    start_time: '2022-02-14T20:30:01+00:00'
    end_time: '2022-02-14T21:00:00+00:00'
    renewables: 17
    spike_status: none
    range_min: 0.08
    range_max: 0.3
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T07:30:00+10:00'
    per_kwh: 0.26
    spot_per_kwh: 0.11
    start_time: '2022-02-14T21:00:01+00:00'
    end_time: '2022-02-14T21:30:00+00:00'
    renewables: 22
    spike_status: none
    range_min: 0.08
    range_max: 0.16
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T08:00:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.09
    start_time: '2022-02-14T21:30:01+00:00'
    end_time: '2022-02-14T22:00:00+00:00'
    renewables: 28
    spike_status: none
    range_min: 0.07
    range_max: 0.14
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T08:30:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.09
    start_time: '2022-02-14T22:00:01+00:00'
    end_time: '2022-02-14T22:30:00+00:00'
    renewables: 33
    spike_status: none
    range_min: 0.06
    range_max: 0.14
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T09:00:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T22:30:01+00:00'
    end_time: '2022-02-14T23:00:00+00:00'
    renewables: 37
    spike_status: none
    range_min: 0.05
    range_max: 0.12
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T09:30:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-14T23:00:01+00:00'
    end_time: '2022-02-14T23:30:00+00:00'
    renewables: 40
    spike_status: none
    range_min: 0.06
    range_max: 0.12
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T10:00:00+10:00'
    per_kwh: 0.22
    spot_per_kwh: 0.08
    start_time: '2022-02-14T23:30:01+00:00'
    end_time: '2022-02-15T00:00:00+00:00'
    renewables: 43
    spike_status: none
    range_min: 0.03
    range_max: 0.1
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T10:30:00+10:00'
    per_kwh: 0.22
    spot_per_kwh: 0.07
    start_time: '2022-02-15T00:00:01+00:00'
    end_time: '2022-02-15T00:30:00+00:00'
    renewables: 44
    spike_status: none
    range_min: 0.03
    range_max: 0.09
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T11:00:00+10:00'
    per_kwh: 0.22
    spot_per_kwh: 0.07
    start_time: '2022-02-15T00:30:01+00:00'
    end_time: '2022-02-15T01:00:00+00:00'
    renewables: 45
    spike_status: none
    range_min: 0.03
    range_max: 0.09
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T11:30:00+10:00'
    per_kwh: 0.22
    spot_per_kwh: 0.07
    start_time: '2022-02-15T01:00:01+00:00'
    end_time: '2022-02-15T01:30:00+00:00'
    renewables: 46
    spike_status: none
    range_min: 0.03
    range_max: 0.09
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T12:00:00+10:00'
    per_kwh: 0.21
    spot_per_kwh: 0.07
    start_time: '2022-02-15T01:30:01+00:00'
    end_time: '2022-02-15T02:00:00+00:00'
    renewables: 45
    spike_status: none
    range_min: 0.04
    range_max: 0.09
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T12:30:00+10:00'
    per_kwh: 0.22
    spot_per_kwh: 0.07
    start_time: '2022-02-15T02:00:01+00:00'
    end_time: '2022-02-15T02:30:00+00:00'
    renewables: 43
    spike_status: none
    range_min: 0.05
    range_max: 0.1
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T13:00:00+10:00'
    per_kwh: 0.23
    spot_per_kwh: 0.08
    start_time: '2022-02-15T02:30:01+00:00'
    end_time: '2022-02-15T03:00:00+00:00'
    renewables: 42
    spike_status: none
    range_min: 0.05
    range_max: 0.12
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T13:30:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.09
    start_time: '2022-02-15T03:00:01+00:00'
    end_time: '2022-02-15T03:30:00+00:00'
    renewables: 41
    spike_status: none
    range_min: 0.06
    range_max: 0.15
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T14:00:00+10:00'
    per_kwh: 0.24
    spot_per_kwh: 0.09
    start_time: '2022-02-15T03:30:01+00:00'
    end_time: '2022-02-15T04:00:00+00:00'
    renewables: 40
    spike_status: none
    range_min: 0.07
    range_max: 0.21
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T14:30:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.1
    start_time: '2022-02-15T04:00:01+00:00'
    end_time: '2022-02-15T04:30:00+00:00'
    renewables: 41
    spike_status: none
    range_min: 0.07
    range_max: 0.21
  - duration: 30
    date: '2022-02-15'
    nem_date: '2022-02-15T15:00:00+10:00'
    per_kwh: 0.25
    spot_per_kwh: 0.1
    start_time: '2022-02-15T04:30:01+00:00'
    end_time: '2022-02-15T05:00:00+00:00'
    renewables: 40
    spike_status: none
    range_min: 0.07
    range_max: 0.23
channel_type: general
unit_of_measurement: $/kWh
attribution: Data provided by Amber Electric
icon: mdi:transmission-tower
friendly_name: AmberElectricity - General Forecast

my card config yaml

type: custom:apexcharts-card
header:
  show: true
  title: Amber Electricty Forecast
  show_states: true
  colorize_states: true
series:
  - entity: sensor.amberelectricity_general_forecast
    float_precision: 2
    data_generator: |
      return entity.attributes.forecasts.map((entry) => {
        return [new Date(entry.nem_date), entry.per_kwh];
      });

[scotta]

FYI - I’ve solved my own problem. It was not showing the correct range. Updated YAML below

type: custom:apexcharts-card
graph_span: 24h
span:
  start: minute
header:
  show: true
  title: Amber Electricty Forecast
  show_states: false
  colorize_states: true
series:
  - entity: sensor.amberelectricity_general_forecast
    float_precision: 2
    data_generator: |
      return entity.attributes.forecasts.map((entry) => {
        return [new Date(entry.nem_date), entry.per_kwh];
      });
yaxis:
  - min: 0
    max: ~0.40
    decimals: 2
    apex_config:
      forceNiceScale: true

[flobidan]

Is there a simple way (does someone have example code) to have a horizontal dotted line in the diagram to display a threshold? I would assume that it just needs a single value via the data generator which is then prolonged endlessly, but I am not sure how this would practically look like

[cpo]

Do i do this correctly?
I want to update the chart not at every change (this works, but is way to often with my sensor).
When i insert the update_interval: 5min nothing updates at all. Delete it - it updates again with every sensor update.

- type: custom:apexcharts-card
  update_interval: 5min
  header:
    title: test (48h)

Thank you.

[armaster]

Hi,

thanks for great chart!

I’m currently configuring my first chart and I have a question: my chard displays only one sensor data for period of 2 days. Is it possible to display max value of sensor on the right side of div id=header__states and how to do that?

I checked this (https://github.com/RomRider/apexcharts-card/issues/218), but this is not what I want. I want to see max history value “max 25.4°C” in the header.

This is my card:

type: custom:apexcharts-card
hours_12: false
graph_span: 2d
header:
  show: true
  title: Out temperature
  show_states: true
  colorize_states: true
show:
  loading: true
  last_updated: true
experimental:
  color_threshold: true
series:
  - entity: sensor.viking_0203502038_51_06_temperature
    stroke_width: 4
    type: column
    group_by:
      func: avg
      duration: 30min
    color_threshold:
      - value: 0
        color: blue
      - value: 1
        color: yellow
      - value: 10
        color: orange
      - value: 25
        color: red

Thanks for help.

[flobidan]

The help of the transform function says:
With transform, you can modify raw data comming from Home-Assistant’s history using a javascript function.

I try to use that to draw a line that is always 4 points below another sensor being displayed in the same graph. But I would expect that this considers also the history and therefore moves up and down as per the reference sensor, but it doesn’t - instead it draws a straight line where the last point of the reference sensor is. Have I misunderstood something?

The red line should move up and dosn with the blue line, 4 points below. But it remains a straight line.

Here is my code:

type: custom:apexcharts-card
header:
  show: true
  show_states: true
  colorize_states: true
series:
  - entity: sensor.bsb_lan_trinkwassertemperatur
    stroke_width: 3
  - entity: sensor.bsb_lan_trinkwassersollwert
    stroke_width: 2
    curve: stepline
    fill_raw: last
  - entity: sensor.bsb_lan_kesseltemperatur
    transform: return x = hass.states['sensor.bsb_lan_trinkwassersollwert'].state - 4
    stroke_width: 1
    unit: °C
    curve: stepline

Btw., the help on the github page is not really clear about the statements of the transform function, thas was quite some try and error to get at least anything displayed.

[Lunkobelix]

Can’t find a way to define number of decimals in the header (only yaxis), can someone pelase point me in the right direction?

Edit: The float_precision: 2 works but if the value is “1” it is just shown as “1” instead of “1.00”.

[MrGlad8 (Andree)]

Hello! With my Heat/AC pump model Daikin there was created a sensor named “sensor.daikinap42587_heat_energy_consumption”.
And according to this site It do show me the energy kwh per hour:

Daikin AC

This is how it looks in the settings:

Knowing that, if i put that sensor in this code:

type: custom:apexcharts-card
graph_span: 168h
header:
  title: Värmepump Energi Värme 24h
  show: true
series:
  - entity: sensor.daikinap42587_heat_energy_consumption
    type: column
    name: Värmepump Energi Värme
    group_by:
      func: sum
      duration: 24h

Will that show me correct consumption per day?
It do show up like this:

But it seem to show the energy between the middle of the days? Not 00:00 to 24:59?
Or am I missing something?

Thanks!

[Lunkobelix]

I think I have found a bug.

In the chart below I only want one series to be drawn in the graph, and that is “Aktuell förbrukning”. The other two, “Easee-laddning” and “Ampere fas 1” should only be shown in the header. The problem is that the yaxis get’s a scale that also takes “Ampere fas 1” into consideration.

If I also plot the “Ampere fas 1” you see why the yaxis goes all the way up to 25:

One work around would be to use max: 5 but since I already have min: 0 I haven’t been able to combine them. Code below, all help with getting this to look correct would be appreciated.

type: custom:apexcharts-card
header:
  title: ''
  show: true
  show_states: true
graph_span: 24h
apex_config:
  tooltip:
    enabled: true
  yaxis:
    forceNiceScale: true
  xaxis:
    axisBorder:
      show: false
    labels:
      style:
        fontSize: 10px
        fontFamily: Segoe UI Light
  chart:
    height: 225
  grid:
    show: false
    borderColor: '#404040'
    strokeDashArray: 3
    position: back
  legend:
    show: false
  dataLabels:
    enabled: false
  stroke:
    width: 0
  fill:
    type: gradient
    gradient:
      type: vertical
      shadeIntensity: 0
      inverseColors: false
      opacityFrom: 0.9
      opacityTo: 0.6
      stops:
        - 10
yaxis:
  - min: 0
    apex_config:
      forceNiceScale: true
      decimalsInFloat: 1
      labels:
        style:
          fontSize: 10px
          fontFamily: Segoe UI Light
series:
  - entity: sensor.el_forbrukning_kw
    name: Aktuell förbrukning
    color: white
    float_precision: 2
  - entity: sensor.easee_laddbox_power
    color: white
    name: Easee-laddning
    show:
      in_chart: false
    float_precision: 1
  - entity: sensor.el_forbrukning_kw
    name: Aktuell avg förbrukning
    type: column
    color: fc7703
    show:
      in_header: false
      legend_value: true
    fill_raw: last
    group_by:
      func: avg
      duration: 15min
    float_precision: 2
  - entity: sensor.current_l1_vagen
    name: Ampere fas 1
    color: white
    type: column
    float_precision: 1
    show:
      in_chart: true
style: |
  ha-card {
     --ha-card-background: rgba(0, 0, 0, 0);
     box-shadow: none;
     margin: 8px 8px 38px 8px;
     font-size: 15px;
     font-family: 'Segoe UI Light";
     text-align: center
   }
   div#header__title {
     font-size: 20px;
     font-weight: 300;
     font-family: 'Segoe UI Light";
     font-color: #ff0000
   }

[LJustin]

Hi I have a string of dates and I’m trying to parse them onto the chart. On the javascript compiler, it works fine, but when I try to use it in a data_generator it would just load infinitely.

The string is: "2022-02-17 04:00:00+02:00 2022-02-17 02:00:00+02:00 2022-02-17 03:00:00+02:00"

var dates = "2022-02-17 04:00:00+02:00   2022-02-17 02:00:00+02:00   2022-02-17 03:00:00+02:00"

console.log(dates.split("   ").map((entry) => {return [new Date(entry).getTime() + 7200000, 1];}))

And the compiler outputs

[ [ 1645070400000, 1 ],
  [ 1645063200000, 1 ],
  [ 1645066800000, 1 ] ]

- type: 'custom:apexcharts-card'
        view_layout:
          grid-area: col3
        header:
            show: true
            title: Electricity Price Today & Tomorrow
            show_states: false
        graph_span: 2d
        span:
            start: day
        series:
            - entity: sensor.nordpool_hours_to_charge_today
              name: Today
              data_generator: |
                 return entity.split("   ").map((entry) => {
                   return [new Date(entry).getTime() + 7200000, 1];
                 });
              type: column
              show:
                 legend_value: false
                 in_header: false
              extend_to_end: false

However this chart is stuck at Loading… Any suggestions?

Thank you!

EDIT: I believe the problem was that I needed to add .state next to entity return entity.state.split
the graph now loads however it doesn’t show any data

My sensor:

Any ideas what could it be?

SOLVED: it appears that the spaces between the dates were actually “\n \n \n” so adding these to the split solved the issue

[flobidan]

The transform function seems to really not do what it should. Referring to my post above (ApexCharts card - A highly customizable graph card - #1427 by flobidan), without changing the code, now it looks like this:

The red line is supposed to be parallel to the blue line, because it takes the blue line minus 4. Where is this time shift coming from? And as soon as the blue line goes down to 44 again, the red line does also change for the past.

There does not seem to be that much support here for that otherwise great project, many questions but only few answers

[VDRainer]

@flobidan

There does not seem to be that much support here for that otherwise great project, many questions but only few answers

This comment is very unfair to the author of ApexCharts.
I think we can agree that RomRider is a developer who answers most questions in his limited time.
By the way, I had the same problem as you and I found the solution by searching this thread.
I wish you success .

[lcmg (Luis Coelho)]

Hi,
I store daily values on a simple database, 2 columns date and value. I’ve created a sensor that returns the values based on a selected month (input_select) and return the values from that month. Till here all work fine.
I’m now trying to create the graph showing the selected month.
If I query the last 30 days it work without issues, the problem is if I select a specific month, as I I can’t manage to define the xaxis range, it always show the latest 30days (defined on graph_span) and not the values on queried interval.
Does anyone have any tip to overcome this? I’ve search a solution but couldn’t find so far.
Many thanks in advance

[flobidan]

This is not against the author personally. Compared to e.g. button-cards, where always someone has an answer, I just see a mismatch of people that try to use this and people that have the necessary experience with this. Scroll up and you see more than a week of multiple questions by multiple people, no reply on any of them.
But thanks for sharing the solution. “I know something, but I don’t tell you”.

[Lunkobelix]

Has anyone been able to remove the red part below? Feels like the date information is unnecessary to show twice? Or is it possible to show the value in the red part and skip the top tooltip?

[MrGlad8 (Andree)]

I have a slight problem.
I have one chart that measure my heat pump energy “per hour” and one for “per day”.
And it didnt match what numbers the heat pumps own app said.
The heat-energ-sensor gives me the pumps kWh per hour.
But when I look more into it it seems that the chart takes the value in the “00:00:00” and put that value in the next day. But that is wrong and the first value for the new day should be at “01:00:00”.
How do I tell the chart to do this?

This is my code atm:

type: custom:apexcharts-card
graph_span: 48h
yaxis:
  - min: 0
    max: 1.5
span:
  end: hour
header:
  standard_format: true
  title: Värmepump - Per Timme
  show: true
  show_states: true
  colorize_states: true
all_series_config:
  type: column
  group_by:
    func: sum
    duration: 1h
series:
  - entity: sensor.daikinap42587_heat_energy_consumption
    name: Värmepump Värme Energi

[lcmg (Luis Coelho)]

Hi, not sure if will solve your issue, but try to add: “extend_to_end: false” under “series”.

[MrGlad8 (Andree)]

hm, nope it still count that data from 00:00 from the day before.
Do I need to remove something when adding it?
If I set the duration to 23 hour I get the correct sum of the kWh this current day! But is that the real solution here? hm…

[MrGlad8 (Andree)]

I think this did it for me…

span:
  end: day
  offset: +1h

That way it start the day from the data of 01 !

[RomRider]

@ntompson

One thing I’m stuck on: sometimes I like to include one or more series on a chart that I don’t want included in the legend. Is there any way I can mark a series to be excluded from the legend?

Unfortunately the library I use doesn’t allow to hide a serie from the legend.

@hajo62

Does someone know a trick how to get really nice y-axis scaling?

Only way would be to set the number of ticks I believe

@swifty

I tried out the color threshold option, but that seems to give a gradiant for each data point rather than setting the whole chart.

Also, is it possible to fade to a lower opacity for the chart (ie. fade it out at the bottom) regardless of the value? - again I can see an opacity option for the colour_threshold setting, but not sure how I can use that to get a fade so that all cards look consistent…

If the color threshold give a weird look, it’s because you have null data in your chart, that could be fixed with fill_raw: last

For your other question, you have the option to create a gradiant with options from here

@rufiik

Is it possible to fill area chart only for values below treshhold?
I’d like to fill negative temperature (below zero) on my graph, like that:

That’s not possible unfortunately. One way to hack it is to make 2 series, on which filters out everything that is >0 and displayed as an area and the other one which filters everything that is <0 and displayed as a line

@michapr

I have found (in ApexCharts docu) the “customIcons” in toolbar with the possible mapping to a function, but not sure how it could work here.

Not sure I understand what you want to achieve

@foraster

Any advice for solving this? (apart from limiting the y_axis to a min value of 0)?

Why not create a utility meter which resets every hour? (not sure it’s possible though)

@dutchguy

Any idea what is wrong here?

Why not use an annotation to highlight a band in the chart?

@BolleK

I’m guessing it is in the data_generator part but I’m not proficient enough to figure this out on my own.

You’ll need to prepend the current value with the current timestamp in the data generator

@flobidan

Any way to achieve that?

Not possible to skip a period on the timeline unfortunately. You could however stack the 3 days on top of each other using offset and reduce the timeline to only 6-22 in this case

@BratislaveBoy

Is it possible to decrease the space reserved for the header?

You could use card-mod for that

@skyborgff

How can i plot a sensor value, but subtracting the first value in the graph?

You can use group_by with the diff function and a duration of 1d

@henrikrox

is there no way to remove legends?

You can remove the legend with:

apex_config:
  legend:
    show: false

@m0uH

Is there any possibility to set the series color dynamically based on a sensor value or attribute other than config-template-card?

Not at the moment, but I might add templates like in button-card at some point

@m0uH

The zoom is reset after each update of the sensor values (without config-template-card), is it possible to keep the zoom level also in case the graph is updated by new sensor values?

That is something that might be able to fix, please open a feature request

@m0uH

I’d like to display a whole grill session at once. Is it possible to display all data starting at a specific time point and display all data up to “now”? Or all data since a sensor was “unavailable”?

Not possible at the moment, please open a feature request

@Lunkobelix

it possible to have one series area gradient like below and then add another series as a line (not area) on top of it? Looks like gradient is being applied to both series.

The gradient configuration supports to be defined as an array, that’s the way to fix your issue

@flobidan

Is there a simple way (does someone have example code) to have a horizontal dotted line in the diagram to display a threshold

Yes, you can use annotations

@armaster

I’m currently configuring my first chart and I have a question: my chard displays only one sensor data for period of 2 days. Is it possible to display max value of sensor on the right side of div id=header__states and how to do that?

That is not possible, at least for now.

@flobidan

Have I misunderstood something?

Just do return x - 4;

@MrGlad8

Or am I missing something?

You’ll need end: day to align the chart to the end of the day

@Lunkobelix

The problem is that the yaxis get’s a scale that also takes “Ampere fas 1” into consideration.

That might be a bug, please open one on gh

@Lunkobelix

Has anyone been able to remove the red part below?

You can remove that with

apex_config:
  xaxis:
    tooltip:
      enabled: false

@MrGlad8

How do I tell the chart to do this?

You can’t, apexcharts-card relies on your history, so you need to fix your sensor (or ignore the first hour like you did)