The Gateway connects but both registers return no value. What now?

Verify that the Modbus-API Controller is active in OpenEMS Edge and that the _sum component is listed in its export configuration. If the controller is disabled or the component is not exported, the address block containing registers 315 and 359 will not exist and all reads will return exceptions.

Register 315 reads a plausible value but register 359 is always zero or NaN.

Address 359 is a float64 spanning four consecutive holding registers (FC3). Some Modbus masters default to reading only two registers for any address. Confirm the ModbusCloud template is configured with type float64, which instructs the Gateway to request all four registers in a single transaction. A partial read will produce an invalid value.

I get a connection refused error on port 502. How do I fix it?

The OpenEMS Edge Modbus-API Controller must be running and bound to the Edge device's network interface. Check that the controller is enabled in the OpenEMS configuration, that no local firewall or router ACL is blocking port 502, and that you are targeting the correct IP address of the Edge host, not a gateway or NAT address.

After an OpenEMS Edge firmware update, my register values shifted or disappeared.

The OpenEMS Modbus-API generates a dynamic register table that depends on which components are configured and in what order. A firmware update or component reconfiguration can shift block offsets. Re-download the System Profile Excel from the OpenEMS UI to confirm that addresses 315 and 359 still map to the expected grid power and energy channels in your updated installation.

Free Modbus template: OpenEMS Modbus-API (grid)

The OpenEMS Modbus-API is a software interface built into the OpenEMS Edge energy management platform. Configured as a grid meter component, it exposes the grid connection point's real-time data over Modbus TCP on port 502. This template reads two key channels: instantaneous grid active power at address 315 and cumulative grid energy at address 359. Both are floating-point values polled directly from the OpenEMS _sum component block. Connecting the ModbusCloud Gateway to any OpenEMS Edge installation running the Modbus-API Controller gives installers continuous grid visibility inside the ModbusCloud portal without additional hardware.

Name	Address	Function	Type	Unit	Access
power Instantaneous grid active power in watts, positive = import, negative = export.	315	FC04	float32	W	R
energy Cumulative net energy exchanged with the grid, in watt-hours.	359	FC03	float64	Wh	R

OpenEMS Modbus-API (grid)

Overview

Use cases

Installation

Things to watch for

Registers (2)

Working with Modbus in your projects?

More OpenEMS templates

OpenEMS Modbus-API (battery)

OpenEMS Modbus-API (pv)

More TCP templates

Domekt R 400 V

Fronius - Modbus TCP

NIBE Nibe S-Series (SG Ready)

SunSpec Model 709 — DER Trip LF

Victron Meter AcOut

FoxESS Avocado (grid)