SofarSolar HYD 3…6K-EP (pv)
The SofarSolar HYD 3…6K-EP is a single-phase hybrid inverter for residential PV and battery storage installations. This Modbus TCP template reads the four PV input power channels (power_a through power_d) covering individual string or MPPT inputs, plus the 32-bit cumulative energy yield register. Together these registers give installers a complete picture of PV generation performance without requiring access to the SofarSolar cloud portal. The template covers the HYD 3…6K-EP, HYD 5…20K-3PH, SOFAR 80…136KTL, and SOFAR 5…24KTL-G3 families.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 5, read only
- Brand
- SofarSolar
- Compatible models
- HYD 5…20K-3PH · HYD 3…6K-EP · SOFAR 80…136KTL · SOFAR 5…24KTL-G3
- Last updated
Registers (5)
5 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power_a | W | Read | |||
| power_b | W | Read | |||
| power_c | W | Read | |||
| power_d | W | Read | |||
| energy | Wh | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor per-channel PV power (power_a through power_d) to detect shading or soiling on individual strings.
- Track cumulative energy yield over time to verify production against the original PV system design estimate.
- Alert on a persistent zero reading on any power channel to catch a blown string fuse or disconnected MPPT input.
- Compare power_a and power_b readings during peak hours to identify imbalance between roof sections or orientations.
- Report daily and monthly energy totals from the energy register to building owners or asset managers.
Installation
Enable 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).
Connect 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.
In 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.
Verify 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
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.
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.
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.
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.
Want to see how it works?
