Sunsynk

[2001space]

Hi

I have Predbat add-on installed in HA. In the apps tab I can see Reserve keeps getting set to sensor.predbat_SK_0_reserve = 3.22% which is incorrect but in apps.yaml I have reserve: - number.inverter_sunsynk_battery_capacity_shutdown
So In dash my SOC is showing as 0%.

I have no errors in the logs - help !

Apps.yaml

pred_bat:
  module: predbat
  class: PredBat
  prefix: predbat
  timezone: Europe/London
  currency_symbols: ['£', 'p']
  threads: auto
  template: False 

  # SYSTEM DEFINITION
  num_inverters: 1
  inverter_type: SK  

  # SENSOR MAPPING  
  battery_soc: 
    - sensor.inverter_sunsynk_battery_soc
  battery_power:
    - sensor.inverter_sunsynk_battery_power
  load_power:
    - sensor.inverter_sunsynk_load_power
  grid_power:
    - sensor.inverter_sunsynk_grid_ct_power
  pv_power:
    - sensor.inverter_sunsynk_solar_power

  # Energy Totals
  load_today:
    - sensor.inverter_sunsynk_day_load_energy
  pv_today:
    - sensor.inverter_sunsynk_day_pv_energy
  import_today:
    - sensor.inverter_sunsynk_day_grid_import
  export_today:
    - sensor.inverter_sunsynk_day_grid_export


  # INVERTER CONTROL
  scheduled_charge_enable:
    - switch.inverter_sunsynk_toggle_system_timer
  scheduled_discharge_enable:
    - switch.inverter_sunsynk_toggle_system_timer

  charge_rate:
    - number.inverter_sunsynk_grid_charge_battery_current
  discharge_rate:
    - number.inverter_sunsynk_battery_max_discharge_current
  
  charge_limit:
    - number.inverter_sunsynk_prog1_capacity

  # RESERVE 
  reserve:
    - number.inverter_sunsynk_battery_capacity_shutdown
    
  # Battery Size
  soc_max: 
    - 16.1
  
  # SETTINGS
  days_previous:
    - 7
  inverter_limit: 
    - 5000 
  battery_rate_max: 
    - 5000
  metric_octopus_import: 're:(sensor.octopus_energy_electricity_.*_current_rate)'
  metric_octopus_export: 're:(sensor.octopus_energy_electricity_.*_export_current_rate)'

[gcoan]

I can see Reserve keeps getting set to sensor.predbat_SK_0_reserve = 3.22% which is incorrect but in apps.yaml I have reserve: - number.inverter_sunsynk_battery_capacity_shutdown

the predbat_SK sensor is a dummy sensor predbat has created to manage battery reserve because the Predbat definition of a Sunsynk inverter is that it doesn't have a reserve setting (hence the Predbat dummy entity).

The reserve line in the template apps.yaml is commented out because of this.

If predbat is going to control your inverter reserve then it needs a sensor it can read and write to, a number.xxxx is read only I believe

[2001space]

I'm using slipx06/Sunsynk-Home-Assistant-Dash ESPHome-1P-Sunsynk-Deye.yaml with my ESP32&RS485. I have updated it to set number: for inverter_sunsynk_battery_capacity_shutdown and tested write works by works changing in the HA ESP32 web gui and validating the change in the sunsunk web app.

Should I be using an alternate template to SK ? or remove number.inverter_sunsynk_battery_capacity_shutdown from app/yaml

[gcoan]

I'm using slipx06/Sunsynk-Home-Assistant-Dash ESPHome-1P-Sunsynk-Deye.yaml with my ESP32&RS485. I have updated it to set number: for inverter_sunsynk_battery_capacity_shutdown and tested write works by works changing in the HA ESP32 web gui and validating the change in the sunsunk web app.

Predbat's in built SK Sunsynk inverter definition has been coded using a different integration, https://github.com/kellerza/sunsynk as per the inverter setup guide

https://springfall2008.github.io/batpred/inverter-setup/

the inverter definition (from the code) is as follows:

    "SK": {
        "name": "Sunsynk",
        "has_rest_api": False,
        "has_mqtt_api": False,
        "output_charge_control": "current",
        "charge_control_immediate": False,
        "current_dp": 0,
        "has_charge_enable_time": False,
        "has_discharge_enable_time": False,
        "has_target_soc": True,
        "has_reserve_soc": False,
        "has_timed_pause": False,
        "charge_time_format": "S",
        "charge_time_entity_is_option": False,
        "soc_units": "%",
        "num_load_entities": 1,
        "has_ge_inverter_mode": False,
        "time_button_press": False,
        "clock_time_format": "%Y-%m-%d %H:%M:%S",
        "write_and_poll_sleep": 5,
        "has_time_window": False,
        "support_charge_freeze": False,
        "support_discharge_freeze": False,
        "has_idle_time": False,
        "can_span_midnight": True,
        "charge_discharge_with_rate": False,
        "target_soc_used_for_discharge": True,
    },

as I said this does not expect the inverter to have a reserve value, and predbat will ignore it

so if you are using SK then yes, you will need to comment this line out of apps.yaml and you can use the automations etc with the predbat template apps.yaml https://springfall2008.github.io/batpred/inverter-setup/#sunsynk

alternatively you could construct a new custom inverter definition https://springfall2008.github.io/batpred/inverter-setup/#i-want-to-add-an-unsupported-inverter-to-predbat if you want to use the different controls provided by your inverter integration