KEBA KeyContact P30 Firmware 2.0.0

[MikeTheTux]

There is a major update of the firmware for my KEBA KeyContact P30 out:

• Firmware 2.0.0

Changelog is quite short:

The operating system of the KeContact P30 x-series has been upgraded to a newer, more
robust version that resolves several security and stability issues. This update also establishes
the technical foundation for upcoming features, including Autocharge and ISO 15118
support.

Did anybody give this version already a try?
How does it work in combination with EVCC or in general?

[lgusewski]

Yes, i installed today and it works. I also had Home Assistant with the KEBA integration in use and it works like before, too.

[691208]

I also installed the KEBA FW 2.0.0 now I have a "out of service" problem
Charging grid P30x master, P30c slave
At the moment no solution, cannot trace the defect in the log files, not sure if this is a KEBA bug :-(

[lgusewski]

If it is a bug, then perhaps with the combination of the P30c. Is this wallbox also on the latest firmware? I only own the X and it works fine. Today I have enough solar power to load the car and also the switching between fast, only pv, 3 phase to 1 phase works like before with the 1.0 releases.

[691208]

P30c is updated by P30x automatically
P30x Master P30c slave combined as load grid via network
Both with 1p/3p switching capability
Connect a car -> out of service
Set available via P30x UI, everything works fine
Disconnect car -> out of service
Effect is the same on both boxes

[thokaro]

The same behavior as with my P30 PV-Edition and firmware version 2.0.0

[691208]

I don’t know if this is new in FW 2.0.0 and don‘t rememder the setting before updating

P30x web ui -> System -> Modbus TCP Settings
Modbus TCP Port: 1502 (I am not able to change to 502)
Description: The port to connect to the Modbus TCP server

[lgusewski]

I can confirm that the setting is 1502, but it is deactivated, and my EVCC communicated with the P30 X. I did not change anything in my YAML file for EVCC between the update from version 1 to version 2.

[MikeTheTux]

On the KEBA KeContact P30 x-series, Port 1502 is used for internal communication within a KEBA charging network (Master-Client setup), rather than for general Modbus TCP communication with third-party systems.

Purpose in the Charging Network

• Internal Communication: In a local load management system, one wallbox acts as the "Master" (x-series) and coordinates up to 15 "Client" (c-series) wallboxes. Port 1502 facilitates the internal data exchange required for this coordination.
• Separation from Standard Port: The standard Modbus TCP port is 502. Using 1502 for internal master-client tasks helps isolate this traffic from external system integrations, such as Smart Home servers.

Configuration Guidelines

• Standard Modbus TCP: If you want to connect your wallbox to an external energy management system (HEMS) or a Smart Home server, you should generally use the standard port 502.
• Master-Client Setups: Port 1502 is used automatically when you combine several KEBA P30 units into a local load management cluster.
• Requirements: For any Modbus communication to work, the interface must typically be enabled via DIP switch DSW1.3 (set to "ON").

[691208]

Thanks for the additional information. But for the moment I found no solution, also other users are reporting same issue. Hope Keba will fix it very quickly

[691208]

Just to double check, after installation of FW 2.0.0 the following SW components are shown at the P30x
Component Version
CPM 4.19.5
KEEP 5.10.0
OS 4.19.5
WEBUI 4.19.5
RESTAPI 2.4.1
PDC 3.10.80

[TobiasHuber1980]

I had a call with Keba; apparently there are problems with the master/slave setup (x-series -> c-series // ladeverbund). Unfortunately, I don't know anything more than that. Therefore, for master/slave setup, updating to version 2.0.0 is not recommended.

[thokaro]

I already informed KEBA's e-mobility support last week via telephone that I have the “out of service” issue. And I only have a KEBA P30 PV Edition running. They should know that it's not only a master/slave setup (x-series -> c-series // ladeverbund) problem.

I can not understand why that buggy 2.0.0 release can still be downloaded and is even being recommended.

[tieskuh]

It looks like they removed the 2.0 update from their website. I already updated to 2.0 and have problems with my charger being out of sync. Anyone found a solution for that or a way to downgrade to a previous version?