Solar Inverter Fault Codes: The Protections Behind the Number

The code on a solar inverter's screen is not the beginning of the problem but its end. A moment before it appeared, one specific protection measured a value outside its window, cut the output, and then wrote the code. Reading the code alone therefore gives you half the answer. The other half is the window the value left, and that is printed as a figure on your model's spec record.

If a code is in front of you right now, start where it belongs: our reference is arranged by device rather than by number — the error-code reference — and for Deye inverters specifically there is Deye Inverter Error Codes by Model. What follows here is the layer underneath the code.

We are an authorised distributor of Deye products, and every figure below is lifted from the spec records we publish — 134 of them for Deye inverters. You will not find a cause or a fix for an individual code on this page: that belongs to the device, and its place is the reference above.

If you want your own model's limits before you touch anything, send the model code on WhatsApp +971 4 255 0887 or to sales@deyeinverters.net and we will send its rows back exactly as the record states them.

Six protections stated on all 134 records

Protections are not options you buy. Six of these rows appear on all 134 records without exception, and four more on most of them. Each one is a potential code the moment a value leaves its limit.

The rows that are not written on everything describe the families of the range itself. Anti-islanding is Not Applicable on three records only — the three off-grid OG01LP1 units, which have no grid to disconnect from. Residual current detection is Not Applicable on 15 records: those three plus the 12 micros. DC component monitoring and the DC switch are both Not Applicable on the 12 micros and Yes on 122. An absent row here is not a missing feature but a different job.

Optional is not present, and unstated is not No

Three rows read Optional across the range, which means the function may not be in the unit you receive unless you ask for it. The arc fault circuit interrupter reads Optional on 119 records, Yes on three only — the OG01LP1 units — and Not Applicable on the 12 micros. String monitoring reads Optional on 70 records, all string inverters, unstated on 52 and Not Applicable on 12. Anti-PID reads Optional on 70 and unstated on 64.

Ground fault monitoring reads Yes on ten records only — the three-phase G06P3 family from 3 to 15 kW — and is unstated on 124. An unstated row is not a No: it is a figure we do not hold, so we do not publish one. The difference between does not have it and we do not know matters precisely when a technician asks whether your unit has the function.

The windows the protections compare against

Every protection has a window, and the windows are printed as figures on the record itself. Across the 134 records they publish like this:

What gets set inside those windows — the grid standard, the charge current, the six periods — is the subject of a different page: How to Program a Deye Solar Inverter.

Three behaviours reported as faults that are not faults

1. Output falls at midday with no code. 113 records state a derating start temperature of 45 °C, and above it the unit deliberately reduces output to protect itself. The ceiling written into the operating temperature range — 60 or 65 °C — is still far away, so the unit is inside its range while it derates.
2. The unit stops the instant the grid goes. Anti-islanding protection reads Yes on 131 records, and its job is exactly to prevent output into a dead grid. What keeps the house lit afterwards is the battery, and the battery type row reads Not Applicable on 82 records.
3. Output never exceeds the load in full sun. Zero-export support reads Yes on 70 records, all of them string inverters, and is unstated on 64. The row states support, not state: if it is enabled in your installation, the ceiling is the house's instantaneous consumption rather than the available sun.

What to record before restarting

A restart clears the screen without clearing the cause, and what it takes with it is the evidence. Before you restart, write down these six — they are what the first technician you speak to will ask for:

1. The model code as printed on the unit itself, not as written on the invoice: records differ between two models whose names look alike.
2. The code exactly as it appeared, and what the unit was doing when it did: charging, discharging or exporting.
3. The time of day. Early morning and midday point at two completely different rows — the first at startup voltage, the second at the 45 °C derating point.
4. The grid voltage as you measured it, against the 0.85–1.1 of nominal voltage stated on 131 records.
5. The string voltage as you measured it, against the maximum PV input voltage on your model's record — 550, 1,100, 1,000, 500, 800 or 60 V depending on the model.
6. What changed: a panel added, a battery swapped, a new load, or grid work in the street.

What we do not write

You will not find a cause or a fix for an individual code written from memory on this page. What we hold is the spec records, and they state protections and windows rather than codes; we will not fill the gap from somewhere else to make the page look longer. Two missing rows deserve to be named rather than hidden: ground fault monitoring is unstated on 124 records, and the derating start temperature is unstated on 21. Code meanings belong in the reference, which is arranged by device because that is the correct shape of the question.

And if the code returns after every restart, the next step is not a fourth one: send the model code, the code shown and the three readings above on WhatsApp +971 4 255 0887 and we will read your record's rows against them.