Predbat car start charge time (don't increment) #269

Activity

1. springfall2008

   changed the title [-]Predbat car start charge time[/-] [+]Predbat car start charge time (don't increment)[/+] on Sep 1, 2024
2. springfall2008

   added

   enhancementNew feature or requestNew feature or request

   on Sep 1, 2024
3. chalfontchubby

   added a commit that references this issue on Sep 18, 2026

   fix(ohme,gateway): don't treat a still-active long window as a year r…

   ...

   47bba41
4. chalfontchubby

   added a commit that references this issue on Sep 26, 2026

   fix(car): stop the car charge start time walking forward (#269)

   ...

   61b67a0
5. chalfontchubby

   added a commit that references this issue on Oct 6, 2026

   fix(car): stop the car charge start time walking forward (#269)

   ...

   0483777
6. springfall2008

   added 2 commits that reference this issue on Oct 8, 2026

   fix(car): stop the car charge start time walking forward (#269)

   ...

   4cf0338

   fix(car): stop the car charge start time walking forward every cycle (#…

   ...

   55c887f
7. springfall2008 commented on Oct 8, 2026

   

   springfall2008

   on Oct 8, 2026

   Owner

   More actions

   (Posted by Claude on behalf of @springfall2008.)

   A partial fix for this has been merged in #5120 and will be in the next release.

   What it does now

   • The car charge start time no longer moves forward by five minutes on every update. Once a charging window is underway, predbat.car_charging_start and the planned attribute of the car charging slot sensor show the start of the cheap-rate window the charge is in.
   • The charge session itself is unchanged, as before.

   What still moves

   • The start is fixed within one cheap-rate window, but moves when the plan steps into the next one. With Predbat's default settings cheap periods are planned in 30-minute windows, so on a long overnight charge the start will typically step forward every 30 minutes instead of every 5. It stays put for the whole charge if Combine Charge Slots is turned on.
   • At midnight a window that began the evening before shows as starting at 00:00.
   • Octopus Intelligent slots are not covered: an Intelligent dispatch that is underway still shows a start that moves.

   Question

   Is that good enough, or would you like the start to stay at the time the charge really began for the whole session, including across midnight? That is a further change, so we would like to know it is wanted before doing it. I have left this issue open until we hear back.