EVCS Modbus Issue after Firmware Upgrade to 2.05

Hi,

Long term reader, first post.

I have a 3Ph Victron and Pylontech setup which has been running for a few years. It has not skipped a beat.

About 3 years ago I added a Victron EVCS, linked it to the Cerbo GX and have not had any dramas. I have been using modbus TCP in Home Assistant to comms with both the Cerbo and the EVCS. I use a simple dashboard in HA to control the mode, start and stop the charging and monitor the power usage. I also use the Status register to send a “Car is Charged” notification once complete.

This has all worked seamlessly until I decided to update the EVS firmware today when it popped up on my Victron Connect App. Since then the connection between HA and the EVCS has been constantly dropping offline, and between the EVCS and the CGX it has been even worse. One of the attached pictures shows the 2 comparable entity history in HA showing the drop outs.

The other pictures show 3 of the errors on the cerbo.

  • First error shows the read error from the EVCS .139 when configured as a “saved device” in the cerbo modbus device list. I am not sure why it is trying to read from ID 228 or ID 242, these seam to be VE.Bus ID’s but do not exist on the cerbo Modbus available device list.
  • Second error shows the rear error from HA .102 when trying to read a register relating to the EVCS

On the Cerbo “Devices” page the EVCS constantly changes between being visible and not visible, when it is visible it changes between showing the state and power (W) of the EVCS and “Not Connected”

I have a fully managed UniFi network with reserved IPs, and the network history shows no device drop outs excluding when I rebooted and reset the devices.

EVCS: 192.168.1.139 HA: 192.168.1.102 Cerbo: 192.168.1.140

After a lot of reading I have tried all the following with no success

  • Reboot EVCS, manually re-enter IP and VRM ID for cerbo. When I use the “Check” button about half the time it says OK, half says FAILED
  • Try to use “Discover” button, “No device found”
  • Reboot CGX through web GUI
  • Re-Install Firmware 3.72 on Cerbo GX
  • Factory Reset EVCS and re-configure
  • Manually downgrade EVCS firmware back to 2.0 (last working) and re-configure
  • Full power cycle of EVCS
  • Full power cycle of CGX

Also in case it is relevant, I did notice on my network controller the link-local MAC on the cerbo has changed a few times now with all the reboots.

I’m stumped. Any help would be greatly appreciated.

When I use the “Check” button about half the time it says OK, half says FAILED

WiFi / Router Problems?

Hi,

I didn’t think it was but it might just be that. I read on another post about turning on Enhanced IoT Compatibility mode on my UniFi 2.4Ghz Wi-Fi.

The EVCS has now remained online for an hour since I changed the setting. I’ll see how it goes long term.

Interesting that this only started happening once I did a firmware upgrade?

This is what I found:

https://help.ui.com/hc/en-us/articles/27053048844055-Ensure-Your-IoT-Devices-Work-with-WiFi-7-on-U7-Access-Points

I have found that many older WiFi thingies,
do not connect to my FritzBox7530 Router, when WPA2 + WPA3 is enabled.

Switching to WPA2 only, usually solves this and devices connect without problems
Why? :roll_eyes:

Yeah, I already had a designated 2.4 SSID and only WPA2.

Amazing how much drama 1 tick box has resolved :slight_smile: