SolarEdge Fault Code Index
Every SolarEdge fault code from SetApp and the monitoring portal — what it means, the most likely cause, and what to do. Find your code in the index below or use the category sections to browse by system area.
Jump to category
If your SolarEdge inverter is showing a fault code and you need expert diagnosis, a remote diagnostic identifies the cause and recommends the fix — usually within 30 minutes.
Book SolarEdge diagnosis — £75 → How diagnostics workFault codes generated by the inverter in response to AC supply problems, DC overvoltage from panels, or ground faults. These typically cause the inverter to stop generating.
1001
Grid fault
1003
Grid voltage high
1004
Grid voltage low
1006
Grid frequency high
1007
Grid frequency low
1010 / 3x11 — AFCI arc fault
⚠ Arc fault
2x11 — Over temperature
Newer residential inverters
Status codes from individual power optimisers — communication failures, under-voltage events, and pairing issues. One faulty optimiser does not stop the whole system, but reduces generation on that panel.
S_OK
Status normal
N/A · Not communicating
Optimiser offline
Under voltage
Input voltage low
Open circuit
No panel connection
Temporary inhibit
Startup inhibit
Grid connection codes and events triggered by G98/G99 grid code settings. These are protection functions, not faults — they prevent the inverter from generating during grid faults.
Grid connection failed
Connection error
Reactive power limitation
DNO export limit
Export limitation active
Export limit configured
2x28 — Grid is down
Newer residential models
2x1F / 2x20 / 2x21 / 2x29 — Grid voltage limit
Voltage above or below country limit
Faults related to data communication between inverter and monitoring portal, and between the inverter and other system components.
Communication error with monitoring
Portal connectivity
Inverter not paired
SetApp pairing lost
RS485 communication error
Bus communication fault
Faults related to DC string voltage, power, and insulation — the PV side of the system.
PV voltage too high
DC overvoltage
Minimum string power
Low power threshold
PV isolation fault / 2x19
⚠ PV not isolated from ground
2x0A — Ground fault
⚠ Ground fault — newer models
2x0F — DC overvoltage
Newer residential models
SolarEdge releases updates that may introduce new fault codes. If your code isn't listed, share the exact code from your event log and we'll identify it. SolarEdge also maintains fault code documentation on their support portal.
Pairing, under-voltage, shading, and hardware fault diagnosis.
What triggers AFCI, when it is safe to restart, and when to call an engineer.
G98/G99 disconnects, DNO export limits, and reactive power settings.
SolarEdge fault code questions
SolarEdge fault codes appear in two places — the monitoring portal Events tab at monitoring.solaredge.com, and in SetApp under Status > Troubleshooting. SetApp gives the most detail and works via Bluetooth without an internet connection. Note the exact fault code number and the inverter serial number before contacting support.
An optimiser showing N/A means it is not communicating with the inverter. This is usually caused by the optimiser losing pairing after a power cycle, a shading event causing under-voltage, or a hardware fault in the optimiser. Open SetApp > Status > Optimisers to see which unit is affected and its last reported voltage. If voltage is zero, the optimiser or the panel connection may be the fault.
Many SolarEdge fault codes clear automatically when the fault condition resolves — grid voltage events are an example. For persistent codes, a power cycle (AC isolator off, wait 30 seconds, back on) is the first step. Do not repeatedly cycle power if the same code returns — that indicates a persistent fault that needs diagnosis. AFCI arc faults and PV isolation faults should not be cleared without a qualified engineer checking DC cabling first.
Recurring fault codes often indicate a hardware issue rather than a software glitch. If a reset temporarily clears the code but it returns, STS recommends a diagnostic visit (from £75) to check components like optimisers, DC cabling, and the inverter itself.
Got a fault code and need it diagnosed?
Share the exact fault code from your event log or SetApp, what the system is doing, and when it started. We'll identify the cause and tell you whether it needs a remote settings fix or a site visit.