Huawei TOU setup

[pedromrg]

Hello,

First let me congratulate the developer, this integration works very well, using it for 2-3days and it's very good.

My configuration is almost good, but yesterday I had an issue (I suspect it was because I changed from TOU to Maximise self-consumption) therefor at 4am my battery went to standby and forcible charge failed to start(I suspect it was because of this)

Now I was reading the documentation https://springfall2008.github.io/batpred/inverter-setup/#huawei again and found "Set the Huawei inverter work mode to 'TOU' (Time Of Use)."

Question is, how should I configure the TOU charging and discharging periods ?

Thanks.

[gcoan]

Question is, how should I configure the TOU charging and discharging periods ?

you should set it to TOU for all the time so predbat can then set charging and discharging periods within that

[pedromrg]

Also found this in the documentation.

has_target_soc
When True, Predbat uses the charge_limit sensor configured in apps.yaml to set the target charge SoC % setting for the inverter. The charge limit is the limit that the inverter will charge the battery up to. When False, charging will be turned on and off by Predbat rather than the inverter doing it based on the target SoC %.

In Huawei inverter a service is called.
Forcible charge to 100% at 3000w

Meaning the inverter controls when the charge finishes (100%)

So would it be worth it to use this for Huawei?

Saying this because at the moment looks like predbat waits for battery to reach x % to call service forcible charge/discharge stop? But in case of 100% the inverter stops the charge before predbat detects the 100% ?!

Any idea on this ?

Thanks

[gcoan]

in the huawei apps.yaml, charge_limit is already set:

  charge_limit:
    - number.battery_end_of_charge_soc

although this is actually being ignored by predbat as has_target_soc is set to False in the HU inverter definition in config.py:

    "HU": {
        "name": "Huawei Solar",
        "has_rest_api": False,
        "has_mqtt_api": False,
        "output_charge_control": "power",
        "charge_control_immediate": True,
        "has_charge_enable_time": False,
        "has_discharge_enable_time": False,
        "has_target_soc": False,
        "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": 4,
        "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,
    },

potentially we could change the standard inverter definition for Huawei inverters in the predbat code, or you could make a custom inverter definition if you wanted to overwrite the standard behaviour

but before we do that, we need to understand whether the inverter has the concept of a target SOC sensor?

The target SOC is used not just for charging to 100% as you suggest it is, but more, it gives Predbat the ability to charge the battery to an appropriate SOC level based on the plan. Predbat can do this by monitoring the SOC as you note, but it's more accurate if the inverter can do this itself.

my guess is the Huawei doesn't have this concept in the inverter so that's why the inverter definition doesn't include it

[pedromrg]

number.battery_end_of_charge_soc looks like an old sensor for Huawei integration, I cant find it anymore.

Ok, now I understand.

number.battery_end_of_charge_soc does not exist anymore, BUT we have sensor.batteries_forcible_charge with attributes:

mode: Stop
setting: Time
charge_power: 3000
discharge_power: 0
target_soc: 100
duration: 0
icon: mdi:battery-charging-medium
friendly_name: Batteries Forcible charge

Maybe this could be used ?

[pedromrg]

Coming back to this.
Setting soc max to 14.5 did not do the trick, today it happened again, somehow Predbat did not detect the battery reaching 100%

The battery was discharging, when I checked predbat interface it says the battery is charging until let's say 57% but that is not the case, battery was discharging.
To fix it I restarted predbat addon, and it got back in track, triggered charging (Im still in the cheap period)

Any idea how I can troubleshoot this further?

Thanks

[pedromrg]

Today the battery charged from empty 16% to full 100%

Got the log here, maybe it can help.

31829	2026-03-02 05:12:04.166199: Note: Inverter does not support discharge freeze - disabled
31828	2026-03-02 05:12:04.165054: Note: Cannot find battery discharge curve (no full rate discharge curve found for battery to empty), one of the required settings for soc_percent, discharge_rate, battery_power and predbat.status do not have history, check apps.yaml
31827	2026-03-02 05:12:04.139236: Looking for discharge curve, have found 8.0 days of history data, max days 8
31826	2026-03-02 05:12:03.725036: Looking for discharge curve with sensors sensor.batteries_state_of_capacity, number.batteries_maximum_discharging_power, predbat.status and sensor.batteries_charge_discharge_power
31824	2026-03-02 05:12:03.724903: Inverter 0 sensor.predbat_HU_0_scheduled_discharge_enable set to False
31823	2026-03-02 05:12:03.724878: Inverter 0 write_and_poll_switch: No write needed for scheduled_discharge_enable as False == False
31814	2026-03-02 05:10:04.514353: Inverter 0 Skipped service discharge_stop_service domain discharge service_name huawei_solar.stop_forcible_charge as it was previously called.
31809	2026-03-02 05:10:04.513873: Adjust idle time, charge 05:00:00-09:00:00 discharge 00:00:00-00:00:00
31808	2026-03-02 05:10:04.513764: Inverter 0 Hold charging as SoC 100% is above target SoC 100% set_discharge_during_charge True
31738	2026-03-02 05:10:03.220397: Note: Inverter does not support discharge freeze - disabled
31737	2026-03-02 05:10:03.219344: Note: Cannot find battery discharge curve (no full rate discharge curve found for battery to empty), one of the required settings for soc_percent, discharge_rate, battery_power and predbat.status do not have history, check apps.yaml
31736	2026-03-02 05:10:03.194365: Looking for discharge curve, have found 8.0 days of history data, max days 8
31735	2026-03-02 05:10:02.806590: Looking for discharge curve with sensors sensor.batteries_state_of_capacity, number.batteries_maximum_discharging_power, predbat.status and sensor.batteries_charge_discharge_power
31734	2026-03-02 05:10:02.806555: Inverter 0 discharge windows currently []

Maybe something with the discharge curve ?
Or

31838	2026-03-02 05:14:18.737715: Note: Cannot find battery discharge curve (no full rate discharge curve found for battery to empty), one of the required settings for soc_percent, discharge_rate, battery_power and predbat.status do not have history, check apps.yaml
31828	2026-03-02 05:12:04.165054: Note: Cannot find battery discharge curve (no full rate discharge curve found for battery to empty), one of the required settings for soc_percent, discharge_rate, battery_power and predbat.status do not have history, check apps.yaml
31815	2026-03-02 05:10:04.514404: Inverter 0 Skipped service charge_start_service domain charge service_name huawei_solar.forcible_charge_soc as it was previously called.
31813	2026-03-02 05:10:04.514195: Inverter 0 Current Target SoC is 100%, already at target
31812	2026-03-02 05:10:04.514152: Inverter 0 adjust target SoC for charge to 100% based on requested all inverter SoC 100%
31811	2026-03-02 05:10:04.514116: Setting charging SoC to 100% as per target
31808	2026-03-02 05:10:04.513764: Inverter 0 Hold charging as SoC 100% is above target SoC 100% set_discharge_during_charge True
31807	2026-03-02 05:10:04.513689: Inverter 0 Target SoC 100%, (this inverter 100%), battery temperature 20°C, select charge rate 3000W (real 3000W), current charge rate 3000W
31806	2026-03-02 05:10:04.513564: Inverter 0 Charge window will be: 2026-03-02 05:00:00+00:00 - 2026-03-02 09:00:00+00:00 - current SoC 100%, target 100%
31793	2026-03-02 05:10:04.181234: Best charging limit SoC's [15.0, 2.5, 15.0, 15.0]kWh, export []kWh gives import battery 20.7kWh, house 47.29kWh, export 0.26kWh, metric 1115.78c, metric10 1720.6c
31781	2026-03-02 05:10:03.863343: SoC: [ 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 14.39, 13.79, 13.21, 12.78, 12.72, 12.51, 12.32, 12.33, 12.74, 12.07, 10.55, 9.47, 8.82, 8.41, 8.21, 7.73, 7.36, 6.84, 6.21, 5.27, 3.2, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.5, 3.96, 5.41, 6.87, 8.32, 9.78, 9.42, 9.38, 9.53, 9.86, 10.53, 11.05, 12.06, 13.27, 14.33, 14.88, 14.96, 14.9, 14.68, 14.61, 14.69, 14.27, 13.8, 13.15, 12.02, 10.56, 8.96, 7.41, 6.08, 4.84, 3.67, 2.55, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4] kWh
31779	2026-03-02 05:10:03.861597: predict best end_record 03-04 05:05:00, final soc 2.64kWh, metric 1115.78c, metric_keep 0kWh, min_soc 2.4kWh @ 03-02 19:35:00, load 131.09kWh, PV 47.17kWh
31771	2026-03-02 05:10:03.761040: SoC: [ 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 14.21, 13.3, 12.09, 10.83, 9.74, 8.6, 7.28, 6.14, 5.48, 3.9, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.5, 3.66, 4.83, 5.99, 7.16, 8.32, 7.67, 7.16, 6.46, 5.75, 5.21, 4.78, 4.71, 4.87, 4.92, 4.68, 4.07, 3.34, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4] kWh
31769	2026-03-02 05:10:03.759250: predict best10 end_record 03-04 05:05:00, final soc 2.59kWh, metric 1720.6c, metric_keep 0kWh, min_soc 2.4kWh @ 03-02 14:15:00, load 136.94kWh, PV 20.66kWh
31761	2026-03-02 05:10:03.663120: SoC: [ 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 15.0, 14.21, 13.3, 12.09, 10.83, 9.74, 8.6, 7.28, 6.14, 5.48, 3.9, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 2.4, 3.56, 4.73, 5.89, 7.06, 8.22, 9.38, 10.55, 11.71, 11.06, 10.55, 9.85, 9.14, 8.6, 8.17, 8.1, 8.26, 8.31, 8.07, 7.46, 6.73, 5.79, 4.97, 4.29, 3.34, 2.4, 2.4, 2.4, 2.4

Target is always at 100% predbat should change to hold charge, hence set discharge power of Inverter to 0.

But plan just shows charge.

[pedromrg]

44369 | 2026-03-03 23:39:20.242734: Note: Cannot find battery discharge curve (no full rate discharge curve found for battery to empty), one of the required settings for soc_percent, discharge_rate, battery_power and predbat.status do not have history, check apps.yaml -- | -- 44368 | 2026-03-03 23:39:20.195071: Looking for discharge curve, have found 15.0 days of history data, max days 15

checked all sensors they have history going back 14days +

!? any idea why the error?

[pedromrg]

OK @gcoan let's wrap this TOU subject.

Been testing many combinations and I must say the best is this:

Set TOU to:
00:00-12:00/1234567/-
12:00-23:59/1234567/-

This will ensure TOU is active and battery will discharge/charge 24h (if necessary), and we will be able to use Capacity control.

Also another important part is to set

Capacity Control mode: Active capacity control - select.batteries_capacity_control_mode

End-of-charge: 15% (or something you would find approriate) - number.batteries_end_of_discharge_soc
Peak Shaving 17% (needs to be +2% above End-of-charge) - number.batteries_peak_shaving_soc

And set Capacity control period:
00:00-23:59/1234567/20000W
(20 000w is unreal for my house so this will never trigger but will keep the battery awake to receive charge commands)

What active capacity control mode with peak shaving does is expect the house load toe be above 20 000w and use the battery to support it. (This is important to keep the battery awake all night, if this is not set the battery will go into sleep mode hence not accepting charge/discharge commands until PV wakes it up in the morning)

--
References:
https://github.com/wlcrs/huawei_solar/wiki/Capacity-control
https://github.com/wlcrs/huawei_solar/wiki/Time-of-Use-control