Solar Inverter Low Output: Causes and Safe Checks

Short version. Check the conditions, compare the local display against the app, then determine whether PV input and AC output are both low or only the AC side. That single split points you at the array, the grid, or the monitoring chain, and it takes minutes.

Start by splitting generation from export

This is the highest value step, because it eliminates most of the possibilities at once.

These are directions for investigation, not verdicts. Record a baseline on a clear day with timestamps and any available PV, AC and grid readings, because a comparison is worth more than an isolated figure.

Compare like with like

A large share of reported underperformance turns out to be normal variation, and checking this first avoids unnecessary call outs.

Output legitimately changes with sun angle through the year, day length, cloud cover, monsoon conditions and module temperature. A system compared against its own summer peak will look broken in winter. Module output also falls as module temperature rises, so the hottest days do not produce the highest yields despite the strongest sunshine.

Where you have a year of history, compare the same weeks year on year. Where you do not, compare clear days against clear days and note the date.

A useful order of checks

1. Weather and time. Establish whether the comparison is fair before investigating a fault.
2. Shading and soiling. Observe from a safe position. New shading appears over time as vegetation grows or neighbouring construction rises. Cleaning should follow the module manufacturer’s instructions and a safe access plan.
3. Local display against app. If the inverter reports normal generation and the app does not, the problem is in the monitoring chain.
4. PV side against AC side. Both low points at the array. Only AC low points at the grid, a limit or derating.
5. Array rating against inverter rating. A flat AC output sitting at a constant ceiling during peak hours may be clipping or a configured export limit rather than a fault.
6. Temperature and ventilation. Reduced output confined to hot afternoons that recovers by evening is the signature of thermal derating. The overheating guide covers this.
7. Tracker comparison. Where the inverter has independent MPPTs under similar conditions, a large difference between them isolates the problem to one string.

Use these observations to choose the next test rather than assuming a cause.

What UAC-low indicates

On many inverters UAC refers to AC voltage, so a UAC-low message points toward an AC or grid side condition rather than weak panels. The exact definition still belongs to the manual for the displayed model and firmware, and it should not be translated automatically into a statement about the array.

Record the complete message, the operating state, the time and any displayed AC value before asking for qualified checks.

Standby is a related source of confusion. Standby is frequently an expected operating state, at night or while start conditions are unmet. A standby indication combined with a UAC-low message commonly means the unit is waiting for the AC side to return inside its window. It matters when it persists at a time when normal operation would be expected.

For a high voltage rather than low voltage message, see the grid overvoltage guide. For other displayed codes, the error code guide covers safe first responses.

Causes that develop gradually

Sudden faults get noticed. Gradual decline often does not, which is why a baseline matters.

Vegetation growth introduces shading that did not exist at commissioning. Soiling accumulates at a rate specific to your location and season. Connector degradation and moisture ingress can raise resistance over years. A single underperforming string may reduce total output enough to notice but not enough to trigger a fault.

None of these announce themselves. They show up as a slow divergence from what the system used to do, which you can only see if you kept a record.

Keep a baseline worth comparing against

Almost every diagnosis on this page is easier with a record, and almost nobody has one.

The value appears years later, when the question is whether the system is genuinely down by a meaningful margin or whether this simply is what November looks like. Without a baseline that is an argument. With one it is a measurement.

What a professional should check

If a difference remains after the observations above, ask for a review covering the string schedule (the string sizing calculator helps check it) against the as built array, module and inverter datasheets, monitoring logs across a period rather than a single day, electrical measurements at the specified points, and the commissioning records.

The wiring guide identifies the major interfaces. If output has stopped entirely rather than fallen, use the failure guide instead, since that is a different diagnostic path.

Service handover

Send the model and serial number, any code with timestamps, local and app readings, and photographs taken from a safe position. Describe when the change began, whether it was gradual or sudden, and whether anything changed in the array, the router or the utility supply around that time.

Contact Qbits for an exact model equipment enquiry, or use the service partner directory. Keep the commissioning report available, since a diagnosis is considerably faster when current readings can be compared against the installed design.