Vestel Firmware Update

0 views

Skip to first unread message

Paz Warsager

unread,

Aug 20, 2024, 12:21:21 AM8/20/24

to blasrapumang

Avoid bricking the device
Ensure that you're operating with the correct firmware version and it's compatibility to its respective models via Vestel Tech team before proceeding, as the wrong firmware for a model can brick the device.

The modbus TCP manifest from vestel wallbox states the following:
Vestel EVC04 charging station acts as a slave device in the Modbus TCP/IP communication. Charging station should be in the same network with the master device or a proper routing should be applied to provide communication between slave and the master devices in different sub networks. Each charging station should have different IP address. Modbus TCP communication port number is 502 and Modbus Unit ID is 255 for Vestel EVC04 charging stations. There can be only one active Modbus master connection at any time.

vestel firmware update

DOWNLOAD https://oyndr.com/2A3fzC

Hi, I have also a Webasto Unite and will give your Modbus sensor template a try asap. I believe if you have activated modbus in the Unite Web Gui and the keep alive register is not triggered every X seconds, the max. Charge Power will be limited to 6A/4,2kW for grid safety/overload protection reasons. This in conjunction that the Wallbox Modbus connection is used (enabled) either for Loadmangement purposes, e.g. by external EMS/HEMS Systems in case several Wallboxes are combined to one bigger charging station cluster, or for PV-Surcharge charging. In case the EMS fails, charging power will be limited automatically due to the missing keep alive trigger, normally/frequently send by the EMS.

Hi, I have inserted your code into the configuration.yaml and restarted the Home Assistant but my Vestel EVC04, which is connected via a network cable, is not recognized as a device although I have activated Modbus TCP on the Vestel EVC04. Do I have to do anything else besides inserting your code into the configuration.yaml?

In my situation I have an automation that handles the keep alive (and functions correctly, proven by no diconnect logs). But all values read zero.
Maybe the configurations matters/ My Webasto Unite uses:

I have DLM enabled as follows:
image1379612 61.5 KB
This is generally named DLM, but is technically called Power Optimizer in this wallbox.
I still see that the wallbox is reading the energy meter (as RX/TX is still shown on the Garo).