Skip to content
Problem diagnosis · Sigenergy

Sigenergy Battery Module Fault — SigenStor BMS Alarm Diagnosis

SigenCloud showing a battery module alarm on your SigenStor? Most battery module faults are BMS communication dropouts — transient errors cleared by a power cycle. If the alarm persists, it could be a firmware mismatch, a loose communication cable, or a hardware fault in a specific module. This guide walks through the diagnosis.
Free remote diagnostic £125 only if we fix it remotely
  • BMS alarm log review via SigenCloud
  • Power cycle clears most transient faults
  • Do not open battery enclosures
Battery alarm won't clear?

We review your SigenCloud alarm log and BMS communication data remotely. If a module has failed, we confirm which one and advise on warranty or replacement.

Book your free remote diagnosticBack to Sigenergy hub

Safety: do not open battery enclosures. Lithium battery systems carry serious electrical risk.

An amazing experience and service from Ronald - totally 100% recommend. All remotely sorted with no need to wait around for someone to pop in and sort. I was a little nervous about doing this but was really easy and he talks you through the steps. Just such relief and we are back up and running again.

Emma Fletcher · Oct 2026 Trustpilot

Wow!!! I have a Givenergy system. The battery stopped charging and depleted fully. Obviously Givenergy went into administration, so I was working with the reseller / installer to get it fixed. They told me they couldn't resolve it and the best they could do was offer me a replAcement at cost, so basically having to buy a new system. I happened to come across STS when searching for how to fix it myself. Ronald has been a god send, within 2 days all is working perfectly and set up correctly. When it comes to experts. He truly is the expert. If you have issues with your Givenergy system and don't know where to go for good help, give him call. 07944 877329. Thanks Ronald, regards Neil W

Neil · Jul 2026 Trustpilot

Excellent response to diagnose a problem on our SolarEdge installation. Kept us informed at every step. Diagnosis quickly completed and solution implemented.

Les Bennett · May 2026 Trustpilot

Sts does a extremely great job. Thank you.

Roy Morgan · Jul 2026 Google

Brilliant. He fitted a new dongle and set the system up properly. Even better, he explained why the storage batteries don't work in a power cut - not correctly wired up - expensive to fix, but a simple turn of the master switch will give emergency power. He is the third technician to look at this issue and the only one to resolve it. Friendly and appoachable, comes when he says he will and reasonable charges. What's not to like!

GEOFFREY EADE · Jul 2026 Trustpilot

Ronald was great to help me sort out my giv energy inverter issue since company has gone bankrupt in april 26.

Ankur Kr. Gupta · Jun 2026 Google

Last updated

Diagnostics

5-step battery module fault diagnosis

Most SigenStor battery module alarms are transient BMS communication faults. Work through these steps in order — the majority are resolved at step 2 (power cycle).

1

Check SigenCloud alarm log for the specific fault code

Log into SigenCloud (web portal or Sigenhome app). Navigate to your SigenStor system and open the alarm or event log. Look for:

• Fault code — the specific alarm type (BMS communication, cell voltage, temperature, etc.)
• Module number — which battery module in the stack is affected
• Timestamp — when the alarm first appeared and whether it is still active
• Pattern — is it a one-off event or a recurring alarm?
Common battery alarm types
BMS communication alarm: Module lost communication with inverter — usually transient
Cell voltage imbalance: One cell in a module is drifting outside normal range
Module temperature warning: Module operating above safe temperature threshold
Module offline: Module not responding to the inverter at all

Screenshot or note down the alarm details before proceeding — your engineer will need this information.

2

Power cycle the entire SigenStor system

A full power cycle resets BMS communication between the inverter and all battery modules. This resolves most transient communication faults. The AC comes off first and the battery modules go off last:

1. Turn off the AC isolator for the SigenStor inverter.
2. Turn off the DC/PV isolator.
3. Turn off each battery module isolator last. If you have multiple modules in a stack, switch off each one.
4. Wait 60 seconds. This allows BMS controllers in each module to fully shut down and clear fault states.
5. Turn the AC isolator back on, then the DC/PV isolator.
6. Turn battery module isolators back on last, one at a time, waiting 10 seconds between each module.
7. Wait 5–10 minutes for BMS communication to re-establish across all modules.

Why this order: SigenStor modules have no separate power button, so the module isolator is the battery's only control. That is why the AC comes off first.

Check SigenCloud after 10 minutes. If all modules show online with current SoC readings and the alarm has cleared, no further action is needed.

3

Check BMS communication status for each module

After power cycling, check SigenCloud for the communication status of each battery module in the stack:

All modules online

Every module shows a current SoC, voltage reading, and no active alarms. The fault was transient — monitor for recurrence over the next few days.

One module still offline

A specific module is not responding after power cycle. This points to a hardware fault in that module's BMS board or a loose communication cable.

If one module is consistently offline, note the module number and serial number from SigenCloud. This identifies the specific unit for warranty or replacement.

4

Verify firmware versions match across all battery modules

In SigenCloud, check the firmware version reported by each battery module. Firmware mismatches between modules in a stack can cause persistent BMS communication errors:

• All modules same version: Firmware is not the issue — proceed to step 5.
• One or more modules on different versions: This happens when a new module is added to an existing stack, or when a firmware update partially completes. The modules need firmware alignment.

Firmware updates on SigenStor battery modules require installer-level SigenCloud access or physical access to the system. STS can coordinate this remotely if you have installer credentials, or arrange for an on-site update.

5

Identify the faulty module for warranty or replacement

If a specific module consistently triggers alarms after power cycling and firmware checks, it likely has a hardware fault. From SigenCloud, gather:

• Module serial number and position in the stack
• Complete alarm history for that module
• SoC and voltage readings compared to other modules in the stack

This evidence package supports a warranty claim with Sigenergy. SigenStor battery modules are covered under the manufacturer warranty — typically 10 years for residential systems.

Do not attempt to remove or disconnect battery modules yourself. Lithium battery systems operate at dangerous voltages. Module isolation and replacement must be performed by a qualified engineer.

How SigenStor battery modules communicate — and why faults happen

Sigenergy SigenStor battery systems use a modular stacking architecture. Each battery module has its own BMS (Battery Management System) controller that monitors cell voltages, temperatures, and charge state. The modules communicate with the SigenStor inverter via a daisy-chained communication bus. When one module loses communication — due to a transient glitch, a loose cable, or a firmware error — the inverter raises a BMS alarm and may restrict charging or discharging to protect the stack.

The good news is that most BMS communication faults on SigenStor systems are transient. A power cycle resets all BMS controllers and re-establishes the communication chain. This clears the majority of alarms. Persistent alarms typically point to one of three things: a firmware version mismatch between modules (common when a new module is added to an existing stack), a loose or corroded communication cable between modules, or a genuine hardware fault in one module's BMS board.

Sigenergy is a relatively new brand in the UK market, and their battery management firmware is still evolving. Firmware updates sometimes introduce new alarm thresholds or change how modules report faults. If you see new alarm types appearing after a firmware update, this may be the system reporting conditions that were previously not flagged — not necessarily a new physical fault.

Back to

Return to the Sigenergy brand hub to explore other common faults and services.

Sigenergy support hub
FAQ

Battery module fault — common questions

The most common causes are: transient BMS communication dropouts (cleared by power cycle), firmware version mismatches between modules in a stacked system, loose communication cables between modules, or a hardware fault in a specific module's BMS controller. SigenCloud alarm logs identify the exact module and fault type.
Log into SigenCloud via the web portal or Sigenhome app. Navigate to your plant, select the SigenStor inverter, and open the alarm or event log. Filter by battery or BMS alarms. Each entry shows the timestamp, fault code, affected module number, and whether the alarm is active or cleared.
Yes. Most transient BMS faults are resolved by a full power cycle. SigenStor modules have no separate power button: the module isolator is the battery's only control, which is why the AC comes off first. Turn off the AC isolator, then the DC/PV isolator, then the battery module isolators last. Wait 60 seconds. Restore in this order: the AC isolator first, then the DC/PV isolator, then the battery modules last, one at a time with 10 seconds between each. If the alarm returns after power cycling, the fault is likely hardware-related and needs engineer diagnosis.
Small SoC drift between modules (5–10%) is normal. Larger drift indicates a cell imbalance, BMS calibration issue, or a module not communicating correctly. The BMS should passively balance modules over time. If drift exceeds 15%, the affected module may need recalibration or replacement.
STS free remote diagnostics — no fix, no fee. This covers alarm log review, BMS communication analysis, firmware checks, and a clear diagnosis. If on-site work is needed to test or replace a module, we provide a separate quote after the remote diagnosis. Book a remote diagnostic to get started.
Book

Battery module alarm won't clear?

We review your SigenCloud alarm log and BMS data remotely. If a module has failed, we confirm which one and provide evidence for a warranty claim or replacement quote.

  • No fix, no fee
  • BMS alarm log analysis included
  • Warranty evidence pack if module has failed

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