elaborate-routine

I've been using the above Agile Charge window settings for a few weeks now to ensure that I have enough charge to get through the lower morning peak. The aim for me is to just have enough charge so that I don't import at higher rates than my export rate when I know solar will be filling the battery the next day. My overnight usage is very predictable.

Its performance at doing this varies depending on when WW picks up the 3 cheapest slots. If all three occur early in the night the long hold period that follows discharges the batteries so that there is insufficient charge to cover the peak. If I increase the charge level I find that the next night WW picks up 3 cheap slots later in the night and I miss out on some Solar export the following day as I can still have almost 30% in the battery at the end of the morning peak. Another problem is that if all three cheapest slots are contiguous the state of charge is only measured once at the start of the first slot which, if slightly higher than the threshold, means that all three charge slots are ignored needing a higher charge threshold level to be set to compensate.

What would be the best approach to coping with this?

(I also have a similar problem on low solar days with the evening peak which uses a different Agile schedule.)

(My batteries store 8kW and my hold discharge rate is about 330W so effectively they hold charge for up to 24 hours or 35% charge will hold for 8 hours)

    WindyMiller . Another problem is that if all three cheapest slots are contiguous the state of charge is only measured once at the start of the first slot which, if slightly higher than the threshold, means that all three charge slots are ignored needing a higher charge threshold level to be set to compensate.

    We can do something about that for sure. Similar to if an instruction fails and it's a contiguous slot, we move the start half an hour back (-> future), where the condition would get re-evaluated again.

        admin That would go some way to improving the way this works. Currently I check to see which slots are selected and "adjust" them to not be contiguous and to make sure at least one of them is late in the night. I guess your algorithm can't do this as it simply picks the three cheapest slots which could be early or late? Time to include a bit of AI? Tell it what you're trying to achieve and let it work out what to do?

        If Agile rates drop, which I hope they will do soon, I'll be back to full charging overnight and exporting all the solar.

          10 days later

          admin Same situation last night with 3 contiguous chosen slots. First slot got an inverter offline. This time however WW retried 30 minutes later at the start of the 2nd slot. This worked fine.

          Thank-you for that fix.

            admin This fix has been applied actually. @WindyMiller - contiguous Agile slots where the threshold in terms of SOC etc is not met, will result in the next 30 min check being retried.