Staging environment
Phaeton

Phaeton documentation

Supported chargers

Find your charger, see how Phaeton connects and check the requirements for your model.

Local connections run directly over your network. Cloud connections need internet and access to the manufacturer service. Select a model for its setup requirements.

1P/3P Switches between 1 and 3 phases when the charger allows it. mA Current regulation finer than 1 A, better for surplus charging.

Chargers and their connection to Phaeton
Brand and modelConnection
Alfen Eve1P/3PLocal · Modbus TCP
go-eLocal · HTTP
PeblarmALocal · HTTP
KEBA P30 c/x, P40 / P40 PromALocal · Modbus TCP
WARP2 Pro / WARP3 PromALocal · HTTP
Bender CC612 / CC613Local · Modbus TCP
Zaptec Go / Go 2 / PromAManufacturer cloud
Easee Home / Charge / Charge Lite / Charge CoreManufacturer cloud

Alfen Eve

Enable licensed Active Load Balancing and select the EMS as the source. Allow Modbus current writes and configure the fallback current and validity time through the installer.

Phase switching requires a suitable installation and the charger option allowing one and three phases. Configure each socket separately on dual-socket chargers.

go-e

Requires local HTTP API v2. Enable it in the go-e app and enter the local charger address. The older API v1 and go-e cloud are not used.

Phaeton controls current and charging permission. Phase switching is unavailable through this integration.

Peblar

Requires local REST API v1 and firmware 1.6 or later. Enable ReadWrite API access, copy the API token and select the Default charging strategy. Set the current limit for the actual 11 or 22 kW model.

Phaeton waits at least 201 seconds after a pause before resuming. Phase switching and RFID authorization are unavailable through this integration.

KEBA P30 c/x, P40 / P40 Pro

Requires a model with an energy meter and Modbus TCP enabled. P30 c-series requires firmware 3.10.42; x-series requires 1.11. Configure EMS failsafe current to 0 A and timeout to 30–600 seconds.

P20, units without a meter and rebadged models are outside this integration. Phaeton does not switch phases.

WARP2 Pro / WARP3 Pro

Requires the local HTTP API and the charger energy meter with phase-current readings. Enable external control and disable automatic phase switching on the charger and any separate Energy Manager.

WARP1, WARP4 and Smart models are outside this integration. Phaeton controls charging current, but does not switch phases or control a separate Energy Manager.

Bender CC612 / CC613

Requires a controller with the modern Ebee/Bender/OMCCI Modbus map and a suitable energy meter. Ask the installer to verify the controller and interface; the brand name alone is insufficient.

This controller occurs in some Mennekes, Webasto and SMA products. It does not include every model from those brands, legacy maps or Webasto NEXT. Phase switching is unavailable.

Zaptec Go / Go 2 / Pro

Requires internet, a Zaptec API service account with owner/service access and the selected charger UUID. The installer must confirm that external per-charger current control is appropriate. Phaeton does not manage shared installation allocation. Use this cloud integration for one charger per API account.

Cloud or internet outages can prevent control, including stopping. Phase switching and energy/session accounting are unavailable through this integration.

Easee Home / Charge / Charge Lite / Charge Core

Requires internet and approved Easee API access for this installation. Select the exact model and serial number. Commercial use has separate vendor access requirements.

Resuming requires a power budget covering the configured charger maximum; a low solar budget can therefore keep charging paused. Phase switching is unavailable, and cloud outages can prevent stopping. Use Phaeton as the Auto controller; positive GX MQTT controls remain unavailable without verified phases.

Planned

Phaeton adds chargers per controller, not per brand: one integration covers every brand that ships the same controller. These families are next on the plan. They do not work with Phaeton yet, so do not buy a license for them today. Contact us if your brand decides your purchase.

Planned controller families and their brands
FamilyBrands
Bender CC612 / CC613 controllerCUBOS, Ebee, Ensto, Garo, Juice, Mennekes, Optec, SMA, Spelsberg, TechniSat, Ubitricity, Webasto (Live)
Phoenix Contact EV-ETH controllerPhoenix Contact, Compleo, E3/DC, ESL, Wallbe
Heidelberg Energy ControlHeidelberg, Amperfied, SENEC, Walther Werke
Vestel EVC04Vestel, Ampure, E.ON Drive, Webasto (NEXT, Unite)

Bender CC612 / CC613 controller

The controller Phaeton already drives, sold under other names. Each brand still needs verification before it is listed as supported.

CUBOS · Ebee · Ensto · Garo · Juice · Mennekes · Optec · SMA · Spelsberg · TechniSat · Ubitricity · Webasto (Live)

Phoenix Contact EV-ETH controller

Local Modbus TCP controller used by several German wallboxes.

Phoenix Contact · Compleo · E3/DC · ESL · Wallbe

Heidelberg Energy Control

Modbus RTU wallbox family, usually reached through a Modbus TCP gateway.

Heidelberg · Amperfied · SENEC · Walther Werke

Vestel EVC04

Local Modbus TCP wallbox platform behind several brands.

Vestel · Ampure · E.ON Drive · Webasto (NEXT, Unite)

Is your model missing?

Contact support before buying and include the brand, model and firmware. Use the same form if you need help with a connection problem.

Contact support · Configure your charger

Need help? Contact support