go-e APIv2 Connect for Home Assistant (Marketplace integration)

Installs: 1.6k sharing analytics
GitHub stars: 233
Connection: Works locally
Upkeep: Updated in the last 6 months
Version: 2026.10.7, October 25, 2026
Category: Energy, EV charging
Kind: Marketplace integration
Brand: go-e
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: goecharger_api2
Source: github.com/marq24/ha-goecharger-api2
Issues: Report an issue

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

Screenshots From the README of marq24/ha-goecharger-api2.

About

go-e APIv2 Connect is an integration that links go-eCharger wallboxes and go-eController units to Home Assistant. It communicates locally through a WebSocket connection or the HTTP API v2, and it also covers wallboxes built on go-eCharger hardware, such as the Fronius Wattpilot. It adds sensors, binary sensors, numbers, selects, switches and buttons for reading status and changing wallbox settings. Charging can be stopped for five minutes through an action, and another action sends PV data to the wallbox so charging can follow solar surplus without extra hardware. With a WebSocket password set, data updates as soon as something changes, and an option limits updates to the polling interval to protect the database. Setup runs in the UI over the local network or the cloud.

Automatic summary of the README and code of marq24/ha-goecharger-api2. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

Works locally Talks to your devices on your own network. No vendor cloud in between.
From the Marketplace Installed through the Marketplace, formerly HACS.
Actively maintained Its author released or pushed a change in the last six months.

Provides

Switches
Sensors

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

Connect

Select LAN(Local Network) or WAN(Cloud/Internet)

User lan

Integration type: Charger or Controller?
Host or IP of your go-eCharger WallboxAdditionally you can include the prefix 'https://', if this is required
Local WebSocket Wallbox password (Optional)Providing the Password is optional. When you specify one, the integration will make use of the websocket communication. This makes the polling interval obsolete, and you will get the latest data in HA as soon as something changes. This includes any changes in the wallbox configuration.
Polling Interval in seconds [min: 5sec]
Apply 'Polling Interval' also to WebSocket updatesIf you have specified a password, the sensors in Home Assistant will be updated immediately when new data arrives via the WebSocket connection. This can lead to some sensors being updated very frequently and potentially overloading your HA database. If you enable this option, the sensors will only be updated at the configured update interval.
Apply 11kW limit (for 22kW variants only) - will restrict all relevant settings to a max of 16A (instead of 32A)

User wan

Integration type: Charger or Controller?
Your go-eCharger Wallbox Serial number
Your go-eCharger Cloud API-KeyYou can find the Cloud API-Key in the go-eApp under Settings -> APIv2 -> Cloud API-Key
Cloud WebSocket Wallbox password (Optional)Providing the Password is optional. When you specify one, the integration will make use of the websocket communication. This makes the polling interval obsolete, and you will get the latest data in HA as soon as something changes. This includes any changes in the wallbox configuration.
Polling Interval in seconds [min: 30sec]
Apply 'Polling Interval' also to WebSocket updatesIf you have specified a password, the sensors in Home Assistant will be updated immediately when new data arrives via the WebSocket connection. This can lead to some sensors being updated very frequently and potentially overloading your HA database. If you enable this option, the sensors will only be updated at the configured update interval.
Apply 11kW limit (for 22kW variants only) - will restrict all relevant settings to a max of 16A (instead of 32A)

Texts from the code of marq24/ha-goecharger-api2.

Entities

Binary sensorsCar connected, Phase L1 after contactor, Phase L2 after contactor, Phase L3 after contactor, Phase L1 before contactor, Phase L2 before contactor, Phase L3 before contactor, 16A adapter used, Charging allowed, energy set kwh (only stored for app), Force single phase, Test charging finished, and 4 more
ButtonsRestart go-e device, Read Configuration, Request data sync
NumbersMaximum current limit, Requested current, Automatic stop energy, Automatic stop time, Awattar maximum price threshold, Consumption per 100 km, Charging energy limit, Min charge time, Starting power, LED brightness, Load-Management fallback current, Load-Management priority, and 24 more
SelectsVehicle compatibility mode, Button: Allow Current change, Button: Allow Start charging (double press), Force state, logic mode, Load-Management Mode, Phase Switch-Mode, Timezone daylight-saving Mode, Authorize Loading, Cable unlock Mode, Assign phase Internal 1, and 10 more
SensorsVoltage L1, Voltage L2, Voltage L3, Voltage N, Current L1, Current L2, Current L3, Power L1, Power L2, Power L3, Power N, and 164 more
SwitchesAllow Charge Pause (car compatibility), Card Authorization required, Automatic Stop remain in Awattar, Use Awattar (Charge when price is low), Controller-Scan always active, Cloud WebSocket enabled, Energy set kWh (only stored for app), Use PV surplus, Zero Feed-in, HTTP STA authentication, Load-Management enabled, and 17 more

Actions

Send PV data to Wallbox (to allow charging with PV surplus)This is a simple proxy service so that we can configure the automation a bit easierFields: Specify the go-eCharger, Power from/to grid (in Watt), Power from PV (in Watt), Power from/to battery (in Watt)
Force changing-OFF (for 5 minutes)Will ensure that the go-eCharger will stop charging. After 5 minutes the charger will return to default modeFields: Specify the go-eCharger

From the README

Support for all go-eCharger Wallboxes & go-eController's supporting the APIv2 or a WebSocket connection. This also included other branded Wallboxes that are based on the go-eCharger hardware (like the Fronius Wattpilot) — as long as they support the WebSocket or HTTP APIv2 connection.

From the README of marq24/ha-goecharger-api2, Apache License 2.0. Shortened.