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 hubIndependent of GivEnergy Ltd (in administration since 9 April 2026).
I work for a Solar Company and had a customer with a GivEnergy system that we are not versed in. Ron took the time to explain the issues my customer was having and between us managed to rectify the issues. 10 Stars ... Thanks again STS
Contacted Solar Tech about my Givenergy battery storage system that wasn't working. Battery status was "idle". Given the company Givenergy had gone bust, I need independent quality technical help. Very patient and clearly very knowledgeable about battery systems Ron diagnosed possible issues and suggested several possible remedies. Worked our way through them and fortunately it began to work. The fault was very specific and only an experienced engineer would have thought to check. Suffice to say I'll be back if I need independent support again. Lastly you only pay if there is a solution. Outstanding.
Contacted Ron with a problem and he sorted it out quickly with no problems at all. Very knowledgeable on anything solar/ batteries. I would recommend him to anyone
When my GivEnergy battery started playing up it became basically useless and several companies I called said they couldn’t help. Solar Tech Support really knew their stuff, communicated very well and resolved the problem quickly. Without them I’d have had to buy a replacement battery.
Absolutely wonderful. Would recommend without hesitation. I had an issue I was thinking would never be fixed and they fixed it. Help, advice and support every step of the way. I can't recommend highly enough. Thank you so much ⭐
Wow... a firmware update to my inverter sent the whole system into meltdown – the battery discharged, and the house seemed to be drawing power, and the solar, who knows where that was going? Aghhh... A short email exchange with Roland and Solar Tech Support sorted the problem... the firmware had reversed a setting (from when it was installed), and the CT clamp needed to be reversed. As soon as I had done that, the world returned to normal. Thanks, Roland; there is no way I would have come to that conclusion. Would I recommend them? You bet! Worth the fee? You bet, again!
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
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.
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.
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.
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.
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.
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 →
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 →
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.
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 →
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.
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.
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.
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 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 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.
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.
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.
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.
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 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.
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 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 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).
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.
I’ve worked on hundreds of GivEnergy systems and know the kit inside out. If yours is playing up, my promise is simple — no fix, no fee: just £95 if we fix it, free if we don’t.
We use cookies to measure traffic and improve our ads — including sharing limited, hashed details with Meta (Facebook) and Google to measure ad performance. Accept, or decline for essential cookies only. Privacy policy