EV charging is invisible: no planned-start time, no car-declined signal, silent PV-only deferral, and Start kills the planner

[frahlg]

Field report from the maintainer's own site (Easee carport, 16 A main fuse, recurring schedule 80 % by 07:00).

What happens today

1. Plug in the car and nothing visibly happens. The planner correctly waits for the cheap overnight slots, but no surface says so. The natural reaction is to press Start, which installs a persistent manual hold and silently disables the planner for the whole session.
2. The box cannot tell "the car declines" from "we paused". The Easee driver never emits request_active, so when the car reached its own charge limit the box kept offering 11 kW all night (fuse clamp active at 06:09) and sent two spurious charging.interrupted notifications from the car's ~900 W renegotiation bursts.
3. deferGridPlan is invisible. A deadline past the published price horizon forces surplus-only until tomorrow's Nordpool prices land (~13:00). Any plug-in before ~13:00 with a next-morning deadline behaves exactly like PV-only without the user having chosen it — only an INFO log says why.
4. Start pins power until unplug. An 11 kW hold on a 16 A fuse also fights the per-phase clamp continuously (worst phase measured at 23 A).

Agreed changes

• Show the planned charge window on the loadpoint ("Charging planned 02:15–06:30, 18 kWh"), plus an explicit state for "no schedule, no surplus-only, no hold → will not charge".
• Surface "charger is offering X kW but the car is not taking it" (commanded W vs delivered W + reason_no_current).
• Surface the grid-plan deferral: "waiting for tomorrow's prices — PV surplus only until then".
• Start becomes "Charge now → target SoC": releases at the schedule target (estimated or BMS SoC) and falls back to the plan, in addition to the existing release on unplug and on vehicle decline.
• Easee driver emits request_active=false on reason_no_current=50 / op_mode=4 (srcfl/device-drivers), which enables the existing session-completion latch, manual-hold auto-release and interruption-noise suppression for Easee.

[frahlg]

Everything is in flight:

• feat(ev): say why the charger is (not) charging and when it will #1004 — planned-window / grid-deferral / car-declined visibility in the EV modal + /api/loadpoints (browser-verified against the dev stack with a plugged-in EV sim and the real SE4 price feed).
• feat(ev): Start becomes "charge now → target", releasing back to the plan #1005 — Start becomes "Charge now → target SoC", releasing back to the plan (stacked on feat(ev): say why the charger is (not) charging and when it will #1004; full press-boost-release cycle verified live).
• feat(easee_cloud): emit request_active so the host can tell car-declined from box-paused device-drivers#103 — easee_cloud 1.2.0 emits request_active (reason 50 / op_mode 4), which enables the existing session-completion latch, manual-hold auto-release and interruption-noise suppression for Easee. After it merges, the FTW follow-up is moving the pin in drivers/BUNDLED_SOURCE.json + scripts/sync-bundled-drivers.sh.

Remaining after merges: nothing code-side; the interrupted-notification noise resolves via #103 (the latch never arms when the car has declined).