Why does a solar battery show 100% but deliver no power?

The 100% figure may not be a live battery measurement

An inverter screen can group several different signals under the word "battery." Terminal voltage is an electrical measurement at that moment. SOC is an estimate maintained by the BMS or, in some modes, by the inverter. Charge permission, discharge permission and current limits are separate data. One can still appear while another is missing.

A healthy closed-loop connection normally carries more than a percentage. If the inverter sees DC voltage but the BMS fields are zero, that is a communication clue rather than proof that the cells are full, empty or damaged. Check the timestamp too: a cloud dashboard may retain the last valid value after the local equipment has stopped reporting.

Write down the outage sequence before clearing it

The order of events often says more than the final screen. Capture the SOC before the outage, reserve and shutdown settings, active loads, first alarm and what changed when the grid returned. In a multi-inverter installation, note whether both units lost the same battery data at the same time.

The programmed reserve and the BMS's final protection threshold may be separate controls. Temperature, an individual cell limit, current, communication loss or a load-qualification check can also affect whether the battery permits operation. Save screenshots and logs before an approved restart or recovery step removes that context.

1. 1

   Capture the event

   Save the local SOC, voltage, alarms, grid state and active loads before clearing anything.

2. 2

   Check the timestamp

   Compare the local equipment time with the portal's last update so stale data is not treated as live.

3. 3

   Read the BMS fields

   Look for SOC, permissions, current limits and alarms exposed by the approved interface.

4. 4

   Separate the networks

   In a parallel system, distinguish inverter-to-inverter communication from battery-to-inverter communication.

5. 5

   Confirm the operating mode

   Record whether the exact pairing is using its approved closed-loop or open-loop configuration.

6. 6

   Escalate with evidence

   Send model codes, firmware, configuration and the event timeline to the manufacturer or qualified service party.

Separate the battery state from the communication path

Ask two questions. Is the battery bank awake and willing to charge or discharge? Is the inverter receiving valid data from it? A protection event can stop the first. A protocol, addressing, termination, firmware or communication-path problem can stop the second. Both can follow the same outage, so one voltage reading cannot settle the diagnosis.

Dual-inverter systems have an inverter parallel network and a separate battery BMS path. The manuals decide the leader role, termination and way battery limits reach the other inverter. Several parallel batteries add another layer because the aggregate display can hide one module that is offline or protected. Compare every module through the manufacturer's approved interface rather than treating a network cable as a generic plug-and-play part.

Closed loop and open loop are different operating agreements

In closed-loop operation, a compatible BMS communicates limits and status to the power-conversion equipment. Discover's HELIOS documentation describes the battery requesting charging parameters and publishes separate integration instructions for supported inverter families. Sol-Ark's 18K documentation also treats lithium-battery communication as a defined configuration and identifies loss of BMS communication as a specific fault condition.

Open-loop operation uses a manually configured battery profile and voltage-based controls instead of the same live exchange. It can be approved for some exact pairings, but it does not repair a broken communication path or make a stale SOC trustworthy. If support recommends a temporary mode change, record the original configuration, approved settings source and criteria for returning to closed loop.

Do not turn a data problem into a battery hazard

Online discussions often propose using another battery, a resistor or an external charger to "wake" a protected lithium bank. That is not a safe universal remedy. The correct recovery path depends on cell condition, contactor state, pre-charge design, terminal voltage, battery firmware and the manufacturer's protection logic. An improvised connection can create high fault current, bypass protection or damage equipment that was trying to remain disconnected.

Do not open battery enclosures, bypass contactors, bridge batteries or apply a charging source that the battery manufacturer has not approved for that exact recovery. If the bank has reached low-voltage protection, been left deeply discharged, shows physical damage, smells unusual, is hot, or will not return to a documented state, stop and escalate to the manufacturer or qualified service party. IEC 62485-5 addresses hazards associated with stationary lithium battery installations; a dashboard anomaly should never be treated as permission to improvise on the DC side.

A useful support packet is short and specific

Support is much faster when the first message contains the exact system and event instead of only "battery says 100%." Include the full inverter and battery model codes, module count, communication accessory, firmware, operating mode and a simple connection overview. Add dated screenshots of every relevant local page and the alarm history.

State what has already been tried and whether it changed battery voltage, communication fields, alarms or contactor status. If there are two inverters, list the leader and follower roles exactly as configured. If there are several battery modules, include the module-level status available through the approved service tool. This gives the manufacturer or installer enough evidence to choose the next documented check without guessing from a percentage.