Keba P30 DE440 "Deutschland Edition"

[pixbalance]

Describe the bug

Hi,

it seems there is no firmware upgrade for this edition and I do not get the DE440 working after lvcc 0.312.0.
The old template: Keba does no longer work and the modbus connection is not supported with the DE440 firmware. Is there any other chance to get this callbox working?

Steps to reproduce

...

Configuration details

chargers:
  - name: keba
    type: template
    template: keba
    host: 172.16.0.233

Log details

-

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

Linux

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

No response

[github-actions]

Thanks for the report. A few observations from the code/templates:

• The classic keba template (template: keba in your config) maps to keba-udp (templates/definition/charger/keba-udp.yaml), which is already marked deprecated: true and requires the legacy UDP protocol to be enabled via DIP switch 1.3 = ON. If your DE440 firmware no longer exposes this UDP interface (common on newer/"Eichrecht" calibration-law firmwares for the German market), that template can no longer work — this isn't a switch evcc controls, it's a wallbox-side firmware/DIP setting.
• The supported successor is keba-modbus (templates/definition/charger/keba-modbus.yaml), but it requires a minimum firmware (3.10.42 for C-series / 1.11 for X-series) and Modbus TCP explicitly enabled in the wallbox settings (register 5050 = 3 on C-series, or via the web menu on X-series).

There's no existing template or code path in evcc specific to the "DE440 Deutschland Edition" hardware, so I can't tell from the report alone whether:

1. Modbus is genuinely unsupported/disabled on your DE440 firmware, or
2. Modbus support exists but isn't enabled per the requirements above.

To make progress, could you provide:

• The exact firmware version shown in the KEBA web UI / app (Device/Info page)
• Whether Modbus TCP has been explicitly enabled in the wallbox settings (not just DIP switches)
• The exact error/log output from evcc when configured with type: keba-modbus (not the legacy keba template) and connecting to 172.16.0.233:502

Without logs or a firmware version, I can't confirm whether this is an evcc limitation or a wallbox configuration issue.

🤖 Generated with Claude Code

[rpsmonkey]

Hi,

I hope I can help here. Just installed my Keba P30 DE440 "Deutschland Edition" over the past two days.

I activated DIP switch 1.3 = ON and configured charger in EVCC via UI with this device: KEBA KeContact P30 C-Series
I think via UI the Modbus TCP template is being used. I'm using the newest firmware for Keba P30 v 3.10.80.

So at least for the newest firmware Modbus TCP can be activated via DIP switch 1.3 and can be used to connect with EVCC.

[pixbalance]

@rpsmonkey thanks for your input, but it seems it depends on which hardware generation you actually have — "Deutschland Edition" was sold across multiple series, not just one.

Decoding the order code per KEBA's own scheme (KC-P30-ES2400[x]2-000-xx, where [x] is the series digit: 0=e-series, 1=b-series, 2/3/A=c-series, B/C/E/G/H=x-series): the 7th character in EC220112 is 1 → b-series.

The b-series only has USB / Ethernet / WLAN / UDP interfaces — no Modbus TCP at all (confirmed on KEBA's own b-series vs. c-series comparison page).

Seems like I have to buy a new one. But then I am looking for a good one with MID.

[rpsmonkey]

@pixbalance Did you check and tried the Modbus-tcp template with your box? The "Deutschland Edition" is neither a pure b-series nor a c-series, but something between it.
I have a "KC - P30 - EC220112-000-DE" and my wallbox has Modbus tcp and is it working. Also the Data sheet for my box is stating Modbus udp and also tcp. See attached data sheet - sorry only have it in German available:
Keba KeContact P30 datenblatt_deutschland_edition.pdf

If you are using evcc you can also install a cheap MID in your sub-distribution board and just connect in evcc with your wallbox to get all the data.