Adding Victron Multiplus as an inverter

[persil1971]

Victron Multiplus and other inverters have an integration to Home Assistant already and also have available MQTT and Modbus over TCP interfaces. Would it be possible to add this to a development queue for future integration? I have implemented predbat with GivTCP and GivEnergy for friends but developing an integration is not something I can do!

[Cameleon99]

I just came here to see if anyone has done this. I have a lot of control over my MPII from HA for saving sessions and such already but would like to get PredBat working and move to Agile.

I'm somewhat struggling to understand the documentation in whats required for non-Giv inverters. It looks like I already have a lot of HA entities for whats required (house/car/solar/export/etc) for a template but struggling to stitch it together.

[nicobresseleers]

+1 for me.. i am now using the Victron ESS/DESS but would like to take it into HA
.

[steviloidz]

+1 for me too. I'm surprised Victron isn't supported,

[gcoan]

It needs someone with a Victron inverter to work out what the entities for SoC, current state, discharge rate, etc and control commands are to charge, discharge, hold charge, etc.

There's at least 4 people here who have Victron inverters, the author of Predbat doesn't, so it's really up the community to work it out. This is how all the non-GivEnergy inverters have been added

Instructions on adding a new inverter type are in the documentation https://springfall2008.github.io/batpred/inverter-setup/#. The formatting has got messed up, but it starts half way through the Sigstore entry: https://springfall2008.github.io/batpred/inverter-setup/#sigenergy-sigenstor

[DirkB19]

Did someone already got this working. If so please share the yaml to show the entities we need to use....eg with latest HA integration that talks to Victron over MQTT

[nicobresseleers]

Yes, I am reporting Victron via MQTT now... adding the sensor in config yaml (the one you use) .. to now the sensor to read i use mqtt-explorer... pretty easy
examples:

AC Current NET

• state_topic: "victron/N/b827eb0c9fb5/grid/30/Ac/Current"
  name: "AC Current NET"
  unique_id: "ac_current_NET"
  device_class: current
  value_template: "{{ value_json.value }}"
  unit_of_measurement: "A"
  icon: mdi:current-ac

AC Loads

• state_topic: "victron/N/b827eb0c9fb5/system/0/Ac/Consumption/L1/Power"
  name: "AC Loads"
  unique_id: "ac_loads"
  device_class: power
  value_template: "{{ value_json.value }}"
  unit_of_measurement: "W"
  icon: mdi:power-socket-uk

DC Loads

• name: "DC Loads"
  device_class: power
  unique_id: "dc_loads"
  state_topic: "victron/N/b827eb0c9fb5/system/0/Dc/System/Power"
  value_template: "{{ value_json.value|float(0)|round(0) }}"
  unit_of_measurement: "W"
  icon: mdi:power

[gcoan]

@nicobresseleers can you copy/paste your apps.yaml and template sensor definitions here please so I can. add this to the predbat documentation for others.

But please put three back quotes (`) before and after each section you paste in to stop github trying to format the yaml

thanks

[Billyturkey]

I’ve started testing Victron integration in Predbat, and I’m also running it alongside my existing SolarEdge setup. I’ll raise a proper ticket soon and share the YAML once it’s tidied up, but here’s a quick overview of what I’ve done so far.

Existing setup (before Victron):

• SolarEdge 5 kW inverter
• SolarEdge 9.7 kWh battery
• Predbat integration

New setup (Victron system):

• Victron MultiPlus II 5000 VA
• 2 × Pylontech US5000 batteries
• 250/60 Smart Solar Charger (3.03 kW array)
• GX device
• Victron Energy Meter

I’m running the MultiPlus in ESS mode, with only the AC In connected for testing at the moment. I’ve used the [Victron MQTT integration](https://github.com/tomer-w/ha-victron-mqtt) to bring data into Home Assistant.

For Predbat, I used the existing solaredge.yaml as a base template. I’m still using the SolarEdge meter for readings like “load today” and “export today”, but if you want to use the Victron Energy Meter instead, you’ll need to create a few helpers to tie it into the template. I also referenced the “MINE ” inverter example from the Predbat documentation as a guide.

To control the inverter, I created a select list in Home Assistant with three options:

• Charge Start
• Charge Stop
• Discharge Start

Each option sets a specific AC set-point through the Victron MQTT integration:

• Charge Start → 4500
• Charge Stop → 50
• Discharge Start → –4500

It’s currently running alongside my SolarEdge setup and appears to be working well for charge and discharge control. I’m still seeing a few log warnings — things like “Out of range index 1 within item” — which might be related to how I’ve combined the charge/discharge commands with the SolarEdge control.

[AlexCPU]

I got mine going a couple of days ago, my set up is a little older (from before Victron supported MQTT), so I'm using ModbusTCP to command it to do things, but that's not relevant to the control process (yet).

But ultimately, like you, I'm using the AC set-point to force charging/discharging. One thing to note, is you probably need to use bigger numbers for your set point, if I was charging an EV at 7.4kW and changed the set-point to 4500, the battery would still discharge to power the car, so I'm using 24000 (100A fuse limit).

Maybe @gcoan can help explain, I'm looking at the bits for freeze charging and freeze discharging and can't work out what we should be getting the Multiplus to do. As mentioned, we've got the ability to change the grid setpoint to force charging and discharging, but I've also got the ability to set the max discharge %age (i.e. what %age of rated output the DC/AC inverter will do). Before starting with predbat I've set this to 0 to stop the battery discharging during a cheap period once I've got to the target SoC.

Completely other option @VibroAxe is using setting the minimum SoC to force charging and stop discharging when needed, so we could do that instead.

[jasonyates]

I'd be interested to know how you use MQTT to force a charge. I'm using my Cerbo with a fixed charged schedule over night but I'd like to move that to use HA automations to allow me to force a charge during Octopus free energy sessions and ultimately use batpred to trigger a charge. I too am using [Victron MQTT integration](https://github.com/tomer-w/ha-victron-mqtt) for the Victron integration.

[VibroAxe]

I'd be interested to know how you use MQTT to force a charge. I'm using my Cerbo with a fixed charged schedule over night but I'd like to move that to use HA automations to allow me to force a charge during Octopus free energy sessions and ultimately use batpred to trigger a charge. I too am using [Victron MQTT integration](https://github.com/tomer-w/ha-victron-mqtt) for the Victron integration.

Jason with the mqtt integration set the "ESS Min SOC" and it will immediately start charging (note: this may be a Cerbo GX feature but I think you need that for the mqtt anyway). See my charging automation triggering this repeatedly over the last 24 hours

[Billyturkey]

I’ve had the system running on test for the last four days now, including a weekend where Octopus Agile was actually paying to charge the battery — so as you can imagine, charge and discharge cycles were constant. I’m genuinely impressed with how well it’s working alongside my SolarEdge setup so far.

I did manage to blow a 100A fuse on the Lynx, but that was my own fault for not limiting the discharge properly. I’ve since reduced it to –4000, which seems to keep things stable. I’ve also adjusted the charge stop setpoint to –200 to cover household loads and allow the SolarEdge system to take up the remainder.

If your goal is simply to charge the battery, then setting the ESS Min SOC would likely be the most straightforward approach. But for anyone interested in developing Predbat further, you’ll definitely need the discharge feature enabled if you plan to take advantage of energy trading or tariff optimisation.

Victron provides a useful reference for this in their guide on ESS Modes 2 and 3, which includes the Modbus registers you can also find in MQTT:
https://www.victronenergy.com/live/ess:ess_mode_2_and_3

Next, I’m considering using additional input logic alongside the AC setpoint control to switch between inverter-only and charger-only modes dynamically. Hopefully, we can pull something together to officially integrate Victron into Predbat for wider use.

If anyone has suggestions or ideas for improving this setup, I’m happy to test them on my system and share the results.

[Billyturkey]

Just for info this is the template I have setup in configuration.yaml to bring in the list (vic_ess_mode_select) to apps.yaml. Note the <your_cerbo_gx_id>, put your unquie number in there from Cerbo GX.

template:
  - select:
       - name: "Victron ESS Mode"
         unique_id: vic_ess_mode_select
 
         # (optional) reflect the current label based on the setpoint value
         state: >
           {% set sp = states('number.victron_mqtt_<your_cerbo_gx_id>_system_0_system_ac_power_set_point')|float(0) %}
           {% if sp >= 4500 %}
             Charge Start
           {% elif sp <= -4500 %}
             Discharge Start
           {% elif sp <= 75 %}
             Charge Stop
           {% else %}
             Unknown
           {% endif %}
 
         # options must be a single template that renders a list
         options: >
           {{ ['Charge Start', 'Charge Stop', 'Discharge Start'] }}
 
         # when a user picks an option, run the right branch
         select_option:
           - choose:
               - conditions: "{{ option == 'Charge Start' }}"
                 sequence:
                   - service: number.set_value
                     target:
                       entity_id: number.victron_mqtt_<your_cerbo_gx_id>_system_0_system_ac_power_set_point
                     data:
                       value: 4500
 
               - conditions: "{{ option == 'Charge Stop' }}"
                 sequence:
                   - service: number.set_value
                     target:
                       entity_id: number.victron_mqtt_<your_cerbo_gx_id>_system_0_system_ac_power_set_point
                     data:
                       value: -200
 
               - conditions: "{{ option == 'Discharge Start' }}"
                 sequence:
                   - service: number.set_value
                     target:
                       entity_id: number.victron_mqtt_<your_cerbo_gx_id>_system_0_system_ac_power_set_point
                     data:
                       value: -4500
             default: []

[gcoan]

Guys, are you able to share your apps.yaml and custom config entries to get Victron inverters working with the MQTT HA integration?

I have put a placeholder in the documentation but it needs your content!

[Billyturkey]

Hi Geoffrey,
Sorry I've only just got round to testing Victron as a single inverter. I have used Victron MQTT Integration (https://github.com/tomer-w/ha-victron-mqtt) and used the power setpoint as the charge/discharge start and stop. I've had this running on along side my SolarEdge battery since I first posted and it has been working fine, this week I have tested it solely on it own and works well. I'm going to look to see if its possible to to create a charge/discharge freeze but below is currently as far as I've got, if anyone comes up with any better way of doing it or see any mistakes please share. :)

[gcoan]

great thanks @Billyturkey, looks a fairly simple apps.yaml setup

can you share details of the template helpers as well please and then I can merge it into the documentation

[Billyturkey]

Here's the configuration.yaml template:-

template:
     
  - sensor:
      - name: "GX Grid Import Power"
        unique_id: gx_grid_import_power
        unit_of_measurement: "W"
        device_class: power
        state: >
          {% set p = states('sensor.gx_device_grid_power_l1') | float(0) %}
          {{ max(p, 0) }}

      - name: "GX Grid Export Power"
        unique_id: gx_grid_export_power
        unit_of_measurement: "W"
        device_class: power
        state: >
          {% set p = states('sensor.gx_device_grid_power_l1') | float(0) %}
          {{ max(-p, 0) }}

      - name: "GX Load Power"
        unique_id: gx_load_power
        unit_of_measurement: "W"
        device_class: power
        state: "{{ states('sensor.gx_device_consumption_power_l1') | float(0) }}"

sensor:
  - platform: integration
    source: sensor.gx_grid_import_power
    name: gx_grid_import_energy_total
    unit_prefix: k
    round: 3
    method: left

  - platform: integration
    source: sensor.gx_grid_export_power
    name: gx_grid_export_energy_total
    unit_prefix: k
    round: 3
    method: left

  - platform: integration
    source: sensor.gx_load_power
    name: gx_load_energy_total
    unit_prefix: k
    round: 3
    method: left

utility_meter:
  gx_load_energy_today:
    source: sensor.gx_load_energy_total
    name: GX Load Energy Today
    cycle: daily
  gx_grid_import_energy_today:
    source: sensor.gx_grid_import_energy_total
    name: GX Import Energy Today
    cycle: daily
  gx_grid_export_energy_today:
    source: sensor.gx_grid_export_energy_total
    name: GX Export Energy Today
    cycle: daily

[Billyturkey]

People just need to be wary if they have a three phase system as this sensor (sensor.gx_device_grid_power_l1) could be different.

[Billyturkey]

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

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

  # 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

  # 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
  #
  #Created helper to totalise daily load from consumption sensor
  load_today:
    - sensor.gx_load_energy_today
  #Created helper to totalise daily load from grid sensor, will need logic to distinguish between import and export
  import_today:
    - sensor.gx_grid_import_energy_today
  #Created helper to totalise daily load from grid sensor, will need logic to distinguish between import and export
  export_today:
    - sensor.gx_grid_export_energy_today
  pv_today:
    - sensor.gx_device_pv_energy

  # Victron Inverter Type
  inverter:
    name: "VMP2"
    has_rest_api: False
    has_mqtt_api: False
    has_service_api: True
    output_charge_control: "power"
    charge_control_immediate: False
    current_dp: 0
    charge_discharge_with_rate: False
    has_charge_enable_time: False
    has_discharge_enable_time: False
    has_target_soc: False
    target_soc_used_for_discharge: True
    has_reserve_soc: True
    has_timed_pause: False
    time_button_press: False
    support_charge_freeze: False
    support_discharge_freeze: False
    has_ge_inverter_mode: False
    has_fox_inverter_mode: False
    has_idle_time: False
    has_time_window: False
    charge_time_format: "S"
    charge_time_entity_is_option: False
    can_span_midnight: False
    clock_time_format: "%Y-%m-%d %H:%M:%S"
    num_load_entities: 1
    soc_units: "%"
    write_and_poll_sleep: 2

  # 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
  #
  # Controls/status - must by 1 per inverter
  #
  num_inverters: 1
  inverter_type: VCMP2
  
  # Services to control charging/discharging
  # charge_start_service - Should be set to a service that is called when charging starts
  # This inputs charging setpoint into Victron Multi Plus, your value might be bigger or smaller depending on Inverter size
  charge_start_service:
    service: number.set_value
    entity_id: number.gx_device_ac_power_setpoint
    value: 4000

  # charge_freeze_service - If your inverter supports charge freeze set to a service that starts this mode
  # The Back-up work mode does not exist on older firmware versions
  #charge_freeze_service:
  #  service: select.select_option
  #  entity_id: select.foxess_work_mode
  #  option: "Back-up"

  # charge_stop_service - Should be set to a service that is called when charging/charge freeze stops
  # This inputs charging setpoint into Victron Multi Plus, 50W is recommended so you dont drain battery into grid
  charge_stop_service:
    service: number.set_value
    entity_id: number.gx_device_ac_power_setpoint
    value: 50

  # discharge_start_service - Should be set to a service that is called when force export (discharge) starts
  # This inputs negative charging setpoint into Victron Multi Plus, your value might be bigger or smaller depending on Inverter size
  discharge_start_service:
    service: number.set_value
    entity_id: number.gx_device_ac_power_setpoint
    value: -4000

  # 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.foxess_work_mode
  #  option: "Feed-in First"

  # discharge_stop_service - Should be set to a service that is called when export/export freeze stops
  # This inputs charging setpoint into Victron Multi Plus, 50W is recommended so you dont drain battery into grid
  discharge_stop_service:
    service: number.set_value
    entity_id: number.gx_device_ac_power_setpoint
    value: 50

  #
  # Run balance inverters every N seconds (0=disabled) - only for multi-inverter
  #balance_inverters_seconds: 60
  #

  # charge_rate and discharge_rate come from the https://github.com/nathanmarlor/foxess_modbus/ integration, they are in kW but works without problems.
  #charge_rate:
  #  - number.foxess_force_charge_power
  #discharge_rate:
  #  - number.foxess_force_discharge_power
  battery_power:
    - sensor.gx_device_dc_battery_power
  battery_power_invert:
    - True
  # Replace pv_power sensor with appropriate sensor name when using a separate solar power monitor for AC-coupled FoxESS
  pv_power:
    - sensor.gx_device_pv_power
  load_power:
    - sensor.gx_device_consumption_power_l1
  grid_power:
    - sensor.gx_device_grid_power_l1
  soc_percent:
    - sensor.gx_device_dc_battery_charge
  #soc_max could be different to this figure, adjust accordingly
  soc_max:
    - 9.6
  battery_min_soc:
    - sensor.gx_device_active_soc_limit
  # Battery temperature might be labelled differently, this one is for Pylontech batteries
  battery_temperature:
    - sensor.pylontech_battery_id_512_battery_temperature

  # 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:
    - 4000

  # Set the maximum charge/discharge rate of the battery
  battery_rate_max:
    - 4000

  # 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:
  # - 3600
  # - 3600

  # 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

  inverter_limit_charge:
   - 4000

  inverter_limit_discharge:
   - 4000

  # 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 or set to 'auto' for predbat to determine the curves.
  # the default is 1.0 (full power)
  #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

  # 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 Go and are not using the Octopus Direct connection method, 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 the intelligent slot from the Octopus Energy integration
  octopus_intelligent_slot: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_intelligent_dispatching)'
  octopus_ready_time: 're:((select|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)'

  # 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

  # Can be used instead of the plugin to get import rates directly online
  # Overrides metric_octopus_import and rates_import
  # See the 'energy rates' part of the documentation for instructions on how to find the correct URL for your tariff and DNO region
  #
  # 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-24-10-01/electricity-tariffs/E-1R-AGILE-24-10-01-A/standard-unit-rates"

  # Overrides metric_octopus_export and rates_export
  # rates_export_octopus_url: "https://api.octopus.energy/v1/products/FLUX-EXPORT-23-02-14/electricity-tariffs/E-1R-FLUX-EXPORT-23-02-14-A/standard-unit-rates"
  # rates_export_octopus_url: "https://api.octopus.energy/v1/products/AGILE-OUTGOING-19-05-13/electricity-tariffs/E-1R-AGILE-OUTGOING-19-05-13-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 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:
    - 7

  # 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:
    - 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
  # 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}'

[planetming]

Hi all,
I've managed to integrate Predbat with my Victron Inverter. My system is.
Victron MultiPlus-II 48/10000/140-100/100.
12kWh BYD Battery pack.
2015 installed grid tied 3.68kW PV inverter.
Export limit is 7.2kW but I impose a 4kW export limit.
Solar iboost, gen 1.

Installation method Home Assistant OS
Core 2026.7.4
Supervisor 2026.07.5
Operating System 18.1
Frontend 20260624.6
Predbat v8.48.6
Bottlecapdave, Octopus Energy Integration, Version 19.0.0
Solcast PV Forecast, Version v4.6.1

I have previously setup a number of sensors to see some of the Victron Cerbo-GX registers using the Modbus integration.
Also scripts to set the grid-setpoint, and SOC

Hope this helps people with Victron inverters. Happy to share more info as required.

Here is my apps.yaml file
I am optionally running ML Load prediction.

pred_bat:
  module: predbat
  class: PredBat


  # Enable ML load prediction
  load_ml_enable: true
  # Use the output data in Predbat (can be false to explore the use without using the data)
  load_ml_source: true

  # Optional: Maximum days of historical data to fetch from HA on each poll (default: 28)
  load_ml_max_days_history: 28

  # Optional: Number of days of history to accumulate in the on-disk database (default: 90)
  # load_ml_database_days: 90  

  # 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

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

  # Enable temperature predictions (RECOMMENDED for ML load prediction)
  temperature_enable: true

  # Optional: specify coordinates (defaults to zone.home)
  # temperature_latitude: 51.5074
  # temperature_longitude: -0.1278

  # 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

  # If you are using Predbat outside of HA then set the HA URL and Key (long lived access token here)
  #ha_url: 'http://homeassistant.local:8123'
  #ha_key: !secret ha_key

  # 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

  #
  # Energy today (not power) 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.victron_home_energy_consumption_today
  import_today:
  - sensor.grid_import_daily
  export_today:
  - sensor.grid_export_daily
  pv_today:
  - sensor.et112_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
  #
  #
  # Controls/status - must by 1 per inverter
  #
  num_inverters: 1
  inverter_hybrid: false
  #
  # Run balance inverters every N seconds (0=disabled) - only for multi-inverter
  #balance_inverters_seconds: 60
  # 
  # Inverter model: MultiPlus-II 48/10000/140-100/100
  inverter_type: Victron
  inverter:
    name: "Victron Multiplus-II"
    has_rest_api: false
    has_mqtt_api: false
    has_service_api: true
    output_charge_control: "power"
    charge_control_immediate: true
    current_dp: 0
    charge_discharge_with_rate: false
    has_charge_enable_time: false
    has_discharge_enable_time: false
    has_target_soc: true
    target_soc_used_for_discharge: true
    has_reserve_soc: false
    has_timed_pause: false
    time_button_press: false
    support_charge_freeze: false
    support_discharge_freeze: false
    has_ge_inverter_mode: false
    has_fox_inverter_mode: false
    has_idle_time: false
    has_time_window: false
    charge_time_format: "S"
    charge_time_entity_is_option: false
    can_span_midnight: true
    clock_time_format: "%Y-%m-%d %H:%M:%S"
    num_load_entities: 1
    soc_units: "%"
    write_and_poll_sleep: 2

  # Services to control charging/discharging
  charge_start_service:
    service: script.turn_on
    entity_id: script.predbat_start_charging

  charge_stop_service:
    service: script.turn_on
    entity_id: script.predbat_stop_charging

  discharge_start_service:
    service: script.turn_on
    entity_id: script.predbat_start_discharging

  discharge_stop_service:
    service: script.turn_on
    entity_id: script.predbat_stop_discharging

  charge_rate: input_number.predbat_battery_charge_rate
  discharge_rate: input_number.predbat_battery_discharge_rate

  battery_power: sensor.victron_battery_power
  battery_power_invert: true
  pv_power: sensor.et112_pv_power
  load_power: sensor.victron_ac_loads_l1
  grid_power: sensor.victron_ac_grid_l1
  grid_power_invert: true

  battery_voltage: 52.5
  soc_percent: sensor.victron_battery_state_of_charge
  #Sets the maximum battery charge/discharge rate in watts. Must be set for non-GivEnergy inverters or Predbat will default to 2600W.
  battery_rate_max: 8000
  soc_max: 12
  battery_min_soc: 5
  battery_temperature: sensor.victron_battery_temperature

  #Grid tied 3.68kW G98 PV Inverter
  pv_ac_limit: 3680

  #Target SOC
  #Used by Victron inverter scripts to set the target SOC.
  charge_limit: input_number.predbat_target_soc


  # 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: 8000

  # Export limit is a software limit set on your inverter that prevents exporting above a given level
  # When enabled Predbat will model this limit
  # When set defines the maximum watts of AC power your inverter can export to the grid at (e.g. 2500). 
  # This is used by Predbat in calculating the plan to emulate your inverter's software export limit setting 
  # that you will have if your G98/G99 approval was lower than your maximum inverter power.
  export_limit: 4000

  # When set in Watts, caps the maximum discharge rate used specifically during forced export windows, 
  # without affecting the ECO mode discharge rate.
  #inverter_limit_export: 4000

  #When set in Watts, overrides the maximum charge/discharge rate settings used when controlling the inverter.
  inverter_limit_charge: 7000
  inverter_limit_discharge: 4000

  # 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
  #
  # Predbat can compute this curve automatically if you have enough data, restart the app and look in the logfile for the data
  # once set here Predbat will no longer re-compute the curve.
  # Can also be set to 'auto' to just use the calculation curve, not recommended if you are using low power charging mode.
  battery_charge_power_curve:
    5: 1.0
    96: 1.0
    97: 1.0
    98: 0.5
    99: 0.5
    100: 0.22

  battery_discharge_power_curve:
    1: 1.0

  # Set these to match solcast sensor names if not using the cloud interface
  # 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))

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

  # 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)
  # Changed 7/8/2026 RML to match Bottlecapdave changes to event names
  #octopus_saving_session: 're:(event.octopus_energy([0-9a-z_]+|)_saving_session_event(s|))'
  octopus_saving_session: 're:(event.octopus_energy([0-9a-z_]+|)_power_down_event(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
  # Changed 7/8/2026 RML to match Bottlecapdave changes to event names
  #octopus_free_session: 're:(event.octopus_energy_([0-9a-z_]+|)_octoplus_free_electricity_session_events)'
  octopus_free_session: 're:(event.octopus_energy_([0-9a-z_]+|)_octoplus_power_up_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)'

  # 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: 7

  # 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: 36

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

  # 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: 1.0

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

  # 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.immersion_energy_today'
  #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

I'm running 4 scripts to control the Inverter.
predbat_start_charging

sequence:
  - delay:
      hours: 0
      minutes: 0
      seconds: 1
      milliseconds: 0
  - data:
      minimum_soc: "{{states('input_number.predbat_target_soc')|int}}"
    action: script.set_minimum_soc
    enabled: true
  - metadata: {}
    data:
      option: "True"
    target:
      entity_id: select.daily_energy_battery_grid_charge
    action: select.select_option
  - action: switch.turn_off
    metadata: {}
    target:
      entity_id: switch.garage_iboost_control
    data: {}
    note: >
      Turning off the switch enables the iBoost CT sensor and the immersion
      heats with excess solar.
fields: {}
alias: predbat_start_charging
description: Start charging to defined SOC. Also called for Hold Charging.

predbat_stop_charging

sequence:
  - if:
      - condition: state
        entity_id: binary_sensor.target_timeframes_octopus_energy_octopus_plunge_pricing
        state:
          - "on"
    then:
      - metadata: {}
        data:
          minimum_soc: 100
        action: script.set_minimum_soc
        note: Set SOC to 100%
        enabled: true
      - action: notify.send_message
        metadata: {}
        target:
          entity_id: notify.robs_phone
        data:
          title: Predbat
          message: Charging Stopped, Plunge Pricing On
    else:
      - metadata: {}
        data:
          minimum_soc: 5
        action: script.set_minimum_soc
        note: Set SOC to 5%
        enabled: true
      - action: script.victron_ess_mode_optimized_without_battery_life
        data: {}
        enabled: true
      - metadata: {}
        data:
          option: "False"
        target:
          entity_id: select.daily_energy_battery_grid_charge
        action: select.select_option
      - action: notify.send_message
        metadata: {}
        target:
          entity_id: notify.robs_phone
        data:
          message: Charging stopped
          title: Predbat
fields: {}
alias: predbat_stop_charging
description: ""

predbat_start_discharging

sequence:
  - delay:
      hours: 0
      minutes: 0
      seconds: 1
      milliseconds: 0
  - action: switch.turn_on
    metadata: {}
    target:
      entity_id: switch.garage_iboost_control
    data: {}
    note: >-
      Turning on the switch disables the iBoost CT sensor and the immersion
      heater is off.
  - action: script.victron_ess_mode_optimized_without_battery_life
    data: {}
  - data:
      minimum_soc: "{{states('input_number.predbat_target_soc')|int}}"
    action: script.set_minimum_soc
    enabled: true
  - note: Export is controlled by input_number.predbat_battery_discharge_rate
    action: script.1704635957615
    metadata: {}
    data:
      grid_setpoint: "{{(-1*(states('input_number.predbat_battery_discharge_rate')|int))}}"
fields: {}
alias: predbat_start_discharging
description: Predbat start discharge at input_number.predbat_battery_discharge_rate

predbat_stop_discharging

sequence:
  - data:
      grid_setpoint: "{{states('input_number.default_grid_setpoint')|int}}"
    action: script.1704635957615
  - action: script.victron_ess_mode_optimized_without_battery_life
    data: {}
  - if:
      - condition: state
        entity_id: input_boolean.holiday_mode
        state:
          - "off"
    then:
      - action: switch.turn_off
        metadata: {}
        target:
          entity_id: switch.garage_iboost_control
        data: {}
        note: >
          Turning off the switch enables the iBoost CT sensor and the immersion
          heats with excess solar.
  - metadata: {}
    data:
      minimum_soc: 5
    action: script.set_minimum_soc
    enabled: true
  - metadata: {}
    data:
      option: "False"
    target:
      entity_id: select.daily_energy_battery_grid_charge
    action: select.select_option
  - action: notify.send_message
    metadata: {}
    target:
      entity_id: notify.robs_phone
    data:
      message: Discharging stopped
      title: Predbat
fields: {}
alias: predbat_stop_discharging
description: ""

[planetming]

Custom Config entries.

input_number.predbat_battery_loss=0.025
input_number.predbat_battery_loss_discharge=0.025
input_number.predbat_inverter_loss=0.05
switch.predbat_inverter_soc_reset=false
switch.predbat_inverter_set_charge_before=false
input_number.predbat_metric_battery_cycle=2.8p/kWh
input_number.predbat_metric_self_sufficiency=9.0p/kWh
input_number.predbat_set_reserve_min=5%

[planetming]

Further scripts called from above scripts.
There's no need to call the ESS mode scripts, ignore those.
Also iboost control is specific to my system, ignore these too.

script set_minimum_soc

alias: Set the minimum SOC
icon: mdi:battery
fields:
  minimum_soc:
    name: Minimum SOC
    description: Set the minimum SOC (0-100%)
    default: 5
    selector:
      number:
        min: 0
        max: 100
        step: 1
        unit_of_measurement: "%"
    required: true
mode: queued
sequence:
  - data:
      hub: victron
      address: 2901
      slave: 100
      value: "{{minimum_soc*10}}"
    action: modbus.write_register
max: 10

script set_the_grid_setpoint (script.1704635957615 in above code)

alias: Set the Grid Setpoint
icon: mdi:transmission-tower-import
fields:
  grid_setpoint:
    selector:
      number:
        min: -7000
        max: 8000
        unit_of_measurement: W
        step: 10
    default: 0
mode: single
sequence:
  - if:
      - condition: template
        value_template: "{{grid_setpoint <0}}"
    then:
      - data:
          hub: victron
          address: 2700
          slave: 100
          value: "{{ (grid_setpoint + 65536)| int }}"
        action: modbus.write_register
    else:
      - data:
          hub: victron
          address: 2700
          slave: 100
          value: "{{grid_setpoint | int}}"
        action: modbus.write_register
  - variables:
      grid_setpoint:
        setpoint: "{{states('sensor.victron_ess_grid_target')}}"
  - stop: Done
    response_variable: grid_setpoint

[trullock]

How come your start charging script doesn't mention the ESS mode?

[trullock]

And why are you changing the grid setpoint on stop-discharge only?

I'd love an explainer of generally whats going on here :)

Thanks

[planetming]

OK I'll have a go at a wordy description of what I'm doing. Also please understand that I am evolving my scripts too. I've now added slow charging and discharging options, which seem to work very well. I'll come back to that later.

In my experience with Victron, since my install in Dec 2023. This is how I controlled the system from the start, developing sensors and control scripts.
Charging
By adjusting the Minimum SOC register. In my system this is usually set at 5%, but to charge I set it at anything up to 100%. This mimics what the SOC slider does in the App. This always charged at maximum rate 7kW.
I further discovered that also by setting the ESS mode to "keep batteries charged" sometimes seemed to keep the SOC at 100% better than not using it. That's why ESS mode is mentioned in the "stop_charging" script above. I would now not recommend changing the ESS mode as well as setting SOC to 100%.

Discharging
Discharging is done by adjusting the Grid Setpoint. The default for this is 0W, i.e. keep the export to around 0W, batteries supply the load. I usually set mine to -20W so I have a slight bias to export. So to start discharging I adjust the Grid Setpoint Register to say -4000W. This causes the Victron to export from Batteries and PV if available. I keep the Minimum SOC at 5% and usually time my discharge. Exporting was always a very manual process for me. In these older scripts I had to make sure the ESS mode was set back to " keep batteries Optimised", again not recommended to use this.

Moving to using Predbat
Start Charging and Start Discharging basically uses the same ideas above.

Hold Charging and Hold Discharging
With no direct ability to Hold Charge in Victron, I allowed Predbat to control the minimum SOC. This effectively mimics the functionality by setting the maximum SOC during charging and controlling the minimum SOC during discharge.

Hope this helps.

[trullock]

Thanks, thats super useful. I was kind of at the same point that you are now, but as you say your legacy ESS bits were making me think I didn't understand something :) I'll post my setup which uses a GX device (no need for direct modbus) soon

[planetming]

OK, so are you using the Victron GX Integration and communicating over MQTT?
I went for a ground up approach (The hard way) and wrote all my own scripts to talk over modbus.
End result is the same 👍

[trullock]

Yes, but I'm using the Victron MQTT Integration via HACS, as it provides faster metric updates

[planetming]

Adjusting the charge and discharge rates
I've now additionally set the following Config for low power charge and discharge rates.
switch.predbat_set_charge_low_power=TRUE
switch.predbat_set_export_low_power=TRUE

Discharge rate
The discharge rate in Watts is immediately controlled by the value in
input_number.predbat_battery_discharge_rate Up to the maximum discharge/export values defined in my Apps.yaml

Charge rate
To control the charge rate you have to set the Victron DVCC charge current. In my system the max charge current is around 125A. So I do the calculation from Charge Watts to current in the Predbat_start_charging script using a nominal battery voltage of 55V (could tweak this). A value of -1 is Max Charge rate. Otherwise I set a value of 0-200A.

Predbat_start_charging script

sequence:
  - delay:
      hours: 0
      minutes: 0
      seconds: 1
      milliseconds: 0
  - variables:
      charge_current: '{{(states(''input_number.predbat_battery_charge_rate'')|float / 55)|int }}'
    note: Calculate the charge current (power/55V)
  - action: script.set_max_charge_current
    metadata: {}
    data:
      dvcc_max_charge_current: '{{charge_current}}'
    note: Set the DVCC charge current
  - data:
      minimum_soc: '{{states(''input_number.predbat_target_soc'')|int}}'
    action: script.set_minimum_soc
    enabled: true
  - metadata: {}
    data:
      option: 'True'
    target:
      entity_id: select.daily_energy_battery_grid_charge
    action: select.select_option
  - action: switch.turn_off
    metadata: {}
    target:
      entity_id: switch.garage_iboost_control
    data: {}
    note: >
      Turning off the switch enables the iBoost CT sensor and the immersion
      heats with excess solar.
  - action: notify.send_message
    metadata: {}
    target:
      entity_id: notify.robs_phone
    data:
      message: >
        {{states('predbat.status')}} to {{states
        ('input_number.predbat_target_soc')}}%
      title: Predbat
    enabled: false
fields: {}
alias: predbat_start_charging
description: Start charging to defined SOC. Also called for Hold Charging.

Predbat_stop_charging Script

sequence:
  - if:
      - condition: state
        entity_id: binary_sensor.target_timeframes_octopus_energy_octopus_plunge_pricing
        state:
          - 'on'
    then:
      - metadata: {}
        data:
          minimum_soc: 100
        action: script.set_minimum_soc
        note: Set SOC to 100%
        enabled: true
      - data:
          minimum_soc: '{{states(''input_number.predbat_target_soc'')|int}}'
        action: script.set_minimum_soc
        enabled: false
      - action: notify.send_message
        metadata: {}
        target:
          entity_id: notify.robs_phone
        data:
          title: Predbat
          message: Charging Stopped, Plunge Pricing On
    else:
      - metadata: {}
        data:
          minimum_soc: 5
        action: script.set_minimum_soc
        note: Set SOC to 5%
        enabled: true
      - data:
          minimum_soc: '{{states(''input_number.predbat_target_soc'')|int}}'
        action: script.set_minimum_soc
        enabled: false
      - action: script.victron_ess_mode_optimized_without_battery_life
        data: {}
        enabled: true
      - metadata: {}
        data:
          option: 'False'
        target:
          entity_id: select.daily_energy_battery_grid_charge
        action: select.select_option
      - action: notify.send_message
        metadata: {}
        target:
          entity_id: notify.robs_phone
        data:
          message: Charging stopped
          title: Predbat
  - action: script.set_max_charge_current
    metadata: {}
    data:
      dvcc_max_charge_current: -1
fields: {}
alias: predbat_stop_charging
description: ''

Set Max Charge Current Script

sequence:
  - if:
      - condition: template
        value_template: '{{dvcc_max_charge_current <0}}'
    then:
      - data:
          hub: victron
          address: 2705
          slave: 100
          value: '{{ (dvcc_max_charge_current + 65536)| int }}'
        action: modbus.write_register
    else:
      - data:
          hub: victron
          address: 2705
          slave: 100
          value: '{{dvcc_max_charge_current | int}}'
        action: modbus.write_register
icon: mdi:battery-charging-100
fields:
  dvcc_max_charge_current:
    selector:
      number:
        min: -1
        max: 200
        unit_of_measurement: A
        step: 1
    default: -1
    required: true
mode: single
description: ''
alias: Set Max Charge Current

Hope this helps

[trullock]

Here's my setup

I have two PV arrays, one DC coupled (feeding the MP2/batteries) and one AC coupled

I've made various Integral and Utility Meter helpers attached to the GX device for the missing native energy tracking sensors

---
pred_bat:
  module: predbat
  class: PredBat
  prefix: predbat
  timezone: Europe/London
  currency_symbols:
    - "£"
    - "p"
  threads: auto

  num_inverters: 1
  inverter_type: Victron
  inverter:
    name: "Victron Multiplus-II"
    has_rest_api: false
    has_mqtt_api: false
    has_service_api: true
    output_charge_control: "power"
    charge_control_immediate: true
    current_dp: 0
    charge_discharge_with_rate: false
    has_charge_enable_time: false
    has_discharge_enable_time: false
    has_target_soc: true
    target_soc_used_for_discharge: true
    has_reserve_soc: true
    has_timed_pause: false
    time_button_press: false
    support_charge_freeze: false
    support_discharge_freeze: false
    has_ge_inverter_mode: false
    has_fox_inverter_mode: false
    has_idle_time: false
    has_time_window: false
    charge_time_format: "S"
    charge_time_entity_is_option: false
    can_span_midnight: true
    clock_time_format: "%Y-%m-%d %H:%M:%S"
    num_load_entities: 1
    soc_units: "%"
    write_and_poll_sleep: 2

  charge_start_service:
    service: script.predbat_start_charging
    power: "{power}"
    target_soc: "{target_soc}"
    
  charge_stop_service:
    service: script.predbat_stop_charging

  discharge_start_service:
    service: script.predbat_start_discharging
    power: "{power}"
    target_soc: "{target_soc}"
    
  discharge_stop_service:
    service: script.predbat_stop_discharging

  battery_power: sensor.gx_device_dc_battery_power
  battery_power_invert: true
  battery_temperature: sensor.fogstar_batteries_temperature
  battery_temperature_history: sensor.fogstar_batteries_temperature
  battery_scaling: 1.0
  battery_charge_power_curve:
    1: 1.0
  battery_discharge_power_curve:
    1: 1.0
  soc_percent: sensor.gx_device_dc_battery_charge
  soc_max: 48.3
  battery_min_soc: 10
  battery_rate_max: 30000
  
  inverter_hybrid: false
  inverter_limit: 8000
  export_limit: 7000
  pv_ac_load_calcs: false
  
  # Target SoC
  charge_limit: input_number.predbat_battery_target_soc
  reserve: input_number.predbat_battery_reserve_soc
  charge_rate: input_number.predbat_battery_charge_rate
  discharge_rate: input_number.predbat_battery_discharge_rate

  load_ml_enable: false
  load_ml_source: true
  load_ml_max_days_history: 28
  load_filter_threshold: 30
  temperature_enable: true
  
  load_today: sensor.gx_device_load_energy_today
  load_power: sensor.gx_device_total_load_power
  grid_power: sensor.gx_device_grid_power_l1
  import_today: sensor.gx_device_grid_import_energy_today
  export_today: sensor.gx_device_grid_export_energy_today
  
  pv_today: sensor.gx_device_pv_total_energy_today
  pv_power: sensor.gx_device_pv_total_power
  pv_ac_today: sensor.gx_device_pv_inverter_energy_today
  pv_ac_power: sensor.gx_device_pv_on_output_power_l1
  pv_dc_today: sensor.gx_device_pv_charger_energy_today
  pv_dc_power: sensor.gx_device_pv_power

  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))
  forecast_hours: 48
  
  num_cars: 0

  carbon_postcode: "XXXX XXX"
  carbon_automatic: true

  octopus_saving_session: "re:(event.octopus_energy([0-9a-z_]+|)_saving_session_event(s|))"
  octopus_saving_session_octopoints_per_penny: 8
  octopus_free_session: "re:(event.octopus_energy_([0-9a-z_]+|)_octoplus_free_electricity_session_events)"

  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)"
  metric_standing_charge: "re:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_standing_charge)"

  days_previous: 7

  days_previous_weight: 1

  iboost_energy_today: "sensor.landing_eddi_xxxxxx_myenergi_eddi_xxxxxx_energy_consumed_session"
  
  ## These must be set in HA
  # iboost_gas_scale: 1.13 # boiler is 89% efficent
  # iboost_enable: true
  # iboost_max_energy: 3.0
  # iboost_max_power: 3000
  # iboost_gas: true
  # iboost_gas_export: true
  
  metric_octopus_gas: "re:(sensor.(octopus_energy_|)gas_[0-9a-z]+_[0-9a-z]+_current_rate)"

Start charging:

sequence:
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ac_power_setpoint
    data:
      value: |
        {{ power | int(8000) }}
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ess_min_soc_limit
    data:
      value: |
        {{ target_soc | int(100) }}
fields:
  power:
    name: Power
    description: The charge power in W
    example: 7000
    default: 7000
  target_soc:
    name: Target State of Charge
    description: The target SoC in %
    example: 10
    default: 10
alias: PredBat Start Charging

Stop Charging

sequence:
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ac_power_setpoint
    data:
      value: |
        {{ states("input_number.predbat_default_grid_setpoint") | int(-50) }}
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ess_min_soc_limit
    data:
      value: |
        {{ states("input_number.predbat_battery_reserve_soc") | int(10) }}
fields: {}
alias: PredBat Stop Charging
description: ''

Start Discharging

sequence:
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ac_power_setpoint
    data:
      value: |
        {{ -1 * (power | int(7000)) }}
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ess_min_soc_limit
    data:
      value: |
        {{ target_soc | int(10) }}
fields:
  power:
    name: Power
    description: The discharge power in W
    example: 7000
    default: 7000
  target_soc:
    name: Target State of Charge
    description: The target SoC in %
    example: 10
    default: 10
alias: PreBat Start Discharging

Stop Discharging

sequence:
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ac_power_setpoint
    data:
      value: |
        {{ states("input_number.predbat_default_grid_setpoint") | int(-50) }}
  - action: number.set_value
    metadata: {}
    target:
      entity_id: number.gx_device_ess_min_soc_limit
    data:
      value: |
        {{ states("input_number.predbat_battery_reserve_soc") | int(10) }}
fields: {}
alias: PredBat Stop Discharging
description: ''

[planetming]

A few observations on your setup.
battery_rate_max: 30000 Is this correct, does your battery charge/discharge at 30kW?

I can see you are using has_reserve_soc: true I had no luck with this and instead use input_number.predbat_set_reserve_min

I think you are setting the grid_setpoint for charging as well as the minimum_SOC. Do you find that the actual SOC overshoots using this method? I am only setting the minimum_SOC. Although I find that sometimes if the new minimum_SOC is close to the actual SOC, then the inverter thinks it has reached the required SOC.

and thanks for pointing out that I should set defaults for the int() function 👍

I think otherwise we are pretty much doing all the same things to control the inverter.

[trullock]

Thanks for the critique.

Re battery rate, well I wondered this.
My batteries can charge/discharge at 200A, and I've got 3 of them, at 48V nominal.
so, 48*200*3 = 28800

My batteries can be charged directly by my MPPT controller from 3.84kWp of panels, and the MP2 is 8kW, so the maximum real charge rate is 11.84kW. Do you know if the other PredBat settings will result in this? Or am I confusing things here.

Discharge rate is realistically similarly limited by the 8kW MP2...

re SoC - don't have enough data yet, will report back

[planetming]

I'm thinking the charging algorithm in Predbat could try and set the charge power to 11.8kW, if you used that figure. So maybe set it at 8000W and see what happens. Im assuming your MPPT power is your pv_dc_power so is accounted for in the PV calculation.

[sandyman44]

hi, I'm looking for an example victron inverter predbat yaml to start from, can someone help?
I have powerwall2 working, but I have a 2nd setup which is victron. there's a victron.yaml linked in the predbat docs, but that file doesn't exist in github. Just looking for a start point for victron, realise it may not be fully perfect :-)

I have the "tomer-w/ha-victron-mqtt" MQTT integration working already (for some time).

[sandyman44]

great thanks. I have GX, I can already control grid setpoint via MQTT from HA. I'll take a look at your config. many thanks.

[trullock]

I've probably made a few tweaks since the above, I'll update it asap.

One thing of note is setting the discharge rate into the grid setpoint bypasses all the max limits in the predbat config, so you need to artificially cap them at your max.
I.e. my battery can discharge at 30kw, but I'm capped at 7kw export, and my inverter at 8kw

[sandyman44]

tal. in my case the victron is a secondary inverter (physically and logically behind the primary), smaller capacity batt as well. I use it more like a V2G setup would be used - charge if primary full and spare/cheap grid (or want to stockpile for next day) - discharge if primary near empty and grid expensive. So the control loop needs some thought, not sure if predbat can do this. In HA I do it with a whole nest of if-thens and option-choose which is butt ugly :-).

[planetming]

I've probably made a few tweaks since the above, I'll update it asap.

One thing of note is setting the discharge rate into the grid setpoint bypasses all the max limits in the predbat config, so you need to artificially cap them at your max. I.e. my battery can discharge at 30kw, but I'm capped at 7kw export, and my inverter at 8kw

Can you elaborate on this, what issue are you facing here, is this related to your setting of battery_rate_max: 30000?

[trullock]

Yeah, I can't decide if this is predbats "fault" or not. I think it is, I think this is a bug? Or at least a poor design choice?

I've updated my post above to include getting predbat to pass the power and soc values to the start/stop scripts

here is the latest trace from Start Discharging:

params:
  domain: number
  service: set_value
  service_data:
    value: -30000
    entity_id:
      - number.gx_device_ac_power_setpoint
  target:
    entity_id:
      - number.gx_device_ac_power_setpoint

As you can see, inverter_limit and export_limit are completly ignored, and battery_rate_max is passed directly to the script.

So I need to edit my scripts to cap the setpoint to the real limits, but I shouldnt have to (not shown in the scripts above as I'm still experimenting)