In dire need for help with my predbat code! 😫

[Wishy1997]

Hi everyone,

I'm extremely new to all this, I've been trying to set my system but keep receiving log faults: 9389 2026-01-11 09:42:15.304880: Completed run status Freeze charging with Errors reported (check log)
9380 2026-01-11 09:42:14.682817: Warn: record_status Warn: Inverter 0 write to inverter_mode failed
9379 2026-01-11 09:42:14.570009: Warn: Inverter 0 Trying to write inverter_mode to Eco didn't complete got Load First
9378 2026-01-11 09:42:04.565924: Warn: Service call select/select_option data {'option': 'Eco', 'entity_id': 'select.growatt_pv_inverter_priority'} failed
9377 2026-01-11 09:42:04.563413: Warn: Web Socket result failed {'id': 123, 'type': 'result', 'success': False, 'error': {'code': 'service_validation_error', 'message': 'Validation error: Option Eco is not valid for entity select.growatt_pv_inverter_priority, valid options are: Load First, Battery First, Grid First', 'translation_key': 'not_valid_option', 'translation_placeholders': {'entity_id': 'select.growatt_pv_inverter_priority', 'option': 'Eco', 'options': 'Load First, Battery First, Grid First'}, 'translation_domain': 'select'}}

I've recently had a solar panel system installed:

12 465w Aiko Panels
5kw SPH Growatt inverter
5kw Growatt battery

I have a solax modbus integration pointed to my shinewifi lan X2 datalogger.

I'm trying to code my predbat add-on to control my inverter but predbat asks to change to eco, timed_charge, time_discharge. However growatt modes are battery first, load first, grid first.

Here is my current code for the predbat apps yaml:

Pred_bat:
  module: predbat
  class: PredBat
  prefix: predbat
  timezone: Europe/London
  template: false

  # --- TIME & CURRENCY ---
  last_updated_fmt: "%H:%M:%S"
  currency_symbols:
  - '£'
  - 'p'

  # --- OCTOPUS DIRECT API ---
  octopus_api_key: "xxxx"
  octopus_api_account: "xxxx"
  octopus_automatic: true

  # --- SOLCAST DIRECT API ---
  solcast_host: 'https://api.solcast.com.au/'
  solcast_api_key: "xxxx"
  solcast_sites:
  - "xxxx"
  - "xxxx"
  solcast_poll_hours: 8

  # --- GROWATT CONTROL ENTITIES ---
  inverter_mode:
  - select.growatt_pv_inverter_priority
  inverter_mode_entity:
  - select.growatt_pv_inverter_priority
  inverter_mode_eco: "Load First"
  inverter_mode_charge: "Battery First"
  inverter_mode_grid: "Grid First"

  # --- MINIMUM SOC SENSORS (Mode-Specific) ---
  eco_reserve:
  - number.growatt_pv_inverter_load_first_battery_minimum_soc
  charge_reserve:
  - number.growatt_pv_inverter_load_first_battery_minimum_soc
  discharge_reserve:
  - number.growatt_pv_inverter_grid_first_battery_minimum_soc

  # --- TIME SLOTS (Eco/Normal Mode) ---
  eco_start_time:
  - select.growatt_pv_inverter_load_first_time_1_begin
  eco_end_time:
  - select.growatt_pv_inverter_load_first_time_1_end

  # Battery First (Charge)
  charge_start_time:
  - select.growatt_pv_inverter_battery_first_time_1_begin
  charge_end_time:
  - select.growatt_pv_inverter_battery_first_time_1_end

  # Grid First (Discharge)
  discharge_start_time:
  - select.growatt_pv_inverter_grid_first_time_1_begin
  discharge_end_time:
  - select.growatt_pv_inverter_grid_first_time_1_end

  # --- ENABLERS & SWITCHES ---
  grid_charge_enable:
  - select.growatt_pv_inverter_battery_first_charge_from_grid
  scheduled_charge_enable:
  - select.growatt_pv_inverter_battery_first_time_1
  scheduled_discharge_enable:
  - select.growatt_pv_inverter_grid_first_time_1

  # Standardized to eco_enable
  eco_enable:
  - select.growatt_pv_inverter_load_first_time_1

  # --- BATTERY & POWER ---
  soc_max:
  - 4.6
  reserve_min: 10
  soc_max_charge: 95
  charge_rate_percent:
  - number.growatt_pv_inverter_battery_first_charge_rate
  discharge_rate_percent:
  - number.growatt_pv_inverter_grid_first_discharge_rate
  battery_power:
  - sensor.growatt_pv_inverter_battery_discharge_power
  pv_power:
  - sensor.growatt_pv_inverter_pv_power_total
  load_power:
  - sensor.growatt_pv_inverter_house_load
  grid_power:
  - sensor.grid_usage
  soc_percent:
  - sensor.growatt_pv_inverter_battery_soc

  # --- ENERGY HISTORY ---
  load_today:
  - sensor.growatt_pv_inverter_today_s_load
  import_today:
  - sensor.growatt_pv_inverter_today_s_grid_import
  pv_today:
  - sensor.growatt_pv_inverter_today_s_solar_energy
  export_today:
  - sensor.growatt_pv_inverter_today_s_grid_export

  # --- TARIFF & CALCS ---
  metric_octopus_import: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_rate)'
  calculate_best: true
  calculate_charge: true
  calculate_discharge: false

I've had many a sleepless night, so any help would be welcome.

Many thanks,

Will

[gcoan]

A couple of bits of housekeeping before I answer your question ...

Firstly if you are copying your apps.yaml file into github (and thank you for doing so, it is essential to understand your configuration, so many people don't bother 😠), but when you do, please put ``` before and after your YAML as otherwise github tries to format the yaml and its impossible to read

Second, you ought not to share your octopus and solcast API keys. You can use the secrets file in HA (see documentation) to avoid this.

I have edited your github question to fix both of the above but do recommend you revoke and create new API keys.

Onto your question, where did you get this apps.yaml file from? There are example configurations for different inverters in the predbat documentation https://springfall2008.github.io/batpred/inverter-setup/
It looks like you have created a custom apps.yaml file, which is absolutely fine, BUT several of the configuration entries are not things Predbat recognises and crucially you have not told Predbat what type of inverter you are using. Predbat has in built knowledge of many inverter types and if you don't tell Predbat (by setting inverter type) to your inverter name then Predbat will assume you have a GivEnergy inverter.
And I think that is what is happening, predbat is assuming you have a givenergy inverter (the fuller logfile would show this) and is trying to set inverter_mode to Eco and that's not a valid option for your inverter.

Either start from one of the existing inverter examples, there are two for Growatt, or define a custom inverter type https://springfall2008.github.io/batpred/inverter-setup/#i-want-to-add-an-unsupported-inverter-to-predbat

[Wishy1997]

Apologies,

Thank you for your speedy response, I've tried to answer the question best as possible.
if you require further, then let me know.

Where: Unfortunately as I'm not a coder, I was using Gemini AI to assist.

the code

  module: predbat
  class: PredBat
  prefix: predbat
  timezone: Europe/London
  template: false

  # --- TIME & CURRENCY ---
  last_updated_fmt: "%H:%M:%S"
  currency_symbols:
  - '£'
  - 'p'

  # --- OCTOPUS DIRECT API ---
  octopus_api_key: "xxxx"
  octopus_api_account: "xxxx"
  octopus_automatic: true

  # --- SOLCAST DIRECT API ---
  solcast_host: 'https://api.solcast.com.au/'
  solcast_api_key: "xxxx"
  solcast_sites:
  - "xxxx"
  - "xxxx"
  solcast_poll_hours: 8

  # --- GROWATT CONTROL ENTITIES ---
  inverter_mode:
  - select.growatt_pv_inverter_priority
  inverter_mode_entity:
  - select.growatt_pv_inverter_priority
  inverter_mode_eco: "Load First"
  inverter_mode_charge: "Battery First"
  inverter_mode_grid: "Grid First"

  # --- MINIMUM SOC SENSORS (Mode-Specific) ---
  eco_reserve:
  - number.growatt_pv_inverter_load_first_battery_minimum_soc
  charge_reserve:
  - number.growatt_pv_inverter_load_first_battery_minimum_soc
  discharge_reserve:
  - number.growatt_pv_inverter_grid_first_battery_minimum_soc

  # --- TIME SLOTS (Eco/Normal Mode) ---
  eco_start_time:
  - select.growatt_pv_inverter_load_first_time_1_begin
  eco_end_time:
  - select.growatt_pv_inverter_load_first_time_1_end

  # Battery First (Charge)
  charge_start_time:
  - select.growatt_pv_inverter_battery_first_time_1_begin
  charge_end_time:
  - select.growatt_pv_inverter_battery_first_time_1_end

  # Grid First (Discharge)
  discharge_start_time:
  - select.growatt_pv_inverter_grid_first_time_1_begin
  discharge_end_time:
  - select.growatt_pv_inverter_grid_first_time_1_end

  # --- ENABLERS & SWITCHES ---
  grid_charge_enable:
  - select.growatt_pv_inverter_battery_first_charge_from_grid
  scheduled_charge_enable:
  - select.growatt_pv_inverter_battery_first_time_1
  scheduled_discharge_enable:
  - select.growatt_pv_inverter_grid_first_time_1

  # Standardized to eco_enable
  eco_enable:
  - select.growatt_pv_inverter_load_first_time_1

  # --- BATTERY & POWER ---
  soc_max:
  - 4.6
  reserve_min: 10
  soc_max_charge: 95
  charge_rate_percent:
  - number.growatt_pv_inverter_battery_first_charge_rate
  discharge_rate_percent:
  - number.growatt_pv_inverter_grid_first_discharge_rate
  battery_power:
  - sensor.growatt_pv_inverter_battery_discharge_power
  pv_power:
  - sensor.growatt_pv_inverter_pv_power_total
  load_power:
  - sensor.growatt_pv_inverter_house_load
  grid_power:
  - sensor.grid_usage
  soc_percent:
  - sensor.growatt_pv_inverter_battery_soc

  # --- ENERGY HISTORY ---
  load_today:
  - sensor.growatt_pv_inverter_today_s_load
  import_today:
  - sensor.growatt_pv_inverter_today_s_grid_import
  pv_today:
  - sensor.growatt_pv_inverter_today_s_solar_energy
  export_today:
  - sensor.growatt_pv_inverter_today_s_grid_export

  # --- TARIFF & CALCS ---
  metric_octopus_import: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_rate)'
  calculate_best: true
  calculate_charge: true
  calculate_discharge: false```


The templates for the growatt examples are via solar assistant, however I'm using a solax modbus pointed to my growatt
shinwifi lan x2 datalogger as I'm running it through my green home assistant box?


Thanks for your help so far, it's greatly appreciated,

Cheers,

Will

[gcoan]

Thanks Will for clarifying the source of your apps.yaml, this is an excellent example of why you should not trust anything that an LLM AI engine provides!

Almost all of the configuration provided is an AI hallucination that Predbat won't recognise !
I like the phrase hallucination, I heard it on a podcast recently, it excellently captures the dangers of using AI that makes stuff up if it doesn't know the answer, but it does so confidently so you think its correct when its in fact garbage.

Looking the template you have, these seconds are valid:

--- OCTOPUS DIRECT API ---

--- SOLCAST DIRECT API ---

--- BATTERY & POWER ---

--- ENERGY HISTORY ---

--- TARIFF & CALCS ---

The rest (i.e. most of the battery/inverter control) is not. The configuration items Gemini has provided are simply not recognised by predbat as being part of apps.yaml - the apps.yaml documentation https://springfall2008.github.io/batpred/apps-yaml/ and custom inverter setup (linked earlier) contains details of what Predbat will recognise.

If you can't use the existing Growatt configurations (and can't change to using that integration method - which would give you a proven configuration), then your job will be a bit harder, but if you're using the solax modbus then you maybe can start from the existing solax modbus integration configurations and adapt that to the sensor names that your Growatt has.

If that doesn't work then you are into creating a completely custom configuration. Details are in the link I provided earlier, but in essence:

• you define its a custom inverter type
• you define what capabilities your inverter has
• you configure the sensors that match those capabilities (things like start/end charge time, battery charge target, charge rate, battery reserve, etc)
• you define the commands to start/stop charging/discharging

If you have an app or existing method of controlling your inverter then you can use that to work out what settings you need to change in Home Assistant to start your inverter charging and stop it charging, etc. Focus on the charging side first, discharging is only necessary if you have an export tariff and your battery size and import/export rates make it profitable to charge overnight and export before the next cheap period.

Once you know the series of commands you need to start and stop the inverter charging you can either program those in to predbat's start charging service list, or you can write them in an automation script and call the script from predbat.

And leave Gemini alone would be my advice