Standalone Battery Timed Discharge Not Working Without Eco

We’ve had our standalone battery system for about a year and all has been fine until we changed from Octopus Go to E.on Next Drive last week, and had to change settings in the app.

The first issue, which I’ve emailed support about is that the downloaded Next Drive tariff caused the app to show entirely screwy costs. For example, over £25K for the past 28 days. So I installed our two-tier tariff by hand.

The problem I have now is that our cheap rate is from 00:00 to 07:00. I want to charge during that period until full (we have 19 kWh of battery) and then discharge from 07:00 to 00:00. I had to turn Eco mode off to get charge-only during off-peak. But now I discover that the timed discharge is not working. At the moment, the battery is over 60% full but won’t discharge unless I turn Eco mode back on.

I have updated the firmware and software, checked the time zone (UTC, London) and reset the inverter from the app a couple of times.

The battery options are the default: 4% reserve, charge and discharge 3.6 kW.

I believe you want to set it as follows

Eco - ON
Timed discharge - OFF
Timed charge - ON 0000 - 0700

Not had a single inverter for a while, but a Timed Charge will top the battery up from the grid during to the percentage you set in the times you want. Pretty sure it overrides ECO

that’s what I would advise as well

timed discharge is confusing and operates differently on different inverter models, leaving Eco mode on and setting a timed charge should be all that you need @whudon

I never worked out ‘Timed Discharge’.
I would also just set up ‘Timed charge’ for 00.00 - 07.00, leaving Eco to look after other times.

I have been spoilt since finding Predbat to look after all this for me!

Rob

1 Like

Thanks for the replies. I did eventually hear from GivEnergy support who applied some firmware patches that resolved the slow charging issue. Two things I did discover are that Eco mode does have to be on but when the firmware isn’t confused it nanages tomed charge and discharge as expected. The second lesson is that I had to reboot the system (power down and back up) after the initial firmware upgrade 2 weeks ago to get any sensible behaviour back. But even then, chargingvwas leisurely, rather than at the 3600 W limit in the settings.