go-e APIv2 Connect
marq24/ha-goecharger-api2 · v2026.10.3
HA integration for go-eCharger series (or the compatible Fronius Wattpilot series) & go-eController communicate via WebSocket or the HTTP API v2.0. Please note, that this integration is not official and not supported by the go-e developer team. This project is not affiliated with go-e.com in any way.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
What people report
go-e chargers work over LAN or cloud API; cloud users were hit by API lockouts in 2026. CORE and PRO models work since 2025.9.0.
- Works1
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| go-e Charger CORE/PRO | Works | HTTP 400 on unsupported fields handled; works since version 2025.9.0Saved copyDescription Currently, setup of go-e CORE and PRO chargers fails in the integration. From logs, it appears that some features/states are not supported by these models. When such unsupported parameters are included in the API query, the charger responds with HTTP 400 (Bad Request) instead of 200. Notably, the API still returns all supported values in the JSON response, but the status code is 400, which causes the integration to fail. > APP-API: read_all_states failed cause: 400, message='Bad Request', … Excerpt saved from GitHub on 2026-10-23. | Issue #66 · 2025-09 | |
| Fronius Wattpilot | Partly works Local | WebSocket-only; LAN setup fails, fallback fix PR closed unmergedSaved copyProblem Fronius Wattpilot chargers cannot be added via the LAN flow. The setup always fails with "Host/IP is wrong - could not reach system", even when the WebSocket wallbox password is provided. Root cause: the Fronius firmware does not offer the local HTTP APIv2 at all, `GET http:// /api/status` is answered by the device's nginx with `502 Bad Gateway`, and `GET /` responds with `The WebSocket handshake Upgrade field is missing` (the device is WebSocket-only). Since `_test_host()` (config flow) and `read_versions()` (entry setup) exclusively use `_read_filtered_data()` (HTTP), a Wattpilot … Excerpt saved from GitHub on 2026-10-23. | PR #158 · 2026-09 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Details
| Installs (analytics) | 1,600 (0.23%) |
|---|---|
| GitHub stars | 232 |
| Latest version | 2026.10.3 (2026-10-18) |
| Set up in the UI | Yes |
| Maintainers | @marq24, @s3ppo |
| License | Apache-2.0 |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/marq24/ha-goecharger-api2
- Source code: https://github.com/marq24/ha-goecharger-api2
- Issues: https://github.com/marq24/ha-goecharger-api2/issues
- HACS: https://hacs.xyz
