search

evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
3.39k stars 619 forks source link

Resend charge current setpoint after Modbus connection is restored #16487

Open busyb-now opened 2 hours ago

busyb-now commented 2 hours ago

Is your feature request related to a problem? Please describe. I use a Vestel EVC04 wallbox together with evcc via Modbus communication. Because the network connection to the garage is a bit unstable, there are i/o timeout messages in evcc from time to time. During and after a connection interruption, the wallbox continues to run with the “fail-safe current” configured in the wallbox. I have currently set this to the minimum current of 6 A. My problem: Even after the connection is restored, the box continues to run at this fail-safe current. This is particularly annoying in the "Fast" and "PV" modes until the configured minimum charge level is reached. In these modes, evcc presumably only sends the charging current setpoint to the box once and expects the box to continue running with this current until a new setpoint is sent.

Describe the solution you'd like Is it possible to extend evcc so that the last setpoint sent to the wallbox is sent again after a lost connection is restored? With a stable connection, this should never happen and therefore not cause any restrictions. With my unstable connection, however, this would prevent the box from getting stuck on the wrong current setpoint.

Describe alternatives you've considered I have tried other settings for the “fail-safe power” setting in the wallbox. At 0 A, the car aborts the charging process completely after a few connection interruptions and thus charging interruptions. At 16 A, the proportion of energy erroneously not charged from PV increases because, for example, charging is carried out at full power from the grid for 3 minutes at night when the connection is interrupted.

Additional context Furthermore I would be happy about every hint on how I can make evcc more tolerant to connection interruptions. evcc-20241003-215727-debug.log evcc.yaml.txt

andig commented 2 hours ago

Evcc does not „see“ this connection los. If setpoint current could be read that could be used to verify. In general, you‘ll need to fix the root cause- unstable network.