EVCC: Alfen Charger Stops Tesla Charging

Experiencing issues where your EVCC (Electric Vehicle Charging Control) system, specifically with an Alfen charger and a Tesla vehicle, starts and then abruptly stops charging? You're not alone! This can be a frustrating problem, but with a systematic approach, we can often pinpoint the cause and get your EV powered up smoothly. This article dives deep into the common reasons behind this charging interruption, explores the provided log details, and offers practical solutions to resolve the issue.

Understanding the "Starts and Stops" Charging Phenomenon

One of the most perplexing issues EV owners face is when their charging session begins normally, only to be interrupted moments later. This isn't usually a sign of a major hardware failure but rather a communication hiccup, a configuration mismatch, or a response to rapidly changing grid conditions. When charging starts and stops intermittently, it often means that the EVCC system is receiving signals or detecting conditions that cause it to halt the charging process. These signals can originate from the vehicle, the charger itself, the EVCC software, or even the grid. For instance, if the Alfen charger communicates an issue to EVCC, or if the Tesla vehicle reports a problem, EVCC will typically stop the charge to prevent damage or further complications. Similarly, rapid fluctuations in grid power availability or voltage can trigger safety mechanisms within the charger or EVCC, leading to an aborted session. Understanding that EVCC acts as an intelligent intermediary between your Tesla and your Alfen charger is key. It monitors everything from grid load and solar production to the vehicle's charging status and battery state. When any of these parameters fall outside acceptable limits or trigger a safety protocol, the charging process is gracefully (or sometimes abruptly) stopped. The goal is always to ensure safe and efficient charging, and sometimes, that means pausing or stopping a session.

Deep Dive into the Provided Configuration

Let's dissect the configuration you've provided. The site section shows a grid connection (db:8), solar panels (db:4), and a battery (db:5). This is a typical smart home setup where EVCC orchestrates charging based on available solar power, battery storage, and grid import/export. The loadpoints configuration is particularly important. For loadpoint 7, we see a minCurrent of 6A and a maxCurrent of 16A, with the charger (db:6) being an Alfen Eve. The vehicle is specified as a Tesla (db:3) with a minCurrent of 6A and maxCurrent of 16A. This indicates that EVCC is configured to allow charging between 6A and 16A for this specific load point, and it expects both the Alfen charger and the Tesla vehicle to adhere to these limits. The charger configuration correctly identifies the Alfen Eve charger at 192.168.0.89 using Modbus TCP/IP on port 1502. The Tesla vehicle integration uses a template, likely communicating via the TeslaMate API, with minCurrent and maxCurrent set to 6A and 16A respectively. The meter configurations (db:4 for PV, db:5 for battery, db:8 for grid) are essential for EVCC's smart charging logic. The tariffs section details how EVCC calculates electricity costs using the Nordpool electricity pricing API for both grid import and feed-in, incorporating local charges and taxes. This complex interplay of devices and services means that a fault in any one component or a misinterpretation of data can lead to the observed charging behavior. For instance, if the Alfen charger reports a current limit lower than 6A, or the Tesla reports a vehicle-side limit below 6A, EVCC would enforce its own minimum, potentially causing a conflict. The fact that the charger is set to 192.168.0.89:1502 and the modbusproxy is at 192.168.0.86:502 is also noted, suggesting a specific network setup that could be a point of failure if not configured correctly.

Analyzing the Log Entries for Clues

The log snippet provides critical information about the moments leading up to and during the charging interruption. The line WARNING:taskMain.c:4698:Socket #1: maximum current(0.00) < minimum current(6.00) is a significant indicator. This warning originates from the Alfen charger's internal logging (accessible via its ACE installer interface, as mentioned). It signifies a direct conflict reported by the charger itself: the maximum current it's currently able to supply is 0.00A, which is less than the configured minimum charging current of 6.00A that EVCC is trying to establish. This is the most probable direct cause of the charging failure. When EVCC attempts to initiate charging at the configured minimum of 6A, the Alfen charger responds that it cannot provide anywhere near that current, hence it cannot start or sustain the charge. The subsequent log entries from EVCC ([lp-1 ] INFO 2025/12/20 09:03:02 start charging ->, [lp-1 ] DEBUG 2025/12/20 09:03:02 wake-up timer: stop) show EVCC attempting to start charging, but immediately receiving information that causes it to stop. The charger status [lp-1 ] DEBUG 2025/12/20 09:03:02 charger status: C indicates the charger is in a state of 'Charging' momentarily, but this is quickly followed by the stop command. The earlier debug messages provide context: [site ] DEBUG 2025/12/20 09:03:01 grid power: 2371W and [site ] DEBUG 2025/12/20 09:03:01 site power: 2471W. This shows the overall power consumption at that moment. The crucial warning from the Alfen charger implies an issue at the charger level preventing it from delivering the required minimum current. This could be due to a temporary fault, a firmware issue, a loose connection, or a problem with its internal power measurement or control. The fact that EVCC's minCurrent is set to 6A in the loadpoint configuration and the Alfen reports maximum current(0.00) < minimum current(6.00) points directly to the charger's inability to meet this basic requirement. It's important to note that the Tesla vehicle's status (vehicle soc: 65%, vehicle soc limit: 100%) appears normal and doesn't seem to be the direct cause of the stop, as the issue is flagged by the charger itself.

Troubleshooting Steps and Potential Solutions

Based on the analysis, here’s a structured approach to resolve the