Solar-Log Gateways & PV inverters
| Device Type | Modbus TCP (Ethernet) | RS485 |
|---|---|---|
| Solar-Log 400e Gateway | ✅ | ❌ |
Prerequisite: the Solar-Log 400e is powered and connected to the local network via Ethernet (DHCP by default).
Find the IP address
Use your router’s DHCP list or a network scanner to locate the
Solar-Log 400e on port 80.
Verify local API
Open http://<IP-address>/pc.js?min0 in a browser.
A plain-text JavaScript file should appear – this means the local API is
enabled.
Add the device in Sofar
(Optional) Static IP
For stable operation, reserve the IP in your DHCP server or configure a
static address in the Solar-Log web UI (Settings → Network).
| Key | Description | Unit |
|---|---|---|
actualPowerTot_W | Instantaneous AC power of the PV plant | W |
producedEnergyDeltaTot_Wh | Energy produced since previous read-out¹ | Wh |
importedEnergyDeltaTot_Wh | Imported energy (if the gateway measures it) | Wh |
exportedEnergyDeltaTot_Wh | Exported energy (feed-in) | Wh |
¹ The driver integrates actualPowerTot_W over time when absolute kWh
counters are not available.
No data / status 302 – check that /pc.js?min0 returns HTTP 200 and
contains the variables Serialnr, Pac, SLTyp, WRTyp.
A redirect or login page indicates the local API is disabled.
Power always zero – firmware < 2.1 may report Pac=0.
Update to a recent firmware from the Solar-Log support portal.
Multiple gateways – be sure each Solar-Log has a unique hostname or static IP to avoid discovery conflicts.