How to configure max charge %

[WyndStryke]

Apologies for the half-written title, I can't edit it.

This is a 'how do I configure' type of question. Two interlinked queries - firstly, ideally I don't want the battery going over 90% when either charging overnight, or receiving PV during the day, instead I'd prefer PV to be exported. There is a flat export rate, and it is a big battery, so there is no point in storing PV if the battery is already full enough for the rest of the day. Are there settings to do that?

Is there a way to reserve the top 10% of the SoC range so that it won't be used by PV or by the overnight charge?

Also, it seems to be randomly flicking between the two modes, immediate PV export, or store in the battery for later export. Presumably inverter writes are going up, and also it will be an efficiency loss & unnecessary battery cycles from storing it locally. Hopefully if it knows the top 10% is reserved, it'll just export instead of storing the PV.

Work Mode changed to Feed-in First triggered by action Select: Select
09:19:56 - 20 minutes ago - WyndStryke
Work Mode changed to Self Use triggered by action Select: Select
09:16:07 - 24 minutes ago - Supervisor
Work Mode changed to Feed-in First triggered by action Select: Select
09:09:37 - 30 minutes ago - Supervisor
Work Mode changed to Self Use triggered by action Select: Select
09:09:37 - 30 minutes ago - Supervisor
Work Mode changed to Feed-in First triggered by action Select: Select
09:06:10 - 34 minutes ago - Supervisor
Work Mode changed to Self Use triggered by action Select: Select
08:56:08 - 44 minutes ago - Supervisor
Work Mode changed to Feed-in First
08:47:40 - 1 hour ago
Work Mode changed to Self Use
08:47:30 - 1 hour ago
Work Mode changed to Feed-in First triggered by action Select: Select
08:47:24 - 1 hour ago - Supervisor
Work Mode changed to Self Use triggered by action Select: Select
08:47:11 - 1 hour ago - Supervisor
Work Mode changed to Feed-in First triggered by action Select: Select
07:40:07 - 2 hours ago - WyndStryke
Work Mode changed to Self Use triggered by action Select: Select
07:31:06 - 2 hours ago - Supervisor
Work Mode changed to Feed-in First triggered by action Select: Select
07:02:18 - 3 hours ago - WyndStryke
Work Mode changed to Self Use triggered by action Select: Select
07:01:17 - 3 hours ago - Supervisor
Work Mode changed to Feed-in First triggered by action Select: Select
07:00:24 - 3 hours ago - Supervisor
Work Mode changed to Self Use triggered by action Select: Select
07:00:24 - 3 hours ago - Supervisor

This is on a Fox inverter + battery system.

Feed-in First is the mode where solar is first used for the house load, then used for export, then if the export limit is reached, to change the battery. Self-use is where the solar is used for the house load, then charging the battery, then if the battery is full + overflows, it is exported. I manually set it back to Feed-in First a few times. 'Supervisor' is when it is being set by predbat.

pred_bat:
  module: predbat
  class: PredBat

# MM version for KH7+ECS4300-H4  20241222
# soc_max nominal battery capacity for ECS4300-H4 =16.59kWh   (original was 8.29, maybe for ECS4300-H2)
# battery_rate_max maximum charge/discharge rate, 50A*230V=11500W (note that recommended is 35A, this is handled later) (original was 4200)
# inverter_limit 7000 for KH7 (was 5000, maybe for H1 5000)
# export_limit 7000 (was 3600 commented out, optional in this case since same as inverter_limit)
# inverter_limit_charge/_discharge 8050 (for ECS4300-H4 recommended charge rate 35A * 230v = 8050)
# battery_charge_power_curve for ECS4800, presumably similar to ECS4300, based on 50A max, original was commented out
# rates_import / rates_export as E-on Next Drive + E-on Export
# metric_standing_charge 0.5784 (57.84p)
# rates_export_override +10 at 16:00-19:00 and 22:30-23:45
#
# ### nordpool wholesale prices
#
# carbon_intensity_uk - integration installed
# then input_number.predbat_carbon_metric and switch.predbat_carbon_enable to enable it
#
# Turn on low power mode - switch.predbat_set_charge_low_power
#
# predbat_inverter_loss - 0.02

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

  # Timezone to work in
  timezone: Europe/London

  # Currency, symbol for main currency second symbol for 1/100s e.g. $ c or £ p or e c
  currency_symbols:
    - '£'
    - 'p'

  # 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
  # https://springfall2008.github.io/batpred/apps-yaml/#days_previous
  # Average load data over previous 3 weeks for any given week day.  Homeassistant/configuration.yaml sets history to 22 days.
  days_previous:
  - 7
  - 14
 
  # Number of threads to use in plan calculation
  # Can be auto for automatic, 0 for off or values 1-N for a fixed number
  threads: auto

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

  # Set to auto-match with a GivEnergy serial number, but you can override the serial or the sensor names
  # if it doesn't work or if you have more than one inverter you will need to list both
  #geserial: 're:sensor.givtcp_(.+)_soc_kwh'
  #geserial2: 're:sensor.givtcp2_(.+)_soc_kwh'

  # Sets the maximum period of zero load before the gap is filled, default 30 minutes
  # To disable set it to 1440
  load_filter_threshold: 30

  #
  # Sensors, more than one can be specified and they will be summed up automatically
  #
  # For two inverters the load today would normally be the master load sensor only (to cover the entire house)
  # If you have three phase and one inverter per phase then you would need three load sensors
  #
  # For pv_today if you have multiple solar inverter inputs then you should include one entry for each inverter
  #
  load_today:
    - sensor.load_energy_today
  import_today:
    - sensor.grid_consumption_energy_today
  export_today:
    - sensor.feed_in_energy_today
  pv_today:
    - sensor.solar_energy_today

  # Load forecast can be used to add to the historical load data (heat-pump)
  # To link to Predheat
  # Data must be in the format of 'last_updated' timestamp and 'energy' for incrementing kWh
  #load_forecast:
  #  - predheat.heat_energy$external
  #
  # If you enable ge_cloud_data then the load/import and export data will be fetches from the GE cloud instead of from GivTCP sensors
  # this is usually less efficient and of course prone to internet downtime, but could be useful if you lost your GivTCP data
  # Set the serial to the inverter serial to pull the data from and the key to your API key
  # When this is set load_today, import_today and export_today are not used
  #
  #ge_cloud_data: False
  #ge_cloud_serial: '{geserial}'
  #ge_cloud_key: 'xxxx'
  #
  # Controls/status - must by 1 per inverter
  #
  num_inverters: 1

  inverter_type: FoxESS
  inverter:
    name: "FoxESS"
    has_rest_api: False
    has_mqtt_api: False
    has_service_api: True
    output_charge_control: "power"
    has_charge_enable_time: False
    has_discharge_enable_time: False
    has_target_soc: False
    has_reserve_soc: True
    charge_time_format: "S"
    charge_time_entity_is_option: False
    soc_units: "%"
    num_load_entities: 1
    has_ge_inverter_mode: False
    time_button_press: False
    clock_time_format: "%Y-%m-%d %H:%M:%S"
    write_and_poll_sleep: 2
    has_time_window: False
    support_charge_freeze: true
    support_discharge_freeze: true
#    support_discharge_freeze: True

  # Services to control charging/discharging
# charge_start_service - Should be set to a service that is called when charging starts
  charge_start_service:
    service: select.select_option
    entity_id: select.work_mode
    option: "Force Charge"
#charge_freeze_service - If your inverter supports charge freeze set to a service that starts this mode
#charge_stop_service - Should be set to a service that is called when charging/charge freeze stops
  charge_stop_service:
    service: select.select_option
    entity_id: select.work_mode
    option: "Self Use"
#discharge_start_service - Should be set to a service that is called when force export (discharge) starts
  discharge_start_service:
    service: select.select_option
    entity_id: select.work_mode
    option: "Force Discharge"
#discharge_stop_service - Should be set to a service that is called when export/export freeze stops
  discharge_stop_service:
    service: select.select_option
    entity_id: select.work_mode
    option: "Self Use"
#discharge_freeze_service - If your inverter supports export freeze set to a service that starts this mode
  discharge_freeze_service:
    service: select.select_option
    entity_id: select.work_mode
    option: "Feed-in First"
#
#




  #
  # Run balance inverters every N seconds (0=disabled) - only for multi-inverter
  #balance_inverters_seconds: 60
  #
  # When set use the REST API rather than HA entity for control, should be more reliable/faster to control
  # Set one per inverter
  # If using Docker then change homeassistant.local to the Docker IP address
  #givtcp_rest:
  #  - 'http://homeassistant.local:6345'
  #  - 'http://homeassistant.local:6346'

  # When enabled automatic restart will restart the add-on if communication fails
  # Example below is auto-restart for GivTCP add-on itself
  #auto_restart:
  #  - shell: 'rm -rf /homeassistant/GivTCP/*.pkl'
  #  - service: hassio/addon_restart
  #    addon: a6a2857d_givtcp

  #  Example on how to restart the inverter via GivTCP
  #  - service: switch.turn_on
  #    entity_id: switch.givtcp_{geserial}_reboot_invertor

  # If not using REST then instead set the Control here (one for each inverter)
  # You should keep this section even when using REST as a fallback if it fails and for charge curve calculations
  # bms_charge_rate_estimated template sensor 35*240 (8400W) regardless of the actual result from the integration
  
  # bms_charge_rate available on KH inverters, may need to enable the sensor via settings/integrations/FoxESS/device
  charge_rate:
    - input_number.TonyHoyle_force_charge_power_w 
  discharge_rate:
    - input_number.TonyHoyle_force_discharge_power_w
  battery_power:
    - sensor.invbatpower
  pv_power:
    - sensor.pv_power_w
  load_power:
    - sensor.load_power
  soc_kw:
    - sensor.tonyhoyle_bms_actual_kwh_remaining
  

  soc_percent:
     - sensor.FoxESS_battery_soc_exact
  soc_max:
#    - 8.29   (original, probably ECS4300-H2, guessing this is nominal rather than after DoD%)
    - 16.59
  # battery_rate_max = watts, KH7 50 amps max (battery voltage variable, 85-480, 300 recommended, max DC power 10500, max AC power 14000)
  #                           ECS4300-H4 16.59 nominal capacity, voltage 230.4, recommended discharge 35A (max 50).  35x230.4=8050 but 50x230=11500
  #                           ECS4300-H6 would be 24.8 nominal capacity, voltage 345.6, recommended discharge 35A (max 50).  35x345.6=12096
  # Note that the recommended is 35A but max is 50A.  inverter_limit_charge/_discharge will limit to 35A.
  battery_rate_max:
#    - 4200   (original, probably ECS4300-H2, recommended 35A * 115v)
    - 11500
# Original was commented out .  reserve - sensor name for the reserve setting in %   
# This must never be set to less than 10% (to match 90% DoD), preferably a little higher to be safe
# Also see the predbat setting input_number.predbat_set_reserve_min which should be set to 10 minimum
  reserve:
    - number.min_soc_on_grid
# Original did not contain this line.  Needed since 90% DoD and we must never drop below 10%.
  battery_min_soc:
    - 10
  #inverter_mode:
  #  - select.givtcp_{geserial}_mode
  #inverter_time:
  #  - sensor.givtcp_{geserial}_invertor_time
  #charge_start_time:
  #  - select.givtcp_{geserial}_charge_start_time_slot_1
  #charge_end_time:
  #  - select.givtcp_{geserial}_charge_end_time_slot_1
  #charge_limit:
  #  - number.givtcp_{geserial}_target_soc
  #scheduled_charge_enable:
  #  - switch.givtcp_{geserial}_enable_charge_schedule
  #scheduled_discharge_enable:
  #  - switch.givtcp_{geserial}_enable_discharge_schedule
  #discharge_start_time:
  #  - select.givtcp_{geserial}_discharge_start_time_slot_1
  #discharge_end_time:
  #  - select.givtcp_{geserial}_discharge_end_time_slot_1

  # Inverter max AC limit (one per inverter). E.g for a 3.6kw inverter set to 3600
  # If you have a second inverter for PV only please add the two values together
  inverter_limit:
#    - 5000     (original, Probably H1 5000)
    - 7000

  # 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:
   - 7000
  # - 3600    (original, was commented out)

  # 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

# This models the difference between the max charge rate and recommended charge rate. Max=50A, and recommended = 35A on ECS4300-H4, 230v, = 8050.
# Might be beneficial to drop charge rate below the recommended 8050 to protect from battery degradation.
  inverter_limit_charge:
   - 7000

  inverter_limit_discharge:
   - 7000

  # Workaround to limit the maximum reserve setting, some inverters won't allow 100% to be set
  # Comment out if your inverter allows 100%
  #inverter_reserve_max : 98

  # 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)
  # The example below is from GE 9.5kwh battery with latest firmware and gen1 inverter
  #battery_charge_power_curve:
  #  100 : 0.15
  #  99 : 0.15
  #  98 : 0.22
  #  97 : 0.31
  #  96 : 0.42
  #  95 : 0.48
  #  94 : 0.58
  #  93 : 0.68
  #  92 : 0.77
  #  91 : 0.85
  #  90 : 0.94
  #battery_discharge_power_curve:
  #  4: 1.0
### ECS4800 Charge curve with 50amps as 1.0 https://www.foxesscommunity.com/viewtopic.php?p=4554#p4554
### Linear from 80%-97% then drops abruptly.
  battery_charge_power_curve:
    100 : 0.05
    99 : 0.10
    98 : 0.20
    97 : 0.32
    96 : 0.36
    95 : 0.40
    94 : 0.44
    93 : 0.48
    92 : 0.52
    91 : 0.56
    90 : 0.60
    89 : 0.64
    88 : 0.68
    87 : 0.72
    86 : 0.76
    85 : 0.80
    84 : 0.84
    83 : 0.88
    82 : 0.92
    81 : 0.96

#   (KH register 37618, x10)
  battery_temperature:
   - sensor.bms_cell_temp_low
#
#  # Battery temperature charge adjustment curve
#  # Specific in C which is a multiple of the battery capacity
#  # e.g. 0.33 C is 33% of the battery capacity
#  # values unspecified will be assumed to be 1.0 hence rate is capped by max charge rate
# Battery temperature curve based on recent Fox ESS firmware with 50A as max charge rate.  
#     https://www.youtube.com/watch?v=nDAw0KAYvcE&list=WL&index=86&t=328s
#     <0c 0A, 0-4c 5A, 5-9c 10A, 10-14c 15A, 15-19c 25A, 20-44c 50A, 45-49c 25A, 50-53c 20A, 54,55c 3A, 55c+ 0A
#  battery_temperature_history: sensor.bms_cell_temp_low
#  battery_temperature_charge_curve:
#    19: 0.5
#    18: 0.5
#    17: 0.5
#    16: 0.5
#    15: 0.5
#    14: 0.30
#    13: 0.30
#    12: 0.30
#    11: 0.30
#    10: 0.30
#    9: 0.20
#    8: 0.20
#    7: 0.20
#    6: 0.20
#    5: 0.20
#    4: 0.10
#    3: 0.10
#    2: 0.10
#    1: 0.10
#    0: 0.00    

  # 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: sensor.solcast_pv_forecast_forecast_today
  pv_forecast_tomorrow: sensor.solcast_pv_forecast_forecast_tomorrow
  pv_forecast_d3: sensor.solcast_pv_forecast_forecast_day_3
  pv_forecast_d4: sensor.solcast_pv_forecast_forecast_day_4

  # 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)'

  # Defines the number of cars modelled by the system, set to 0 for no car
  num_cars: 0

  # 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_ready_time: 're:(time.octopus_energy_([0-9a-z_]+|)_intelligent_target_time)'
  octopus_charge_limit: 're:(number.octopus_energy([0-9a-z_]+|)_intelligent_charge_target)'

  # Example alternative configuration for Ohme integration release >=v0.6.1
  # octopus_intelligent_slot: 'binary_sensor.ohme_slot_active'
  # octopus_ready_time: 'time.ohme_target_time'
  # octopus_charge_limit: 'number.ohme_target_percent'

  # 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

  # Octopus free session points to the free session Sensor in the Octopus plugin
  # Note: You must enable this event sensor in the Octopus Integration in Home Assistant for it to work
  octopus_free_session: 're:(event.octopus_energy_([0-9a-z_]+|)_octoplus_free_electricity_session_events)'

  # 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 import and export sensors
  # automatically matches your meter number assuming you have only one (no need to edit the below)
  # Will be ignored if you don't have the sensor but will error if you do have one and it's incorrect
  # NOTE: To get detailed energy rates you need to go in and manually enable the following events in HA
  #       event.octopus_energy_electricity_xxxxxxxx_previous_day_rates
  #       event.octopus_energy_electricity_xxxxxxxx_current_day_rates
  #       event.octopus_energy_electricity_xxxxxxxx_next_day_rates
  # and if you have export enable:
  #       event.octopus_energy_electricity_xxxxxxxx_export_previous_day_rates
  #       event.octopus_energy_electricity_xxxxxxxx_export_current_day_rates
  #       event.octopus_energy_electricity_xxxxxxxx_export_next_day_rates
  # Predbat will automatically find the event. entities from the link below to the sensors
  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 in pounds, can be set to a sensor or manually entered (e.g. 0.50 is 50p)
  # The default below will pick up the standing charge from the Octopus Plugin
  # The standing charge only impacts the cost graphs and doesn't change the way Predbat plans
  # If you don't want to show the standing charge then just delete this line or set to zero
  # metric_standing_charge: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_standing_charge)'
  metric_standing_charge: 0.5784

  # 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 zero rate
  #rates_import:
  #  -  start: "00:30:00"
  #     end: "04:30:00"
  #     rate: 7.5
  #  -  start: "04:30:00"
  #     end: "00:30:00"
  #     rate: 40.0
  #
  #rates_export:
  #  -  rate: 4.2

  ### MM E-on Next Drive import (update as needed)
  ### Tariff name	Next Drive Fixed V5 Gas
  ### Starts from	12:00 AM, 31st Dec 2024
  ### Electricity
  ### Day rate	25.41p per kWh
  ### Night rate	6.70p per kWh
  ### Standing charge	57.84p per day
  ### Gas
  ### Unit rate	6.06p per kWh
  ### Standing charge	31.39p per day
  rates_import:
    -  start: "00:00:00"
       end: "07:00:00"
       rate: 6.7
    -  start: "07:00:00"
       end: "00:00:00"
       rate: 25.41
  
  rates_export:
    -  rate: 16.5
  
  ### MM Encourage export at peak time and before cheap rate period, discorage export during cheap period
  #rates_export_override:
#  - start: '00:00:00'
#    end: '07:00:00'
#    rate_increment: -2
#  - start: '16:00:00'
#    end: '19:00:00'
#    rate_increment: 2
#  - start: '22:30:00'
#    end: '23:45:00'
#    rate_increment: 4


# Tariff comparison feature
  # Adjust this list to the tariffs you want to compare, include your current tariff also
  compare_list:
    - id: 'current'
      name: 'Current Tariff'
#    - id: 'igo_fixed'
#      name: 'Intelligent GO import/Fixed export'
#      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-BB-VAR-23-03-01/electricity-tariffs/E-1R-INTELLI-BB-VAR-23-03-01-J/standard-unit-rates/'
#      rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-BB-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-BB-24-10-26-J/standard-unit-rates/'
#    - id: 'igo_agile'
#      name: 'Intelligent GO import/Agile export'
#      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-BB-VAR-23-03-01/electricity-tariffs/E-1R-INTELLI-BB-VAR-23-03-01-J/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-J/standard-unit-rates/'
    - id: 'go_fixed'
      name: 'GO import/Fixed export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/GO-VAR-BB-23-02-07/electricity-tariffs/E-1R-GO-VAR-BB-23-02-07-J/standard-unit-rates/'
      rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-BB-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-BB-24-10-26-J/standard-unit-rates/'
    - id: 'go_agile'
      name: 'GO import/Agile export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/GO-VAR-BB-23-02-07/electricity-tariffs/E-1R-GO-VAR-BB-23-02-07-J/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-J/standard-unit-rates/'
    - id: 'agile_fixed'
      name: 'Agile import/Fixed export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-24-10-01/electricity-tariffs/E-1R-AGILE-24-10-01-J/standard-unit-rates/'
      rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-BB-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-BB-24-10-26-J/standard-unit-rates/'
    - id: 'agile_agile'
      name: 'Agile import/Agile export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-24-10-01/electricity-tariffs/E-1R-AGILE-24-10-01-J/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-J/standard-unit-rates/'
    - id: 'flux'
      name: 'Flux import/Export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/FLUX-IMPORT-23-02-14/electricity-tariffs/E-1R-FLUX-IMPORT-23-02-14-J/standard-unit-rates'
      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-J/standard-unit-rates'
#    - id: 'cosy_fixed'
#      name: 'Cosy import/Fixed export'
#      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/COSY-22-12-08/electricity-tariffs/E-1R-COSY-22-12-08-J/standard-unit-rates'
#      rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-BB-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-BB-24-10-26-J/standard-unit-rates/'
#    - id: 'cosy_agile'
#      name: 'Cosy import/Agile export'
#      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/COSY-22-12-08/electricity-tariffs/E-1R-COSY-22-12-08-J/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-J/standard-unit-rates/'
    - id: 'snug_fixed'
      name: 'Snug import/Fixed export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/SNUG-24-11-07/electricity-tariffs/E-1R-SNUG-24-11-07-J/standard-unit-rates/'
      rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-BB-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-BB-24-10-26-J/standard-unit-rates/'
    - id: 'iflux'
      name: 'Intelligent Flux import/Export'
      rates_import_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-FLUX-IMPORT-23-07-14/electricity-tariffs/E-1R-INTELLI-FLUX-IMPORT-23-07-14-J/standard-unit-rates/'
      rates_export_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-FLUX-EXPORT-23-07-14/electricity-tariffs/E-1R-INTELLI-FLUX-EXPORT-23-07-14-J/standard-unit-rates/'

  

  # 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: 112
  #    load_scaling: 0.8

  # 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 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
  # Include one value for each days_previous value, each weighting on a separate line.
  # If any days_previous's that are not given a weighting they will assume a default weighting of 1.
  days_previous_weight:
    - 1

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

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

  # 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
  # One per inverter
  battery_scaling:
    - 0.9

  # 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
  # Gas rates for comparison
  #metric_octopus_gas: 're:(sensor.(octopus_energy_|)gas_[0-9a-z]+_[0-9a-z]+_current_rate)'

  # Nordpool market energy rates
  #futurerate_url: 'https://dataportal-api.nordpoolgroup.com/api/DayAheadPrices?date=DATE&market=N2EX_DayAhead&deliveryArea=UK&currency=GBP'
  #futurerate_adjust_import: True
  #futurerate_adjust_export: False
  #futurerate_peak_start: "16:00:00"
  #futurerate_peak_end: "19:00:00"
  #futurerate_peak_premium_import: 14
  #futurerate_peak_premium_export: 6.5

  # Watch list, a list of sensors to watch for changes and then update the plan if they change
  # This is useful for things like the Octopus Intelligent Slot sensor so that the plan update as soon as you plugin in
  # Only uncomment the items you actually have set up above in apps.yaml, of course you can add your own as well
  # Note those using +[] are lists that are appended to this list, whereas {} items are single items only
  #watch_list:
  #  - '{octopus_intelligent_slot}'
  # - '{octopus_ready_time}'
  # - '{octopus_charge_limit}'
  #  - '{octopus_saving_session}'
  #  - '+[car_charging_planned]'
  #  - '+[car_charging_soc]'
  #  - '{car_charging_now}'
  
  # Carbon Intensity data from National grid
carbon_intensity: 're:(sensor.carbon_intensity_uk)'

predbat_plan (2).zip

predbat_debug (2).zip

[gcoan]

I've edited the title for you 😉

Trying to answer your questions:

Predbat doesn't really have a concept of 'reserve top X% and don't use it', it will charge the battery as much as is needed for the predicted future load. So saying that, if Predbat doesn't see that you need the PV generation stored then it will let it be exported rather than charging the battery unnecessarily.
So you might be able to get Predbat to do something like what you want by increasing the plan forecast duration (input_number.predbat_forecast_plan_hours)

You could also look at setting soc_max in apps.yaml to a lower value but I suspect this will only take an effect when force charging the battery. For solar charging Predbat lets the inverter manage things.

In terms of plan oscillation, this is probably due to the plan being quite tightly balanced as to whether its worth exporting or storing the PV. You could increase metric min improvement export to say 5p or higher to encourage it only to export if its financially worthwhile. I also find having the cloud model enabled can cause the plan to oscillate when PV50 and PV10 are not close together, so I turned the cloud model off to prevent this

[WyndStryke]

Many thanks :-)

Hypothetically, do you think it would be worth doing a feature-request to automatically always export solar for slots where the export rate is = the best export rate, and when the SoC is above some user defined limit, or does Trefor already have enough on his plate as it is?

Currently it goes through the optimisation process to decide, but that just adds unpredictability. If it is a simple switch it gets rid of any plan oscillation ... It'd benefit people with flat rate export and batteries bigger than their typical usage. It wouldn't help people with other types of export tariff or smaller batteries who would need the optimisation functionality to figure out if the solar needs to be time-shifted.

[gcoan]

Yes I think Trefor has enough on his plate already ! There are some longer term things like clipping and improved support for multiple inverter plans and preventing cross charging that I personally wish would get to the fore ...

But, there's no harm in adding a FR in. I'd suggest you keep it simple, if there are too many bits to the decision logic then it becomes hard for people to understand and quite niche.

A max soc % would be a simple concept, to stop charging the battery (solar or grid) when a specified percentage is reached would meet your needs, and would help with #1206 clipping as well as it could be dynamically changed

[WyndStryke]

Hopefully this FR ticket makes sense :-)

#2128

[gcoan]

Looks good, comprehensive rationale of the benefits of it, thanks !

[WyndStryke]

Just as an update - the combination of the max_soc setting you suggested, and fixing hold-charge and freeze-charge has significantly improved things as far as the overnight charging is concerned. No repeatedly hitting the 100% mark overnight, which was one of my big concerns (particularly from a battery degradation viewpoint).

During the day it is still sometimes a bit erratic with freeze-export and demand mode (although noticeably improved with recent changes), so I still think the FR has value, particularly from a clipping and solar-export-efficiency viewpoint. I actually cheated and hardwired demand mode to be the same as freeze-export, but that isn't something I'd recommend given that it'd confuse predbat's planning quite a bit. Since the update, it's been sticking to freeze-export 95% of the time now, rather than the 70% that it was previously, so I could probably remove that hardwiring without too much concern.

What I'm actually trying to do at the moment is come up with an improved template for the fox inverters - E-on Drive is really quite simple and doesn't need the level of sophistication that Predbat brings (I have my own homebrew scheduler which does it fine), but the better the template, the better the experience for everyone who uses Fox, and in any case I'm sure that tariffs will change and I'll inevitably end up on something more difficult that needs Predbat's intelligence. I quite want to get the carbon optimisation going, tried on and off for ages with no luck, that's something which my homebrew scheduler simply will never be capable of.