We changed it, so the last current limit is repeated every ca. 15sec. Will be in the next Raspberry beta in a few days.

Thanks for the report and advice :-)

It seems that when controlling the VESTEL EVC04 via MODBUS TCP dynamic charging the EVSE always sets back the dynamic charging current limit to 6A (or the other set failsafe value) unless it receives the 5004 register value (dynamic current limit) within the failsafe timeout (reg 2002) which is by default only 20 seconds(!). That makes the EVSE without either prolonging the failsafe timeout or sending the dynamic current value each 20 secs practically uncontrollable by cFOS CM and charging always only with the failsafe current which is 6A by default regardless of how much power is available for the box in cFos Charging Manager. For more details see the discussion in (German) here: https://forum.iobroker.net/topic/53949/modbus-tcp-mit-vestel-evc04-register-etc/3?_=1674029813607&lang=en-GB  Does anyone have a working dynamic load balancing with EVC04 and cFos CM?

Finally I have a working setup. Tried MODBUS TCP connection of CFos CM to the EVC04 Wallbox. It works. Thanks. Needed to start MODBUS TCP server in the EVC04 configuration by enabling Local Last Management:MODBUS TCP. Then it started MODBUS TCP standard port 502/Device ID 255. Of course the Wallbox needs to be connected either by ethernet or through its own WIFI hotspot. RPI with CFos CM is connected to Wallbox's own wifi hotspot and to LAN by Ethernet. In this setup. The EVC04 is still attached to EON OCPP backend {almost useless} by built/in LTE/VPN and to CFos Charging Manager local load mgmt. Thanks a lot for suggestion.

Haven't tried MODBUS connection to the wallbox yet in order to avoid the necessity to open Wallbox and wire the serial lines up to the RPI running CFos CM (which is even currently not easily physically reachable). I am not sure if the EVC04 with this FW runs MODBUS TCP/IP and allows to be steered over it.  Will give it a try. A physical serial connection would be the last resort for me. I would say VESTEL EVC04 seems to be on first sight feature rich a good bang for the bucks, but poorly documented and supported.

Yes, V2.77.0 seems to be the current FW from eon.
Did you try to connect the unit via Modbus.

Yes it's an eon branded unit. The VESTEL technical support does not seem to be available anywhere. The ZSE Drive (eon group member) don't give a ... There is unfortunately no place to download the new FW from.

Is it an eon brand box? Current Vestel fw is V3.57.0.

Ask Vestel-Support for new FW.

EVC04 fw is 2.77.0

Hello, which firmware is installed on the EVC04.

Hi,

FW is 1.15.1-alpha. The same behaviour was under 1.14.4. I attach the log and screenshots.

Thanks

Daniel

Do you have installed the latest Firmware 1.14.6 ?
Could you please provide a diagnose log that records the issue?