Predbat with Intelligent Go + Hypervolt: should EV target be final SoC or “charge to add”?

[thorrrr]

Hi all,

I’m trying to get Predbat properly set up before I ever let it control anything, and I want to make sure I’ve understood the EV side correctly.

My setup is:

• Tesla Powerwall 3
• Octopus Intelligent Go
• Hypervolt Home 3 Pro
• Hyundai/Kia EV
• Predbat running standalone in Home Assistant

Important detail: Octopus Intelligent Go is controlling the Hypervolt charger, not the car directly.

Also, the EV charger is wired outside / after the inverter, so the system can never charge the EV from the Powerwall. The EV is effectively grid-side, not battery-side.

At the moment the car is away from home, so I understand why Car kWh is blank in the Predbat plan right now.

The part I’m unsure about is how Predbat should interpret the Octopus Intelligent target when OIG is controlling the Hypervolt.

In the Octopus app / HA entities I have:

• ready by time: 07:00
• charge to add: +30%

The car itself is separately limited to 80%.

What I’m trying to work out is whether Predbat expects that EV target to be:

• the final SoC target
  or
• the amount to add

From the Octopus app it looks like this is definitely “charge to add”, not final target %.

So my questions are:

1. When Intelligent Go is controlling the Hypervolt, should octopus_charge_limit / car_charging_limit in Predbat be an absolute final target %, or can it correctly work with Octopus’s “charge
   to add” value?
2. If Predbat expects a final target %, do people normally create a helper/template in HA to convert “charge to add” into the final SoC target?
3. What is the recommended Predbat setup when Octopus controls the Hypervolt charging slots and Predbat is only supposed to plan the house battery around that?
4. Given that the EV charger is outside the inverter and cannot be supplied by the Powerwall, is there anything special I should be doing in Predbat beyond car_energy_reported_load: False?
5. Is it OK to use the select...intelligent_target_time entity for octopus_ready_time, or is it better to enable the disabled time...intelligent_target_time entity?

I’m keeping Predbat in monitor mode for now because I want to be sure the EV side is modelled correctly before switching anything on.

Thanks.
predbat-apps-redacted.txt

[gcoan]

1 & 2. With Octopus led EV charging predbat doesn't care about what is put into the car, its Octopus controlling that. You wouldn't need any helpers for predbat
3. The configuration you need for Octopus led charging is in the documentation https://springfall2008.github.io/batpred/car-charging/#octopus-led-charging
4. No
5. Per the documentation it is recommended to use the time entity https://springfall2008.github.io/batpred/car-charging/#planned-car-charging