KEBA P30 DE440: charger loses all meter capabilities

Describe the bug

KEBA P30 DE440: charger loses all meter capabilities (power/energy/currents/phases) since evcc ≥0.312, persists after firmware update to 3.11.84

evcc version: 0.316.0 (Home Assistant Add-on, database-only mode, no evcc.yaml)

Charger: KEBA P30 DE440 ("Deutschland Edition"), Modbus TCP, id: 255

Since updating evcc (the issue predates 0.316.0 for us, and persists through it), this loadpoint's charger reports no meter capabilities at all on startup:

[lp-1] charger:  power ✗ energy ✗ currents ✗ phases ✗ wakeup ✗
[lp-1] meters:   charge ✗

A second loadpoint on the same instance (a different charger brand) shows all capabilities as ✓, so this is specific to this KEBA integration/device, not a site-wide config issue.

Because there is no real measurement, evcc's UI/API reports chargePower as offeredCurrent × phases × 230V (i.e., the current setpoint it is requesting), not an actual measured value. We confirmed this by cross-referencing against an independent, high-resolution meter on our PV inverter at the same electrical connection point: the reported chargePower values (11040W, 8687W, 4140W at different times) never appear anywhere in the site's real PV/battery/grid power balance. That balance closes correctly to within a few percent without the reported EV load every time, including across large PV swings (passing clouds) where a real load of that size would necessarily show up as increased grid import or a throttled charging setpoint.

We also had a case where the vehicle had already finished charging (full battery, not accepting current) and evcc kept reporting charging: true with a static max-power value and steadily incrementing chargedEnergy/chargeDuration for an extended period — i.e., it cannot detect charge completion either, since it has no real signal to detect it from. Restarting the evcc add-on cleared that particular stuck session, but the capability loss returns immediately with the next session.

Steps we've already tried:

• Verified Modbus id: 255 is correct/expected for this charger (confirmed via evcc community discussions)
• Updated KEBA firmware from 3.10.80 → 3.11.84 specifically to test whether this was a firmware-side issue — no change, identical log output before and after
• Restarted the evcc add-on — clears a stuck phantom session but does not restore meter capability

Configuration details

KEBA P30 DE440, Modbus TCP, id: 255, connected alongside a second, unaffected loadpoint (different charger brand) on the same evcc instance.

Steps to reproduce

Issue is persistent

evcc-20260922-162449-trace.log

Configuration details

See above

Log details

See attachment

What type of operating system or environment does evcc run on?

HomeAssistant Add-on

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.316.0