[frahlg]

A two-phase car on a three-phase site was given current calculated for three phases. Core could not save the car's two-phase choice, and the Easee driver replaced it on the first command.

This change accepts Core's phase_mode: 2p and an explicit driver phases: 2. It sends Easee Auto while retaining two as the charging count for watts/current and diagnostics. Easee's enum value 2 means Auto, not a measured phase count. Whole-amp two-phase offers stay within the watt ceiling, 6 A minimum and per-phase limit. Explicit one-phase charging remains available.

Paired Core PR: srcfl/ftw#1792. Core pins this exact driver commit.

Dependencies

This draft targets codex/easee-two-phase-deps, a test base containing #172, #183 and #159, their combined version 1.3.9, and advancing source times in the existing phase-flip fixture. It preserves those open PRs and keeps this diff to two-phase support (1.3.10). After the dependencies land, rebase and retarget to main, then merge the driver before the paired Core pin.

Validation

• The command regression fails before this change and passes after it.
• Tests cover Core's two-phase choice, driver configuration, 230/240 V, whole-amp rounding, minimum current, fuse limits, one-/three-phase behavior and the current diagnostic.
• make test-driver ID=easee_cloud: 43 passed, 15 skipped.
• make check: 4,987 passed, 936 skipped.
• GitHub validate: passed on 75aeab7 (run 39645172461).

Hardware acceptance remains pending: capture offered current, phase currents and total AC power on an Easee with the two-phase V60, including pause/resume and a return to one phase. The power model uses two phase-to-neutral loads. These simulated responses do not prove that model for Anders's exact model year or firmware. No charger or driver channel was changed.