Goe Modbus
The Goe Modbus template connects go-e EV wallboxes to the ModbusCloud portal over Modbus TCP. go-e chargers are AC wallboxes designed for residential, fleet, and semi-public charging, supporting single- and three-phase operation. The template reads charger status (goe_state) and real-time active power, giving installers and building managers live visibility into charging sessions and load. Import the template once, assign the unit ID, and your portal begins logging every session automatically.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 2, read only
- Brand
- Goe
- Last updated
Registers (2)
2 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| goe_state | Read | ||||
| active_power | W | Read |
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.
Use cases
- Monitor active charging power to verify load stays within your site's contracted grid capacity.
- Track charger status transitions to confirm sessions start and stop as expected each day.
- Alert on goe_state value 0 to detect a defective or faulted wallbox before a driver notices.
- Compare active power readings across multiple go-e units on the same site to identify imbalanced loads.
- Report daily energy consumption per wallbox by logging active power over time in the ModbusCloud portal.
Installation
Enable Modbus TCP on the go-e charger: open the go-e app, go to Settings, select Connection, then Advanced Settings, and activate the Modbus option at the bottom of the screen.
Connect the go-e charger to the same local Ethernet or Wi-Fi network as the ModbusCloud Gateway, and note the charger's IP address. The charger listens on TCP port 502.
In your ModbusCloud portal, add the ModbusCloud Gateway, import the Goe Modbus template, enter the charger's IP address, and set the unit ID to 1.
Spot-check the connection by verifying that the goe_state register returns a value between 1 and 4. A value of 1 confirms the charger is reachable and ready.
Things to watch for
Why does the gateway connect but all register values stay zero?
The Modbus TCP interface is disabled by default on go-e chargers. You must enable it explicitly in the go-e app under Settings, Connection, Advanced Settings, and then the Modbus section. Without this step the charger will accept the TCP connection but return no data.
Multi-word registers return scrambled values. What is wrong?
go-e chargers use big-endian byte order with word swap. A firmware bug in version 60.3 reversed the byte order; this was fixed in firmware 60.4. Update the charger firmware to 60.4 or later. Confirm your Modbus client also uses big-endian word order when decoding uint32 registers.
The portal cannot reach the charger at all. What should I check?
Confirm the charger and the ModbusCloud Gateway are on the same LAN segment and that no firewall blocks TCP port 502. Also verify the unit ID is set to 1, which is the fixed device ID for all go-e chargers. A wrong unit ID returns no response even when the IP is correct.
Register IDs in other tools differ from what the template uses. Why?
go-e documents its registers with 0-based indexing. Some Modbus clients add 1 to all input-register addresses automatically. If you see an offset of exactly 1 on every register, your client is applying a 1-based offset. The addresses in this template match the go-e API v2 specification directly and should be used as-is with the ModbusCloud Gateway.
Want to see how it works?
