go-eCharger
cathiele/homeassistant-goecharger · v0.27.0
Home Assistant custom_component for controlling the go-eCharger EV-Charger
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 | |
sensor | Sensor (temperature, humidity, air quality…) |
What people report
Works locally with go-eCharger hardware that offers API v1; newer API v2 chargers are not supported because the maintainer has none to test.
- Works2
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| go-eCharger (older model, local API) | Works Local | Enable API v1 and enter the charger IP; no cloud neededSaved copyHoi Carsten or someone who can help me, the cloud of go-e is not reliable and therefor I have problems with some automations. I activated the local mqtt broker but it seem that I made a mistake or something else.. I activated the mqtt with the app ( ich habe ich eine alte go-e) and and and the error (cloud is down) What I have to change that the local access via the local mqtt broker works? Many thanks in advance Excerpt saved from GitHub on 2026-10-23. | Discussion #85 · 2023-07 | |
| go-eCharger V1 | Works Local | Broke on HA 2025.6; fixed in 0.27.0 (firmware 0.42)Saved copyIt looks like the integration no longer works with the june version. Is there a fix for this? Versions 2025.6.b4 - home-assistant: OS - Operating System: 15.2 - Charger Hardware: V1 - Charger Firmware Version: 0.42 - Plugin Version: 0.26 Excerpt saved from GitHub on 2026-10-23. | Issue #108 · 2025-06 | |
| go-eCharger HW V3 / API v2 | Requested | API v2 not supported; maintainer has no v2 charger and wants a PRSaved copyMy go-e offers a new API v2 (/api/status). It would be great to use that API instead of the v1 version (/status). e-go states that the new API reveals more information and is is surely the one that will be subject to further development. I am not sure though whether the existence of the v2 API depends on hardware or firmware versions. Mine are: Hardware V3, firmware 050.2 (as stated in the app). Excerpt saved from GitHub on 2026-10-23. | Issue #40 · 2021-06 |
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 polling
Talks to the device on your network, asking it for updates every so often.
Details
| Installs (analytics) | 493 (0.07%) |
|---|---|
| GitHub stars | 99 |
| Latest version | 0.27.0 (2025-06-06) |
| Set up in the UI | Yes |
| Maintainers | @cathiele |
| License | MIT |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| cryptedx/homeassistant-goecharger Newer code | ★ 1 | 2026-07-22 | Home Assistant custom_component for controlling the go-eCharger EV-Charger |
| mpw96/homeassistant-goecharger Newer code | ★ 0 | 2026-01-11 | Home Assistant custom_component for controlling the go-eCharger EV-Charger |
| BenjaminWitte/homeassistant-goecharger Newer code | ★ 0 | 2026-10-11 | Home Assistant custom_component for controlling the go-eCharger EV-Charger |
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.
