SolarEdge not producing — no generation from HD-Wave inverter
Your SolarEdge shows sunshine but zero generation. The monitoring portal shows the inverter online but power output is stuck at 0W. We walk you through SetApp diagnostics, DC isolator checks, and optimiser fault isolation — step by step.
SolarEdge not producing despite good weather. Share your SetApp alerts or monitoring portal screenshot and we'll identify the fault path remotely.
Book remote diagnostic → Back to SolarEdge hubSafety: Do not touch DC cabling or open the inverter enclosure. All checks on this page use the monitoring portal and SetApp only.
Safety: Do not open the inverter or touch any DC cabling. If you discover a fault code suggesting a DC wiring issue or arc fault, isolate the DC and AC switches and contact a qualified engineer immediately.
5-step diagnostic to find the no-production cause
Follow these steps in order. Most no-production faults are found in the first two checks.
Check SetApp / monitoring portal for active alerts
Open the SolarEdge monitoring portal (monitoring.solaredge.com) or SetApp on your phone. Look for the Alerts or Status section. Write down any fault codes you see. The most common codes are:
If no fault code appears but production is zero, move to Step 2.
Check DC input voltage — DC isolator and fuses
In the monitoring portal, find the Inverter Details or Live Data section. Look for "DC Input Voltage" or "DC Volts". A healthy system should show 300–450V depending on the time of day and array size. If it shows 0V:
If DC volts show 0V, start with checking the DC isolator. If it's on and fuses are intact, you likely have a wiring issue — stop here and contact a qualified engineer.
Check optimiser status in SetApp — P404 and P401 analysis
Open SetApp and navigate to the Inverter Status or Optimiser Overview. Review each optimiser in the list. Look for patterns:
This is a string-level problem. The inverter cannot communicate with any optimisers. Most likely cause: damaged DC wiring, loose connector, or blown string fuse.
Those specific optimisers have failed or lost DC power. The rest of the array should still produce. Affected units need replacement.
Note which optimiser(s) show fault codes — you'll need this information for your engineer or warranty claim.
Check AC isolator and grid connection
SolarEdge will not produce if disconnected from the grid, even if the DC side is fully operational. Check two things:
If the AC isolator is on and the portal shows 0V AC, the problem is downstream of the isolator — likely a tripped circuit breaker or grid connection fault. Check your main board for tripped breakers.
Check for SetApp firmware lockout — post-update commissioning
If no-production started after a firmware update, the inverter may have triggered a commissioning lockout. SetApp may display "System incomplete" or similar messaging. Try a brief manual power cycle:
If the problem persists after a full power cycle, the inverter may need formal re-commissioning through SetApp (this requires Bluetooth access during setup). Contact your installer or a qualified SolarEdge engineer.
How SolarEdge architecture affects no-production diagnosis
SolarEdge HD-Wave inverters use power optimisers mounted on each panel. Unlike string inverters where one fault can kill the entire array, individual optimiser faults reduce output proportionally — if one of eight optimisers fails, you lose about 12.5% of production, not 100%. This is why the monitoring portal's panel-level data is so valuable for diagnosis.
SetApp is the configuration and commissioning tool. It communicates with the inverter over Bluetooth during setup and provides real-time fault codes and optimiser status. The monitoring portal (accessible online) shows historical data and per-panel production. Common no-production fault codes: P404 (optimiser communication lost), P401 (output below expected), P700 (arc fault detection).
A DC isolator or blown fuse will cause immediate and complete loss of DC power — the monitoring portal will show 0V DC input. An AC isolator fault or grid disconnection will cause the inverter to stop producing even though the DC side shows full voltage — the portal will show 0V AC and the inverter will display a grid fault code.
Common SolarEdge no-production questions
No production usually means either: (1) a DC power issue — tripped DC isolator, blown fuse, or wiring fault; (2) an AC grid disconnection; or (3) an inverter/optimiser fault code that's blocking operation. Check SetApp for active alerts first. If you see P404, P700, or P401, that's your specific fault path.
P404 means the optimiser has lost communication with the inverter. If all optimisers show P404, the problem is at the string level — usually a wiring fault, loose connector, or blown fuse. If only one or two units show P404, those specific optimisers have failed or lost DC power and need replacement.
If the portal shows optimisers as 'offline' or 'N/A' but the inverter display is lit and the portal is responding, the inverter is powered but those specific optimisers aren't communicating. This indicates a local fault with those units (or their DC wiring), not a total system failure. Check SetApp for the specific fault code to identify which optimisers are affected.
Only if it's a simple isolator or configuration issue. Checking that DC and AC isolators are on, resetting after a firmware update, and reviewing SetApp settings are safe. If you find a fault code (P404, P700) or suspect a wiring issue, stop and contact a qualified engineer — do not open the inverter or touch DC cabling.
Need help with your SolarEdge no-production fault?
Share your SetApp alerts or monitoring screenshot. We identify the exact fault path remotely in a single session.
Return to the SolarEdge brand hub to explore other common faults and services.
SolarEdge support hub →