ioBroker.go-eCharger

Versions

ioBroker adapter for go-e Charger EV wallboxes

This adapter integrates one or more go-e Charger wallboxes into your ioBroker home automation. It cyclically polls each wallbox via its local HTTP API, provides all relevant data as ioBroker states, and lets you control charging directly from your smart home.

For more information about the go-e Charger hardware, visit the manufacturer's website: go-e GmbH.

Features

• supports multiple go-e Chargers within a single adapter instance

• monitoring of car state, charging power, charging current, grid phases, and energy statistics

• ChargeNOW – start charging immediately at a configurable current

• ChargeManager – automatic PV surplus charging: the charging current is continuously adjusted to the available solar power, taking house consumption and the state of charge of your home battery into account. Charging of your EV can be delayed until the home battery has reached a configurable minimum state of charge.

  Note: PV surplus charging is currently designed for controlling a single charger. When ChargeManager is enabled on multiple chargers at the same time, the charging currents are not coordinated between them and the solar surplus calculation will produce incorrect values. An extension with coordinated multi-charger load management will be available soon.

• switching between 1-phase and 3-phase charging (hardware generation 3 and newer)

• energy statistics per RFID card (card name, ID, and charged energy)

• read-only mode per wallbox – monitor a charger purely, without sending any control commands to it (no charge release, no charging current, no phase switching), e.g. when charging is controlled elsewhere or access is managed via RFID tags

Tested with firmware V033, V040.0, V041.0, V054.7, V054.11, V055.5, V055.7, V055.8, V56.1, V56.2, V56.8, V56.9, V56.11, V57.0, V57.1, V59.4, V60.0, V60.1, V60.2 and with up to 3 chargers operated in parallel.

Requirements

• For hardware generation 3 and 4 you have to enable "HTTP API v1" in your go-e app.
• For phase switching you additionally have to enable "HTTP API v2" in your go-e app (hardware generation 3 and newer).

Configuration

Add one entry per go-e Charger to the wallbox list and enter its IP address. Optionally assign a name to each charger.

Enable read-only mode for a charger if the adapter should only read its data and never write to it. In read-only mode the adapter sends no control commands at all – neither the charge release, nor the charging current, nor phase switching. The ChargeNOW and ChargeManager states can still be toggled, but they have no effect on a read-only charger. Use this mode when the charging of that wallbox is controlled by another system or managed locally via RFID tags.

For PV surplus charging with ChargeManager, configure the object IDs of the following states from your PV system:

• currently available solar power [W]
• current home power consumption [W]
• current state of charge of your home battery [%]

If the power consumption of the wallbox is already included in your home power consumption value, enable the corresponding checkbox so the adapter can correctly calculate the available surplus.

The poll cycle time defines how often the adapter reads data from the chargers and adjusts the charging current (minimum 3 seconds, default 10 seconds).

Sentry

This adapter employs Sentry libraries to automatically report exceptions and code errors to the developers. For more details and information on how to disable error reporting, please consult the Sentry-Plugin Documentation!

Donate

If you enjoyed this project – or are just feeling generous – consider buying me a beer. Cheers! :beers:

Changelog

1.2.0 (2026-07-12)

• (hombach) added statisticsGlobal.chargePower state with the current total charging power of all chargers
• (hombach) removed chai-based unit test dependencies; modernized test harness to Node.js assert (fixes Appveyor, #836)

1.1.0 (2026-07-05)

• (hombach) fixed reading of "unlocked by RFID" (uby) on gen 3+ chargers via API V2
• (hombach) read-only mode now suppresses all control commands (charge release, charging current, phase switching)
• (ioBroker-Bot) Adapter requires admin >= 7.8.23 now.

1.0.4 (2026-07-04)

• (hombach) harmonized i18n files
• (hombach) improved README and English texts
• (hombach) reworked translations in all languages
• (hombach) added 5s timeout to all HTTP requests to chargers
• (hombach) fixed adapter stop when no charger is reachable at startup; warn per unreachable charger
• (hombach) fixed German fallback text for RFID card channel names
• (hombach) added upper bound validation for cycle time
• (hombach) added link to manufacturer's website
• (hombach) code optimizations

1.0.3 (2026-07-03)

• (hombach) added translations
• (hombach) fixed state roles

1.0.2 (2026-07-01)

• (hombach) fix RFID data readout for gen 3+ chargers via API V2 (#802)
• (hombach) prepared for beta repo
• (hombach) eliminate yarn
• (hombach) upgraded adapter-core
• (hombach) updated axios
• (hombach) updated dependencies

Older changelogs can be found there

License

MIT License

Copyright (c) 2020-2026 C.Hombach

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.