go-eCharger (MQTT)
syssi/homeassistant-goecharger-mqtt · v3.1.0
go-eCharger integration for Home Assistant using the MQTT API
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-eCharger wallboxes work locally over MQTT; a user needed a firmware update and correct broker auth. Model selection (11/22 kW) was added; v1 devices have an open PR.
- Works2
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| go-eCharger 11 kW / 22 kW models | Works Local | Charger model dropdown added to config flowSaved copyCloses #66, follow-up of #65 ## Summary - Adds a "Charger model" dropdown to the setup and reconfigure flow with two options: 11 kW (max. 16 A) and 22 kW (max. 32 A) - The selected model is stored as `charger_model` in the config entry data - `amp` (Requested current) and `ama` (Maximum current limit) number entities use the model to enforce the correct upper bound (16 A or 32 A) - Existing entries without `charger_model` default to 22 kW for backwards compatibility - German translation updated ## Test plan - [x] All 293 tests pass (3 new config flow tests added) - [x] Setup a new charger as … Excerpt saved from GitHub on 2026-10-23. | PR #214 · 2026-06 | |
| go-eCharger HOME V3 (firmware 054.x) | Works Local | Works after firmware 054.9 update and fixing MQTT broker authSaved copyI could intenrate go-eCharger successfully - the device and 98 entities can be found. But only the switches are available, all read-only entities are not available and the sensors could not be read. Do I miss something or does this just not work with the latest firmware? I'm using 054.7., the hardware number is V3. Excerpt saved from GitHub on 2026-10-23. | Issue #60 · 2022-12 | |
| go-eCharger v1 devices | Requested Local | Single status topic; support PR openSaved copyDevices v1 behaviour v1 Devices write changes into a single topic: _go-eCharger/Serialnumber/status_ for example: _go-eCharger/030794/status_ That topic contains a json string with all parameters available. Parameters are described in the Official API v1 Repo Example: ``` { "version": "B", "tme": "1910261102", "rbc": "140", "rbt": "258394358", "car": "1", "amp": "16", "amx": "16", "err": "0", "ast": "0", "alw": "0", "stp": "0", "cbl": "20", "pha": "8", "tmp": "28", "tma": [ 19.63, 18.75, 19.25, 19, 21.63, 22.5 ], "amt": "32", "dws": "0", "dwo Excerpt saved from GitHub on 2026-10-23. | PR #235 · 2026-10 |
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.
Found automatically over
- MQTT
Details
| Installs (analytics) | 1,008 (0.14%) |
|---|---|
| GitHub stars | 131 |
| Latest version | 3.1.0 (2026-08-24) |
| Set up in the UI | Yes |
| Maintainers | @syssi |
| 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.
