go-e Charger Gemini, CORE, PRO
EV wallbox: charging power, current and energy per phase, charging state, current limit and phase switching.
The go-e Charger Gemini, CORE and PRO are wallboxes for charging electric cars at home and at work that connect to the local network. This Modbus TCP template reads charging power, current per phase, session and total energy and the charging state, and lets you set the charging current, phase switching and charging permission from ModbusCloud.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 78, read and write
- Brand
- go-e
- Key readings
- Charging power · Current per phase · Voltage per phase · Session energy · Total energy · Charging state · Error code
- Available commands
- Allow charging · Charging current · Phase switching · Force state · Energy limit · Access control
- Compatible models
- go-e Charger Gemini · go-e Charger Gemini flex · go-e Charger Gemini 2.0 · go-e Charger Gemini flex 2.0 · go-e Charger CORE · go-e Charger PRO
- Last updated
Registers (78)
78 read, 21 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| Total Power | W | Read | |||
| Power L1 | kW | Read | |||
| Power L2 | kW | Read | |||
| Power L3 | kW | Read | |||
| Current L1 | A | Read | |||
| Current L2 | A | Read | |||
| Current L3 | A | Read | |||
| Voltage L1 | V | Read | |||
| Voltage L2 | V | Read | |||
| Voltage L3 | V | Read | |||
| Voltage N | V | Read | |||
| Power Factor L1 | % | Read | |||
| Power Factor L2 | % | Read | |||
| Power Factor L3 | % | Read | |||
| Power Factor N | % | Read | |||
| Session Energy | kWh | Read | |||
| Total Energy | kWh | Read | |||
| Car State | Read | ||||
| Error | Read | ||||
| Charging Allowed | Read | ||||
| Cable Current Coding | A | Read | |||
| Adapter Input | Read | ||||
| Unlocked By RFID Card | Read | ||||
| Phases | Read | ||||
| RFID Card 1 Energy | Wh | Read | |||
| RFID Card 2 Energy | Wh | Read | |||
| RFID Card 3 Energy | Wh | Read | |||
| RFID Card 4 Energy | Wh | Read | |||
| RFID Card 5 Energy | Wh | Read | |||
| RFID Card 6 Energy | Wh | Read | |||
| RFID Card 7 Energy | Wh | Read | |||
| RFID Card 8 Energy | Wh | Read | |||
| RFID Card 9 Energy | Wh | Read | |||
| RFID Card 10 Energy | Wh | Read | |||
| Allow Charging | Read and write | ||||
| Charging Current | A | Read and write | |||
| Charging Current Saved | A | Read and write | |||
| Phase Switch Mode | Read and write | ||||
| Force State | Read and write | ||||
| Energy Limit | Wh | Read and write | |||
| Access Control | Read and write | ||||
| Maximum Current | A | Read and write | |||
| Cable Lock Mode | Read and write | ||||
| Button Current Level 1 | A | Read and write | |||
| Button Current Level 2 | A | Read and write | |||
| Button Current Level 3 | A | Read and write | |||
| Button Current Level 4 | A | Read and write | |||
| Button Current Level 5 | A | Read and write | |||
| Price Mode Minimum Hours | h | Read and write | |||
| Price Mode Ready By | Read and write | ||||
| Price Zone | Read and write | ||||
| LED Brightness | Read and write | ||||
| LED Energy Saving | Read and write | ||||
| Cloud Disabled | Read and write | ||||
| Norway Mode | Read and write | ||||
| Firmware Version | Read | ||||
| Serial Number | Read | ||||
| Hostname | Read | ||||
| MAC Address Word 1 | Read | ||||
| MAC Address Word 2 | Read | ||||
| MAC Address Word 3 | Read | ||||
| IP Address Octet 1 | Read | ||||
| IP Address Octet 2 | Read | ||||
| IP Address Octet 3 | Read | ||||
| IP Address Octet 4 | Read | ||||
| Subnet Mask Octet 1 | Read | ||||
| Subnet Mask Octet 2 | Read | ||||
| Subnet Mask Octet 3 | Read | ||||
| Subnet Mask Octet 4 | Read | ||||
| Network Gateway Octet 1 | Read | ||||
| Network Gateway Octet 2 | Read | ||||
| Network Gateway Octet 3 | Read | ||||
| Network Gateway Octet 4 | Read | ||||
| Last RFID Card Word 1 | Read | ||||
| Last RFID Card Word 2 | Read | ||||
| Last RFID Card Word 3 | Read | ||||
| Last RFID Card Word 4 | Read | ||||
| Last RFID Card Word 5 | 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
- Show charging power and current per phase next to the PV system and the energy meter on one dashboard.
- Lower the charging current from an automation when the grid connection reaches its limit, and raise it again when there is room.
- Switch the charger to one phase from the portal to charge on a small solar surplus.
- Get an email when the charger reports an error code.
- Keep a year of history of the energy per session and in total for reports per customer.
- Pause charging remotely with the force state and release it again later.
Installation
Connect the charger to the local network over Wi-Fi or, on the CORE and PRO, over LAN. On the CORE and PRO, Modbus TCP does not work over the cellular connection.
In the go-e app, open the Internet tab, then Advanced settings, and switch on Modbus at the bottom. The charger then answers on port 502.
Connect the ModbusCloud Gateway to the same network and look up the IP address of the charger in the go-e app or in the router.
In ModbusCloud, add a Modbus device with Modbus TCP, the IP address of the charger, port 502 and unit ID 1, and import this template.
Check that charging power and car state come in and match the go-e app.
Things to watch for
The Gateway gets no answer from the go-e Charger. What should I check?
Check that Modbus is switched on in the go-e app and that the Gateway and the charger are on the same network. The charger answers on port 502 with unit ID 1. A CORE or PRO that is only online over its cellular connection cannot be read over Modbus TCP, so connect it over Wi-Fi or LAN.
Power and energy values are far too high or make no sense. Why?
Firmware 60.3 sent the bytes of each value in the wrong order, and 60.4 fixed this. Update the charger. If the values stay wrong, check that the Modbus options to swap bytes and to swap registers are off on the charger.
Why does the charging current return to the old value after a restart?
The volatile charging current is not saved, and the charger falls back to the saved value at every restart. It is meant for load management that sets the current again and again. The saved charging current stays after a restart, but the charger allows about 100,000 changes, so do not write it from a frequent automation.
Can I control charging from ModbusCloud?
Yes. Charging permission, charging current, phase switching, force state, energy limit and the settings can be written. Writing is off per gateway until you request it in the portal. Read the current value first, change one setting at a time and keep the charging current between 6 and 32 A and below the maximum set on the charger.
Why does the power per phase change in steps of 100 W?
The charger gives the power per phase in steps of 0.1 kW and the total power much finer. Use the total power for an exact figure and the phase values to see how the load is spread over the phases.
More go-e templates
Want to see how it works?
