• SolaxIOG

  • Smart discharge schedule and IOG charge clash

michaelm Whilst users with IOG and solar storage can take advantage of our IOG functionality to top up their solar battery, our IOG integration is especially useful for users who have their system wired in a such a way that the house does see the car load.

So you just end up charging the car.

If you wanted to truly export, it's pretty obvious you'd unplug the car, and no IOG adhoc slots would be assigned, therefore I feel it makes sense to have IOG charging take priority even when export schedules are configured.

Just allows IOG users to not have to worry that their active export schedules (which they may well use from time to time) will interrupt adhoc charges that are running.

Happy to hear other IOG users' input on this.

      admin I'm pretty sure I made this point about 7-10 days ago, on another thread.

      Just for clarity, I definitely don't want my batteries emptying into the EV. That's the whole point of using WW for me.

          MrMessy Thanks, yep, I remember the thread.

          This should now be addressed, deployed via a server fix. Let us know how it goes.

            admin Thank you for the quick fix as always

            So was the fix along the lines of my sugegstion whereby the Smart Discharge Schedule does NOT activate if an IOG schedule is in place?

            How did you account for the fact that Octopus cwaps schedules at will recently!!

            Thanks

                michaelm So was the fix along the lines of my sugegstion whereby the Smart Discharge Schedule does NOT activate if an IOG schedule is in place?

                If there's an IOG schedule coming active or coming up in the next few mins, a configured export schedule will be skipped.

                michaelm How did you account for the fact that Octopus cwaps schedules at will recently!!

                We check every minute for new IOG schedules.

                There may be a race-condition, but we'll have to see how we go. I think it'll be fine. (Famous last words!)

                      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

                                            jablad Right, if you do not see mapped charges in the Octopus app, it means Octopus do not control it and when we query the Octopus API, we get no mapped slots, see the logs below:

                                            This is an issue with Ohme chargers, which are currently not integrated with Octopus' API - as in, Octopus controlling the IOG charges.

                                                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.

                                                        admin interestingly, looking at this morning it looks like there were instructions set to charge beyond 05:30 am but I’m not sure they worked as the battery started draining at 05:30 when the car was still charging!

                                                            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?

                                                                    jablad Right, I see. We do have adhoc charges for you on the 15th in the morning. See logs below.

                                                                    And it looks like they were received and correctly sent.

                                                                    Hmm. I think there's a fix we need to apply. Will keep you posted.