Hanchu iESS Inverter Configuration

[upton68]

Hi, I'd like to share my Hanchu iESS inverter configuration for possible inclusion in the supported inverter list. I've been running this stably with Predbat for several months.
System
Hanchu iESS dual battery system (2× 9.4kWh = 18.8kWh total)
Cloud API integration via HACS: hanchu-ess-ha
Single inverter
apps.yaml extract
Note: All entity IDs contain xxxxxx as a placeholder for the device serial number. This is automatically assigned by the hanchu-ess-ha integration during setup and will be unique to your installation. Check your own HA entity IDs to find your serial number and substitute it throughout.
`charge_rate:

• number.hanchuess_xxxxxx_charge_power_limit
  discharge_rate:
• number.hanchuess_xxxxxx_discharge_power_limit

soc_percent:

• sensor.hanchuess_xxxxxx_battery_soc
  soc_max:
• sensor.hanchuess_xxxxxx_battery # Returns capacity in kWh, used to derive soc_kw
  soc_kw:
• sensor.home_battery_state_of_charge_kwh

battery_power:

• sensor.hanchuess_xxxxxx_battery_power
  battery_power_invert:
• true # Hanchu sign convention is opposite to Predbat's
  pv_power:
• sensor.hanchuess_xxxxxx_power
  load_power:
• sensor.hanchuess_xxxxxx_load_power
  load_power_invert:
• false
  grid_power:
• sensor.hanchuess_xxxxxx_grid_power
  grid_power_invert:
• true # Hanchu sign convention is opposite to Predbat's

charge_start_service:

• service: input_boolean.turn_on
  entity_id: input_boolean.predbat_charge_start
• service: input_boolean.turn_off
  entity_id: input_boolean.predbat_discharge_start
  charge_stop_service:
• service: input_boolean.turn_off
  entity_id: input_boolean.predbat_charge_start
  discharge_start_service:
• service: input_boolean.turn_on
  entity_id: input_boolean.predbat_discharge_start
• service: input_boolean.turn_off
  entity_id: input_boolean.predbat_charge_start
  discharge_stop_service:
• service: input_boolean.turn_off
  entity_id: input_boolean.predbat_discharge_start

inverter_battery_rate_min:

• 0 # Older firmware may require 500
  inverter_limit:
• 5000 # Set to match your inverter's rated capacity
  inverter_limit_charge:
• 5000 # Set to match your inverter's rated capacity
  inverter_limit_discharge:
• 5000 # Set to match your inverter's rated capacity
  inverter_limit_export:
• 5000 # Set to match your inverter's rated capacity
  battery_rate_max:
• 5000 # Set to match your battery's maximum charge/discharge rate

battery_charge_power_curve:
97: 0.5
98: 0.2
99: 0.1
battery_discharge_power_curve:
4: 1.0

inverter_clock_skew_start: 0
inverter_clock_skew_end: 0
inverter_clock_skew_discharge_start: 0
inverter_clock_skew_discharge_end: 0
inverter_can_charge_during_export: false # Single inverter setup
clock_skew: 0`

Bridge automations
Hanchu has no explicit charge/discharge enable toggles, and no native Predbat integration, so control is via four HA automations triggered by input_boolean helpers. Charge and discharge are mutually exclusive — the start services enforce this by turning off the opposing boolean.
Start charge
`alias: Predbat Bridge - Start Charge
triggers:

• entity_id: input_boolean.predbat_charge_start
  to: "on"
  trigger: state
  actions:
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_charge_slot_1_start
  data:
  time: "{{ now().strftime('%H:%M:%S') }}"
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_charge_slot_1_end
  data:
  time: "11:00:00"Stop Chargealias: Predbat Bridge - Stop Charge
  triggers:
• entity_id: input_boolean.predbat_charge_start
  to: "off"
  trigger: state
  actions:
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_charge_slot_1_start
  data:
  time: "00:00:00"
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_charge_slot_1_end
  data:
  time: "00:00:00"Start Dischargealias: Predbat Bridge - Start Discharge
  triggers:
• entity_id: input_boolean.predbat_discharge_start
  to: "on"
  trigger: state
  actions:
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_discharge_slot_1_start
  data:
  time: "{{ now().strftime('%H:%M:%S') }}"
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_discharge_slot_1_end
  data:
  time: "11:00:00"Stop Dischargealias: Predbat Bridge - Stop Discharge
  triggers:
• entity_id: input_boolean.predbat_discharge_start
  to: "off"
  trigger: state
  actions:
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_discharge_slot_1_start
  data:
  time: "00:00:00"
• action: time.set_value
  target:
  entity_id: time.hanchuess_xxxxxx_discharge_slot_1_end
  data:
  time: "00:00:00"`
  Caveats
  Automation latency: start/stop commands are occasionally delayed by up to ~2 minutes due to HA automation scheduling. This has not caused any practical issues over several months of use.
  No explicit enable/disable: Hanchu has no charge/discharge enable toggle. The slot zeroing mechanism (setting both start and end to 00:00:00) is the disable method.
  Slot end sentinel: the charge/discharge start automations set the slot end to 11:00:00 as a safe outer bound. Predbat controls the actual window by firing stop when needed.
  Min SOC is managed through Predbat's own configuration, not via an inverter entity.
  Happy to answer questions or provide additional detail.