SolarEdge load_today monitoring and documentation/template

[jrviz]

The template/documentation for SolarEdge inverter says load_today should be set to sensor.solaredge_i1_ac_energy_kwh

I have for a while been a bit concerned that my evening load forecast have been far too high and was not sure why. I have now seen a discussion elsewhere which said sensor.solaredge_i1_ac_energy_kwh includes battery discharge which would explain my incorrect forecasts. I had implemented the additional power sensors from @Ashpork but had not used one of these values in load_today

What are other SolarEdge configurations using?

If there is a clear answer on this then perhaps the template / documentation needs an update.

[Noodleyman]

I think the docs were out of date.

I'm using what is described here, seems to work OK for me.

https://springfall2008.github.io/batpred/inverter-setup/

Here is my full config file in case it's helpful.

pred_bat:
  module: predbat
  class: PredBat

  # Sets the prefix for all created entities in HA - only change if you want to run more than once instance
  prefix: predbat

  # XXX: This is a configuration template, delete this line once you edit your configuration
  # template: True

  # Timezone to work in
  timezone: Europe/London

  #
  # Sensors, currently more than one can be specified and they will be summed up automatically
  # however if you have two inverters only set one of them as they will both read the same.
  #
  load_today:
    - sensor.solar_house_consumption_kwh
    #- sensor.solaredge_i1_ac_energy
    #- sensor.solaredge_i1_ac_energy_kwh
  import_today:
    - sensor.solaredge_m1_imported
    #- sensor.solaredge_m1_imported_kwh
  export_today:
    - sensor.solaredge_m1_exported
    #- sensor.solaredge_m1_exported_kwh
  pv_today:
    - sensor.solar_panel_production_kwh   # This is a custom sensor - see Readme on how to create or comment out
  #
  # Controls/status - must by 1 per inverter
  #
  num_inverters: 1
  # Inverter type stubbed to SX4 to allow execution - SE is an invalid type in current head version
  inverter_type: "SE"

  # Can be enabled if you have a backup interface
  inverter:
    has_reserve_soc: True
    support_charge_freeze: False
    support_discharge_freeze: False

  battery_rate_max:
    #- sensor.solaredge_b1_max_charge_power
    - sensor.calc_power_batteries_max_charge_power
  charge_rate:
    - number.solaredge_i1_storage_charge_limit
  discharge_rate:
    - number.solaredge_i1_storage_discharge_limit
  battery_power:
    #- sensor.solaredge_b1_dc_power
    - sensor.calc_power_batteries_dc_power
  pv_power:
    - sensor.solar_panel_production_w # This is a custom sensor - see Readme on how to create or comment out
  load_power:
    - sensor.solar_house_consumption_w # This is a custom sensor - see Readme on how to create or comment out

    # This is a helper sensor, to help avoid predbat from stopping charing when B1SoE reaches 100%, because SolarEdge Inv/Batteries often charge whilst at 100% SoE. 
    # Whilst charging at 100% you'll often find the "b1_available_energy" increasing as it adjusts what it considers the definition of 100%
    #This sensor helper employs the below template:
        # {% set b1_Status_isCharge = is_state('sensor.solaredge_b1_status', 'B_STATUS_CHARGE' ) %}
        # {% set b1_Status_PreserveCharge = is_state('sensor.solaredge_b1_status', 'B_STATUS_PRESERVE_CHARGE' ) %}
        # {% set b1_SoE_roundDown = float(states('sensor.solaredge_b1_state_of_energy'))|round(0, 'floor') %}
        # {% if b1_Status_isCharge and b1_SoE_roundDown > 98 %}
        # 98
        # {% elif b1_Status_PreserveCharge and b1_SoE_roundDown >= 97 %}
        # 100
        # {%- else -%}
        # {{b1_SoE_roundDown }}{##states('sensor.solaredge_b1_state_of_energy')##}
        # {%- endif %}
    
  soc_percent:
    # - sensor.solar_b1_rounddown_soe
    - sensor.calc_battery_all_state
  soc_max:
    # - sensor.solaredge_b1_maximum_energy
    - sensor.calc_battery_total_capacity
  # Can be enabled you have a backup interface
  reserve:
    - number.solaredge_i1_backup_reserve
  charge_start_time:
   - "02:00:00"
  charge_end_time:
   - "05:00:00"
  charge_limit:
   - number.solaredge_i1_ac_charge_limit
  scheduled_charge_enable:
   - off
  scheduled_discharge_enable:
   - off
  discharge_start_time:
   - "18:30:00"
  discharge_end_time:
   - "19:00:00"

  # Services to control charging/discharging
  #charge_start_service:
    #service: select.select_option
    #entity_id: "select.solaredge_i1_storage_command_mode"
    #option: "Charge from Solar Power and Grid"
  #charge_freeze_service:
   # - service: select.select_option
    #  entity_id: "select.solaredge_i1_storage_command_mode"
#      option: "Charge from Clipped Solar Power"    
  #charge_stop_service:
   # service: select.select_option
    #entity_id: "select.solaredge_i1_storage_command_mode"
    #option: "Maximize Self Consumption"
  #discharge_freeze_service:
   # - service: select.select_option
    #  entity_id: "select.solaredge_i1_storage_command_mode"
     # option: "Maximize Self Consumption"    
  #discharge_start_service:
   # service: select.select_option
    #entity_id: "select.solaredge_i1_storage_command_mode"
    #option: "Discharge to Maximize Export"
    
  # Services to control charging/dischargingng the command, in the event that the solar edge integration doesn't accept the command
  charge_start_service:
    - service: select.select_option
      entity_id: "select.solaredge_i1_storage_default_mode"
      option: "Charge from Solar Power and Grid"
      always: True

  charge_freeze_service:
    - service: select.select_option
      entity_id: "select.solaredge_i1_storage_default_mode"
      option: "Charge from Clipped Solar Power"
      always: True

  discharge_start_service:
    - service: select.select_option
      entity_id: "select.solaredge_i1_storage_default_mode"
      option: "Discharge to Maximize Export"
      always: True

  discharge_freeze_service:
    - service: select.select_option
      entity_id: "select.solaredge_i1_storage_default_mode"
      option: "Maximize Self Consumption"

  charge_stop_service:
    - service: select.select_option
      entity_id: "select.solaredge_i1_storage_default_mode"
      option: "Maximize Self Consumption"

  discharge_stop_service:
    - service: select.select_option
      entity_id: "select.solaredge_i1_storage_default_mode"
      option: "Maximize Self Consumption"    
    

  # Inverter max AC limit (one per inverter)
  # If you have a second inverter for PV only please add the two values together
  #inverter_limit:
  # - 3600
  # - 3600
  # Export limit is a software limit set on your inverter that prevents exporting above a given level
  # When enabled Predbat will model this limit
  export_limit:
    - 3680
  #  - 3670
  #
  # The maximum rate the inverter can charge and discharge the battery can be overwritten, this will change
  # the register programming and thus cap the max rates. The default is to use the maximum supported rates (recommended)
  #
  inverter_limit_charge:
    - 7200
  inverter_limit_discharge:
    - 10000


  # Some inverters don't turn off when the rate is set to 0, still charge or discharge at around 200w
  # The value can be set here in watts to model this (doesn't change operation)
  #inverter_battery_rate_min:
  #  - 200

  # Some batteries tail off their charge rate at high soc%
  # enter the charging curve here as a % of the max charge rate for each soc percentage.
  # the default is 1.0 (full power)
  battery_charge_power_curve:
    91 : 0.91
    92 : 0.81
    93 : 0.71
    94 : 0.62
    95 : 0.52
    96 : 0.43
    97 : 0.33
    98 : 0.24
    99 : 0.24
    100 : 0.24

  # Inverter clock skew in minutes, e.g. 1 means it's 1 minute fast and -1 is 1 minute slow
  # Separate start and end options are applied to the start and end time windows, mostly as you want to start late (not early) and finish early (not late)
  # Separate discharge skew for discharge windows only
  inverter_clock_skew_start: 0
  inverter_clock_skew_end: 0
  inverter_clock_skew_discharge_start: 0
  inverter_clock_skew_discharge_end: 0

  # Clock skew adjusts the Appdaemon time
  # This is the time that Predbat takes actions like starting discharge/charging
  # Only use this for workarounds if your inverter time is correct but Predbat is somehow wrong (AppDaemon issue)
  # 1 means add 1 minute to AppDaemon time, -1 takes it away
  clock_skew: 0

  # Set these to match solcast sensor names
  # The regular expression (re:) makes the solcast bit optional
  # If these don't match find your own names in Home Assistant
  pv_forecast_today: re:(sensor.(solcast_|)(pv_forecast_|)forecast_today)
  pv_forecast_tomorrow: re:(sensor.(solcast_|)(pv_forecast_|)forecast_tomorrow)
  pv_forecast_d3: re:(sensor.(solcast_|)(pv_forecast_|)forecast_(day_3|d3))
  pv_forecast_d4: re:(sensor.(solcast_|)(pv_forecast_|)forecast_(day_4|d4))

  # car_charging_energy defines an incrementing sensor which measures the charge added to your car
  # is used for car_charging_hold feature to filter out car charging from the previous load data
  # Automatically set to detect Wallbox and Zappi, if it doesn't match manually enter your sensor name
  # Also adjust car_charging_energy_scale if it's not in kwH to fix the units
  car_charging_energy: 're:(sensor.myenergi_zappi_[0-9a-z]+_charge_added_session|sensor.wallbox_portal_added_energy)'

  num_cars: 0

  # car_charging_planned is set to a sensor which when positive indicates the car will charged in the upcoming low rate slots
  # This should not be needed if you use Octopus Intelligent Slots which will take priority if enabled
  # The list of possible values is in car_charging_planned_response
  # Auto matches Zappi and Wallbox, or change it for your own
  car_charging_planned:
    - 're:(sensor.wallbox_portal_status_description|sensor.myenergi_zappi_[0-9a-z]+_plug_status)'
    - 'connected'

  car_charging_planned_response:
    - 'yes'
    - 'on'
    - 'true'
    - 'connected'
    - 'ev connected'
    - 'charging'
    - 'paused'
    - 'waiting for car demand'
    - 'waiting for ev'
    - 'scheduled'
    - 'enabled'
    - 'latched'
    - 'locked'
    - 'plugged in'

  # To make planned car charging more accurate, either using car_charging_planned or Octopus Intelligent
  # specify your battery size in kwh, charge limit % and current car battery soc % sensors/values
  # If you have intelligent the battery size and limit will be extracted from Intelligent directly
  # Set the car SOC% if you have it to give an accurate forecast of the cars battery levels
  # One entry per car if you have multiple cars
  car_charging_battery_size:
    - 75
  car_charging_limit:
    - 're:number.tsunami_charge_limit'
  car_charging_soc:
    - 're:sensor.tsunami_battery'

  # Octopus saving session points to the saving session Sensor in the Octopus plugin, when enabled saving sessions will be at the assumed
  # Rate is read automatically from the add-in and converted to pence using the conversion rate below (default is 8)
  octopus_saving_session: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_saving_session(s|))'
  octopus_saving_session_octopoints_per_penny: 8

  # If you have Octopus intelligent, enable the intelligent slot information to add to pricing
  # Will automatically disable if not found, or comment out to disable fully
  # When enabled it overrides the 'car_charging_planned' feature and predict the car charging based on the intelligent plan (unless octopus intelligent charging is False)
  # This matches either the intelligent slot from the Octopus Plugin or from the Intelligent plugin
  #octopus_intelligent_slot: 're:(binary_sensor.octopus_intelligent_slot|re:binary_sensor.octopus_energy_intelligent_dispatching)'
  octopus_intelligent_slot: 're:binary_sensor.octopus_energy_intelligent_dispatching'
  octopus_ready_time: 're:time.octopus_energy_intelligent_ready_time'
  octopus_charge_limit: 're:number.octopus_energy_intelligent_charge_limit'

  # Energy rates
  # Please set one of these three, if multiple are set then Octopus is used first, second rates_import/rates_export and latest basic metric

  # Set import and export entity to point to the Octopus Energy plugin
  # automatically matches your meter number assuming you have only one
  # Will be ignored if you don't have the sensor
  # Or manually set it to the correct sensor names e.g:
  # sensor.octopus_energy_electricity_xxxxxxxxxx_xxxxxxxxxxxxx_current_rate
  # sensor.octopus_energy_electricity_xxxxxxxxxx_xxxxxxxxxxxxx_export_current_rate
  #metric_octopus_import: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_rate)'
  #metric_octopus_export: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_export_current_rate)'

  # Standing charge can be set to a sensor (e.g. Octopus) or manually entered in pounds here (e.g. 0.50 is 50p)
  #metric_standing_charge: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_standing_charge)'
  metric_standing_charge: 0.6812

  # Or set your actual rates across time for import and export
  # If start/end is missing it's assumed to be a fixed rate
  # Gaps are filled with 0
  rates_import:
    -  start: "00:00:00"
       end: "06:59:59"
       rate: 6.7
    -  start: "07:00:00"
       end: "23:59:59"
       rate: 24.36

  rates_export:
    -  start: "00:00:00"
       end: "04:59:59"
       rate: 0
    -  start: "07:00:00"
       end: "23:59:59"
       rate: 16.5
  # Can be used instead of the plugin to get import rates directly online
  # Overrides metric_octopus_import and rates_import
  # rates_import_octopus_url : "https://api.octopus.energy/v1/products/FLUX-IMPORT-23-02-14/electricity-tariffs/E-1R-FLUX-IMPORT-23-02-14-A/standard-unit-rates"
  # rates_import_octopus_url : "https://api.octopus.energy/v1/products/AGILE-FLEX-BB-23-02-08/electricity-tariffs/E-1R-AGILE-FLEX-BB-23-02-08-A/standard-unit-rates"

  # Overrides metric_octopus_export and rates_export
  # rates_export_octopus_url: "https://api.octopus.energy/v1/products/FLUX-EXPORT-BB-23-02-14/electricity-tariffs/E-1R-FLUX-EXPORT-BB-23-02-14-A/standard-unit-rates"
  # rates_export_octopus_url: "https://api.octopus.energy/v1/products/AGILE-OUTGOING-BB-23-02-28/electricity-tariffs/E-1R-AGILE-OUTGOING-BB-23-02-28-A/standard-unit-rates/"
  # rates_export_octopus_url: "https://api.octopus.energy/v1/products/OUTGOING-FIX-12M-BB-23-02-09/electricity-tariffs/E-1R-OUTGOING-FIX-12M-BB-23-02-09-A/standard-unit-rates/"

  # Import rates can be overridden with rate_import_override
  # Export rates can be overridden with rate_export_override
  # Use the same format as above, but a date can be included if it just applies for a set day (e.g. Octopus power ups)
  # This will override even the Octopus plugin rates if enabled
  #
  #rates_import_override:
  # -  date: '2023-09-10'
  #    start: '14:00:00'
  #    end: '14:30:00'
  #    rate: 5
  #rates_import_override:
  # -  date: '2024-10-20'
  #    start: '13:00:00'
  #    end: '14:00:00'
  #    rate: 0

  # For pv estimate, leave blank for central estimate, or add 10 for 10% curve (worst case) or 90 or 90% curve (best case)
  # If you use 10 then disable pv_metric10_weight below
  # pv_estimate: 10

  # Days previous is the number of days back to find historical load data
  # Recommended is 7 to capture day of the week but 1 can also be used
  # if you have more history you could use 7 and 14 (in a list) but the standard data in HA only lasts 10 days
  days_previous:
    - 2
    - 3
    - 4
    - 5
    - 6
    - 7
    - 8

  # Days previous weight can be used to control the weighting of the previous load points, the values are multiplied by their
  # weights and then divided through by the total weight. E.g. if you used 1 and 0.5 then the first value would have 2/3rd of the weight and the second 1/3rd
  days_previous_weight:
    - 1
    - 0.8
    - 0.7
    - 0.6
    - 0.5
    - 0.4
    - 0.3

  # Number of hours forward to forecast, best left as-is unless you have specific reason
  forecast_hours: 48

  # The number of hours ahead to count in charge planning (for cost estimates)
  # It's best to set this on your charge window repeat cycle (24) but you may want to set it higher for more variable
  # tariffs like Agile
  forecast_plan_hours: 24

  # Specify the devices that notifies are sent to, the default is 'notify' which goes to all
  #notify_devices:
  #  - mobile_app_treforsiphone12_2

  # Set the frequency in minutes that this plugin is run
  # recommend something that divides by 60 (5, 10 or 15) or you won't trigger at the start of energy price slots
  run_every: 5

  # Battery scaling makes the battery smaller (e.g. 0.9) or bigger than its reported
  # If you have an 80% DoD battery that falsely reports it's kwh then set it to 0.8 to report the real figures
  battery_scaling: 1.0

  # Can be used to scale import and export data, used for workarounds
  import_export_scaling: 1.0

  # Export triggers:
  # For each trigger give a name, the minutes of export needed and the energy required in that time
  # Multiple triggers can be set at once so in total you could use too much energy if all run
  # Creates an entity called 'binary_sensor.predbat_export_trigger_<name>' which will be turned On when the condition is valid
  # connect this to your automation to start whatever you want to trigger
  export_triggers:
     - name: 'large'
       minutes: 60
       energy: 1.0
     - name: 'small'
       minutes: 15
       energy: 0.25

  # If you have a sensor that gives the energy consumed by your solar diverter then add it here
  # this will make the predictions more accurate. It should be an incrementing sensor, it can reset at midnight or not
  # It's assumed to be in Kwh but scaling can be applied if need be
  #iboost_energy_today: 'sensor.xxxxx'
  #iboost_energy_scaling: 1.0

[jrviz]

Thanks. I moved over to sensor.solar_house_consumption_kwh and my load forecasts are much more sensible. This needs updating in the template referenced in the documentation and the calculated sensors (in configuration.yaml) need to be a bit more consistent in terms of the instruction on what to do to accommodate multiple batteries. I'll have a go at drafting something for other to check

[jrviz]

@Noodleyman I see in your apps.yaml you have inverter_limit_charge and discharge as well as a battery curve set. I have these commented out (as per current documented template). Were there reasons you changed these?

[Noodleyman]

Morning.

Glad that worked for you. I have two batteries in my setup. It's working well with the combined senseor approach per the documentation. I've not yet found a reason to modify the dual battery setup config.

inverter_limit_charge is set, because I have two batteries. When charging from the grid, that can pull 10kWh via the circuit breaker, which is currently rated to 32A. 10kWh = 43.5A, so it can trip out the breaker. I'll be swapping out the MCB for something higher rated at some point soon. We also have a flakey grid and the DNO is quite restrictive with import/export. In winter, with a full b attery charge, and other background usage we may likely exceed their import limits. so I've set this proeprty for now. that property does come with an issue, which I've raised here:
#2449

Import Limit is not the same as charge limit. there isn't a way to define both at the moment that I know of. If I left it at 10,000 my charge plans were wrong because it doesn't know of the grid import limit. The downside is I'm also limiting my charge throughput from PV to 7.2kWh, where as it can do 10. It's also why I have a rather annoying 3.68kWh export limit.

I set discharge to 10,000, which is the max my two combined batteries can provide. I have an 8kW inverter. I think with SE inverters, it will default to over 11kW, which may cause the plans to be incorrect. I would just set the values to whatever you have for your system. 1 battery - 5k, 2=10k, 3=11.xK (I can't recall the exact 11.x value, thus x)

Predbat is changing:
number.solaredge_i1_storage_charge_limit and number.solaredge_i1_storage_discharge_limit on the fly depending on what it wants to do.

The curve is important for the calculations. The values I am using are my own estimates based upon the inverter documentation and personal observations. SE kit does tail off the charge rate at higher SOC's, although on reflection I think my curve is totally wrong. I wasn't aware that this curve would get calculated for you. I guess that's a new feature since I set this up a long time ago. so I've just commented that out today. thanks for pointing that out :)

[Noodleyman]

forgot to add. the file I shared as well, I was playing around with my rate schedules. I get midnight to 7AM at 6.7p import, and can export at 16.5p 24/7.

I zero out the export for a few hours in the charge window to avoid it going nuts so I get a stable charge. Import/Export/Import/Export. But, I've been bringing my export window forward to get in some earlier export options to max the export revenue. very important with minimal export limits :)