SolarEdge Photovoltaik Production and Consumption as Daily Graph

[citoki]

This is an implementation of Home Assistant Plotly graph library, to show a daily graph in a very similar way like the vendor iOS app is doing it.

Original Vendor App	Plotly Graph Card

type: custom:plotly-graph
hours_to_show: 12
refresh_interval: 30
entities:
  - entity: sensor.pv_ac_power_combined_integral
    name: PV Production
    statistic: state
    period: auto
    legendgroup: 1
    filters:
      - derivate
      - store_var: pv_ac_power
    line:
      width: 1
      color: palegreen
      shape: spline
    fill: tonexty
  - entity: sensor.solaredge_m1_exported_kwh
    name: Self Consumption
    statistic: state
    legendgroup: 2
    period: auto
    fill: tozeroy
    filters:
      - derivate: h
      - map_y: parseFloat(vars.pv_ac_power.ys[i]) - parseFloat(ys[i])
      - store_var: selfcons
    line:
      width: 1
      color: dodgerblue
      shape: spline
  - entity: sensor.solaredge_m1_imported_kwh
    name: Import
    statistic: state
    legendgroup: 3
    period: auto
    filters:
      - derivate
      - map_y: '(parseFloat(y[i-1]) === parseFloat(ys[i])) ? 0 : parseFloat(vars.selfconsys[i]) + parseFloat(ys[i])'
    line:
      width: 0
      color: lightsalmon
      shape: spline
    fill: tonexty

Some remarks:

• I used standard CSS colours and didn't go for specific RGBA numbers
• I use (SolarEdge Modbus Multi)[https://github.com/WillCodeForCats/solaredge-modbus-multi] integration to get SolarEdge data directly from the inverters every 10 seconds. It's needed to add RJ45 cable to the inverters, as Modbus isn't available via Wifi anymore
• since I've got two inverters running I combine the photovoltaik production with an template
• the data aggregation for the Solar Edge output API (iOS app) is 15 minutes and cannot be changed, therefore you'll see slightly different graph values

Edit: updated configuration after discussion here with some improvements

[Thlerry]

!

Thanks for sharing. This is my version using Plotly-graph and SolarEdge modbus integration.

type: custom:plotly-graph
entities:
  - entity: sensor.tb_solaredge_ac_power
    name: Solar
    fill: tozeroy
    line:
      shape: spline
      color: '#ff8800'
    show_value: false
    extend_to_present: false
    on_legend_click: {}
    on_click: {}
    on_dblclick: {}
    filters:
      - fn: |-
          ({xs, ys}) => ({
              xs: xs.flatMap((x, i) => ys[i+1] === null ? [x,x]:[x]),
              ys: ys.flatMap((y, i) => ys[i+1] === null ? [y,null]:[y])
          })
      - map_y: 'y === null ? 0 : y'
      - resample: 2m
      - sliding_window_moving_average: null
      - map_y_numbers: 'y < 0 ? 0 : y'
  - entity: sensor.tb_house_consumption_kw
    name: Grid
    fill: tozeroy
    line:
      color: '#77aaff'
      shape: spline
    show_value: false
    extend_to_present: false
    on_legend_click: {}
    on_click: {}
    on_dblclick: {}
    filters:
      - fn: |-
          ({xs, ys}) => ({
              xs: xs.flatMap((x, i) => ys[i+1] === null ? [x,x]:[x]),
              ys: ys.flatMap((y, i) => ys[i+1] === null ? [y,null]:[y])
          })
      - map_y: 'y === null ? 0 : y'
      - resample: 2m
      - sliding_window_moving_average: null
      - map_y_numbers: 'y < 0 ? 0 : y'
  - entity: sensor.tb_house_solar_only_consumption_kw
    name: Self Consumption
    fill: tozeroy
    line:
      color: '#00eeee'
      shape: spline
    show_value: false
    extend_to_present: false
    on_legend_click: {}
    on_click: {}
    on_dblclick: {}
    filters:
      - fn: |-
          ({xs, ys}) => ({
              xs: xs.flatMap((x, i) => ys[i+1] === null ? [x,x]:[x]),
              ys: ys.flatMap((y, i) => ys[i+1] === null ? [y,null]:[y])
          })
      - map_y: 'y === null ? 0 : y'
      - resample: 2m
      - sliding_window_moving_average: null
      - map_y_numbers: 'y < 0 ? 0 : y'
hours_to_show: current_day
refresh_interval: 1
config:
  scrollZoom: false
  displayModeBar: false
  staticPlot: true

[Thlerry]

I noticed you used "fill: tonexty" in yours for 2 colors ? what does it do ?
If I use is instead of tozeroy my graph looks funny.

tonexty: on 2 colors like you

tozeroy everywhere:

[citoki]

Good point, well the order didn't helped, as I need to set the selfcons variable from sensor.solaredge_m1_exported_kwh first, to use it in the next entity. Or is there a different approach possible?

A fast solution I found, and is totally fine for me, is to set the width of the imported entity (red), to 0 and now it doesn't show up anymore:

complete config for reference

type: custom:plotly-graph
hours_to_show: 12
refresh_interval: 30
entities:
  - entity: sensor.pv_ac_power_combined_integral
    name: PV Production
    statistic: state
    period: auto
    legendgroup: 1
    filters:
      - derivate
      - store_var: pv_ac_power
    line:
      width: 1
      color: palegreen
      shape: spline
    fill: tonexty
  - entity: sensor.solaredge_m1_exported_kwh
    name: Self Consumption
    statistic: state
    legendgroup: 2
    period: auto
    fill: tozeroy
    filters:
      - derivate: h
      - map_y: parseFloat(vars.pv_ac_power.ys[i]) - parseFloat(ys[i])
      - store_var: selfcons
    line:
      width: 1
      color: dodgerblue
      shape: spline
  - entity: sensor.solaredge_m1_imported_kwh
    name: Import
    statistic: state
    legendgroup: 3
    period: auto
    filters:
      - derivate
      - map_y: '(parseFloat(y[i-1]) === parseFloat(ys[i])) ? 0 : parseFloat(vars.selfconsys[i]) + parseFloat(ys[i])'
    line:
      width: 0
      color: lightsalmon
      shape: spline
    fill: tonexty

[dbuezas]

Oh, good idea!
For completeness, if you want to give the ordering a try just use a var to store the data and then bringbit back using load_var in a subsequent trace. That subsequent trace can have an empty string as entity (entity: '').
I think I made a mistake somewhere and the order of the entities ends up being backwards in the plot, so tonexty actually means to previous y

[Thlerry]

Mine looks OK when the solar production is below consumption. It just looks the same as on the graph I posted above. The orange bit is just higher than the green. I don't have any issue with the rendering using the fill option "tozeroy".

The self consumption for me is the same as consumption, except that I zero it when there is no solar production. So they overlap completely since they are identical on the rest of the curve.

[citoki]

if you want to give the ordering a try just use a var to store the data and then bringbit back using load_var in a subsequent trace. That subsequent trace can have an empty string as entity (entity: '').

@dbuezas I got it now working with an additional entity, which is copied with the filters from solaredge_m1_exported_kwh and I set the property internal: true. That's working as well and I could set all fill properties to tozeroy and set the width back to 1 for the solaredge_m1_imported_kwh entity.
As from the documentation the data is fetch now for every entity and I have 4 instead of 3, hope this will not cause performance issues someday 😄

updated code with internal entity for data sharing

type: custom:plotly-graph
hours_to_show: 12
refresh_interval: 15
entities:
  - entity: sensor.pv_ac_power_combined_integral
    name: PV Produktion
    statistic: state
    period: auto
    legendgroup: 1
    filters:
      - derivate
      - store_var: pv_ac_power
    line:
      width: 1
      color: lime
      shape: spline
    fill: tozeroy
  - entity: sensor.solaredge_m1_exported_kwh
    internal: true
    statistic: state
    period: auto
    filters:
      - derivate: h
      - map_y: parseFloat(vars.pv_ac_power.ys[i]) - parseFloat(ys[i])
      - store_var: eigenverbrauch
  - entity: sensor.solaredge_m1_imported_kwh
    name: Importiert
    statistic: state
    legendgroup: 3
    period: auto
    filters:
      - derivate
      - map_y: >-
          (parseFloat(y[i-1]) === parseFloat(ys[i])) ? 0 :
          parseFloat(vars.eigenverbrauch.ys[i]) + parseFloat(ys[i])
    line:
      width: 1
      color: orangered
      shape: spline
    fill: tozeroy
  - entity: sensor.solaredge_m1_exported_kwh
    name: Eigenverbrauch
    statistic: state
    legendgroup: 1
    period: auto
    filters:
      - derivate: h
      - map_y: parseFloat(vars.pv_ac_power.ys[i]) - parseFloat(ys[i])
    line:
      width: 1
      color: dodgerblue
      shape: spline
    fill: tozeroy
    fillcolor: lightskyblue

[dbuezas]

Hehe, entities with empty strings as names don't fetch data. And if two traces have the same entity they share a cache. I put so much love into it, that even if both have different time offsets, data will still only be fetched once.
The caching system keeps track of all intervals it has data for for each individual entity. So even if you hide one, then scroll, then show again, only the gaps will be fetched.