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 hubSafety: do not open battery enclosures. Lithium battery systems carry serious electrical risk.
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.
I sent a message on their website regarding a problem I have on my Givenergy system. Although not supplied by Ronald, I thought it was worth an email. Within the hour on a Saturday, he phoned and we discussed the problem. He logged in remotely and gave excellent advice. I'm too far away for his on-site help but he did diagnose the problem and was happy also to chat through my thoughts about an upcoming solar/battery install I'm planning. Great bloke.... if only he was nearer!
Ron was really helpful. He remotely adjusted my battery settings on the same day I contacted him, and at a reasonable price. Great service.
Ronald was great to help me sort out my giv energy inverter issue since company has gone bankrupt in april 26.
Ron want out of is way to help, nothing was to much. He was very thorough in what he did Very knowledgeable I would highly recommend Ron and his company He did a fantastic job for me. if you have any problems, he'll do his best to help you out and resolve your problem. I wouldn't hesitate to recommend them
Absolutely wonderful support. I have a GivEnergy system that was installed in 2022, and a firmware update was flagged in the app, so I proceeded to update the software .... and immediately regretted it, as my inverter came up with an error, and was not working at all! With no GivEnergy support available, and my installer saying there was nothing he could do, I googled help, and found Ron. What a stroke of good luck! Submitted an on line enquiry late morning, and received phone call just after 5 pm, and later that evening Ron was able to supply me with old firmware no longer available on the GivEnergy web site. I was then able to update the firmware using a GivEnergy youtube video as reference, and hey presto the system was back up and running. One further slight adjustment by Ron and we are back normal. What a relief. I have no hesitation in recommending Solar Tech Support if you have a problem. Great service! And if you are a GivEnergy system owner, whatever you do, DO NOT UPDATE FIRMWARE!
Safety warning: Never open a SigenStor battery enclosure or attempt to disconnect individual battery modules. Lithium battery systems operate at dangerous voltages even when the inverter is switched off. If you see physical damage, swelling, smell burning, or hear unusual sounds from a battery module, isolate the system at the consumer unit and call 999.
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).
Log into SigenCloud (web portal or Sigenhome app). Navigate to your SigenStor system and open the alarm or event log. Look for:
Screenshot or note down the alarm details before proceeding — your engineer will need this information.
A full power cycle resets BMS communication between the inverter and all battery modules. This resolves most transient communication faults:
Check SigenCloud after 10 minutes. If all modules show online with current SoC readings and the alarm has cleared, no further action is needed.
After power cycling, check SigenCloud for the communication status of each battery module in the stack:
Every module shows a current SoC, voltage reading, and no active alarms. The fault was transient — monitor for recurrence over the next few days.
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.
In SigenCloud, check the firmware version reported by each battery module. Firmware mismatches between modules in a stack can cause persistent BMS communication errors:
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.
If a specific module consistently triggers alarms after power cycling and firmware checks, it likely has a hardware fault. From SigenCloud, gather:
This evidence package supports a warranty claim with Sigenergy. SigenStor battery modules are covered under the manufacturer warranty — typically 10 years for residential systems.
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.
Return to the Sigenergy brand hub to explore other common faults and services.
Sigenergy support hubWe 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.
We use cookies to measure traffic and improve our ads — including sharing limited, hashed details with Meta (Facebook) to measure ad performance. Accept, or decline for essential cookies only. Privacy policy
