Easee auto phase mode can map low EV targets to 0 A

[frahlg]

Bug Description

After upgrading to 0.128.0, EV charging with Easee may not start when EV phase mode is set to auto. The plan/diagnostics can show an EV target around 3.0–3.6 kW, but the Easee driver ends up writing dynamicChargerCurrent=0 A and the charger remains stopped.

Report

Discord support report from Anders:

• version: 0.128.0
• charger: Easee Cloud, 3-phase capable, firmware settings showed phaseMode=3, maxChargerCurrent=16A
• modes tried: PV charging, manual, schedule
• observed log after update:
  • Easee: phaseMode → 3
  • Easee: re-asserted dynamicChargerCurrent=0 A after phaseMode reset
• diagnostics showed loadpoint schedule/target changed with planned EV power around 3.0–3.6 kW
• workaround confirmed: switching EV phase mode from auto to 1-fas made charging start

Likely Cause

At ~3.0–3.6 kW on locked/effective 3-phase, requested current is about 4–5 A/phase, below Easee's 6 A minimum. The driver therefore snaps to 0 A. In auto, either the driver is not receiving/using the auto phase setting as intended, or the UI/plan permits a target that is valid for 1p but invalid for effective 3p.

Expected Behavior

With EV phase mode auto, low EV targets should result in 1-phase charging when possible, or the planner/UI should avoid producing targets that the selected/effective phase mode maps to 0 A.

Actual Behavior

The EV target is non-zero, but Easee receives/keeps dynamicChargerCurrent=0 A, so charging does not start until the user manually selects 1-phase.

Notes

Check the path from EV settings -> loadpoint config -> ev_set_current command (phase_mode) and the Easee driver's pick_phases/minimum-current behavior.