Practical guide

No solar input: diagnose the array without bypassing protection

Check light, connector seating and polarity, array voltage and current, input mode, cable damage, temperature, and controller limits. Do not short, probe, or rewire live connectors beyond safe competence. Use current primary documentation, measured loads, and a tested recharge and fallback plan before relying on the system.

Last materially reviewed 2026-08-28

Quick answerCheck light, connector seating and polarity, array voltage and current, input mode, cable damage, temperature, and controller limits. Do not short, probe, or rewire live connectors beyond safe competence.
Direct answer

No solar input: define the symptom or error

Check light, connector seating and polarity, array voltage and current, input mode, cable damage, temperature, and controller limits. Do not short, probe, or rewire live connectors beyond safe competence.

A sound no solar input decision has four boundaries: the load that must run, the hours it must survive, the method and time available to replenish it, and the fallback if either assumption fails. Write those boundaries down before comparing price, capacity, or accessories.

  • Define what success means for no solar input.
How it works

Diagnose the cause without changing everything

Translate specifications into a day of operation. Note startup events, idle draw, duty cycle, temperature, simultaneous loads, reserve, charging windows, and what happens after a cloudy day or missed drive.

Record the one uncertain fact that could reverse the choice. That becomes the next measurement or support question.

  • Measure the actual load.
  • Verify the exact model and connection.
  • Record the fact that would reverse the decision.
Decision framework

Test and verify the fix

Use a complete ownership test. Add equipment, panels, chargers, batteries, integration, transport, energy, storage, and one plausible service event. Then ask whether no solar input still solves enough repeated value to justify its burden.

The cheapest box is not automatically the lowest-cost system, and the most expandable system is not automatically the easiest to own.

  • Compare the same power job.
  • Keep runtime and recharge in one model.
  • Protect a fallback with a different failure mode.
Final check

Escalate a repeated failure

Commission no solar input like a small piece of infrastructure. Photograph connections, label cables, record baseline input and output, run the intended load, verify the recharge window, and place the current instructions where another person can find them.

Review the plan after a real event. Update the load estimate and operating sequence from observed evidence rather than preserving an optimistic first assumption.

  • Save the manual and load record.
  • Assign the system owner.
  • Retest before relying on it.
Continue when useful

Next: Overload

Disconnect loads, inspect for damage or heat, identify running and startup demand, reset only as the manual permits, and reintroduce one load at a time. Repeated protection events mean the plan needs correction. Use current primary documentation, measured loads, and a tested recharge and fallback plan before relying on the system.

Open Overload →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. BLUETTI AC180 support and documentation — DOCUMENTATION · checked 2026-08-28
  2. US Department of Energy homeowner guide to solar — GOVERNMENT · checked 2026-08-28