Smart discharge schedule and IOG charge clash

admin

Hi - I’ve got a number of export schedules setup after taking advice on this forum and they work perfectly, but I’ve always wondered how to get the dynamic charge slots allocated by IOG to override them and charge the battery, so I’m pleased to see this has been resolved.

However, I can’t seem to get it working for some reason. Tonight, IOG have given me slots from 20:30 but the export schedules have run.

Can you help please?

embarrassed-description

jablad Thanks for reporting, this is odd. We've enabled some extra logging on your account so we can better diagnose what's gone wrong here. Particularly if it happens again.

admin thanks - same tonight, car started charging at 23:00 but export schedules ran. In the IO section, it always just shows the 23:30 - 05:30 charge slot

jablad Thanks, looks like somehow your adhoc slots aren't being picked up. More logging added, we'll keep you updated.

jablad Could you let us know when you plug in your EV please and when you get an adhoc slot mapped from Octopus? We can then check our logs to see what's going on, thank you!

Just because it was mentioned above, Octopus prefer that you leave the car plugged in when at home, so that they can maximise the slots available to them to manage the load. And, if we consider the new world of vehicle to load/grid that will become a requirement. The likelihood is that the car will nearly always be connected to a point that is seen as house load (and for reasons of monitoring, one would argue it should be) but then this brings about the dreaded battery to EV discharge scenario.
Hopefully you can remove all instances of this being the outcome until we get to a point when this becomes almost impossible to do via standard API calls on any home battery and EV solution installed. We are a long way off that yet though.

admin hi - just plugged in and it’s given me a load of slots before the normal 23:30, first one starts at 18:45

admin I see, so do Octopus tell Ohme and it’s Ohme that control the charges then?

jablad Not 100% sure how it works, but I think Ohme control it yeah. And send details to Octopus after the fact.

All we know is that if you do not see mapped charges in the Octopus app, we don't know which charges are the adhoc cheap ones.

jablad Would make sense if we cannot see the mapped charges from the Octopus API.

admin Sorry I don’t think I worded that very well, when IO decided to charge past 05:30 then the logs suggest that WW sent an instruction to charge the batteries past 05:30, but it didn’t actually execute. Does that make sense?