Battery discharge

Hi, my battery generally discharges about once a week and I understand the need to discharge, especially if the battery is not being exhausted over several days. it recently discharged twice within a few days and I would like your opinion on the following questions?

1. What are the parameters that instruct the battery to discharge?
2. Is it possible to set the discharges remotely?
3. If so, how?
4. Is there any long term benefit/problems in doing so?
   ps. I have removed all gas from the house and recently installed an electric multi point boiler in order to maximise the battery use, as it was regularly being underused at night. Has this changed the discharge pattern, if so, you would think the discharges would be less??
   Any help and information would be appreciated.
   Thank you Mike Budd

See here: https://community.givenergy.cloud/d/713-firmware-3007-has-not-fixed-sudden-soc-drop-to-0-problem/625

The battery doesn't need to discharge and it shouldn't be doing that. I have 2 x 8.2s and they don't discharge in this manner, despite being kept at over 55% for weeks.

It's a bug in the system and a fix is being worked on. However, it appears to be taking a long time to implement.

Many thanks Zakalwe, I was not aware that there was an ongoing issue with battery discharges. I will raise it with Giv Energy, if nothing else to add my issue to the list.!!
It would be interesting to establish if any discharges are required for the health of the battery and if so what the interval should be?

Having now fully understood that there are various battery issues out there and fixing the issue is proving difficult, I have held off updating my system. At present my firmware is at 3001 version (as fitted). I am reluctant to update to the latest as it would appear that the new versions have not been successful and things could get worse? What are the thoughts on this; and if it is a good idea to update now the update notes state that the battery will carry out a discharge to recalibrate, so I assume that this update should only be done when the battery charge is low in order to a avoid another loss of a fully charged battery etc.
All advice would be welcome

MBudd I'm still on the original firmware mine was installed with in April, 3005. I'm not willing to update until I know there are no issues, as touch wood everything is working fine for me

MBudd the new versions have not been successful and things could get worse?

From what I've read, there are some Givenergy batteries that present problems to their owners. The majority of owners don't experience the issues reported, or if they do, it is a fairly rare occurrence. I suspect that there's lots of effort being put in by Givenergy to attempt to solve the issue (whatever the cause is) with firmware updates, rather than wholesale replacement of batteries affected. Those owners who don't/haven't experienced the issue should be able to install the firmware updates without issue. Our batteries were updated from 3001 which they were commissioned with, to 3005 and are now at 3007. The process involved recalibration which we just fell lucky with but the performance of the batteries hasn't changed noticeably.

If you're one of the lucky owners whose batteries aren't affected by sudden SoC drop/rise, it probably won't make any difference which firmware you are on, unless you are experiencing another issue solved by one of the firmware releases.

Thanks Tim, appreciate the comments. I have just had a battery discharge today (28/10) which makes it three in a week, so things are getting worse. It is particularly galling on a bad day as the system cannot recover quickly. Although it was happening about once a week in the summer (we thought at the time its was part of the operating system) it was not too much of an issue as the battery recovered quickly in the good weather.
Of course, now I know it should not have been happening and the lost energy would have been more to export.
However, I have raised the above issues again with GivEnergy to check whether I should update my firmware from 3001, or not, and also to get the latest position on the current program to fix things.