SofarSolar HYD 3…6K-EP (pv)

Installation

1. 1Enable Modbus TCP communication on the inverter via the inverter LCD menu or the LSE-3 logger web interface under the communication or Modbus section, and note the assigned unit ID (default is 1).
2. 2Connect the SofarSolar inverter's LSE-3 LAN logger or RS485-to-TCP adapter to the same local network as the ModbusCloud Gateway, ensuring the inverter is reachable on TCP port 8899 or 502 depending on your logger firmware.
3. 3In your ModbusCloud portal, add the Gateway, import the SofarSolar HYD 3…6K-EP (pv) template, and enter the inverter's IP address and unit ID so the Gateway can poll registers 1414 to 1422 and 1670.
4. 4Verify the connection by checking live readings for power_a and energy in the portal dashboard; a non-zero power_a value during daylight confirms polling is working correctly.

Things to watch for

01

All power channels read zero even though the inverter is producing.

Confirm that Modbus is enabled in the inverter's communication settings and that the unit ID in the portal matches the inverter's configured slave address. Also verify that your LSE-3 or LAN adapter firmware supports direct Modbus TCP access; some older firmware versions block external polling on port 8899.

02

The gateway connects but the energy register returns garbage values.

Register 1670 is a 32-bit uint32 value split across two consecutive 16-bit Modbus registers. The SofarSolar HYD protocol uses big-endian byte order with the high 16-bit word first. Ensure your gateway or tool is reading two registers and combining them high-word-first, otherwise the value will appear nonsensical.

03

Only power_a and power_b return values; power_c and power_d always read zero.

The HYD 3…6K-EP is a single-phase inverter with dual MPPT inputs. Registers power_c and power_d map to additional channels that may not be wired in all installations. A zero reading on those channels is normal if fewer than four PV strings are connected.

04

Communication drops every few minutes, then reconnects by itself.

The SofarSolar LSE-3 logger limits simultaneous TCP connections and may close idle sessions. Reduce your polling interval to keep the connection active, or configure the ModbusCloud Gateway to reconnect automatically after a timeout. Also check that no other device such as the SolarmanV5 cloud logger is competing for the same TCP session.

Registers (5)

5 read / 0 write

More SofarSolar templates

SofarSolar Hybrid Inverter (battery)

SofarSolar

Modbus RTU

2 registers

SofarSolar Hybrid Inverter (pv)

SofarSolar

Modbus RTU

2 registers

SofarSolar HYD 3…6K-EP (grid)

SofarSolar

Modbus TCP

8 registers

SofarSolar Hybrid Inverter (grid)

SofarSolar

Modbus RTU

5 registers

SofarSolar HYD 5…20K-3PH (battery)

SofarSolar

Modbus RTU

1 registers

SofarSolar HYD 3…6K-EP (battery)

SofarSolar

Modbus RTU

1 registers

More TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers