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: When ChargeManager is enabled on several chargers at the same time, the available surplus is split between them in the order of the wallbox list – see Several wallboxes on one PV surplus.

• 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, V60.5, V60.6 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.

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).

Per-wallbox current limits

Each wallbox can optionally be given its own minimum and maximum charging current [A]. These apply to both ChargeManager (PV surplus) and ChargeNOW, for example to throttle a single charger or to balance the load between several boxes on a shared supply.

• A value of 0 means "not set": the minimum falls back to the technical minimum of 6 A, and the maximum falls back to the installation-wide maximum charging current from the standard settings.
• A per-box maximum can only lower a charger below the installation limit, never raise it above.
• If the configured minimum ends up higher than the maximum, the minimum is clamped down to the maximum and a warning is logged.

The adapter also reads the current caps reported by each charger – the absolute maximum current, the cable current limit and (via API v2) the minimum charging current – and folds them into the effective limits, so a charger is never driven beyond what its hardware or the plugged cable allows. The detected caps are published as Wallbox_X.info.hardwareMaxChargeCurrent and Wallbox_X.info.hardwareMinChargeCurrent to help you choose sensible per-box values.

PV surplus charging with ChargeManager

ChargeManager calculates the charging current from numeric ioBroker states supplied by an energy-management, inverter, meter, or user-created data source. It does not depend on a particular vendor, but the selected states must represent the quantities described below.

Configure the object IDs of the following states:

• currently available solar power [W]
• current home power consumption [W]
• current state of charge of your home battery [%] (only required in the battery-aware modes, see Home battery mode below)

Input requirements

All configured states must contain numeric values. Power values in kW must be converted to W before they are selected. A grid import/export state cannot be used directly because ChargeManager currently expects separate generation and consumption values.

If no home battery is installed, set the Home battery mode to Disabled (see below). No battery state of charge has to be configured, and ChargeManager charges purely from the available PV surplus. The former helper-state workaround (a constant state set to Settings.Setpoint_HomeBatSoC) is no longer needed.

Wallbox consumption in the home-consumption value

Enable Charger consumption is included in the home power consumption value when the selected home-consumption state rises by approximately the charging power after charging starts. ChargeManager then adds the measured wallbox power back before calculating the available surplus. This prevents the controller from treating its own charging load as additional household demand.

Leave the option disabled when the selected state already excludes wallbox consumption.

Calculation

ChargeManager uses the following calculation once per poll cycle:

available power =
    solar power
  - home power consumption
  + wallbox power, if it is included in home power consumption
  - grid reserve
  + battery bonus (Battery priority mode only)

target current = floor(available power / 230 V / active phases)

Six settings on the ChargeManager configuration page tune this calculation:

• Home battery mode (default Battery priority) – how the home battery is taken into account:
  • Disabled – no home battery is used. No SoC state has to be configured, and no battery power is ever assigned to the car.
  • Minimum SOC – EV charging is blocked below Settings.Setpoint_HomeBatSoC, but the battery never contributes power to the car.
  • Battery priority – as above, plus the battery bonus described below.
• Battery SoC hysteresis [%] (default 0) – how far the SoC may fall below the minimum before a running controller stops. It keeps a battery hovering around its minimum from toggling the charge release every cycle; starting still requires the full minimum SoC.
• Maximum battery SoC age [s] (default 0 = off) – surplus control stops when the SoC state has not been updated within this time, so a dead helper state cannot silently keep the car charging.
• Grid reserve power [W] (default 100) – power kept free on the grid connection instead of being assigned to the car. Increase it to keep more safety headroom; set it to 0 to hand the full surplus to the car.
• Maximum battery bonus [W] (default 2000) – how much extra power, on top of the pure solar surplus, may be drawn while the home battery is above its minimum state of charge. The bonus is 0 when the battery is exactly at the minimum SoC and grows linearly to this maximum as the battery approaches 100 %, so a fuller battery lets the car charge faster. Set it to 0 to charge purely from the measured solar surplus without ever discharging the home battery into the car.
• Minimum ChargeManager current [A] (default 6) – the surplus charging current below which the charger is switched off after a short delay. This applies to PV surplus charging only.

The maximum charging current [A] (default 16, up to 32) is configured on the standard settings page, not here: it is an installation-wide limit of the shared power supply (main breaker / circuit protection) rather than a ChargeManager tuning value. It caps the current the adapter will ever assign to any wallbox, in both ChargeManager (PV surplus) and ChargeNOW.

⚠️ Do not set the maximum charging current higher than your go-e Charger hardware and your electrical installation support. go-e Charger models are rated for different maximum currents (e.g. 16 A or 32 A), and the actual limit also depends on your cable, plug and wiring. Setting a value above the hardware/installation rating can trip protection devices or damage equipment. When in doubt, keep the default of 16 A.

In the battery-aware modes, EV charging is disabled below Settings.Setpoint_HomeBatSoC so that the home battery has priority. Charging starts once the internal target reaches 10 A (or the minimum current if it is set higher); a running charge then follows the target down to the minimum current. The calculated current is limited to the configured maximum, and the internal current target changes by at most 1 A per poll cycle to reduce sudden changes.

Several wallboxes on one PV surplus

The surplus is a single shared resource, so it is split between the wallboxes rather than offered to each of them in full. The wallboxes are served in the order of the wallbox list, which is therefore also their priority: the first entry takes as much surplus as it can use, and the following entries only see what is left. Reorder the list to change which car is charged first.

A wallbox only reserves surplus while a vehicle is connected to it. An empty wallbox is skipped, so it cannot hold back surplus that another wallbox could use right now.

The per-wallbox current limits described above still apply to each box individually, which lets you cap a single charger even when it is first in the list.

Enabling ChargeManager

After the adapter has started, use the writable states below. Replace instance 0 and wallbox number 0 where necessary.

For surplus charging, set ChargeManager to true. ChargeNOW charges at the configured ChargeCurrent without considering the available surplus. The two modes are exclusive: switching one on switches the other off.

ChargeNOW ends by itself and switches off when the vehicle is unplugged, or, with withdraw release when the vehicle stops charging enabled for the wallbox, when the vehicle draws no power for 5 minutes. Switching ChargeNOW on before plugging in is fine: it waits for the vehicle without waking the charger.

One-phase and three-phase charging

On hardware generation 3 and newer, Charge3Phase selects the phase mode:

• false: one-phase charging
• true: three-phase charging

Because the current implementation starts charging when its internal target exceeds 9 A, the effective starting point is 10 A. This requires approximately 2.3 kW in one-phase mode or 6.9 kW in three-phase mode after the reserve and battery adjustments. One-phase mode therefore provides a wider operating range for smaller PV systems or variable weather.

Automatic phase switching

Enable automatic 1-/3-phase switching per wallbox (gen 3+ only, off by default) to let ChargeManager pick the phase mode from the available surplus:

• It switches up to three phases once one-phase charging is saturated (the surplus exceeds the one-phase maximum), giving access to the higher three-phase ceiling.
• It switches down to one phase once the surplus can no longer sustain the three-phase minimum (~4.1 kW at 6 A), so a shrinking surplus keeps charging one-phase instead of stopping.
• The gap between those thresholds plus a dwell time prevents rapid back-and-forth switching, which would interrupt charging each time.

While the option is enabled the adapter controls Charge3Phase for that wallbox; leave it disabled to keep selecting the phase mode manually. Because a switch briefly interrupts charging and not every vehicle handles it gracefully, it is opt-in.

Operating modes

With both modes off, the adapter withdraws only a charge release it gave itself. A charge started from the go-e app, the button on the charger or the charger's own default is left alone.

In read-only mode, these states can still be changed but no resulting control command is sent to the charger.

Verification and troubleshooting

Before relying on automatic charging, verify the selected input states in the ioBroker object view:

1. Solar power is close to zero at night and follows current generation during the day.
2. Home power consumption remains positive and reacts plausibly when household loads are switched on.
3. Battery state of charge remains between 0 and 100.
4. All power values are expressed in W rather than kW.
5. The wallbox-consumption option matches whether charging power is included in the selected home-consumption value.
6. Wallbox_0.info.connection is true.
7. Wallbox_0.Power.Charge, Wallbox_0.Power.GridPhases, and, on supported hardware, Wallbox_0.Power.EnabledPhases contain plausible values.

Charging may take several poll cycles to start because the internal target increases by only 1 A per cycle. With the default 10-second cycle and an initial target of 0 A, reaching the default 10 A starting point can take approximately 100 seconds.

When ChargeManager runs several wallboxes at once, the PV surplus is shared between them in wallbox-list order, so the first entry has priority and later ones only receive the remaining surplus (see PV surplus charging with ChargeManager above).

Total current budget (fuse protection)

To protect a shared fuse or supply line feeding several wallboxes, set the maximum total charging current [A] on the standard settings page. It is an installation-wide budget: the summed charging current of all wallboxes never exceeds it, in both ChargeManager and ChargeNOW. Unlike the PV surplus (which is measured in watts), the fuse is protected in amperes, because a feed rated for e.g. 20 A carries 20 A regardless of whether a wallbox charges one- or three-phase.

The budget is allocated in priority order: ChargeNOW wallboxes first, then ChargeManager wallboxes in wallbox-list order. A wallbox that no longer fits is throttled to the remaining current, or switched off when even its minimum would not fit. While the budget is active, a wallbox without a connected vehicle is kept off and reserves nothing, so several idle wallboxes plugged in at the same time can never exceed the fuse before the next cycle re-plans, and an idle wallbox never starves one that is already charging.

A value of 0 (default) disables the budget; the adapter then does not enforce a combined limit, so make sure the sum of the per-wallbox maximum currents stays within your installation's capacity.

While the budget is active, the adapter also follows the actually measured charging current: if a wallbox draws noticeably less than it is allowed (e.g. a vehicle with a lower onboard-charger limit, a car tapering near full, or temperature derating), its unused current is reclaimed after a few cycles and handed to the next wallbox in priority order. The wallbox keeps a small headroom above its real draw and is offered one ampere more each cycle as long as it uses what it gets, so it can grow back to its limit. To stay safe, a wallbox is only ever throttled down to reclaim capacity — its command is never left high while the freed amperes are given away — so the summed current can never exceed the fuse even if a vehicle suddenly ramps back up.

This is a conservative per-phase-agnostic model: every ampere counts against one budget regardless of which phase it lands on. It never exceeds the fuse rating, but with loads spread across phases it may leave some capacity unused.

Donate

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

Changelog

WORK IN PROGRESS

• (typhosj) with ChargeNOW and ChargeManager both off, the adapter no longer aborts a charge it did not start - a charge started from the go-e app, the button or after a charger restart used to be cut off in the next cycle, until the vehicle gave up
• (typhosj) ChargeNOW now switches itself off when the vehicle is unplugged, and with the option above when the vehicle stops drawing power; it used to hold the charge release until switched off by hand, so the next vehicle plugged in started charging at the full ChargeNOW current. While ChargeNOW waits for a vehicle, nothing is sent to the charger
• (typhosj) ChargeNOW and ChargeManager are now exclusive: switching one on switches the other off, instead of ChargeNOW silently taking precedence
• (typhosj) a ChargeManager that takes over a charger - at adapter start or after ChargeNOW - continues a running charge at its current, with a fresh shutdown delay; it used to start from its previous state and could withdraw the release in its first cycle

1.9.0 (2026-10-28)

• (solar0x) new states Wallbox_X.Power.VoltageL1, VoltageL2 and VoltageL3 show the voltage the charger measures on each grid phase, in V; all hardware generations. As in the go-e app, a single-phase supply with L and N swapped shows its N voltage as L1
• (typhosj) new state Wallbox_X.Power.GridFrequency shows the grid frequency the charger measures, in Hz; hardware gen 3 and newer with HTTP API v2 enabled only, and it stays empty while the charger reports the frequency as unknown [#898]
• (typhosj) new state Wallbox_X.info.chargeState explains why the charger is charging or not - waiting for a vehicle, charging the home battery first, not enough PV surplus, ramping up to the start current, charging, current budget exhausted, both modes off; every change of the reason is also logged once. A charger that never started used to leave no trace in the log, because most of these reasons were only logged together with a write to the charger
• (typhosj) ChargeManager: new per-wallbox option to withdraw the charge release when the vehicle draws no power for 5 minutes - vehicles such as the Renault Zoe otherwise stay in charging mode, e.g. in the evening when the battery bonus keeps the release active (reported by a user)
• (hombach) phase voltages and grid frequency are rounded to 2 decimal places
• (hombach) updated dependencies

1.8.1 (2026-10-11)

• (typhosj) after an automatic switch from one to three phases the ChargeManager now continues at the power the car was charging with instead of the one-phase current; 16 A on one phase used to become 16 A on three phases (about 11 kW) and came down only one ampere per cycle, drawing the difference from the battery or the grid
• (typhosj) after an automatic switch from three to one phase the ChargeManager now also continues at the power reached so far, capped at what the surplus carries on one phase; it used to keep the three-phase current, so a car plugged in while the charger still held three phases from the last charge took about a minute longer to start

1.8.0 (2026-10-04)

• (hombach) added an installation-wide total current budget (maximum total charging current) that caps the summed current of all wallboxes to protect a shared fuse, serving ChargeNOW before ChargeManager and keeping a wallbox without a connected vehicle off so idle wallboxes neither trip the fuse nor starve one that is already charging
• (hombach) the total current budget now follows the measured charging current: a wallbox that draws less than allowed has its unused current reclaimed after a dwell and handed to the next wallbox, growing back one ampere per cycle when it uses what it gets - reductions are always applied before increases so the summed current never exceeds the fuse
• (hombach) added concise debug logging for the ChargeManager control loops (surplus sharing, phase switching, total current budget)
• (hombach) docs: documented the total current budget
• (typhosj) the phase mode (psm) is now only written when the charger reports a different mode instead of every cycle, because it is a stored charger setting
• (typhosj) ChargeManager: no charge release, charging current or phase switch is sent while no vehicle is plugged in, and an unchanged release or current is no longer re-sent every cycle - each write woke the charger's LEDs
• (typhosj) the charging current is no longer re-sent every cycle: the charger reports a written amx back as 0 and only shows the applied current in amp, so the check for an unchanged value never matched
• (typhosj) the charge release is no longer re-sent on every single cycle while the vehicle reports that it has finished charging - the charger confirms each write and keeps ignoring it, for up to 90 minutes in one logged case; it is still retried, just at a lower rate after the first five minutes
• (typhosj) ChargeManager: the charging current no longer follows a one-ampere change of its target, so a passing cloud no longer makes it step back and forth every cycle
• (typhosj) ChargeManager: a running charge now follows a falling surplus down to the minimum current - the 10 A start current also applied to a running charge, so currents between the minimum and 10 A were never written and the charger stayed at the 10 A written last, drawing the difference from the grid or the home battery until the surplus recovered or the shutdown delay ran out
• (hombach) updated dependencies

1.7.0 (2026-09-18)

• (typhosj) admin: the wallbox list now explains that its order is the ChargeManager priority - the first entry receives the PV surplus first, later entries only the remainder
• (typhosj) ChargeManager: the PV surplus is now shared between all wallboxes instead of being offered to each one in full; wallboxes are served in configuration order, so the first entry has priority and later ones only receive the remaining surplus
• (typhosj) ChargeManager: a wallbox without a connected vehicle no longer reserves surplus and can no longer starve a wallbox that has a car waiting
• (hombach) ChargeManager: optional automatic 1-/3-phase switching per wallbox (gen 3+, off by default) - switches up when one-phase charging saturates and back down when the surplus can no longer sustain three phases, with a dwell time to prevent flapping
• (hombach) fixed: automatic phase switching no longer overwrites the manual Settings.Charge3Phase request - the automatic decision is now tracked internally, so the user's manual 1-/3-phase setting is preserved (and no longer persisted across restarts as if the user had set it)
• (hombach) docs: clarified the multi-wallbox behaviour (list order = priority) and noted that no combined current limit across wallboxes is enforced yet
• (hombach) updated axios
• (hombach) switch to iobroker testing 6.x
• (hombach) fixed repochecker warnings
• (hombach) added node 26 tests

1.6.1 (2026-09-04)

• (typhosj) fixed: a wallbox whose effective maximum charging current is below 10 A - e.g. an 8 A coded cable or a per-wallbox maximum of 8 A - was rejected as invalid ChargeManager input and never charged from PV surplus. Such a wallbox now starts charging at its own maximum

License

MIT License

Copyright (c) 2020-2026 C.Hombach go-e-charger@homba.ch

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.