Repository navigation
IOG ESS Battery Charging at 1200 when car_charging_now off #5424
Description
Activity
Automated first-pass triage — a bot's first pass; a maintainer will review before any action is taken.
Classification: bug · Priority: low (the recurring form of this is already fixed in v9.3.6, and what remains is bounded to a few minutes and self-reverts — detail below)
What your attachments show (v9.3.5, confirmed from the log):
- At the 12:00 cycle the Octopus Energy integration published two planned Intelligent dispatches for your car, including
10-06 12:00:00-10-06 12:30:00, ~3.48kWh, source SMART— arriving exactly with the midday refresh you suspected. Your car was already at its charge limit (SoC 54.0 kWh vs limit 48.6 kWh) andcar_charging_nowwas off. - In v9.3.5,
rate_add_io_slots()prices every future planned dispatch off-peak for the house battery with no check that the car can still use the energy. It did drop the car's own slot —Car 0 is already charged, ignoring additional charging slot from 10-06 12:00:00 - 10-06 12:30:00(12:00:17) — but that skip only stops the car, not the house plan. With 12:00–12:30 priced at 6.57p, Predbat wrote Force Charge 12:00–12:30 (target 100%) to the Fox ESS at 12:00:17. That is the ESS charging you saw. - The only catch-up mechanism v9.3.5 had for a dispatch the car isn't charging in is the dynamic-load check, and it deliberately waits 3 minutes into a dispatch (charger wake-up) plus a 2-minute grace before cancelling. It fired at 12:05:27 —
Octopus Intelligent: car 0 is in a dispatch but not charging, cancelling its slots— and a replan followed. So the automatic revert was about 2 minutes after you took manual control at ~12:03; you were just ahead of it. - Predbat also flagged the billing effect itself at 12:04:12: "car 0 dispatch active ... but the car is not charging - import in this slot may be billed at the full rate" (GH#5080) — the 6.57p the plan charged at would really have been billed at the midday rate, because Octopus only bills a dispatch slot cheap when the car charges in it.
- Your overnight dispatches aren't affected by the issue: the fixed 23:30–05:30 IOG band is cheap by tariff regardless of dispatches, so the battery charging there is normal.
What v9.3.6 changes: PR #5403 (merged yesterday, closes #4482) stops pricing Intelligent dispatch minutes that no car can still use off-peak when
octopus_intelligent_consider_fullis on — so a daytime dispatch for a full car published ahead of time is no longer a cheap house-battery window. Your configuration (consider_full on, trust_slots off — both confirmed from your debug yaml) is exactly what the fix targets. It does not remove this exact timing, though: the new gate deliberately starts with the half hour after the current one (a car that charges part-way through the current half hour does make the whole half hour cheap on Octopus's billing), so a dispatch that starts the moment it is published still gets its first half hour priced cheap and can still charge the house battery for up to ~5 minutes until the same dynamic-load cancel + replan reverts it. Your log already shows that revert mechanism working at 12:05:27.Next step: please update to v9.3.6 (your log shows it pending; autoupdate is off, so update manually). If the ESS still charges during a dispatch the car won't use on v9.3.6, attach that time's debug snapshot (Plan → History → Debug column) and
predbat.log— see the debug history docs — and it will be re-examined; the remaining same-instant-start case above is a separate (smaller) question for the maintainer, tracked by #4516.Related: #4482 (closed — fixed by #5403), #4516 (open: dispatches treated as cheap before EV charging earns the slot), #5080 (open: monitoring imports billed at peak during active dispatches).
(For transparency: verified against current main (v9.3.6) and by diffing the published v9.3.5 source; I could not replay your debug file — the dump currently fails to load under the replay tool with a known loader limitation — test
iog_car_need_gateon main passes instead.)- At the 12:00 cycle the Octopus Energy integration published two planned Intelligent dispatches for your car, including
Thanks!
ESS battery charging when car was not and configured for inhibit
Valid Octopus dispatch via Bottlecap Dave integration but should have been prevented by car_charging_now off, this driven by no Wallbox charge current or no Wallbox state charging
Left charging for 3 mins then set manual export due to no reversion.
Possibly due to co-incidence with 12:00 IOG daily reset?
Predbat version V9.3.5
HAOS VM, latest with bottlecap Dave Octopus integration latest.
predbat (1).log
predbat_debug.yaml (1).txt