Easy Modbus
  1. Home
  2. Modbus register maps
  3. go-e
  4. go-eCharger (Modbus TCP API v1)

EV charger · Modbus register map

go-e go-eCharger (Modbus TCP API v1) Modbus register map

Updated 17 November 2026

Short answer

The go-eCharger wallbox exposes a Modbus TCP server over WLAN once API access is enabled in the app. This map covers the single-register status and control points: charging state, errors, charge permission, access mode, cable lock, current setpoints and the push-button current levels.

This page lists 24 Modbus registers for the go-e go-eCharger (Modbus TCP API v1) — 18 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from go-e’s own free documentation (linked below) and checked against it.

Manufacturer
go-e
Model
go-eCharger (Modbus TCP API v1)
Equipment type
EV charger
Registers
24 (18 writable)
Transport
Modbus TCP
Default unit ID
1
TCP port
502
Documented addressing
0-based (the number printed is the address on the wire)
Also known as
go-eCharger Modbus API v1, go-e Charger
Source document
GO-E Charger Modbus TCP/IP Documentation English · go-eCharger Modbus TCP API v1 EN, version 1.0 · rev. 2020-10-01
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: go-e go-eCharger (Modbus TCP API v1)

Integration in brief

Connect to port 502, unit 1. Read CAR_STATE (100) and ERROR (107), allow charging with ALLOW (200) and set the current with AMPERE_VOLATILE (299) for dynamic load management.

Minimum registers to map

Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.

RegisterNameTypeWhyAccess
IR 100CAR_STATEUINT16Charging stateRead
IR 107ERRORUINT16Error codeRead
HR 200ALLOWUINT16Allow chargingRead/write
HR 299AMPERE_VOLATILEUINT16Set charge current (not saved)Read/write
IR 205PHASESBITMAP16Phases availableRead

Enable Modbus control & writes

Allow API access in the go-eCharger app under Advanced Settings, then restart the charger. Needs firmware 0.40 or newer.

Byte order & addressing

Network setup

Watch out for

go-e go-eCharger (Modbus TCP API v1) Modbus registers

Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.

24 of 24 shown
go-e go-eCharger (Modbus TCP API v1) Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
IR100CAR_STATECharging state as seen on the PWM pilot.UINT16Read0 = Unknown / charging station defective; 1 = Ready, no car; 2 = Car is charging; 3 = Waiting for car; 4 = Charging finished, car still connected
IR101PP_CABLEType 2 cable current coding: 13-32 A, 0 = no cable.UINT16ARead
IR107ERRORError code.UINT16Read1 = RCCB (residual current breaker); 3 = Phase disturbance; 8 = No ground detected; 10 = Internal (others, default)
IR202ADAPTER_INPUTAdapter fitted to the charger.UINT16Read0 = No adapter; 1 = 16 A adapter
IR203UNLOCKED_BYNumber of the RFID card that started this charge.UINT16Read
IR205PHASESPhase presence before/after the contactor.BITMAP16Readbit 0 = Phase 1 after contactor; bit 1 = Phase 2 after contactor; bit 2 = Phase 3 after contactor; bit 3 = Phase 1 before contactor; bit 4 = Phase 2 before contactor; bit 5 = Phase 3 before contactor
HR200ALLOWWhether the PWM charging signal is allowed.UINT16Read/write0 = No; 1 = Yes
HR201ACCESS_STATEAccess control mode.UINT16Read/write0 = Open; 1 = RFID / app needed; 2 = Electricity price / automatic; 3 = Scheduler
HR204CABLE_LOCK_MODEUINT16Read/write0 = Lock while car is connected; 1 = Unlock automatically after charging; 2 = Always locked
HR206LED_BRIGHTNESS0 = off, 255 = maximum.UINT16Read/write
HR207LED_SAVE_ENERGYLEDs switch off automatically after 10 s when on.UINT16Read/write0 = Off; 1 = On
HR208ELECTRICITY_PRICES_HOURSMinimum hours to charge in electricity-price mode.UINT16hRead/write
HR209ELECTRICITY_PRICES_FINISHEDHour of day by which price-mode charging must be done.UINT16Read/write
HR210ELECTRICITY_PRICES_ZONEaWATTar price zone.UINT16Read/write0 = Austria; 1 = Germany
HR211AMPERE_MAXUpper limit for the current setting.UINT16ARead/write
HR212AMPERE_L1Push-button current level 1: 6-32 A, 0 = skipped.UINT16ARead/write
HR213AMPERE_L2Push-button current level 2: 6-32 A, 0 = skipped.UINT16ARead/write
HR214AMPERE_L3Push-button current level 3: 6-32 A, 0 = skipped.UINT16ARead/write
HR215AMPERE_L4Push-button current level 4: 6-32 A, 0 = skipped.UINT16ARead/write
HR216AMPERE_L5Push-button current level 5: 6-32 A, 0 = skipped.UINT16ARead/write
HR217CLOUD_DISABLEDUINT16Read/write0 = Cloud enabled; 1 = Cloud disabled
HR218NORWAY_MODEDisables ground detection; for IT networks only.UINT16Read/write0 = Off (ground detection on); 1 = On (no ground detection)
HR299AMPERE_VOLATILECharge current 6-32 A, not saved; use for energy management.UINT16ARead/write
HR300AMPERE_EEPROMCharge current 6-32 A, saved to EEPROM (about 100,000 writes).UINT16ARead/write

Notes on this map

Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.

Questions about the go-e go-eCharger (Modbus TCP API v1)

What Modbus registers does the go-e go-eCharger (Modbus TCP API v1) have?

This map lists 24 registers: 6 input registers, 18 holding registers. 18 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the go-e go-eCharger (Modbus TCP API v1) Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers 0-based (the number printed is the address on the wire). Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. The document says register IDs are 0-indexed and some clients must add 1. The table numbers are wire addresses: AMPERE_VOLATILE 299 is request address 299 (holding register 40300 in 1-based tools).

What are the minimum Modbus registers to integrate the go-e go-eCharger (Modbus TCP API v1)?

Start with IR 100 CAR_STATE (Charging state); IR 107 ERROR (Error code); HR 200 ALLOW (Allow charging); HR 299 AMPERE_VOLATILE (Set charge current (not saved)); IR 205 PHASES (Phases available).

How do I enable Modbus control of the go-e go-eCharger (Modbus TCP API v1)?

Allow API access in the go-eCharger app under Advanced Settings, then restart the charger. Needs firmware 0.40 or newer.

Where is the official go-e go-eCharger (Modbus TCP API v1) Modbus documentation?

The source is GO-E Charger Modbus TCP/IP Documentation English (go-eCharger Modbus TCP API v1 EN, version 1.0), revision 2020-10-01, published free by go-e at https://raw.githubusercontent.com/goecharger/go-eCharger-API-v1/master/go-eCharger%20Modbus%20TCP%20API%20v1%20EN.md.

More go-e Modbus register maps

Source: GO-E Charger Modbus TCP/IP Documentation English · go-eCharger Modbus TCP API v1 EN, version 1.0 · rev. 2020-10-01. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.