Skip to content
GivEnergy · Fault codes

GivEnergy Fault Code Index

Every GivEnergy fault code from the portal event log — what it means, the most likely cause, and what to do. Specs sourced from the official GivEnergy datasheets and manuals. Note: GivEnergy Ltd entered administration on 9 April 2026, so the manufacturer support route is closed — see the administration page and warranty position. From May 2026 the cloud runs under GivEnergy Software Ltd on a paid subscription model.
  • Every GivEnergy fault code
  • Plain-English cause and fix for every code
  • Most diagnosable remotely over modbus
GivEnergy fault you cannot resolve?

Remote diagnostics over modbus — no GivEnergy portal access required. Same path STS uses regardless of cloud status. Free diagnostic; you only pay if we resolve the fault.

Book GivEnergy diagnosisGivEnergy hub

Independent of GivEnergy Ltd (in administration since 9 April 2026).

5.0
Rated 5.0 on Google
33 Customer reviews

Brilliant support to get my solar battery working again. I didn’t expect help on a Saturday but Ron answered the phone, listened and sent me the information I needed to get it going, answered questions etc. A brilliant service I’d happily recommend.

Alison F. Cockerill · Jun 2026 Google

Ron was brilliant. He really tried to help. He spent hours trying to fix our GivEnergy AIO and ultimately it became apparent that it needed parts to fix the BMS management system. As there appears to be no replacement parts available on the market, he gave excellent advice on what options are now available to move forward. He is incredibly helpful and knowledgeable.

Mark Mayson · Jun 2026 Google

Called back within a day and gave good advice.

Rob and Sue Dempster · Jun 2026 Google

Ron was extremely helpful and tried his best to repair/reset our GivEnergy inverter remotely. In the event he was unsuccessful but he couldn’t have been more helpful. If you have problems with a GivEnergy system please contact him. Highly recommended

Neil Crichton · Jun 2026 Google

Big thanks to Ron. He was incredibly patient and helpful over the phone, taking the time to walk myself and the installer through every troubleshooting step. Through lots of testing he figured out the issue was definitely a hardware issue, which allows us to consider our next steps. Support fees are clear and they operate a “no fix no fee” policy. It is rare to find that kind of honesty combined with dedicated phone support nowadays. I highly recommend Ron, if you need help with your solar system don’t hesitate to give him a call.

Steve M · Jun 2026 Google

A superb service from Ron who went beyond the normal service received from other Tech support companies. I live abroad and was badly let down when my givenergy system failed (and the company went bankrupt) and the local supplier ran away from the problem. Ron sorted the problem and even accessed specialist coding for the inverter that would not be available for suppliers. Ron also ran a full diagnostic to insure that all was in good working order afterwards. Without Rons support and patient assistance I doubt I would ever have got the system back up and running. Well done and thankyou and you have a customer for the future.

Philip Davey · Jun 2026 Google

Brilliant support to get my solar battery working again. I didn’t expect help on a Saturday but Ron answered the phone, listened and sent me the information I needed to get it going, answered questions etc. A brilliant service I’d happily recommend.

Alison F. Cockerill · Jun 2026 Google

Ron was brilliant. He really tried to help. He spent hours trying to fix our GivEnergy AIO and ultimately it became apparent that it needed parts to fix the BMS management system. As there appears to be no replacement parts available on the market, he gave excellent advice on what options are now available to move forward. He is incredibly helpful and knowledgeable.

Mark Mayson · Jun 2026 Google

Called back within a day and gave good advice.

Rob and Sue Dempster · Jun 2026 Google

Ron was extremely helpful and tried his best to repair/reset our GivEnergy inverter remotely. In the event he was unsuccessful but he couldn’t have been more helpful. If you have problems with a GivEnergy system please contact him. Highly recommended

Neil Crichton · Jun 2026 Google

Big thanks to Ron. He was incredibly patient and helpful over the phone, taking the time to walk myself and the installer through every troubleshooting step. Through lots of testing he figured out the issue was definitely a hardware issue, which allows us to consider our next steps. Support fees are clear and they operate a “no fix no fee” policy. It is rare to find that kind of honesty combined with dedicated phone support nowadays. I highly recommend Ron, if you need help with your solar system don’t hesitate to give him a call.

Steve M · Jun 2026 Google

A superb service from Ron who went beyond the normal service received from other Tech support companies. I live abroad and was badly let down when my givenergy system failed (and the company went bankrupt) and the local supplier ran away from the problem. Ron sorted the problem and even accessed specialist coding for the inverter that would not be available for suppliers. Ron also ran a full diagnostic to insure that all was in good working order afterwards. Without Rons support and patient assistance I doubt I would ever have got the system back up and running. Well done and thankyou and you have a customer for the future.

Philip Davey · Jun 2026 Google
How to read this index

The GivEnergy portal event log lists fault codes with timestamps. Find your code below — each row gives the cause and what to check first. Critical (red) codes may indicate live-DC or BMS protection events — do not open the unit. Warning (amber) codes are protective; Info (green) codes are typically commissioning or transient events. Cloud reference: from May 2026 givenergy.cloud is under GivEnergy Software Ltd on a paid subscription.

GivEnergy portal event-log codes — KB cross-referenced

INV_NO_UTILITY
Hybrid inverter — no AC supplyinfo

No AC supply detected at the inverter. Check the AC isolator below the inverter is switched on. Check for tripped breakers at the consumer unit on the solar circuit. Check AC terminal connections are tight.

STORAGE_ERROR_NO_UTILITY
AIO / storage variant — no AC supplycritical

Same as INV_NO_UTILITY but on an AC-coupled All-in-One or storage variant. AC supply not detected. Check the AC isolator, consumer unit breakers, and the AC terminals at the inverter.

INV_PV_OVER_VOLTAGE
Hybrid — DC overvoltagecritical

String voltage from solar panels exceeds the inverter limit — 580V on Gen 1, Gen 2 and Gen 3 3.6/5.0 hybrids; 600V on the Gen 3 8.0. Do not touch DC cabling. Requires an engineer to check the panel string configuration — usually too many panels in series for cold-day Voc.

STORAGE_ERROR_PV_OVER_VOLTAGE
AIO — DC overvoltagecritical

Same as INV_PV_OVER_VOLTAGE on the AIO range. String voltage exceeds the inverter’s Max. PV Voltage. Do not touch DC cabling — engineer required.

INV_OVER_TEMPERATURE
Inverter over temperatureinfo

Inverter heatsink temperature exceeded its safe operating threshold. Check ventilation clearances per the installation manual. No direct sunlight, not enclosed in a sealed cabinet. Clear dust from heatsink vents. If ambient is in range and vents are clear, an internal fan may have failed.

STORAGE_WARN_BMS_COM_FAIL
Warning — BMS comms lostwarning

Inverter has lost communication with the battery BMS. On LV GivBat batteries (51.2V) comms are RS485 over the proprietary plug/lug cable — not RJ45/CAN. Check the battery is switched on, the DC MCB is up, dip-switch addressing is correct (Master = 0,0,0,0; Slave 1 = 1,0,0,0 etc.), and the comms cable is fully seated. On HV stackable batteries the inverter-to-battery interface is CAN — check the orange HV-kit connector. Full comms fault guide →

STORAGE_ERROR_BMS_COM_FAIL
Error — BMS comms failedcritical

Persistent battery comms failure — the warning escalated. The battery has stopped responding to inverter requests. Check the comms cable (RS485 on LV GivBats; CAN on the HV stackable kit), full power cycle, and look for a firmware mismatch between battery and inverter. Full comms fault guide →

STORAGE_WARN_BMS_UNDER_VOLTAGE
Warning — battery voltage lowwarning

Battery voltage is critically low. Ensure the battery is switched on (press the side button until the LEDs illuminate) and the first SoC LED is green. Check the DC MCB between inverter and battery is in the ON (up) position.

STORAGE_ERROR_BAT_UNDER_VOLTAGE_FAULT
Error — voltage below minimumcritical

Battery voltage has dropped below the safe minimum threshold — BMS has entered protection. Commonly caused by deep discharge during EPS operation or a prolonged outage. A slow controlled recovery charge is needed; STS can run this remotely over modbus where the BMS allows. Battery fault guide →

STORAGE_WARN_BATTERY_SOC_LOW
Warning — state of charge lowwarning

SoC is critically low. Ensure the battery is on. Check the discharge cut-off SoC in Battery Options — if set high the battery may be holding back. Note: per the GivEnergy cold-weather KB, charging is inhibited below 0°C and discharge is allowed to about −1°C, so on a frosty morning the system may sit at low SoC until cells warm.

STORAGE_WARN_BATTERY_VOLTAGE_LOW
Warning — voltage lowwarning

Battery voltage is low. Ensure the battery is on and the DC MCB is ON. If the battery is on and voltage stays low after a charge attempt, the BMS may be in a protection mode requiring an engineer-led recovery.

STORAGE_ERROR_OVER_TEMPERATURE
Battery over temperaturecritical

Battery cell or BMS temperature has exceeded its safe limit. The BMS will suspend charge and discharge to protect the cells. Per the GivBat datasheets the operating window is 0–50°C charge / ‒10–50°C discharge (Gen 3) or 0–55°C / ‒10–55°C (Gen 1/2). Ensure the battery is not in direct sunlight, no loft installs in summer, ventilation around the unit is adequate. Do not attempt to charge while the fault is active.

STORAGE_ERROR_BACKUP_OVERLOAD_FAULT
Error — EPS overloadcritical

Load on the EPS backup circuit exceeded the inverter’s backup-terminal rating. Per datasheets: Gen 2 5.0 backup = 3.6kW; Gen 3 3.6 backup = 3.6kW; Gen 3 5.0 backup = 3.6kW; Gen 3 8.0 backup = 8kW with a 50A pass-through; AIO original = 6kW continuous / 7.2kW peak; AIO 3.6 = 3.6kW on-grid / 6kW continuous / 7.2kW peak off-grid; AIO 2 + MPPT = 12kVA continuous / 14.4kVA peak off-grid. Reduce the load on the backup circuit — strip out electric showers, kettles and ovens. EPS-circuit rewiring is an engineer job. EPS guide →

Grid voltage too high
Overvoltage disconnectinfo

Grid AC voltage exceeded the upper threshold. Gen 1/2/3 5.0 datasheets list grid range 180–270V; Gen 3 3.6 lists 180–272V. The actual statutory thresholds are set by EREC G98/G99 (commonly 253V and 273V) not by GivEnergy. Check AC isolator and terminal connections; if sound, contact your DNO. Common on sunny days in areas with high solar density. Grid overvoltage guide →

Grid voltage too low
Undervoltage disconnectinfo

Grid AC voltage dropped below the lower threshold. Check AC isolator and connections. If sound, the supply at your property is outside acceptable limits — contact your DNO.

PV generation not detected
Commissioning checkinfo

No PV generation detected during the commissioning check. On hybrid inverters confirm the DC switch is on and the panel strings are present. On AC-coupled AIO systems, generation is monitored via the EM115 (single-phase external meter) or GEM120 (CT-based monitoring) — not a PV-string CT clamp. Confirm the meter is connected and powered.

Smart Tariff Inverter Lockout
API / tariff lockoutwarning

Per the GivEnergy KB ("Understanding and Removing a Smart Tariff Inverter Lockout"), an active energy-tariff agreement (e.g. Octopus Intelligent) has locked inverter controls. Symptom: settings refuse to save, schedules will not update. Only the energy provider can lift the lockout — do NOT delete the API key first, that orphans the lockout. Contact the tariff provider to be removed from the integration cleanly.

ELECTRICITY_METER_COM_FAIL
External meter comms lostinfo

Communication with the external meter has failed. The meter is likely an EM115 (single-phase, mounted close to the inverter) or GEM120CT (CT-based monitoring bundle). Check the meter comms cable is in the correct socket on the underside of the inverter and that polarity (power and comms) is correct.

Data Point not created recently
Portal data gapinfo

The portal has not received data from the dongle recently. Check the dongle LED — solid means WiFi up. KB-documented WiFi requirements: 2.4 GHz only, WPA2 (not WPA3), RSSI ≥ 60–70% in the dongle STA interface, port 7654 open outbound. Port 7654 being blocked by a router/firewall change is the single most common cause. Portal offline guide →

Meters not enabled
Commissioning — meter setupinfo

Meters have not been enabled in the commissioning portal. Go to My Inverter → Remote Control → Enable Meters and enable the number of meters installed. Installer commissioning step rather than an end-user action.

Home CT — CT1 direction
CT clamp orientationinfo

The grid CT clamp (ID1) is the wrong way round. Per the GivEnergy installer manual and portal commissioning docs, the directional arrow on the CT body must point away from the consumer unit, in the direction of grid-import current flow. A reversed CT inverts import/export readings. CT clamp guide →

battery-not-charging
Commissioning checkinfo

Battery is not charging from excess solar. Restart inverter and battery in the correct sequence. Check system mode, CT direction, and SoC limits. Battery not charging guide →

battery-not-discharging
Commissioning checkinfo

Battery is not discharging to meet house demand. Restart inverter and battery. Check system mode, discharge cut-off SoC, and that the CT clamp is reading the correct circuit (grid, not generation).

FAQ

GivEnergy fault code questions

Fault codes appear in two places. In the GivEnergy app: tap your device and select Event History. In the portal: log in to givenergy.cloud, click My Inverter, then Event Log. The portal log goes back further and is more useful for diagnosis. Note: from May 2026 the cloud runs under GivEnergy Software Ltd on a paid subscription model.
A power cycle clears many transient codes. The correct shutdown sequence per the GivEnergy basic-diagnostic guide is: battery off, DC isolator off, AC isolator off — then reverse on the way back. If the same code reappears after a clean restart, the underlying fault is persistent and needs diagnosis.
Firmware updates can reset settings to defaults, change compatibility requirements, or trigger codes that did not previously appear. Importantly, do NOT run a firmware update while the battery is in a fault state, at 0% SoC, or showing red LEDs — per the GivEnergy diagnostic guide that can leave the system worse off. Resolve any active faults first, then update.
Almost always not. The Control Logs in the portal will show the source — API or SERVER entries indicate a third-party integration (Octopus Intelligent Go, Home Assistant, GivTCP) is rewriting your schedule. Audit Account Security then Connected Services and revoke any token you no longer recognise. This is documented in the GivEnergy "Why Are My Charge Settings Changing Themselves?" KB article.
No. Per GivEnergy’s own KB ("Why Is My GivEnergy System Also Using The Grid Occasionally?"), short grid blips during inverter ramping are normal. Bursts of household load can briefly outrun the battery’s discharge ramp; these show as small imports for a few seconds and are not a fault.
STS can diagnose any GivEnergy code remotely over modbus — we do not need the cloud or portal access to read the live fault state. Free remote diagnostic; pay only if we resolve the fault.
The remote diagnostic is free — if we cannot pin down the fault, there is nothing to pay. If we resolve it remotely over modbus (a setting change, a comms re-pair, a controlled recovery charge) it is a flat £75, and only if it works. If the code turns out to need on-site work, that is quoted up front — on-site repairs start from £245. No fix, no fee.
Usually the same day. Because we read the live fault state directly over modbus — no GivEnergy portal or cloud access needed — we can often identify the cause within a single 30-minute remote session, even with the cloud down or your account locked after the administration.
Book

Got a fault code and need it diagnosed?

Tell us the exact code from the portal event log, when it started, any LED behaviour. STS reads live values over modbus — no portal access required — and identifies the cause same day.

  • Independent — GivEnergy Ltd is in administration
  • Free remote diagnostic · no fix, no fee
  • All GivEnergy generations + AIO + HV stack supported

By submitting you agree to be contacted about your diagnostic request. We don't share your data with 3rd parties.

Call 07944 877 329 Book free diagnostic