Adding Charge/Discharge Hold, and charge rate support for SolarEdge battery

[gpsmith]

I went digging to try to work out how to do this after SE put a battery pause (for charge and discharge) in their app. Based on a conversation over at the SE modbus integration github, it seems that through the integration you can change the charge and discharge rates.

Given this, I believe that the following would be needed. Before I make the change and set predbat loose could someone in the know confirm this might be all I need to give predbat the ability to do it, or if I've missed something obvious? Thank you.

FYI I wasn't sure which is more optimal to have just a modified start and stop service, or also to deploy the charge_freeze_service and discharge_freeze_service . Also do I need discharge_stop_service given there isn't one in the current apps.yaml file?

support_charge_freeze: True  # Enables PredBat's charge hold capability
support_discharge_freeze: True

charge_start_service:
  - service: select.select_option
    entity_id: "select.solaredge_i1_storage_command_mode"
    option: "Charge from Solar Power and Grid"
    repeat: True
  - service: number.set_value
    entity_id: number.solaredge_i1_storage_charge_limit
    value: "{power}"  # PredBat injects the calculated charge rate
    repeat: True

charge_stop_service:
  - service: select.select_option
    entity_id: "select.solaredge_i1_storage_command_mode"
    option: "Maximize Self Consumption"
  - service: number.set_value
    entity_id: number.solaredge_i1_storage_charge_limit
    value: "{power}"  
    repeat: True

discharge_start_service:
  - service: select.select_option
    entity_id: "select.solaredge_i1_storage_command_mode"
    option: "Discharge to Maximize Export"
    repeat: True
  - service: number.set_value
    entity_id: number.solaredge_i1_storage_discharge_limit
    value: "{power}"  # PredBat injects calculated discharge rate
    repeat: True

discharge_stop_service:
  - service: select.select_option
    entity_id: "select.solaredge_i1_storage_command_mode"
    option: "Maximize Self Consumption"
    repeat: True
  - service: number.set_value
    entity_id: number.solaredge_i1_storage_discharge_limit
    value: "{power}" 
    repeat: True

[gpsmith]

@springfall2008 @gcoan Could I grab your sights when you have a second on this before I apply and test it please?

[gcoan]

@gpsmith the logic from a predbat perspective looks good, I can't comment on whether these are the right commands for your inverter though!

Once you have tested them, happy to incorporate them into the predbat template, as @WyndStryke says, the templates are MVP's so more is always better

I think you should have separate freeze charge and freeze export services as they do different things in predbat than charging and discharging https://springfall2008.github.io/batpred/what-does-predbat-do/#predbat-status

Freeze charge and freeze export both have their places. Freeze charge is used by predbat when import rates are low, it lets the house run off grid and preserves the battery SoC - doesn't charge it or let it discharge.
Freeze export is used when there is plenty of solar and predbat predicts that there is no need to further charge your battery (sufficient SoC to last to the next charging period) so it exports it directly

And yes, there should be a stop discharge service to return the inverter to demand mode

[WyndStryke]

The example apps.yaml is basically the 'minimum viable product', i.e., the absolute minimum required to get the inverter working with predbat.

Regarding charge_freeze_service and discharge_freeze_service

Personally I feel that discharge_freeze_service is quite important - this allows you to export PV directly, without storing it into the battery first (which causes both efficiency losses and unnecessary battery cycling).

Does your inverter have a mode which can do this? On the Fox inverters, it is 'feed-in first', which does house load first, export second, and battery last (if the export limit has been reached).

I got the charge_freeze_service working a couple of nights ago - for this one I used a mode on the Fox inverter called 'back-up', which will charge if the current battery SoC is below the 'minimum SoC on grid' setting on the fox inverters, and then I set the predbat reserve_soc to be the number.min_soc_on_grid in the apps.yaml (so that predbat can set the reserve as needed). So similarly, does your inverter have a mode similar to this?

[gpsmith]

Thanks both. I'm travelling for work this week, so I will have a play when I get home. I think I'm going to write some BDD patterns for the different modes and check back with you as a I have a few queries over the behaviour that predbat will expect so I can then see if the SE battery can be configured that way.

[cyberkryten]

On SE, there's no way to implement a Freeze Discharge that I've found, in the way you can on some other inverters.

If you set the inverter to Charge from Clipped Solar Power it will NEVER use the batteries to power the house, so in the event that load>PV you will end up importing from the grid.

If you set a Charge/Discharge maximum rate then that applies to both AC and DC, which means excess PV is lost.

There's no way of setting a target Max SoC

As a result, I have disabled it with support_discharge_freeze: false

[gpsmith]

Thanks for the insights.

[gpsmith]

I've had a play and must be doing something wrong as it's throwing errors in the predbat log. Do I need to set charge_discharge_with_rate for the power to be calculated?

2025-04-22 11:10:23.913032: Warn: Service call number/set_value data {'entity_id': 'number.solaredge_i1_storage_charge_limit'} failed with response None
--
9706 | 2025-04-22 11:10:23.897030: Warn: record_status Warn: can not resolve {'service': 'number.set_value', 'entity_id': 'number.solaredge_i1_storage_charge_limit', 'value_template': '{power}', 'repeat': True} value {power}
9705 | 2025-04-22 11:10:23.865536: Warn: can not resolve {'service': 'number.set_value', 'entity_id': 'number.solaredge_i1_storage_charge_limit', 'value_template': '{power}', 'repeat': True} value {power}
9703 | 2025-04-22 11:10:23.859949: Warn: Service call number/set_value data {'entity_id': 'number.solaredge_i1_storage_discharge_limit', 'value_template': '5000'} failed with response None
9700 | 2025-04-22 11:10:22.983282: Warn: Service call number/set_value data {'entity_id': 'number.solaredge_i1_storage_charge_limit'} failed with response None
9698 | 2025-04-22 11:10:22.965813: Warn: record_status Warn: can not resolve {'service': 'number.set_value', 'entity_id': 'number.solaredge_i1_storage_charge_limit', 'value_template': '{power}', 'repeat': True} value {power}
9697 | 2025-04-22 11:10:22.933708: Warn: can not resolve {'service': 'number.set_value', 'entity_id': 'number.solaredge_i1_storage_charge_limit', 'value_template': '{power}', 'repeat': True} value {power}