SofarSolar HYD 3…6K-EP (grid)
The SofarSolar HYD 3...6K-EP is a single-phase hybrid inverter combining PV generation, battery storage, and grid interaction in one unit, deployed in residential and small commercial solar-plus-storage installations. This ModbusCloud template reads the inverter's grid-side measurements over Modbus TCP: total grid power, per-phase currents and active powers across all three phases, and a cumulative energy counter. Together these registers give installers and asset managers a complete picture of import, export, and throughput at the grid connection point without manual site visits.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 8, read only
- Brand
- SofarSolar
- Compatible models
- HYD 5…20K-3PH · HYD 3…6K-EP · SOFAR 80…136KTL · SOFAR 5…24KTL-G3
- Last updated
Registers (8)
8 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| currents_a | A | Read | |||
| currents_b | A | Read | |||
| currents_c | A | Read | |||
| powers_a | W | Read | |||
| powers_b | W | Read | |||
| powers_c | 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 total grid import and export power in real time to verify self-consumption targets are met.
- Track per-phase active power on all three phases to detect load imbalances across the installation.
- Alert on sustained grid import during daylight hours to identify underperforming PV strings or battery faults.
- Report cumulative grid energy over time to support feed-in tariff reconciliation and billing verification.
- Compare phase currents across phases A, B, and C to spot wiring errors or breaker issues after commissioning.
Installation
Enable Modbus communication on the SofarSolar HYD 3...6K-EP by navigating to the communication or Modbus address section on the inverter's LCD menu and setting a unique unit ID.
Connect the inverter's Ethernet logger (such as the LSE-3 or LSW-3 stick) to the same local network as the ModbusCloud Gateway, ensuring the logger is reachable by IP address on port 8899.
In your ModbusCloud portal, add the Gateway, import the SofarSolar HYD 3...6K-EP template, and enter the inverter's IP address and the unit ID configured on the LCD.
Verify the connection by checking the live value of the power register (address 1160) in the portal: during active grid operation a non-zero signed value confirms successful polling.
Things to watch for
The gateway connects but the power register always reads zero.
Confirm the inverter is in on-grid operating mode and not in standby or EPS mode. Register 1160 returns the signed grid power only when the inverter is actively connected to the grid. Also verify the unit ID in the portal matches the Modbus address set on the inverter LCD.
Phase current registers show unexpected or erratic values.
The HYD 3...6K-EP is a single-phase inverter. Registers for phases B and C (addresses 1181, 1182, 1192, 1193) may return zero or invalid data on single-phase models. The broader template covers multi-phase variants too; check which physical model you have and expect non-zero readings only on the active phase.
All registers time out even though the logger IP is reachable.
The SofarSolar logger exposes Modbus over TCP on port 8899, not the standard port 502. Ensure your ModbusCloud Gateway is configured to connect to port 8899. If using an LSW-3 Wi-Fi stick, note that the Wi-Fi variant may not reliably forward Modbus TCP requests; the wired LSE-3 LAN stick is the recommended interface for stable polling.
The energy counter value looks implausibly large or jumps unexpectedly.
Register 1678 is a uint32 holding a cumulative energy value. The SofarSolar G3 protocol uses big-endian byte order with the high 16-bit word first in 32-bit registers. If your client swaps word order, the resulting number will be wrong by several orders of magnitude. Verify that your Modbus client reads high word first, then low word.
Want to see how it works?
