- Home
- Modbus register maps
- go-e
- go-eCharger (Modbus TCP, API v2)
EV charger · Modbus register map
go-e go-eCharger (Modbus TCP, API v2) Modbus register map
Updated 17 November 2026
go-eCharger wallboxes on the v2 API expose a Modbus TCP server on port 502 once it is enabled in the app or over the HTTP API. This map covers the single-register status and control points: charging state, errors, charge permission, access mode, cable lock, current setpoints, push-button current levels, phase switch mode and force state.
This page lists 23 Modbus registers for the go-e go-eCharger (Modbus TCP, API v2) — 20 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 v2)
- Equipment type
- EV charger
- Registers
- 23 (20 writable)
- Transport
- Modbus TCP
- Default unit ID
- Not stated
- TCP port
- 502
- Documented addressing
- Modicon 3xxxx/4xxxx (drop the prefix, subtract 1)
- Also known as
- go-eCharger Modbus API v2, go-e Charger
Integration notes: go-e go-eCharger (Modbus TCP, API v2)
Enable Modbus, then connect to TCP port 502. Read CAR_STATE (100) and ERROR (107), allow charging with ALLOW (200) and set the current with AMPERE_VOLATILE (299) for dynamic load management, writing with function 16.
Minimum registers to map
Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.
| Register | Name | Type | Why | Access |
|---|---|---|---|---|
| IR 100 | CAR_STATE | UINT16 | Charging state | Read |
| IR 107 | ERROR | UINT16 | Error code | Read |
| HR 200 | ALLOW | UINT16 | Allow charging | Read/write |
| HR 299 | AMPERE_VOLATILE | UINT16 | Set charge current (not saved) | Read/write |
| HR 337 | FORCE_STATE | UINT16 | Force charging on/off | Read/write |
Enable Modbus control & writes
Turn on Modbus in the app (Internet tab > Advanced Settings > Modbus) or with the HTTP API key men=true, e.g. /api/set?men=true. The port is set with msp (reboot needed).
Byte order & addressing
- Writes must use function 16 even for one register; function 06 is not implemented.
- Word and byte order of multi-register values follow the msr/msb settings.
Network setup
- Enable Modbus in the app or via the HTTP API (men=true).
- Default port 502 after enabling; change with msp and reboot.
Watch out for
- Use AMPERE_VOLATILE (299) for frequent changes; AMPERE_EEPROM (300) is stored in EEPROM with roughly 100,000 write cycles.
- AMPERE_VOLATILE resets to the stored EEPROM value at the next boot.
go-e go-eCharger (Modbus TCP, API v2) 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.
| Table | Address | Name | Description | Type | Order | Scale | Units | Access | Values / bits |
|---|---|---|---|---|---|---|---|---|---|
| IR | 100doc 30101 (100) | CAR_STATE | Charging state as seen on the PWM pilot. | UINT16 | Read | 0 = Unknown / charging station defective; 1 = Ready, no car; 2 = Car is charging; 3 = Waiting for car; 4 = Charging finished, car still connected | |||
| IR | 101doc 30102 (101) | PP_CABLE | Type 2 cable current coding: 13-32 A, 0 = no cable. | UINT16 | A | Read | |||
| IR | 107doc 30108 (107) | ERROR | Error code. | UINT16 | Read | 1 = RCCB (residual current breaker); 3 = Phase disturbance; 8 = No ground detected; 10 = Internal (others, default) | |||
| HR | 200doc 40201 (200) | ALLOW | Whether the PWM charging signal is allowed. | UINT16 | Read/write | 0 = No; 1 = Yes | |||
| HR | 201doc 40202 (201) | ACCESS_STATE | Access control mode. | UINT16 | Read/write | 0 = Open; 1 = RFID / app needed; 2 = Electricity price / automatic; 3 = Scheduler | |||
| HR | 204doc 40205 (204) | CABLE_LOCK_MODE | UINT16 | Read/write | 0 = Lock while car is connected; 1 = Unlock automatically after charging; 2 = Always locked | ||||
| HR | 206doc 40207 (206) | LED_BRIGHTNESS | 0 = off, 255 = maximum. | UINT16 | Read/write | ||||
| HR | 207doc 40208 (207) | LED_SAVE_ENERGY | LEDs switch off automatically after 10 s when on. | UINT16 | Read/write | 0 = Off; 1 = On | |||
| HR | 208doc 40209 (208) | ELECTRICITY_PRICES_HOURS | Minimum hours to charge in electricity-price mode. | UINT16 | h | Read/write | |||
| HR | 209doc 40210 (209) | ELECTRICITY_PRICES_FINISHED | Hour of day by which price-mode charging must be done. | UINT16 | Read/write | ||||
| HR | 210doc 40211 (210) | ELECTRICITY_PRICES_ZONE | aWATTar price zone. | UINT16 | Read/write | 0 = Austria; 1 = Germany | |||
| HR | 211doc 40212 (211) | AMPERE_MAX | Upper limit for the current setting. | UINT16 | A | Read/write | |||
| HR | 212doc 40213 (212) | AMPERE_L1 | Push-button current level 1: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 213doc 40214 (213) | AMPERE_L2 | Push-button current level 2: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 214doc 40215 (214) | AMPERE_L3 | Push-button current level 3: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 215doc 40216 (215) | AMPERE_L4 | Push-button current level 4: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 216doc 40217 (216) | AMPERE_L5 | Push-button current level 5: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 217doc 40218 (217) | CLOUD_DISABLED | UINT16 | Read/write | 0 = Cloud enabled; 1 = Cloud disabled | ||||
| HR | 218doc 40219 (218) | NORWAY_MODE | Disables ground detection; for IT networks only. | UINT16 | Read/write | 0 = Off (ground detection on); 1 = On (no ground detection) | |||
| HR | 299doc 40300 (299) | AMPERE_VOLATILE | Charge current 6-32 A, not saved; use for energy management. | UINT16 | A | Read/write | |||
| HR | 300doc 40301 (300) | AMPERE_EEPROM | Charge current 6-32 A, saved to EEPROM (about 100,000 writes). | UINT16 | A | Read/write | |||
| HR | 332doc 40333 (332) | PHASE_SWITCH_MODE | Same as API key psm; accepts 0, 1 or 2 (firmware 55.5+). | UINT16 | Read/write | ||||
| HR | 337doc 40338 (337) | FORCE_STATE | Same as API key frc (firmware 55.6+). | UINT16 | Read/write | 0 = Neutral; 1 = Off; 2 = On |
Notes on this map
- Official go-e documentation hosted in the goecharger GitHub organisation.
- Left out: all 32-bit and 64-bit values (voltages, currents, power, energy, power factor, ENERGY_LIMIT, RFID card energies). Their word order depends on the charger's 'modbus slave swap registers/bytes' settings (msr/msb) and no default is stated.
- Left out: input rows printed only as a bare number (132, 144-159, 200-205, 301-322) because the table does not mark which convention they use, and ASCII/binary blocks (firmware version, MAC, serial, host name, network, RFID).
- The source notes that byte order was swapped in firmware 60.3 and fixed in 60.4.
- API keys psm (phase switch mode) and frc (force state) are described in the repository's API_KEYS_FIRMWARE/apikeys-en.md; only frc's values are spelled out there.
- The v2 Modbus page does not state a unit ID; the older v1 document gives unit 1.
- The v2 Modbus page does not list which charger models it covers.
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 v2)
What Modbus registers does the go-e go-eCharger (Modbus TCP, API v2) have?
This map lists 23 registers: 3 input registers, 20 holding registers. 20 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 v2) Modbus addresses 0-based or 1-based?
The manufacturer's document numbers registers Modicon 3xxxx/4xxxx (drop the prefix, subtract 1). 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 table prints each register as Modicon number plus wire address, e.g. '40300 (299)' and '30101 (100)'. The number in brackets goes in the request PDU.
What are the minimum Modbus registers to integrate the go-e go-eCharger (Modbus TCP, API v2)?
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)); HR 337 FORCE_STATE (Force charging on/off).
How do I enable Modbus control of the go-e go-eCharger (Modbus TCP, API v2)?
Turn on Modbus in the app (Internet tab > Advanced Settings > Modbus) or with the HTTP API key men=true, e.g. /api/set?men=true. The port is set with msp (reboot needed).
Where is the official go-e go-eCharger (Modbus TCP, API v2) Modbus documentation?
The source is go-eCharger API v2 - Modbus (modbus-en.md) (go-eCharger-API-v2 modbus-en.md (main branch)), published free by go-e at https://raw.githubusercontent.com/goecharger/go-eCharger-API-v2/main/modbus-en.md.
More go-e Modbus register maps
Source: go-eCharger API v2 - Modbus (modbus-en.md) · go-eCharger-API-v2 modbus-en.md (main branch). Register numbers, types, scaling and units are reproduced as published; descriptions are our own.