Describe the bug
I use octopus intelligent go with the zappi integration. I have setup predbat to know my cars state of charge and target charge. Predbat is assuming that every intelligent go slot the car will be charging at full rate even when the car will have charged up by then, which means that predbat will not export.
If the car isn't actively charging it then seems like it will mark every slot as car kwh '-'.
I've tried setting up car_charging_planned: and car_charging_planned_response: and while predbat seems to understand it (because the slots will only stay green and low rate if it's plugged in, if I change the regex so it doesn't match predbat will show the slots as normal rate) - the car kwh doesn't get populated. If I take this code out, the car kwh does get populated again.
I've set
switch.predbat_octopus_intelligent_ignore_unplugged to true
switch.predbat_octopus_intelligent_consider_full to true
Expected behaviour
Because predbat knows the car soc and the car target charge (note, not the octopus target charge) and it knows the rate of charge and the car battery kwh total, I would expect predbat to predict when the car will be done charging (in the same sort of way it can predict solar - unless I'm misunderstanding how this should work?)
Predbat version
v8.32.12
Environment details
Sigenergy 12kw inverter
2x sigenergy 9kwh batteries
Docker
Relevant Settings
car_charging_energy: 're:(sensor.myenergi_zappi_[0-9a-z]+_charge_added_session|sensor.wallbox_portal_added_energy)'
num_cars: 1
car_charging_battery_size:
- 76.0
car_charging_soc:
- sensor.millie_battery
car_charging_limit:
- number.millie_charge_limit
Screenshots
When the car isn't charging:

Log file
predbat(2).log
Predbat debug yaml file
predbat_debug2.yaml.txt
Describe the bug
I use octopus intelligent go with the zappi integration. I have setup predbat to know my cars state of charge and target charge. Predbat is assuming that every intelligent go slot the car will be charging at full rate even when the car will have charged up by then, which means that predbat will not export.
If the car isn't actively charging it then seems like it will mark every slot as car kwh '-'.
I've tried setting up car_charging_planned: and car_charging_planned_response: and while predbat seems to understand it (because the slots will only stay green and low rate if it's plugged in, if I change the regex so it doesn't match predbat will show the slots as normal rate) - the car kwh doesn't get populated. If I take this code out, the car kwh does get populated again.
I've set
switch.predbat_octopus_intelligent_ignore_unplugged to true
switch.predbat_octopus_intelligent_consider_full to true
Expected behaviour
Because predbat knows the car soc and the car target charge (note, not the octopus target charge) and it knows the rate of charge and the car battery kwh total, I would expect predbat to predict when the car will be done charging (in the same sort of way it can predict solar - unless I'm misunderstanding how this should work?)
Predbat version
v8.32.12
Environment details
Sigenergy 12kw inverter
2x sigenergy 9kwh batteries
Docker
Relevant Settings
Screenshots
When the car isn't charging:

Log file
predbat(2).log
Predbat debug yaml file
predbat_debug2.yaml.txt