
The go-e Gemini flex is an Austrian-made EV wallbox available in 11 kW (16 A) and 22 kW (32 A) variants, with a newer Gemini flex 2.0 model featuring integrated 4G LTE. TapHome communicates with the charger over its local HTTP API v2 on Wi-Fi — no cloud connection is required. The API must be explicitly enabled in the go-e app before TapHome can connect.
The template provides charger status monitoring, charging current and mode control, phase switching, per-phase voltage and current readings, and write-only inputs for external PV and grid power data to enable surplus charging.
Configuration
Enabling the HTTP API
The local HTTP API v2 is disabled by default. To enable it:
- Connect to the go-e Charger via the go-e app (available for iOS and Android)
- Navigate to Settings > Connection > API Settings
- Enable “Allow access to local HTTP API vX”
Once enabled, the charger responds to HTTP requests on port 80. No authentication is required — access is controlled solely by this toggle.
Network setup
The go-e Gemini flex connects via Wi-Fi (802.11b/g/n, 2.4 GHz only). There is no wired Ethernet port. During TapHome template import, enter the charger’s IP address.
The go-e Charger does not support mDNS discovery. To prevent connectivity issues after a DHCP renewal, configure a static IP address or a DHCP reservation on your router for the charger’s MAC address.
The charger can operate in hotspot mode (direct connection) or join an existing Wi-Fi network. For TapHome integration, the charger must be on the same network as the TapHome CCU.
Device capabilities
Charger status
The Charger Status device reports the current connection and charging state as a read-only multi-value indicator. The API key car returns one of five states: Failure (0), Available (1), Charging (2), Preparing (3), or Finished (4). This allows TapHome automations to trigger based on whether a vehicle is connected, actively charging, or has completed a session.
Charging current and mode control
Two controllable devices manage how the charger operates:
Charging Current — selects the requested charging current from six discrete values: 6, 8, 10, 12, 14, and 16 A. The template maps these to switch positions 0–5 using the formula
amp/2 - 3for reading and(position + 3) × 2for writing. Values are sent to the charger viaapi/set?amp={value}.Charging Mode — selects the charging logic: Basic (default continuous charging), Eco (price-optimized via Awattar tariff), or Daily trip (automatic stop after reaching a target). The API uses values 3, 4, and 5 respectively; the template maps these to positions 0, 1, and 2.
The Charging Current selector maps only six values (6–16 A in 2 A steps). The 22 kW variant of the Gemini flex supports up to 32 A, but values above 16 A are not covered by this template. To use higher currents, the
ampAPI key can be set directly outside the template.
Phase switching
The Phase Switching device controls how many phases the charger uses: Automatic (0), 1-Phase (1), or 3-Phase (2). The go-e Charger supports switching phases even during an active charging session. In Automatic mode, the charger selects the optimal phase configuration based on available power.
Energy monitoring
The template reads per-phase voltage and current from the charger’s nrg energy array, which contains 16 values updated every poll cycle:
| Device | Source | Unit |
|---|---|---|
| L1 Voltage | nrg[0] | V |
| L2 Voltage | nrg[1] | V |
| L3 Voltage | nrg[2] | V |
| L1 Current | nrg[5] | A |
| L2 Current | nrg[6] | A |
| L3 Current | nrg[7] | A |
| Current Consumption | nrg[12] | W |
The Current Consumption device reports total active charging power in watts. All energy values are read-only.
PV surplus charging inputs
Two write-only devices allow TapHome to feed external energy data into the charger for surplus charging calculations:
- Power to Grid — sends the current grid export/import power (in kW, converted to W by multiplying by 1000) via
api/set?ids={"pGrid":value} - PV Power — sends the current photovoltaic production (in kW, converted to W by multiplying by 1000) via
api/set?ids={"pPv":value}
These devices do not read data from the charger. The go-e Charger itself does not measure grid or PV power — it relies on external sources to provide this information. In a typical TapHome setup, values from a separate energy meter or solar inverter (also integrated into TapHome) are forwarded to the charger via these write-only devices, enabling the Eco charging mode to optimize for self-consumption.
To use PV surplus charging, set the Charging Mode to Eco, then use TapHome automations to periodically write current grid power and PV production values to the Power to Grid and PV Power devices. The charger will adjust its charging current automatically based on the available surplus.
Additional capabilities
The go-e Charger API v2 exposes additional data not currently mapped in the template: per-phase power (W) and power factor, neutral voltage, total energy consumed (eto in Wh), per-session energy (wh), error state codes, cable current limit, temperature sensors, grid frequency, force charge state control, energy limit settings, and minimum/maximum ampere configuration. These can be added in a future template update.
Troubleshooting
Device not responding
- Verify the charger is connected to Wi-Fi and has a valid IP address — check the go-e app under Settings > Connection
- Confirm the HTTP API is enabled (Settings > Connection > API Settings)
- Open
http://{charger-ip}/api/statusin a browser — if it responds with JSON, the API is reachable - Check that TapHome CCU and the charger are on the same network / VLAN
Charging current not changing
- The template only maps six values (6, 8, 10, 12, 14, 16 A). If the charger shows a different value (e.g., 20 A set via the app), TapHome will display the nearest mapped position
- Verify the charger firmware is 051.4 or newer — older firmware uses a different filter syntax that may cause parsing issues
PV surplus charging not working
- Confirm the Charging Mode is set to Eco — surplus logic only activates in this mode
- Verify that Power to Grid and PV Power values are being written regularly (at least every 30 seconds)
- Check that the values are in kW (the template converts to W automatically)
- Open
http://{charger-ip}/api/status?filter=pgrid,ppvto verify the charger is receiving the values
The
eto(total energy) API key is included in the status filter but is not exposed as a device in the template. The total energy value is fetched but unused.