Agile Optimisation

adam

Have you considered an "Optimse" option for Agile, aiming to minimise cost/maximise net income?

Using estimated power consumption, upcoming Agile rates, estimated solar production, battery and inverter sizes, and export rates, work out the optimal charging / discharging schedule to minimise cost.

The user would need to provide any data that you can't read from their inverter.

There will surely be a need for such a tool which would save consumers on their bills and also reduce the strain on the grid by soaking up some of the cheapest greenest electricity when there is an excess.

admin

adam Yep - definitely on our list of things to look at. A smarter hands-off option that maximises ROI. Using usage, solar forecast, current SOC, prices etc. to work out whether to hold, import or export.

Needs a fair bit of work, but aiming for a Predbat equivalent in this arena.

adam

Excellent - I'm delighted to hear it.

adam

The tricky part might be the more advanced calculations, such as making allowances for round-trip losses.

Or even leaving a bit of empty space in the battery, so that if there is more solar production than the inverter can handle then the surplus can be stored in the battery and avoid clipping. I thought there might be insufficient controls through the API to achieve this, but I'm managing to do this through the webapp, so I expect it can be done. So, for example, yesterday I was generating 6.5kW, but my 5kW hybrid inverter could only convert 5kW for use in my house and for export to the grid, but it managed to put the remaining 1.5kW into the battery since the SOC was less than 100%.

4watts

adam
I think the round-trip losses/conversion/heat losses should be a user setting based on what they feel comfortable with along with a space/minimum forced discharge level.
Other than these I think a fully automated system should be able to manage based on usage patterns/ expected solar and HH rates.