I’m excited to announce a new project I’ve been working on: Phaeton. It’s a driver that allows you to connect an Alfen Eve Pro-Line EV charger (for now) to a Victron system and have it seamlessly recognized and managed as if it were a native Victron EV charger. (You’ll need the load balancing license)
The main goal is to provide more intelligent charging control directly within the Victron ecosystem. The driver supports several charging modes:
Manual Mode: Start and stop charging on demand, just like with the standard controls.
Auto Mode: This mode is designed for charging with solar surplus. It automatically adjusts the charging power based on the available PV excess, calculated as (Solar Production - System Load - EV Charger Consumption). To maximize the use of your solar energy, the driver will also automatically switch between single-phase and three-phase charging based on the amount of available power. This allows charging to begin with a smaller amount of solar surplus on a single phase and ramp up to full three-phase charging when the sun is shining brightly.
Scheduled Mode: This mode allows you to charge during specific periods to take advantage of cheaper electricity. It can be configured in two ways:
Time Windows: Set up fixed time slots (e.g., overnight) for the charger to be active.
Dynamic Pricing: The driver can integrate with dynamic energy providers like Tibber to automatically charge your vehicle when electricity prices are at their lowest.
Currently, vehicle integration is not yet implemented but is planned for a future release.
The architecture supports integrating other EV chargers.
You can find all the details, including installation instructions for Victron Venus OS (like the Cerbo GX), on the GitHub repository:
I’m still actively developing this, so any feedback, suggestions, or contributions from the community would be greatly appreciated.
Amazing work, love to integrate the Alfen charger in my Victron installation.
Unfortunately I noticed the repo is offline. What is the reason for that?
I Installed the “viltron-alfen-charger” in my testing environment, but can’t seem to get it working. The charger is detected but I can’t change the charging current for example. Also max_set_current and station_max_current values stay on there default value and not the ones set in the .yaml file.
(PM me if you want to discuss this more in dept in Dutch)
This is a very interesting driver and exactly what I am looking for.
What are the config requirements on the Alfen Eve Single Pro side?
I am just in the process of trying to connect the Alfen to the Victron system. I understand next to the Load Sharing License you also need modbus TCP and 1 to 3 phase charging activated . I also undeerstand it is required to change the data source to EMS and mete if you already have a load balancer to the meter in place. Is that correct? Anything else that is required?
Also is there a minimum firmware version on the Alfen required and if yes, which one?
Thanks for the great software and the integration!
The hardware I tested it with is an Alfen Eve Single Pro-Line running AHP 2.5.0. It works well overall. It did take me a little while to figure out the current settings, but I found that the key setting is → Power Settings → Connector Max Current on the charging station.
This is best configured using the → ACE Service Installer. If this value is set too low, the charging current cannot be increased beyond that limit, regardless of the settings in Phaeton.
One small remark: with my setup everything seems to work correctly, and the Configuration Profile Connection Test reports “Successfully”.
However, the Alfen Control Test does not work, and neither do the tests below it (such as voltage and current readings).
Despite this, normal operation and charging control appear to work as expected.
Before I asked my question I should have RTFM. My bad.
I have your driver installed and it works like a charm.
The config of the Alfen Eve Single Pro was a bit of a challenge because there was 1 parameter that could not be set by the Eve iphone app, it required the ACE Service Installer, which is only available to Alfen installers, not end users. I managed to get that sorted and after that the Alfen Test Control passed all checks.
