go-e go-eCharger Home+ Modbus TCP template

go-eCharger Home+

Controls and monitors go-eCharger Home+ EV wallbox charging sessions via Modbus TCP.

This ModbusCloud template reads and controls a go-eCharger Home+ EV wallbox over Modbus TCP. It reads charging state, total and session energy, total power, per-phase current, and error code, and lets you start or stop charging, change the ampere limit, and switch the access state. It is aimed at installers who want a live dashboard of charging sessions and programmatic control for load balancing or tariff optimisation.

Protocol
Modbus TCP
Connection
Ethernet, Modbus TCP
Registers
12, read and write
Brand
go-e
Key readings
Car state · Error code · Total energy · Total power · Session energy charged · Current L1 to L3
Available commands
Allow charging · Ampere limit (volatile) · Access state
Compatible models
go-eCharger HOME+
Last updated

Registers (12)

9 read, 3 write

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
CAR_STATERead
ERRORRead
ENERGY_TOTALWhRead
POWER_TOTALWRead
ENERGY_CHARGEkWRead
AMP_L1ARead
AMP_L2ARead
AMP_L3ARead
ADAPTER_INPUTRead
ALLOWWrite
AMPERE_VOLATILEAWrite
ACCESS_STATEWrite

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.

Number of installations (optional)

Use cases

  • Build a customer self-service dashboard showing current charging state, session energy delivered, and charging cost estimate per session.
  • Throttle the wallbox current limit when total building demand approaches the grid connection capacity.
  • Log total energy per month for employer EV expense reporting or home charging reimbursement.
  • Automatically start charging only during cheap dynamic tariff windows using a ModbusCloud automation rule.
  • Alert the installer when the error code becomes non-zero, including the code in the message for quick diagnosis.

Installation

  1. In the go-eCharger app, enable Modbus TCP under the advanced settings menu.

  2. Note the wallbox IP and set a DHCP reservation so it stays stable after router reboots.

  3. In ModbusCloud, add a Modbus TCP device at the wallbox IP, port 502, slave ID 1.

  4. Import the go-eCharger Home+ template. Readings start updating within one polling cycle.

  5. Test a write, for example setting the ampere limit, to confirm the device accepts control commands.

Things to watch for

ENERGY_CHARGE says kW but looks like kWh. Is the template wrong?

The go-e register documentation labels this as kW but in practice the value behaves like kWh (energy, not power). The template preserves the actual behaviour. Label your dashboard widget as kWh to avoid confusion.

Ampere limit writes work but reset when the wallbox reboots. Is that normal?

Yes. The Modbus ampere limit is volatile by design for safety. If you need the limit to persist across reboots, write it once per boot from a ModbusCloud automation, or use the go-eCharger app to set the non-volatile default.

Want to see how it works?

Electrician working in an open distribution board