GivEnergy SOC bug — battery percentage dropping, jumping, or stuck
Your GivEnergy battery percentage suddenly drops from 70% to 10%, jumps in steps instead of changing smoothly, or gets stuck at a number that clearly isn't right. This is a well-documented BMS calibration issue that GivEnergy has addressed across multiple firmware versions — from BMS 3007 through to 3022. This guide covers every symptom, which firmware you should be on, and how to recalibrate.
Tell us the symptom, your BMS firmware version, and how long it has been happening. We review portal data remotely — battery graph, firmware history, and cell-level health — to determine whether the fix is a calibration cycle, a firmware update, or a hardware issue.
Book Remote Diagnostic — from £75 → GivEnergy hubIndependent — not affiliated with GivEnergy Ltd.
Step-by-step SOC bug diagnosis
Work through these steps in order. Step 1 identifies the symptom pattern. Steps 2–3 fix the majority of cases. Steps 4–5 cover hardware and firmware causes. Step 6 prevents recurrence.
The bug presents differently depending on firmware and battery generation. The main patterns are: sudden large drops (SOC falls 30–50% in under an hour despite low house load — the most common symptom), SOC stuck at a fixed percentage that does not change regardless of charge or discharge, stepping (SOC jumps in discrete blocks instead of changing gradually — vertical lines on the graph), multi-battery divergence (two batteries showing significantly different percentages), or false 100% (battery reports full but clearly is not). Open the portal and check the battery graph for the last 7 days — the shape of the fault tells you what is happening.
In givenergy.cloud, go to My Inverter → Software. The BMS version is the critical number. The key milestones: BMS 3007 and earlier had basic SOC estimation with known jump issues. BMS 3012 (May 2023) added temperature-adjusted calibration and OCV offset correction. BMS 3013 (July 2023) expanded the calibration range from 50% to 80% of capacity and set the discharge calibration voltage to 2810mV per cell. BMS 3017 (May 2024) improved dynamic SOC calibration speed and added compensation for the 30mA static current drain that caused drift after the battery stood idle for over two days. BMS 3018 introduced post-100% top-up charging to combat peak voltage degradation. If you are on 3012 or earlier, updating is strongly recommended.
A calibration cycle gives the BMS two known reference points to correct its estimate. Set the system to Timed Discharge with a target of 4% and let the battery drain — ideally overnight or during a low-load period. Once it reaches 4%, switch to Timed Charge and charge to 100% (from solar the next day or from grid overnight). For multi-battery systems, both batteries must reach 4% at the same time so the BMS modules can resynchronise. One cycle fixes mild drift. If the SOC has been significantly wrong for weeks, repeat the cycle. Best practice: run a proactive calibration once a month to prevent drift accumulating.
This is an under-reported cause. Some GivEnergy battery packs have been found with internal connectors that were not fully tightened during manufacturing — loose by two to three turns. A loose connection causes intermittent voltage measurement errors that the BMS reads as sudden capacity changes. If you can safely access the battery, check that all external cable connections to the terminals are firm. Internal connectors require an engineer. If tightening a loose connection resolves the SOC jumps immediately, the BMS logic was not faulty — it was receiving bad voltage data from the start. This fix is permanent and does not require ongoing calibration cycles.
If your BMS is below 3017, updating may significantly improve SOC accuracy. Before triggering any update, record your system mode, charge/discharge window times, SOC targets, export limit, and CT clamp direction — firmware updates frequently reset these to defaults. Trigger the update in the portal under My Inverter → Software. After the update, the SOC reading may drop sharply — even to 0%. GivEnergy has confirmed this is expected behaviour when updating from pre-3012 firmware: the new logic recalculates the true SOC, which can look alarming but should correct within 24 hours. Restore your settings manually after the update. Note: BMS 3022 has been reported to cause temporary capacity reduction on some 9.5kWh batteries — run a full calibration immediately after if you receive this version.
After calibration, watch the portal graph for two weeks. If the SOC moves smoothly and the daily totals match your expectations, the calibration has worked. To prevent the bug returning, avoid leaving the battery in a narrow charge band for extended periods — batteries that rarely discharge below 50% lose calibration accuracy because the BMS has no low-end reference point. A monthly full calibration cycle is the most reliable preventive measure. If the SOC bug returns within days of a successful calibration, the issue is likely hardware — a degraded cell, a failing BMS module, or a loose internal connection. Contact STS for a remote diagnostic — we review your portal data, firmware version, and cell-level health to determine whether the fix is software or whether the battery needs a site visit.
BMS firmware and the SOC bug — what changed at each version
GivEnergy has released progressive improvements to SOC accuracy across multiple BMS firmware versions. No single version eliminates the issue completely — LiFePO4 chemistry makes accurate SOC estimation inherently difficult — but each version narrows the margin of error.
Early versions had basic SOC estimation with known percentage-jump issues. BMS 3012 added temperature-adjusted calibration and OCV (open-circuit voltage) offset correction during charge and discharge cycles. Calibration thresholds adjusted to 90–95% based on temperature.
Expanded the BMS calibration range from 50% to 80% of capacity — meaning the battery can recalibrate across a wider SOC window. Set discharge calibration voltage to 2810mV per cell. Removed the 20% SOC limitation for parallel battery operations.
Optimised SOC display with improved internal resolution — fewer percentage-step jumps in the portal graph. Added protection against false 0% readings during parallel battery failures, addressing the symptom where one battery in a multi-battery stack would report empty while the other showed charge.
Widely considered the most significant improvement. Modified the speed of dynamic SOC calibration. Added compensation for the 30mA static current drain that caused SOC to drift after the battery stood idle for more than two days. Also added support for mixed Gen 3 and Gen 1 battery stacks.
Introduced post-100% top-up charging at a reduced rate to maintain peak cell voltage. This addresses the root cause identified by GivEnergy: peak voltage degrades over time, causing the BMS to lose its full-charge reference point. Continues gentle charging even after SOC reports 100% until cells reach true peak.
Latest version at time of writing. Some 9.5kWh owners have reported temporary capacity reduction (from 180Ah to 126Ah in one documented case) immediately after updating. GivEnergy's recommendation is to run a full calibration cycle on all batteries after this update. In most cases capacity recovers after calibration.
Why the SOC bug happens — and why it's hard to fix
GivEnergy batteries use LiFePO4 (lithium iron phosphate) chemistry, which is excellent for longevity and safety but presents a fundamental challenge for SOC estimation. Unlike other lithium chemistries, LiFePO4 has a very flat voltage curve between roughly 20% and 80% SOC — the voltage barely changes across 60% of the battery's capacity. This makes voltage-based SOC estimation unreliable in the range where the battery spends most of its time. The BMS falls back on coulomb counting — tracking current flow in and out over time — which works well in the short term but accumulates small measurement errors over weeks and months. Without periodic recalibration at known reference points (near-empty and full), these errors compound until the displayed percentage diverges significantly from reality.
GivEnergy has identified peak voltage degradation as a contributing factor: the maximum voltage the cells reach during charging gradually decreases over time, which shifts the BMS's full-charge reference point downward. This is why later firmware versions (BMS 3018 onwards) continue charging at a reduced rate even after reporting 100% — to push the cells back to their true peak. The issue affects all GivEnergy battery generations (Gen 1, Gen 2, Gen 3, and All-in-One), though Gen 3 batteries with BMS3 hardware have improved SOC tracking out of the box. STS has deep experience with GivEnergy systems across all generations and can determine remotely whether a SOC issue is fixable with firmware and calibration or whether it points to a hardware fault that needs a site visit.
SOC bug — common questions
A sudden drop — typically 30–50% in under an hour — happens when the BMS loses track of true charge level. GivEnergy batteries use LiFePO4 chemistry with a very flat voltage curve between 20–80% SOC, making voltage-based estimation unreliable. The BMS relies on coulomb counting, which accumulates errors over weeks. When the battery eventually hits a voltage the BMS can measure accurately (near full or near empty), the SOC snaps to the true value — appearing as a sudden drop. A full calibration cycle (discharge to 4%, charge to 100%) resets the reference points.
No single version eliminates the bug entirely — LiFePO4 coulomb counting drift is inherent to the chemistry. BMS 3017 (May 2024) is widely considered the most significant improvement, adding faster calibration and static current compensation. BMS 3018 added post-100% top-up charging to combat peak voltage degradation. If you are on BMS 3012 or earlier, updating to 3017 or later is recommended. Even on the latest firmware, monthly calibration cycles are still necessary. See our firmware update guide for safe update procedure.
Set the system to Timed Discharge with a target of 4% SOC and let the battery drain fully. Once at 4%, switch to Timed Charge and charge to 100%. For multi-battery systems, both batteries must reach 4% at the same time so the BMS modules can resynchronise. One cycle fixes mild drift — repeat if the SOC has been wrong for a long time. Running this monthly prevents accumulation. See our full battery calibration guide for the detailed walkthrough.
Yes — inaccurate SOC directly undermines any smart tariff that relies on knowing how much energy is in the battery. On Octopus Flux, Intelligent Go, or Agile, the system uses SOC to decide when to charge (cheap rate) and when to discharge (peak rate). Wrong SOC means the battery may stop discharging mid-peak because it thinks it has hit reserve, or fail to charge fully overnight because it reports 100% prematurely. Users running Predbat automation report the same issue. Keeping BMS on 3017+ and running monthly calibration minimises the tariff impact.
Multi-battery divergence occurs when each battery's BMS drifts at a different rate — more common with mixed generations, different firmware versions, or when the batteries have not been fully discharged together recently. They can only resynchronise when both reach the same low reference point (4% SOC) at the same time. Run a full calibration with both batteries discharging together to 4%, then charging to 100%. If divergence returns quickly, one battery may have a degraded cell or hardware fault. Contact STS and we can check the cell-level data remotely.
SOC still not right after calibration?
If the SOC bug returns within days of a full calibration cycle, the issue may be hardware rather than firmware — a degraded cell, a failing BMS module, or a loose internal connection. We review your portal data, firmware version, battery health metrics, and cell-level readings remotely to determine the next step. Independent from GivEnergy and your installer.