Controlling battery discharges

[MartyMoose30053]

I am just wondering if a controlled discharging of the battery could be added as a feature.
I am trying a rudimentary way to do this based on my Base usage leading up to the cheap rates of IGo tariff.
I know my Base is 400-600wH so have set this schedule up below, adjusting how much charge is needed to ensure I do not deplete the battery to quickly or slowly.
I think that the App could be made to manage this far better and more reliably, what are others thoughts on this?

[Webreaper]

Unclear on what behaviour you're looking for. Are you wanting the app to intelligently discharge the battery faster or slower depending on how much time it has left to discharge, and what the SOC is?

E.g.:

• 1 hour until cheap period & 80% SOC, discharge at 95A
• 3 hours until cheap period & 60% SOC, discharge at 50A

[MartyMoose30053]

The behavior I am thinking of is to always discharge at the Current (Amps) set in the configuration.
Where the intelligence comes in is for it to be monitoring the current SOC and Load and determine how many discharge slots it could afford to discharge based on reaching the minimum SOC by the time the next always use slot or programmed charge slot arrives.
Then at the next slot, if Load had increased or decreased it could recalculate if it should continue to use the next discharge slot or Hold until the next slot and to recalculate.
Of course it is always going to be a best efforts but easier than users checking every 1/2hr if they can discharge another slot.
Hopefully I have explained the logic side better.

[Webreaper]

Yes, I could do that, but it's a bit of a niche use-case, and is quite complex.

Varying the charge amps slot-by-slot is going to be extremely complex, because charge/discharge is not an exact science (e.g., what happens if there's solar being generated that's reducing the discharge? Or high load that's increasing it)? Plus, SolisManager only recalculates the action every 30 minutes, during which anything could have happened that would make the calculation for the next 30 minutes entirely inaccurate. For it to be worth it, the app would have to adjust the charge/discharge rate every few minutes, and that would be complex. It would also use an awful lot of EEPROM writes continually updating the charging rate - which would shorten the life of your inverter (see the Readme technical page).

Also, I'm not sure the benefit is worth it for the complexity it would add. Not having such a feature might mean that occasionally you export more than you want to, or don't export everything you need. But most of the time it'll be fine, and the benefits would only be pennies anyway.

If you want to use the Amps in the general config, then leave the amps field in the scheduled action blank. If you want to ensure that extra load prevents some discharge, then use the "SOC > %age" setting in the scheduled action. You shouldn't need to check the inverter every 30 minutes - SM will stop discharging when it reaches the desired threshold.

[MartyMoose30053]

I was not thinking of adjusting the Amps as you say that would get complex, not doing it as granular ie discharge or hold the next slot seemed the simplest method as per my schedule screen shot should suffice but with the added benefit of looking at the SOC and likelihood of reaching the minimum SOC by the next scheduled charge slot.
Perhaps the schedules have set up has enough logic to achieve the same result. I’ll have a play with those settings and let you know.