Fault code index · Sofar HYD-ES · HYD-EP · ME3000SP
Sofar Solar Fault Code Index
Every Sofar Solar inverter error code from ID01 to ID107 — grid protection trips, PV input faults, battery BMS alarms, internal hardware errors, and communication failures. Covers the HYD-ES, HYD-EP, and ME3000SP ranges commonly installed across the UK.
Codes shown on LCD and in SolarMAN app
ID01–ID107 complete fault reference
HYD-ES · HYD-EP · ME3000SP
Jump to category
How Sofar codes work
Sofar Solar inverters use a numbered ID code system displayed on the LCD screen and logged in SolarMAN monitoring. Each code starts with ID followed by a two- or three-digit number.
ID01–ID04Grid voltage & frequency
ID05–ID08Battery & PV input voltage
ID09–ID31Internal hardware protection
ID48–ID56Communication & relay faults
ID57–ID86Thermal, system & EPS
ID94–ID107Firmware & battery BMS
Grid faults often resolve on their own once conditions stabilise. Internal faults (ID09–ID31) usually need a power cycle — turn off DC and AC isolators, wait five minutes, then restart.
Grid protection faults
Grid protection codes trigger when the mains supply voltage or frequency drifts outside the inverter's programmed safety window. In the UK, these limits are set by G98/G99 regulations. The inverter disconnects from the grid and waits for conditions to return to normal before reconnecting automatically.
ID01 — GridOVP (grid overvoltage)
Grid · voltage high
The mains voltage measured at the inverter terminals exceeds the upper protection limit. In the UK this typically means the grid voltage is above 253V. If the fault occurs occasionally during the afternoon, it is likely caused by high solar generation in your area pushing the local voltage up. If it is persistent, the grid supply voltage at your property is genuinely too high — contact your DNO to report it. An MCS installer can also adjust the protection window within G98 limits if needed. Grid disconnection guide →
ID02 — GridUVP (grid undervoltage)
Grid · voltage low
The mains voltage is below the lower protection threshold. Low grid voltage is less common in the UK but can occur in rural areas with long cable runs or during periods of high demand. The inverter stops exporting and waits for voltage to recover. If this happens frequently, contact your DNO — you may be at the end of a weak supply. Check that the AC wiring between the inverter and consumer unit is adequate gauge for the distance.
ID03 — GridOFP (grid over-frequency)
Grid · frequency high
The grid frequency has risen above the upper limit (typically 50.5Hz in G98 settings). Frequency deviations are usually caused by national grid balancing events and resolve within seconds. The inverter disconnects, waits for frequency to normalise, then reconnects automatically. If the fault is logged repeatedly in SolarMAN but your system seems to operate normally, the frequency may be briefly spiking at the edge of the protection band — this is a grid issue, not an inverter fault.
ID04 — GridUFP (grid under-frequency)
Grid · frequency low
The grid frequency has dropped below the lower limit. Under-frequency events happen when national demand exceeds generation capacity — the grid slows down momentarily. The inverter disconnects as required by G98 and waits. These events are rare and short-lived. If the fault appears alongside ID01 or ID02, the overall grid quality at your property may be poor and worth reporting to the DNO.
ID06 / ID07 — OVRT / LVRT fault
Grid · ride-through
The over-voltage ride-through (OVRT) or low-voltage ride-through (LVRT) function has detected a fault. These are grid support features that allow the inverter to stay connected during brief voltage dips or surges instead of tripping immediately. If the fault triggers, the grid event exceeded what ride-through can handle. Power cycle the inverter — turn off DC and AC, wait five minutes, then restart. If it recurs, contact your installer to check the OVRT/LVRT settings match your G98 configuration.
PV / Solar input faults
PV input faults relate to the DC side — the solar panels and their connections to the inverter's MPPT inputs. The HYD-ES and HYD-EP support dual MPPT with either independent or parallel input modes, and an incorrect mode setting is a common trigger for several of these codes.
ID08 — PVOVP (PV overvoltage)
⚠ DC string voltage exceeded max input
The open-circuit voltage on a PV string exceeds the inverter's maximum DC input rating. The HYD-ES has a maximum input of 600V DC. On cold mornings, panel voltage increases significantly — a string that is borderline on a warm day can exceed the limit in winter. Measure the string Voc with a multimeter. If it is close to or above the inverter's rated maximum, the string needs to be reconfigured with fewer panels in series. Do not ignore this — sustained overvoltage damages the inverter's DC input stage.
ID13 — GFCI OCP (ground fault)
PV · earth leakage
The ground fault current interrupter has detected a mismatch between the master and slave DSP sampling — indicating possible earth leakage on the DC side. If it occurs occasionally, it is likely caused by external conditions like moisture on panels or connectors. If it triggers frequently, check the PV array insulation resistance, inspect MC4 connectors for water ingress, and examine cables for physical damage. A persistent GFCI fault usually points to a degraded cable or connector.
ID14 — HwPVOC (PV overcurrent)
PV · hardware protection
The PV input current has triggered hardware-level overcurrent protection. Check that the PV input mode is set correctly — if two strings of different sizes are connected in parallel mode instead of independent mode, the combined current can exceed the MPPT rating. Also verify the total panel wattage on each MPPT does not exceed the inverter's rated input. Power cycle to clear, and adjust the input mode setting via the LCD menu if needed.
ID16 — IpvUnbalance (input current imbalance)
PV · string mismatch
The current from the two PV inputs is significantly unbalanced. This usually means the PV input mode is set incorrectly. If two strings of different sizes or orientations are connected, they must be in independent mode — not parallel. Parallel mode expects identical strings on both inputs. Check the PV input mode setting on the LCD and change it if needed. Also verify both strings have the same number and type of panels if you intend to use parallel mode.
ID33 — PvConfigSetWrong (input mode error)
PV · configuration
The PV input mode setting does not match the actual panel configuration. If you have one string connected, the mode should be set to independent. If two identical strings share the MPPT inputs in parallel, it should be set to parallel. An incorrect setting causes the inverter to mismanage the DC input and trigger protection faults. Navigate to the input mode setting on the inverter LCD and select the correct option for your installation.
ID56 — PvIsoFault (insulation resistance low)
PV · insulation
The insulation resistance between the PV array and earth is below the safety threshold. This is often caused by moisture in a MC4 connector, a damaged cable, or a panel frame earthing issue. Inspect the DC wiring — look for cracked insulation, water in connector boots, and any cable run that contacts sharp metal edges. If the fault only appears in wet weather, a connector joint is the most likely culprit. Disconnect strings individually to isolate which one has the low insulation.
Battery & BMS faults
Battery faults (ID05, ID27, ID100–ID107) are reported by the battery's own BMS through the communication link to the inverter. These codes appear on both the HYD hybrid inverters and the ME3000SP AC-coupled battery inverter. The inverter stops charging or discharging to protect the cells.
ID05 — BatOVP (battery overvoltage)
Battery · voltage high
The battery voltage is too high — the cells are being overcharged or the battery's charge voltage limit does not match the inverter's charge settings. Verify that the battery charge voltage parameter in the inverter settings matches the battery manufacturer's specification. If the battery type is set incorrectly (e.g. lithium set as lead-acid), the charge profile will be wrong. Also check ID102 (BatOV) which is the battery's own overvoltage protection — both can appear together.
ID27 — BatOCP (battery overcurrent)
Battery · current limit
The battery charge or discharge current has exceeded the protection threshold. If this triggers during high household demand, the maximum discharge current setting in the inverter may be higher than the battery can safely deliver. Reduce the max charge/discharge current to match the battery's rated continuous current. If the setting is correct and the fault still occurs, the battery's internal BMS may be limiting current due to temperature or cell imbalance.
ID100 — BatOCD (discharge overcurrent)
⚠ Battery BMS protection — discharge stopped
The battery's own BMS has triggered overcurrent protection during discharge. This is different from ID27 — it comes from the battery rather than the inverter. If it occurs occasionally, wait a few minutes and the system will resume. If frequent, reduce the maximum discharge current in the inverter settings or improve ventilation around the battery. High ambient temperature causes the BMS to lower its current threshold.
ID101 — BatSCD (charge short circuit)
⚠ Battery BMS protection — charge stopped
The battery BMS has detected a short circuit condition during charging. This is a safety shutdown. Power cycle the entire system — turn off DC and AC isolators, wait five minutes, then restart. If the fault returns, the battery's internal wiring or a cell connection may be damaged. Do not repeatedly power cycle into this fault — it needs professional investigation.
ID102 — BatOV (cell overvoltage)
Battery · BMS overvoltage
The battery BMS has detected that one or more cells have exceeded the maximum safe voltage. Charging stops to prevent damage. This often appears alongside ID05 (BatOVP). Check that the inverter's charge voltage setting matches the battery specification exactly. If the setting is correct, the battery may have a cell balancing issue — one cell is reaching full charge before the others. This typically needs a balancing cycle or BMS recalibration.
ID103 — BatUV (cell undervoltage)
Battery · deep discharge
The battery cells have discharged below the minimum safe voltage. The BMS stops all discharge to prevent permanent cell damage. If the depth of discharge (DOD) setting in the inverter is set too low (e.g. 0% minimum SOC), the battery will discharge further than it should. Set the minimum SOC to 10–20% to prevent this. If the battery has already tripped on undervoltage, it should recover by charging from AC mains or PV. If it will not accept charge, the cells may need professional recovery.
ID85 — SOC ≤ DOD / battery voltage low
Battery · discharge limit
Discharging has stopped because the state of charge has reached the depth-of-discharge limit, or the battery voltage has dropped below the cut-off threshold. This is normal protective behaviour — the system is preserving battery life. If you want more usable capacity, you can lower the minimum SOC setting, but setting it below 10% risks triggering ID103 (cell undervoltage) over time. Force charging from AC or PV will resume normal operation.
ID86 — Force charge failure
Battery · charge failed
The system attempted a force charge (either scheduled or triggered by low SOC) but could not complete it. This usually means there is no PV generation available and no grid charging is permitted by the current settings. Check whether grid charging is enabled in the inverter's time-of-use schedule. Also verify the grid connection is active and the AC breaker is on. If force charge is configured for off-peak hours but the grid supply drops out overnight, this fault will appear in the morning.
Internal hardware faults
Internal hardware faults (ID09–ID31, ID65–ID77) indicate problems with the inverter's internal circuits — power stages, control boards, bus voltages, and protection relays. The first step for all of these is a full power cycle: turn off both AC and DC isolators, wait at least five minutes, then restart. If the fault returns, it usually requires professional repair or warranty replacement.
ID09 — HW_LLCBus_OVP
Internal · bus overvoltage
The internal LLC bus voltage has exceeded the hardware protection threshold. This is an internal power conversion fault — the DC-DC converter stage is producing excessive voltage. Power cycle the system. If the fault clears and does not return, it was likely a transient event caused by a sudden load change or grid disturbance. If it persists after power cycling, the inverter's LLC converter board may have a component failure and needs professional inspection.
ID10 — HW_Boost_OVP
Internal · boost overvoltage
The boost converter voltage is too high and has triggered hardware-level protection. This relates to the DC-DC boost stage that steps up the PV string voltage to the internal bus level. Power cycle to clear. If it recurs, check the PV string voltage — a string close to the maximum input rating can push the boost stage into overvoltage during cold weather when panel Voc rises.
ID11 / ID12 / ID15 — Hardware overcurrent
Internal · overcurrent protection
ID11 (BuckBoost OCP) is overcurrent on the DC-DC converter. ID12 (HwBatOCP) is battery-side overcurrent at the hardware level. ID15 (HwAcOCP) is grid-side overcurrent at the hardware level. All three are internal protection events that require a power cycle. If one of these codes appears once and does not return, no action is needed. If it recurs, the inverter may have a failing power module or a connection issue on the relevant circuit — battery cables for ID12, AC terminals for ID15.
ID17 / ID18 / ID19 — AD sampling faults
Internal · sensor error
ID17 (HwADFaultIGrid) is a grid current sampling error. ID18 (HwADFaultDCI) is a DC injection sampling error. ID19 (HwADFaultVGrid) is a grid voltage sampling error. These indicate the inverter's internal measurement circuits are giving inconsistent readings. A one-off event usually clears with a power cycle. Repeated occurrences suggest a failing sensor or control board — the inverter will need warranty inspection.
ID20 / ID21 / ID22 — Control board faults
Internal · controller
ID20 (GFCIDeviceFault) is a GFCI sensor error. ID21 (MChip_Fault) is a master control chip failure. ID22 (HwAuxPowerFault) is an auxiliary power supply fault. These are serious internal hardware faults. Power cycle the system first. If any of these return after a power cycle, the control board is likely faulty and the inverter needs professional repair or warranty replacement. Do not continue operating with a persistent ID21 fault.
ID25 / ID26 — Bus overvoltage (software)
Internal · bus protection
ID25 (LLCBusOVP) and ID26 (SwBusOVP) are software-level bus overvoltage detections — the inverter's firmware has detected the internal DC bus voltage is too high before the hardware-level protection trips. These are often caused by transient conditions and clear on power cycle. If either recurs alongside ID09 or ID10, the bus voltage regulation circuit may have a fault.
ID29 / ID30 / ID31 — Software overcurrent
Internal · current limit
ID29 (SwOCPInstant) is a software-detected grid overcurrent. ID30 (BuckOCP) is buck converter overcurrent. ID31 (AcRmsOCP) is AC output RMS overcurrent. These are software-level protections that trigger before the hardware limits. Power cycle to clear. If ID29 or ID31 returns, check the AC wiring for a loose connection at the inverter terminals or consumer unit — a high-resistance joint causes current spikes that trigger these protections.
ID65–ID70 — Unrecoverable hardware faults
⚠ Persistent fault — requires engineer
ID65 (unrecoverable AC OCP), ID66 (unrecoverable bus OVP), ID67 (unrecoverable battery OCP in EPS), ID68 (unrecoverable input imbalance), and ID70 (unrecoverable grid OCP) are flagged as permanent faults that have occurred multiple times. The inverter has recorded the fault as non-transient. A power cycle may temporarily clear the code, but it will return until the root cause is repaired. These typically require warranty assessment and board-level repair.
ID55 — RelayFail (relay fault)
Internal · relay
The inverter's internal isolation relay has failed its self-test. The relay connects and disconnects the inverter from the grid — if it sticks or does not respond correctly, the inverter cannot safely export. Power cycle the system. If ID55 returns, the relay is likely physically failing and the inverter needs repair. ID77 (unrecoverable relay fail) is the permanent version of this fault — the inverter has decided the relay is definitively faulty.
ID75 / ID76 — EEPROM read/write fault
Internal · memory
The inverter's internal EEPROM (settings memory) has failed a read or write operation. ID75 is a write failure, ID76 is a read failure. The inverter stores its configuration and operating parameters in EEPROM — if it cannot read them, it may not start correctly. Power cycle first. If the fault returns, the EEPROM chip may be failing or corrupted. A firmware re-flash by an engineer may resolve it, otherwise the control board needs replacing.
Communication faults
Communication faults affect the link between the inverter and the battery BMS, the internal DSP boards, the SolarMAN monitoring dongle, and the CT meter. ID52 (battery communication) is the single most common Sofar fault in UK residential installations.
ID52 — BatCommunicationFlag
Battery · BMS communication
The inverter cannot communicate with the battery BMS — the most common Sofar fault in UK homes. Check that the RJ45 communication cable is plugged into the CAN port on the inverter (not RS485). Verify the battery type is set correctly in the inverter settings — an incorrect battery selection means the protocol does not match. For multi-battery stacks, confirm the master battery DIP switches are set correctly. If using a third-party battery like Pylontech, check the cable pinout matches the Sofar wiring diagram — many generic CAN cables have the wrong pin assignment for Sofar.
ID53 — SpiCommLose (SPI fault)
Internal · board communication
Internal SPI communication between the inverter's control boards has failed. This is an internal hardware fault — the main processor cannot talk to its co-processors. Power cycle the system. If ID53 returns, the control board interconnect may be failing. This is a warranty repair — do not attempt to open the inverter.
ID54 — SciCommLose (SCI fault)
Internal · serial communication
The SCI (serial communication interface) between the control board and the communication board has failed. This affects monitoring and remote access but the inverter may still operate locally. Power cycle to clear. If persistent, the communication board may need replacing — this is the board that hosts the SolarMAN Wi-Fi/4G dongle connection.
ID48–ID51 — Consistency faults
Internal · DSP mismatch
The master and slave DSPs (digital signal processors) inside the inverter are reading different values for the same measurement. ID48 = GFCI consistency, ID49 = grid voltage consistency, ID50 = grid frequency consistency, ID51 = DC injection consistency. These are internal self-check faults. A one-off occurrence after a grid disturbance is normal. Repeated consistency faults suggest a failing sensor or DSP and need warranty investigation.
ID35 — CT Fault
Metering · CT clamp
The current transformer (CT clamp) used for metering is faulty or not detected. Without CT data the inverter cannot manage export limiting or self-consumption scheduling. Check the CT clamp is firmly clamped around the correct cable (grid supply tails, not the solar feed), oriented in the right direction (the arrow should point towards the grid), and the CT cable is securely plugged into the meter port on the inverter. A damaged CT clamp or a broken cable will trigger this.
ID94 — Software version mismatch
System · firmware
The firmware version on the control board does not match the communication board. This happens after a partial firmware update — one board updated but the other did not. Retry the firmware update through the SolarMAN app. If it fails repeatedly, contact Sofar support for a forced firmware push. Do not leave the inverter running with mismatched firmware — features and protection settings may not work correctly.
ID95 / ID96 — Comm board EEPROM / RTC
System · communication board
ID95 means the communication board's EEPROM is faulty — it cannot store or retrieve settings. ID96 means the real-time clock chip on the communication board is faulty — the inverter cannot keep accurate time, which affects scheduling and monitoring timestamps. Both require a power cycle first. If either persists, the communication board needs replacing — the inverter will still generate power but monitoring and time-based features will not work correctly.
ID97 — InValidCountry (country code)
System · configuration
The inverter's country code and grid connection settings need to be reset. This can happen after a firmware update clears the configuration, or if the inverter was imported without UK settings. An MCS-certified installer needs to set the country code to the correct UK G98 or G99 profile. This is not a user-serviceable setting — incorrect grid protection parameters are a safety and compliance issue.
ID98 — SDfault (SD card error)
System · data logging
The internal SD card used for data logging is faulty or loose. Remove the SD card, clean the contacts, and re-insert it firmly. If the fault persists, the SD card may need replacing — use a compatible micro-SD card formatted to FAT32. A faulty SD card does not affect inverter operation or generation, only local data logging. Monitoring through SolarMAN will continue to work via the Wi-Fi/4G dongle regardless.
Thermal & EPS faults
Thermal faults trigger when the inverter or battery exceeds its operating temperature range. EPS (emergency power supply) faults relate to the backup output that powers essential circuits during a grid outage. The HYD-ES and HYD-EP both support EPS functionality.
ID57 — Battery over-temperature
Battery · thermal
The battery temperature has exceeded the safe operating limit. The inverter stops charging and discharging to protect the cells. Common in summer if the battery is in an enclosed cupboard, loft space, or south-facing garage without ventilation. Improve airflow around the battery and ensure it is not exposed to direct sunlight. Reduce the maximum charge/discharge current setting to lower the heat generated during operation. The system will resume once the temperature drops.
ID58 — Heat sink over-temperature
Inverter · thermal
The inverter's internal heatsink temperature is too high. The heatsink dissipates waste heat from the power electronics. If it overheats, the inverter derate its output or shut down entirely. Check that the inverter has adequate clearance around the heatsink (rear of the unit), is not mounted in direct sunlight, and has not been boxed in by a cover or enclosure that restricts airflow. Dust build-up on the heatsink fins also reduces cooling — clean with a dry brush if accessible.
ID59 — Environmental over-temperature
Inverter · ambient
The ambient temperature sensor inside the inverter is reading above the upper operating limit. This is a whole-room temperature issue rather than an inverter-specific fault. Ensure the installation location is ventilated and not sealed. Garages and loft spaces can exceed 50°C in summer heat. If the location cannot be cooled, the inverter may need relocating to a more suitable position. The system will resume automatically once the temperature drops.
ID81 — Temperature derating
Inverter · power reduction
The internal temperature is high but not yet at shutdown level — the inverter has automatically reduced its output power to manage heat. This is normal behaviour in hot weather and means the inverter is protecting itself. You may see reduced generation during peak afternoon hours in summer. Improving ventilation or shading the inverter will help it maintain full output. No action is required unless derating is happening frequently or in cool weather, which would suggest a cooling system fault.
ID104 / ID105 — Battery temp high (discharge / charge)
Battery · over-temperature
ID104 (BatOTD) triggers when the battery temperature is too high during discharge. ID105 (BatOTC) triggers during charging. Both are BMS-level protections — the battery itself is reporting the fault. Improve ventilation around the battery, reduce the max charge/discharge current to lower heat generation, and ensure the battery is not near a heat source like a boiler or in direct sunlight. If the temperature sensor inside the battery is faulty, it may report incorrect readings — this needs professional diagnosis.
ID106 / ID107 — Battery temp low (discharge / charge)
Battery · cold weather
ID106 (BatUTD) triggers when the battery temperature is too low during discharge. ID107 (BatUTC) triggers during charging. Lithium batteries must not be charged below 0°C — doing so causes permanent cell damage. Common in winter when the battery is in an unheated garage or outbuilding. The system will resume once ambient temperature rises. Do not attempt to force charge a cold battery. If this is a regular occurrence, consider relocating the battery to a warmer space or adding insulation to the installation area.
ID34 — Overload (EPS output)
EPS · backup overload
The load on the EPS (backup) output circuit exceeds the inverter's rated backup capacity. During a power cut, appliances like kettles, ovens, and immersion heaters draw more power than the inverter can supply from battery alone. Reduce the load by switching off non-essential appliances on the backed-up circuit. The HYD-ES can deliver up to its rated kW on EPS — check the total connected load stays within this limit. ME3000SP EPS guide →
ID60 — PE connect fault (earthing)
Safety · grounding
The protective earth (PE) wire on the AC output is not properly connected. The inverter has detected the earth path is missing or has high impedance. Check the PE wire at the inverter's AC terminal block and trace it back to the earth bar in the consumer unit. A loose crimp, corroded terminal, or disconnected earth wire triggers this. The inverter will not export until the earth connection is verified. This is a safety-critical fault — do not bypass it.
ID83 / ID84 — Remote derating / shutdown
System · remote command
ID83 means the inverter has received a remote command to reduce its power output. ID84 means it has received a remote shutdown command. These are deliberate actions — either from the DNO via a ripple control signal, from the SolarMAN platform, or from an external energy management system. If you did not initiate this, check your SolarMAN account for any active power limits or schedules. Contact your installer if a DNO export limitation is in place that you were not aware of.
Fault not listed here?
The Sofar ID code system spans over 100 fault types. If you see a code on your LCD or in SolarMAN that is not listed above, share the exact ID number and we will identify it. Some codes only appear on specific firmware versions or newer HYD-EP hardware.
Full diagnostic guides by fault type
ID01 · ID02 · grid voltage · G98
Grid disconnection fault
Why the inverter keeps tripping on grid voltage — DNO reporting, protection settings, and AC wiring checks.
ME3000SP · EPS mode · backup
ME3000SP EPS mode fault
ME3000SP not switching to backup mode, EPS relay issues, and load management during outages.
Manuals · datasheets · wiring
Sofar documents
Official HYD-ES, HYD-EP, and ME3000SP user manuals, datasheets, and installation guides.
Sofar Solar inverter fault questions
Sofar inverters display fault codes on the LCD screen as an ID number — for example ID01 or ID52. The same codes appear in the SolarMAN monitoring app under the device alarm history. Grid-related faults (ID01–ID04) often clear automatically when conditions normalise. Internal hardware faults (ID09–ID31) typically require a power cycle — turn off both DC and AC isolators, wait five minutes, then restart. Battery faults (ID100–ID107) come from the connected battery's BMS rather than the inverter itself.
ID52 means the inverter cannot communicate with the battery's BMS — it is the most common Sofar fault in UK installations. Check the RJ45 cable is in the CAN port (not RS485), verify the battery type is set correctly in the inverter settings, and for multi-battery stacks confirm the master DIP switches are correct. If using a third-party battery like Pylontech, check the cable pinout matches the Sofar wiring diagram — many generic cables have the wrong pin assignment.
Repeated ID01 (GridOVP) or ID02 (GridUVP) faults mean the mains voltage is outside the inverter's G98 protection window. UK nominal voltage is 230V with a tolerance of +10% / -6%. If your local grid sits above 253V consistently, the inverter will trip. This is a grid supply issue, not an inverter fault — contact your DNO to report high voltage. An MCS installer can also widen the protection window within the permitted range if the voltage is borderline. See our grid disconnection guide.
STS offers remote diagnostic assessments from £75. We access your system through SolarMAN monitoring to review the alarm history, operating parameters, and real-time data. Most Sofar faults can be diagnosed remotely — we identify the root cause and provide a written report with the recommended fix, whether that is a settings change, firmware update, communication cable replacement, or a site visit for hardware repair.
The HYD-ES is the original Sofar hybrid inverter for UK residential installations (3–6kW single-phase). The HYD-EP is the newer replacement with updated hardware, improved EPS switching time, and additional safety features. Both share the same fault code system (ID01–ID107) and the same SolarMAN monitoring platform. The EP series also adds support for parallel operation and a wider battery voltage range. Most troubleshooting steps apply to both models.
Book
Sofar fault code you can't clear?
Tell us the ID code on your LCD or SolarMAN alarm, the inverter model, and when the fault first appeared. We'll pull your monitoring data remotely and identify the root cause — whether it needs a settings change, firmware update, or site visit.
Not affiliated with Sofar Solar
Remote diagnostic from £85
Written report with cause and recommended action