batpred
batpred copied to clipboard
springfall2008
Car charging way over max charge
Describe the bug I've a manual input to select the max change I want on the car. I've moved from setting the soc of the car manually to an integration. The max charge percentage set isn't being followed.
Expected behavior Charge to the percentage I want the car to charge to. Predbat version
7.17.4
Environment details
- giv 8.2kw inverter hy gen 2 5kw
- Standard HAOS installer
- Anything else? apps (1).log appdaemon (2).log
Do you have the car charging limit set to the right figure as a % e.g. 75?
Yeah, I had it set to 55% overnight.
[image: image.png]
On Sun, 28 Apr 2024 at 19:54, Trefor Southwell @.***> wrote:
Do you have the car charging limit set to the right figure as a % e.g. 75?
— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/1021#issuecomment-2081600696, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JHZYNNCERMMWSLCXXC3Y7VAVZAVCNFSM6AAAAABG4X6PQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGYYDANRZGY . You are receiving this because you authored the thread.Message ID: @.***>
Have you set the battery size correctly in apps.yaml?
car_charging_battery_size: - 61.7 From what I can see in the logs, your car was set to be ready at 8am, so assume it finished then. The last line in the log is unfortunately at 07:36, so just misses the finish
At 2024-04-28 07:36:44.432295 INFO pred_bat: Current Car SOC kWh: [31.152330000000003] 2024-04-28 07:36:45.735228 INFO pred_bat: Plan car 0 charging from 31.152330000000003 to 33.935
So at 8am, Predbat was expecting the battery to be 33.935 kWh and at 07:36 it was 31.15kWh, which seems on track to hit it. This seems to match your settings 55%*61.7 = 33.935 kWh
Another scenario I guess is if the car stopped reporting the SoC, in which case Predbat assumes the SoC is zero and may have continued to charge until it reported again (by which time it would have overcharged), but would need the later logs to confirm.
Of course Trefor may spot something else entirely
Have you set the battery size correctly in apps.yaml?
car_charging_battery_size: - 61.7 From what I can see in the logs, your car was set to be ready at 8am, so assume it finished then. The last line in the log is unfortunately at 07:36, so just misses the finish
At 2024-04-28 07:36:44.432295 INFO pred_bat: Current Car SOC kWh: [31.152330000000003] 2024-04-28 07:36:45.735228 INFO pred_bat: Plan car 0 charging from 31.152330000000003 to 33.935
So at 8am, Predbat was expecting the battery to be 33.935 kWh and at 07:36 it was 31.15kWh, which seems on track to hit it. This seems to match your settings 55%*61.7 = 33.935 kWh
Another scenario I guess is if the car stopped reporting the SoC, in which case Predbat assumes the SoC is zero and may have continued to charge until it reported again (by which time it would have overcharged), but would need the later logs to confirm.
Of course Trefor may spot something else entirely
Yeah the battery is set in kwh total capacity in the configuration. I see where your coming from with 7.30am but that would be because I turned predbat to use manual soc as I couldn't get it to stop charging the car.
Ok, I've been diving into the data.
At 4:30am this morning Predbat thought my car SOC was...
Yet the entity above was at 53kwh at 4:30 a.m.
It's not looking at this SOC of the entity and adding the numbers of KWh onto something else... maybe the old disabled manual kws predbat entity? I don't know. But it's getting this number from somewhere. it started at 17kwh
Also I've no idea what is going on, on this predbat entity.
Car_charging_soc must be in % whichever mode you are in.
It's not actually used in manual mode, as that mode assumes.your car doesn't report a soc via home assistant (so this doesn't exist). For manual mode.you need to enter the staring soc (in kWh) and Predbat works out the final soc based on the max charge entity (input number in %) and the battery capacity in apps.yaml. It will then calculate the charge time needed.to deliver that.
It's odd because it used manual soc uses the number and automation uses percentage.
Anyway it's working now. Thanks
On Thu, 2 May 2024, 23:45 Geoffrey Coan, @.***> wrote:
I'll update the doc to make it more explicit that Soc is a percentage
— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/1021#issuecomment-2091869156, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JH3IH5MXQ7L7XIYJYLDZAK6ZRAVCNFSM6AAAAABG4X6PQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRHA3DSMJVGY . You are receiving this because you authored the thread.Message ID: @.***>