Fronius integration status/error description

The current integration is just great. However the device has both a status and an error sensor that issue numerical values. Unfortunately they are totally useless, unless you have a service manual handy.

It would be quite useful if the numerical codes can be displayed as a separate textual description too. I know that this would lead to “why is this not translated into my own native language?” problems, but a common (english?) default could nontheless be quite useful.

some kind of sensor.symo_5_0_3_m_errortext in addition to the current sensor.symo_5_0_3_m_errorcode

Hi :wave:!
The error_code mappings are not part of the API documentation. I have no idea if they are the same among the different models we support.

status_code and meter_location on the other hand are, and I’ve just filed a PR to support these as translatable text sensors.

1 Like

The error code mappings are part of the User Manual. They cover a bunch of additional devices that talk to the inverter - which serves as the general data mediator.

I assume they would be quite universal within the Fronius Ecosphere, at least for all “Symo” variants. Not all error codes may apply for all devices. If you do not have a hybrid model, “battery” errors do not apply. I have a different model than the listed document, but at least I successfully could match a handful of error numbers with this document. 306, 307 are to expected, 461 may happen occasionally.

I was not able not verify this in detail however. Fortunately most of those errors are not that common. :grimacing:

I sent an email to Fronius support asking for a list of error codes. They didn’t really seem to get what I was talking about, but said they would open a ticket… let’s see if there will be any response.
If they are the same for all models, I’ll look into adding them. If they are device specific I guess I’ll just leave it as is.

2 Likes

Hi! did you receive some answer? just wonder what is the meaning of 2 or 3 as a “stauts code”… it seems not relate to a specific error but something happening during low sunlight.

That’s not error_code. For status_code there is another entity status_message translating the numeric code.

Thankyou. I have this entity but translate simply in 3 states, like “starting”, “running” and “empty”, i Thought have more information

I know i’m a little late to the party, but I had ChatGPT do some Deep Research to find the Status codes as i’m also interested, and this is the result.

Status Code 1 – Startup (Phase 1):** Indicates the inverter is in an initial startup stage. This occurs when the inverter is just beginning to wake up or initialize. No power is being fed into the grid yet during this phase​. (At night or very low light, the inverter may sit in early startup/standby stages waiting for sufficient sunlight.)

Status Code 2 – Startup (Phase 2):** The inverter is still in its startup sequence (not producing power yet). It may be performing internal checks or waiting for DC input to reach the required level. In darkness (nighttime), the inverter often alternates between codes 2 and 3 as it periodically tests for enough sunlight to start feeding​. This is a normal “not yet active” state.​

Status Code 3 – Startup (Phase 3):** A later stage of the startup process, where the inverter is nearly ready to begin power export but is still not feeding the grid. The inverter has completed most checks and is synchronizing with grid conditions (voltage/frequency) before connecting. At night, the inverter might cycle into this state as it tries to start, then falls back due to insufficient solar power​. Like codes 1 and 2, this means the inverter is on but not yet producing output​.

Status Code 4 – Running (Grid Power Reduction Mode):** This code indicates the inverter is on and capable of feeding in, but its output is being actively limited due to a grid condition. In practice, code 4 is commonly triggered by Grid Voltage Dependent Power Reduction (GVDPR) – also known as Volt-Watt mode​. This means the grid voltage is higher than the acceptable threshold (e.g. above ~250 V), so the inverter continues operating with reduced power to protect the grid​. In other words, the inverter is running but throttled due to high grid voltage.

Status Code 5 – Running (Thermal Derating):** The inverter is on and feeding power, but its output is being curtailed due to an internal limitation, typically overheating. High internal temperature can cause the inverter to automatically derate (reduce output) to prevent damage​. While code 5 is active, a warning may be logged, but the inverter is still online (not off). Once temperatures fall to safe levels, the inverter should return to normal full-power operation. (In summary, code 5 means the inverter is producing power at a reduced level, often due to thermal protection.)

Status Code 6 – Running (Grid Frequency Derating or External Limit):** This code signifies the inverter is operating but not at full output due to external factors. A common cause is over-frequency on the grid – if grid frequency rises above the nominal range, the inverter will reduce power to help stabilize it​. Code 6 could also indicate other curtailment, such as an external command to limit output or a special operating mode. In this state, the inverter remains online and feeding, but at curtailed power. Normal operation (code 7) resumes once grid frequency or other conditions return to normal​.

Status Code 7 – Running (Normal Operation):** The inverter is in full active operation, feeding energy into the grid at maximum available power. This is the standard daytime status when the PV system is producing. In this state the inverter is in MPPT mode, delivering power as per available sunlight​. Code 7 is the typical status during daylight hours when everything is working and no limiting conditions are present​. (In short, code 7 = normal power production.)

I hope that helps if anyone is still trying to figure it out.

Geoff