Why does the gateway connect but all register values stay zero?

The Modbus TCP interface is disabled by default on go-e chargers. You must enable it explicitly in the go-e app under Settings, Connection, Advanced Settings, and then the Modbus section. Without this step the charger will accept the TCP connection but return no data.

Multi-word registers return scrambled values. What is wrong?

go-e chargers use big-endian byte order with word swap. A firmware bug in version 60.3 reversed the byte order; this was fixed in firmware 60.4. Update the charger firmware to 60.4 or later. Confirm your Modbus client also uses big-endian word order when decoding uint32 registers.

The portal cannot reach the charger at all. What should I check?

Confirm the charger and the ModbusCloud Gateway are on the same LAN segment and that no firewall blocks TCP port 502. Also verify the unit ID is set to 1, which is the fixed device ID for all go-e chargers. A wrong unit ID returns no response even when the IP is correct.

Register IDs in other tools differ from what the template uses. Why?

go-e documents its registers with 0-based indexing. Some Modbus clients add 1 to all input-register addresses automatically. If you see an offset of exactly 1 on every register, your client is applying a 1-based offset. The addresses in this template match the go-e API v2 specification directly and should be used as-is with the ModbusCloud Gateway.

Free Modbus template: Goe Modbus

The Goe Modbus template connects go-e EV wallboxes to the ModbusCloud portal over Modbus TCP. go-e chargers are AC wallboxes designed for residential, fleet, and semi-public charging, supporting single- and three-phase operation. The template reads charger status (goe_state) and real-time active power, giving installers and building managers live visibility into charging sessions and load. Import the template once, assign the unit ID, and your portal begins logging every session automatically.

Name	Address	Function	Type	Unit	Access
goe_state Charger status: 1 ready, 2 charging, 3 waiting, 4 finished.	100	FC04	uint16		R
active_power Total active charging power currently drawn, in watts.	120	FC04	uint32	W	R