Easee: forced 7A on scale down is aborting charge
Describe the bug
#29464 is turning out to be problematic after all. I have now seen two aborted charges already, which I have never seen before. Each time after a phase switch. Given the only change in this area in the recent past has been the change to force 7A, I have to assume it is problematic. Reverting will also address #32626 which I observed locally as well.
Steps to reproduce
Frankly not sure. What I observed is a sequence of 6A@3p -> 7A@1p -> 6A@1p leading to the onboard charger not catching up quickly enough on the Fiat, and then the Easee aborts the charge due to an overcurrent. Based on the logs it seems the car has 10s to catch up with the signal from the charger. My best guess is it must be timing related, so sometimes this works, sometimes it breaks.
The forced pauses on scale down will return unfortunately, but a delay is for sure better than a unreliable charge.
Configuration details
Easee via cloud API. Config otherwise not relevant.Log details
[easee ] TRACE 2026/09/22 15:40:59 CommandResponse EHXXXXXX: {SerialNumber: EHXXXXXX ID:48 Timestamp:2026-09-22 13:40:58.611404 +0000 UTC DeliveredAt:2026-09-22 13:40:57.732 +0000 UTC WasAccepted:true ResultCode:0 Comment: Ticks:639256812586114040}
[lp-1 ] DEBUG 2026/09/22 15:40:59 set charge current limit: 6A
[easee ] TRACE 2026/09/22 15:41:00 ProductUpdate EHXXXXXX: (2026-09-22 13:40:58 +0000 UTC) OUTPUT_CURRENT 6
[easee ] TRACE 2026/09/22 15:41:00 ProductUpdate EHXXXXXX: (2026-09-22 13:40:58 +0000 UTC) CIRCUIT_TOTAL_ALLOCATED_PHASE_CONDUCTOR_CURRENT_L1 6
[easee ] TRACE 2026/09/22 15:41:01 ProductUpdate EHXXXXXX: (2026-09-22 13:40:59 +0000 UTC) INT_CURRENT_T2 7.817999839782715
[easee ] TRACE 2026/09/22 15:41:01 ProductUpdate EHXXXXXX: (2026-09-22 13:41:00 +0000 UTC) CIRCUIT_TOTAL_PHASE_CONDUCTOR_CURRENT_L1 7.817999839782715
[easee ] TRACE 2026/09/22 15:41:01 ProductUpdate EHXXXXXX: (2026-09-22 13:40:59 +0000 UTC) INT_CURRENT_T3 7.817999839782715
[easee ] TRACE 2026/09/22 15:41:12 ProductUpdate EHXXXXXX: (2026-09-22 13:41:10 +0000 UTC) LEDMODE 16
[easee ] TRACE 2026/09/22 15:41:12 ProductUpdate EHXXXXXX: (2026-09-22 13:41:10 +0000 UTC) ERROR_CODE 2048
[easee ] TRACE 2026/09/22 15:41:12 ProductUpdate EHXXXXXX: (2026-09-22 13:41:10 +0000 UTC) ERROR_STRING [ERROR] Charger: Overload EV=7826 > 6000 mA^MWhat type of operating system or environment does evcc run on?
Docker container
External automation
- I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.
Nightly build
- I have verified that the issue is reproducible with the latest nightly build
Version
0.315.0
Source: evcc-io/evcc