- Home
- Modbus register maps
- go-e
- 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
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
Integration notes: go-e go-eCharger (Modbus TCP API v1)
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.
| 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 |
| IR 205 | PHASES | BITMAP16 | Phases available | Read |
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
- Addresses are 0-based; 1-based tools need +1.
- Unit ID is 1 and the port is 502 over WLAN.
Network setup
- Enable API access in the app (Advanced Settings) and reboot the charger.
- Connect to the charger IP on TCP port 502, unit ID 1.
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 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.
| Table | Address | Name | Description | Type | Order | Scale | Units | Access | Values / bits |
|---|---|---|---|---|---|---|---|---|---|
| IR | 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 | 101 | PP_CABLE | Type 2 cable current coding: 13-32 A, 0 = no cable. | UINT16 | A | Read | |||
| IR | 107 | ERROR | Error code. | UINT16 | Read | 1 = RCCB (residual current breaker); 3 = Phase disturbance; 8 = No ground detected; 10 = Internal (others, default) | |||
| IR | 202 | ADAPTER_INPUT | Adapter fitted to the charger. | UINT16 | Read | 0 = No adapter; 1 = 16 A adapter | |||
| IR | 203 | UNLOCKED_BY | Number of the RFID card that started this charge. | UINT16 | Read | ||||
| IR | 205 | PHASES | Phase presence before/after the contactor. | BITMAP16 | Read | bit 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 | |||
| HR | 200 | ALLOW | Whether the PWM charging signal is allowed. | UINT16 | Read/write | 0 = No; 1 = Yes | |||
| HR | 201 | ACCESS_STATE | Access control mode. | UINT16 | Read/write | 0 = Open; 1 = RFID / app needed; 2 = Electricity price / automatic; 3 = Scheduler | |||
| HR | 204 | CABLE_LOCK_MODE | UINT16 | Read/write | 0 = Lock while car is connected; 1 = Unlock automatically after charging; 2 = Always locked | ||||
| HR | 206 | LED_BRIGHTNESS | 0 = off, 255 = maximum. | UINT16 | Read/write | ||||
| HR | 207 | LED_SAVE_ENERGY | LEDs switch off automatically after 10 s when on. | UINT16 | Read/write | 0 = Off; 1 = On | |||
| HR | 208 | ELECTRICITY_PRICES_HOURS | Minimum hours to charge in electricity-price mode. | UINT16 | h | Read/write | |||
| HR | 209 | ELECTRICITY_PRICES_FINISHED | Hour of day by which price-mode charging must be done. | UINT16 | Read/write | ||||
| HR | 210 | ELECTRICITY_PRICES_ZONE | aWATTar price zone. | UINT16 | Read/write | 0 = Austria; 1 = Germany | |||
| HR | 211 | AMPERE_MAX | Upper limit for the current setting. | UINT16 | A | Read/write | |||
| HR | 212 | AMPERE_L1 | Push-button current level 1: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 213 | AMPERE_L2 | Push-button current level 2: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 214 | AMPERE_L3 | Push-button current level 3: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 215 | AMPERE_L4 | Push-button current level 4: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 216 | AMPERE_L5 | Push-button current level 5: 6-32 A, 0 = skipped. | UINT16 | A | Read/write | |||
| HR | 217 | CLOUD_DISABLED | UINT16 | Read/write | 0 = Cloud enabled; 1 = Cloud disabled | ||||
| HR | 218 | NORWAY_MODE | Disables ground detection; for IT networks only. | UINT16 | Read/write | 0 = Off (ground detection on); 1 = On (no ground detection) | |||
| HR | 299 | AMPERE_VOLATILE | Charge current 6-32 A, not saved; use for energy management. | UINT16 | A | Read/write | |||
| HR | 300 | AMPERE_EEPROM | Charge current 6-32 A, saved to EEPROM (about 100,000 writes). | UINT16 | A | Read/write |
Notes on this map
- The v1 document does not name which charger hardware generations it covers; check the API version against your charger's firmware.
- Official go-e documentation hosted in the goecharger GitHub organisation.
- Left out: all 32-bit values (voltages, currents, power, energy, power factor). The document only says the 16-bit registers are big-endian and does not state which register of a pair holds the high word, so the word order is not established.
- Left out: firmware version, MAC, serial number, host name and network addresses (ASCII/binary blocks).
- The source spells register 213 'AMLERE_L2'; it is listed here as AMPERE_L2.
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.