Battery Usage - Octopus Intelligent

4 comments started 2023-09-25 last 2023-09-25
GivEnergy ProductsAC CoupledBatteryEV Charger
K
#1 KeithMersh1955RuthMary1971

Hi I now have 17.3kW GE storage and am on Octopus Intelligent. I have an EV.

From 23.30 - 05.30 OI Tariff is 7.5p …… Export Tariff = 15.0p.

I’ve set my night time battery charging to 100% so that once sun shines and battery is fully replenished after consumption from 05.30 onwards, we end up exporting most of the PV generation. It seems the logical thing to do. Am I right and secondly what is the impact on battery life when capacity is constantly between say 60-100%. Do batteries prefer to be run down and recharged from time to time?

Hope that makes sense and thanks.

T
#2 tomorrowman

At 15p export rate I'd export everything from your solar array and if possible run house load from battery that you charge it overnight at your 7.5p rate.

I'd even be tempted to force discharge the battery to grid about an hour or so before cheap rate to get 15p for any remaining charge in the battery.

Sadly still awaiting my DNO letter before can apply for 15p export rate

#3 NC

This is exactly what I try to do. I force discard the battery to the grid from 21:30-21:25 and then charge it overnight at the cheap rate. Try to export all PV generated during the day and run the house from the battery (AIO). I have DNO approval for 13kW, so in theory I can export all the PV can generate (6kW inverter) and the battery at max rate if I’m feeling particularly exporty.

D
#4 DD

KeithMersh1955RuthMary1971 what is the impact on battery life when capacity is constantly between say 60-100%. Do batteries prefer to be run down and recharged from time to time?

I've not kept up to date with all the discussions on the beta thread, but at one time, I got the impression that the firmware was a lot happier if you discharged more fully from time to time. (The voltage curve is very flat, so the BMS could lose track of the charge level, manifesting in sudden drops in SOC.) This has probably been fixed now, though.