Battery SoC Reserve is send in % about sungrow-shx-inverter-modbus-home-assistant

[mkaiser]

incorporated your changes in c2fd053

thanks!

I also would like to know, how to enable the backup stuff (still have not rewired anything to have something useful at the backup ports)

[ViktorReinhold]

I can confirm it. Setting scale: 1 on Battery SoC Reserve and changing from int*10 to ìnt on the corresponding automation.

By the way, do somebody know how to enable or disable the backup mode at all? In the iSolarApp settings menu I can Enable or Disable it but don't see a way to do it with HA.

[elektrinis]

If "backup mode" means a mode when inverter is supplying loads from battery and tries to keep grid at 0W, I also want how to do this.
Also, has anyone figured out whatt all those operatiom modes are? I just noticed that forced charge/dischantge does not work in "self consumption" mode, I have to stitch to "forced" mode for this to work.

[mkaiser]

If "backup mode" means a mode when inverter is supplying loads from battery and tries to keep grid at 0W, I also want how to do this. Also, has anyone figured out whatt all those operatiom modes are? I just noticed that forced charge/dischantge does not work in "self consumption" mode, I have to stitch to "forced" mode for this to work.

"backup mode" refers to the case, when there is a blackout (the grid is not connected/delivering power) and the inverter uses the battery to power selected loads, which are connected to the dedicated backup power port of the inverter.

The EMS mode is the switch to select the general energy management system (EMS). In most cases you want the default self consumption mode (PV power is distributed to loads, excess power is used to charge the battery. When the battery is full (or the maximum charge power is reached) the rest will be exported.

When you change EMS to forced mode, the other selection mode "forced charge / discharge" is evaluated.

So to charge your battery you need to adapt both selections (EMS and force charge/discharge)

[dylan09]

As stated by @mkaiser backup mode is to power some loads from battery and inverter in case of grid blackout. So I think a rename of the sensor would make it a little bit clearer whats the meaning of the value.
If I understand right, its main reason is to reserve some battery capacity to be available in case of blackout.
In protocol definition it is named Reserved SOC for backup

[dylan09]

For me I have changed the 'EMS mode' dropdown and automation a little bit. I have removed External EMS, VPP and MicroGrid from the drop-down selection and automation.
VPP and Microgrid are not applicable to my installation. And for External EMS I haven't enough background? Maybe someone could help and describe the meaning of this setting and what it changes in inverter behaviour.

[dylan09]

When you change EMS to forced mode, the other selection mode "forced charge / discharge" is evaluated.

But be careful. If you select Foreced charge/discharge and set force charge power. If there is not enough PV power, the rest is taken from the grid.
E.g. force charge power is 1000W. PV supplies only 600W. Then 400W will be taken from the grid to charge the battery.

[dylan09]

I also would like to know, how to enable the backup stuff

First you have to connect your backup loads to the inverter. After that change Common Parameter Settings -> Power Control -> Backup Mode (No. 3) to Enable in iSolarCloud (maybe could also be changed in the App with local access).

To test if everything works you could switch off the AC circuit breaker or RCD in "front of" the inverter.

[elektrinis]

In my case I would like to command the inverter to use battery power ONLY, even if grid is available. In this case the inverter would try to discharge the battery at varying rate, equal to total consumption (so power on meter is zero).
I can set specific time for this in the app, but not sure what combination of settings lets me do this through this integration.
Also a reminder that I want to be able to select full 10.6kW for charge/discharge power instead of 5kW :)

[mkaiser]

In my case I would like to command the inverter to use battery power ONLY, even if grid is available. In this case the inverter would try to discharge the battery at varying rate, equal to total consumption (so power on meter is zero).

You are describing the default "Self consumption mode" here

I can set specific time for this in the app, but not sure what combination of settings lets me do this through this integration.

If I remember correctly, there are some modbus registers to program the time windows for charge / discharge. But I don't see a point in doing this "time static" stuff within this integration.
If you want to create an forced charge / discharge automation based on current prices, just copy and adapt the automation settings of the yaml

snippet from

    alias: "sungrow inverter update EMS mode"
    description: "Updates EMS mode"
    trigger:
      - platform: state
        entity_id:
          - input_select.set_sg_ems_mode
    condition: []
    variables:
      ems_mode_self_consume: 0
      ems_mode_forced: 2
      ems_mode_external: 3
      ems_mode_vpp: 4
      ems_mode_microgrid: 8
    action:
      - service: modbus.write_register
        data_template:
          hub: SungrowSHx
          slave: !secret sungrow_modbus_slave
          address: 13049 # reg 13050
          value: >-
            {% if is_state('input_select.set_sg_ems_mode', 'Self-consumption mode (default)') %} {{ems_mode_self_consume}}
            {% elif is_state('input_select.set_sg_ems_mode', 'Forced mode') %} {{ems_mode_forced}}
            {% elif is_state('input_select.set_sg_ems_mode', 'External EMS') %} {{ems_mode_external}}
            {% elif is_state('input_select.set_sg_ems_mode', 'VPP') %} {{ems_mode_vpp}}
            {% elif is_state('input_select.set_sg_ems_mode', 'MicroGrid') %} {{ems_mode_microgrid}}
            {% else %} 
            0
            {% endif %}
    mode: single

Also a reminder that I want to be able to select full 10.6kW for charge/discharge power instead of 5kW :)

See #38 2.)
You can quickly adapt the values you need for your setup in the "input" section of the modbus.yaml file. Maybe I will make some of these values customizable in the secrets. But this would require everyone, who just wants a quick update, to adapt these values as well... I am still hesitating at the moment to go this way. Could not figure out another way, yet (diskussions related to this please in #38)

I guess I can close this issue now.

Thanks again to dylan09 and ViktorReinhold