go-e · EV charger
Charger Gemini / Gemini flex / CORE / HOME+ (V3) Modbus register map
Default configuration
- Protocol
- Modbus TCP
- Port
- 502
- Unit ID
- 1
- Addressing
- 0-based
- Byte order
- Big endian
- Word order
- High word first
Register map
| Address | Count | Name | Type | Unit | Scale | Access |
|---|---|---|---|---|---|---|
| 100 | 1 | Car state 0 = unknown / charging station defective, 1 = charging station ready, no car, 2 = car is charging, 3 = waiting for car, 4 = charging finished, car still connected. | UInt16 | - | 1 | R |
| 101 | 1 | Cable ampere coding Type 2 cable coding: 13 to 32 = ampere coding, 0 = no cable. | UInt16 | A | 1 | R |
| 105 | 2 | Firmware version Firmware version as ASCII (4 bytes). | Ascii | - | 1 | R |
| 107 | 1 | Error 1 = RCCB (residual current circuit breaker), 3 = phase disturbance, 8 = no ground (ground detection), 10 and any other value = internal error. | UInt16 | - | 1 | R |
| 108 | 2 | Voltage L1 | UInt32 | V | 1 | R |
| 110 | 2 | Voltage L2 | UInt32 | V | 1 | R |
| 112 | 2 | Voltage L3 | UInt32 | V | 1 | R |
| 114 | 2 | Current L1 Raw value in 0.1 A. | UInt32 | A | 0.1 | R |
| 116 | 2 | Current L2 Raw value in 0.1 A. | UInt32 | A | 0.1 | R |
| 118 | 2 | Current L3 Raw value in 0.1 A. | UInt32 | A | 0.1 | R |
| 120 | 2 | Power total Raw value in 0.01 kW. | UInt32 | kW | 0.01 | R |
| 128 | 2 | Energy total Total charged energy in 0.1 kWh. | UInt32 | kWh | 0.1 | R |
| 132 | 2 | Energy, current charge Energy of the running charging process in deka-watt-seconds, i.e. raw x 10 Ws (100000 = 1000000 Ws = 277 Wh). | UInt32 | Ws | 10 | R |
| 144 | 2 | Voltage N | UInt32 | V | 1 | R |
| 146 | 2 | Power L1 Raw value in 0.1 kW. | UInt32 | kW | 0.1 | R |
| 148 | 2 | Power L2 Raw value in 0.1 kW. | UInt32 | kW | 0.1 | R |
| 150 | 2 | Power L3 Raw value in 0.1 kW. | UInt32 | kW | 0.1 | R |
| 152 | 2 | Power factor L1 | UInt32 | % | 1 | R |
| 154 | 2 | Power factor L2 | UInt32 | % | 1 | R |
| 156 | 2 | Power factor L3 | UInt32 | % | 1 | R |
| 158 | 2 | Power factor N | UInt32 | % | 1 | R |
| 202 | 1 | Adapter input 0 = no adapter, 1 = 16 A adapter connected. | UInt16 | - | 1 | R |
| 203 | 1 | Unlocked by Number of the RFID card that activated the current charging process. | UInt16 | - | 1 | R |
| 205 | 1 | Phases Binary flags 0b00ABCDEF: A/B/C = phase 3/2/1 before the contactor, D/E/F = phase 3/2/1 after the contactor. 0b00001000 = phase 1 available, 0b00111000 = phases 1-3 available. | Binary | - | 1 | R |
| 304 | 6 | Serial number Serial number of the charger as ASCII (12 bytes). | Ascii | - | 1 | R |
| 315 | 4 | IP address IP address, one byte per register (8 bytes). | Ascii | - | 1 | R |
Read this device live with Modbus Connect, free for Windows, macOS and Linux
Related guides
Notes
Source: go-e, "GO-E Charger Modbus TCP/IP Documentation English", version 1.0, 2020-10-01, published by the vendor as go-eCharger Modbus TCP API v1 in its own repository (https://github.com/goecharger/go-eCharger-API-v1, file "go-eCharger Modbus TCP API v1 EN.md"). The document fixes everything this seed encodes: port 502 over WLAN, unit ID 1, "the Register ID is 0-indexed" (so the numbers below are wire addresses), multi-register values are big-endian 16-bit words, input registers are read-only and holding registers are readable and writable. The API has to be enabled in the go-e app under advanced settings and needs firmware 0.40 or newer. Earlier passes recorded go-e as an HTTP-only device; the vendor Modbus TCP document above lifts that skip. Model scope follows the vendor API family and the evcc go-e-v3 template: Charger Gemini, Gemini flex, CORE, HOME+ and V3. Deliberately left out because the document's own columns cannot be paired: MAC (301-303, a 48-bit integer, and this schema has no 48-bit type), SUBNET (319-322, a 64-bit integer), HOSTNAME (310-314, five registers listed against a six-register length column) and GATEWAY (323-326, four registers against an "ascii (4 byte)" length). The register names in the table are the vendor's API keys (for example AMLERE_L2 for level 2, a typo in the document); the display names here are the same keys spelled out. The power rows are in 0.1 kW and the session energy in deka-watt-seconds, which is why the session row carries a factor of 10 and a unit of Ws instead of a kWh scale that would not be exact.