Charging fail

curry756

Hello. I woke up to a flat battery despite having a 00:00 to 05:30 charge window scheduled.

The reason for this was that I also had a 23:00 to 00:00 scheduled and the battery was at 100% when it tried to schedule the 00:00 to 05:30 so it didn’t do it.

It’s frustrating as I had set the car to charge assuming that it would set the schedule and not charge the car from the house battery, which is exactly what it did :facepalm

Just sharing this with you so you can put some logic in to mitigate this. Maybe check the SOC at the start of each 30 min slot or something.

I have attached screenshots

Cheers

admin

curry756 You should have toggled on the 'Hold charge' option on your Agile charge window settings, which would have prevented this.

curry756

Thanks for the swift reply. I didn’t want to hold charge between charging slots. As there may be a bigger gap. It might have charged 2000-2030 then not again until 0300, so “holding the charge between 2030 and 0300 is not what I was after?

Unless I am misunderstanding how the hold charge works?

Thanks
PC-

admin

curry756 But if you had for your 00:00-05:00 charge window (Hold Charge works at the level of your charge window), it would have used the Hold Charge for that specific period (despite the battery being at 100%) in which you had scheduled your car to charge.

curry756

I get what you are saying. But that’s not my use case.

My rule selects 4 cheapest slots between 0000-0500
If those shots happened consecutive then all 4 slots being applied would be based on the initial SOC percentage. If this was 100% (as in this case) then I’d get no charging during those 4 consecutive slots.
If those slots were split up then the first slot would check the SOC reading and only prevent the one charge slot from being applied. Every other slot would be treated individually by the same logic.

Forget the car charging. That’s more automation that’s is adding complexity to this use case.

So if I “hold charge” during that window, then that does not solve my issue right? I want to be able to bypass your logic and always set charge slots regardless of that initial SOC.

Does that make sense?
Thanks :)

admin

curry756 I see. So the easiest work around for this would be to add a toggle that basically does something like "Don't skip charge slots if at 100% SOC"

Checking every 30 mins is trickier because of our condensing slots logic.

curry756

admin

Exactly :)

Does this feature exist or does it need to go into the backlog?

Cheers
PC-

admin

curry756 Needs to go on backlog, but could be a quick win.

curry756

admin Please can you let me know the outcome. thanks!

curry756

curry756 did this ever get added?

admin

curry756 We have a mechanism for this now yes.

If your conditional SOC for your Agile charge window is greater than your current SOC, we defer the condition for half an hour to the next slot check. For a continuous block of slots.

curry756

admin thanks!!!