Viewing and control of battery SOC limits

[jojodevuk]

I've been poking around in the app after having a PV+Battery system installed recently, and found 3 settings and wondered if these were exposed via modbus. The charge cut-off SOC, discharge cut-off SOC, and the backup reserve SOC.

Sigenergy have only been able to provide me with version 2.5 of the modbus specification so if someone could link v2.7 or attach somewhere that would be wonderful.

[sjonez]

Came here to ask the same, I'm specifically looking to be able to control the battery charge SOC limit but can't see that available in this integration

[jojodevuk]

It may not yet be exposed as RW on modbus, so might require a feature request to sigenergy before being implemented

[dom356]

Looks like registers 40046, 40047 and 40048 are available now as RW to set the SOC values in the Modbus doc I got from Sigenery support this week. But I'm not sure how to update the code to add support for these registers though unfortunately.
Modbus Protocol v2.7 EN - SIGEN .pdf

[sjonez]

In addition to the SOC limits some other interesting changes have been added too that might be useful in this integration, worth checking out @TypQxQ ? I assume the total consumption registers would also mean you no longer have to calculate these yourself?

[TypQxQ]

I will check them out when I get back from vacation. I don't have a dev environment up.

[B-noob]

Was looking for the same. A time based change to the soc limit might be done within the my sigen app. However, a more sophisticated automation would be helpful.

Has anybody made the request to sigenergy yet?

[sjonez]

Yes, I ended up writing a script to alter the time-based SOC limit via the sigen cloud API, which seems to work well but I'd much prefer local control

[ronanohbee]

Do you mind me asking how you did that or where I can find details?

[sjonez]

I just used browser dev tools to monitor the API calls when I made the SOC change on https://app-eu.sigencloud.com/

Specifically, for the time-based SOC Limit it's a POST request to https://api-eu.sigencloud.com/device/dischargesetting/batch/save. Auth tokens last around 12 hours so you'll also need to grab a token (POST request to https://api-eu.sigencloud.com/auth/oauth/token)

[Bandit]

I'm keen to simply add "Backup Cut-off SOC" to these two, then using current draw, I can calculate how much time until my battery runs down etc

[TypQxQ]

Since v.1.1.0 there is now:

• number.sigen_plant_ess_backup_state_of_charge
• number.sigen_plant_ess_charge_cut_off_state_of_charge
• number.sigen_plant_ess_discharge_cut_off_state_of_charge

[Bandit]

I can't see the backup_soc in 1.1.5

[Bandit]

[TypQxQ]

[Bandit]

I'm using the "read only" mode though where all controls are disabled. Can I safely enable those?

[TypQxQ]

Yes you can.

[Bandit]

EDIT: See below comments for a better version #63 (reply in thread)

---

This still needs more testing time (and an elsif for handling when we're under grid outage conditions), but for those who find this later, here's the time remaining Template Helper I wrote just now

{% if states('sensor.sigen_plant_battery_state_of_charge') == states('number.sigenergy_ess_ess_backup_state_of_charge') %}
  0 minutes
{% else %}
  {% set available_soc = states('sensor.sigen_plant_battery_state_of_charge')|float(0) - states('number.sigenergy_ess_ess_backup_state_of_charge')|float(0) %}
  {% set available_kwh = available_soc / 100 * states('sensor.sigen_plant_rated_energy_capacity')|float(0) %}
  {% set hours_remaining = available_kwh / states('sensor.sigen_plant_battery_power')|float(0)|abs %}
  {{ time_until(as_datetime(now() + timedelta(hours = hours_remaining)), 2) }}
{% endif %}

Renders like

[Roving-Ronin]

Thanks @Bandit / James, been meaning to add that also. Might I suggest that include of dropping it out as a text format type output, that you slightly modify the code, so its output is in minutes (you can do seconds, but it only updates every x seconds anyhow).

That way you then have a number as the sensor value instead of text and you can use it in other helper templates / sensors.

Using a Helper --> Template --> Sensor type if you create it like this, you can also nowadays assign it to the Device. For the name (top row) I'd suggest entering it as the entityID name half way down (ensuring its entityID then becomes the same format as the other sigen_plant_battery_xxx sensors), then edit it after submitting to change it to 'Battery Runtime Remaining'.

Slight changes to the 2nd and 3rd last lines:

{% if states('sensor.sigen_plant_battery_state_of_charge') == states('number.sigenergy_ess_ess_backup_state_of_charge') %}
  0
{% else %}
  {% set available_soc = states('sensor.sigen_plant_battery_state_of_charge')|float(0) - states('number.sigenergy_ess_ess_backup_state_of_charge')|float(0) %}
  {% set available_kwh = available_soc / 100 * states('sensor.sigen_plant_rated_energy_capacity')|float(0) %}
  {% set minutes_remaining = available_kwh / states('sensor.sigen_plant_battery_power')|float(0)|abs %}
  {{ (minutes_remaining * 60) | int }}
{% endif %}

and here it is in the Devices --> Sigen Plant device:

[Bandit]

Here's another version that includes your improvements and factors in whether the grid is connected or not. I haven't had a grid outage so haven't tested that part yet, but it should work.

{% set ns = namespace() %}
{% set ns.curr_soc = states('sensor.sigen_plant_battery_state_of_charge') %}
{% set ns.min_soc = states('number.sigenergy_ess_ess_backup_state_of_charge') %}
{% if states('sensor.sigen_plant_grid_connection_status') != "On Grid" %}
  {% set ns.min_soc = states('number.sigenergy_ess_ess_discharge_cut_off_state_of_charge') %}
{% endif %}
{% if ns.curr_soc == ns.min_soc %}
  0
{% else %}
  {% set available_soc = ns.curr_soc|float(0) - ns.min_soc|float(0) %}
  {% set available_kwh = available_soc / 100 * states('sensor.sigen_plant_rated_energy_capacity')|float(0) %}
  {% set minutes_remaining = available_kwh / states('sensor.sigen_plant_battery_power')|float(0)|abs %}
  {{ (minutes_remaining * 60) | int }}
{% endif %}

[Bandit]

Another version to fix the "divide by zero" issue if there's no current battery draw (or the battery is charging) so instead of "Unavailable" it becomes "999"

I also learned that if you change the unit of measurement to h instead of min then it renders with a nice human readable format (e.g. 1h 36m) so the below returns hours not minutes

{% set ns = namespace() %}
{% set ns.curr_soc = states('sensor.sigen_plant_battery_state_of_charge') %}
{% set ns.min_soc = states('number.sigenergy_ess_ess_backup_state_of_charge') %}
{% set ns.battery_draw = states('sensor.sigen_plant_battery_power')|float(0) %}
{% if states('sensor.sigen_plant_grid_connection_status') != "On Grid" %}
  {% set ns.min_soc = states('number.sigenergy_ess_ess_discharge_cut_off_state_of_charge') %}
{% endif %}
{% if ns.curr_soc == ns.min_soc %}
  0
{% elif ns.battery_draw >= 0.00 %}
  999
{% else %}
  {% set available_soc = ns.curr_soc|float(0) - ns.min_soc|float(0) %}
  {% set available_kwh = available_soc / 100 * states('sensor.sigen_plant_rated_energy_capacity')|float(0) %}
  {% set hours_remaining = available_kwh / ns.battery_draw|abs %}
  {{ hours_remaining }}
{% endif %}

If you leave the unit of measurement as 'min' as per the previous example code, here's a bonus friendly formatter template to convert minutes to hours and minutes for display or notifications etc:

{{ states('sensor.sigen_ess_battery_time_remaining') | float // 60 }}h {{ states('sensor.sigen_ess_battery_time_remaining') | float % 60 }}m

[Roving-Ronin]

That last one would produce an output like '16.0h and 15.26m', it needs ' | int' added for:

{{ (states('sensor.sigen_ess_battery_time_remaining') | float // 60) | int }}h {{ (states('sensor.sigen_ess_battery_time_remaining') | float % 60) | int }}m

Also worth changing 999 to 999999, due to if your discharging at some #W you can get a reading of 999 or higher, but no chance you'll ever get 999999.

Using your 'hours' code above, you could use that as the "raw" sensor that you can hide, that will always output a number (that HA then automatically shows in hours/min). However, cut on like the 'divide by zero' issue, when you battery is sitting there and floating / discharging a few watts, instead of getting some crazy '1234h and 56m' reading.

f you create a seperate template sensor to use to display the output, that you can then link to the device in the integration, you could use this below to have a sensor that's going to show the hours and minutes, but then if the draw is less than 100W, that would then be saying 20 days and #m (for a 48kWh ESS) or saying '999 or 999999' it will instead output "Floating".

template:
  - sensor:
      - name: "Battery Runtime Display"
        state: >
          {% set runtime = states('sensor.sigen_plant_battery_remaining_runtime') | float(0) %}
          {% set hours = runtime | int %}
          {% set minutes = ((runtime - hours) * 60) | round(0) | int %}
          
          {% if hours > 480 %}
            Floating
          {% else %}
            {{ hours }}h {{ minutes }}m
          {% endif %} 

[Bandit]

Just added a little notification that runs every 5 minutes during a grid outage

action: notify.mobile_app_YOURDEVICEHERE
metadata: {}
data:
  data:
    ttl: 0
    priority: high
    notification_icon: mdi:home-battery-outline
    channel: Warning
  title: Battery remaining
  message: >-
    {% set ts = now() + timedelta(hours =
    states("sensor.sigen_ess_battery_time_remaining")|float) %}

    {% set dt = as_datetime(ts) %}

    Remaining battery: {{ time_until(dt, 2) }}
enabled: true

Pushes something like

Remaining battery: 5 hours 15 minutes

[TypQxQ]

Test the solution discussed here
#161