I have attempted to migrate a Victron EVCS (that has been in good operation for two years) from using communication via Modbus TCP to using the new MQTT based method but the EVCS does not show up as a device in the GX device.
However from the EVCS side it can communicate with the GX device and get all the data it needs such as SoC, AC inverter load, solar power coming in etc and will run in automode. So it appears the issue may be on the GX device side.
System details
- VenusOS version 3.81 running on a CCGX
- Victron EVCS v1 with no screen running version 2.09
Steps to migrate that I tried
- go to GX device with Remote Console
- Settings → Integrations → Modbus TCP Server
- Disable this as we are moving to using MQTT instead
- Settings → Integrations → MQTT Devices
- tap “Activate”
- Settings → Integrations → Modbus TCP Server
- go to EVCS web UI
- Settings → General → GX Device
- Communication type
- change from Modbus TCP to MQTT
- tap “Discover”
- choose GX device
- tap “Pair”
- tap “Save”
- Communication type
- Settings → General → GX Device
- the EVCS then shows up on GX UI as expected as a paired device in Settings → Integrations → MQTT Devices
- the result is that the GX device does not show the EVCS in the devices list as it should
- in the devices list the EVCS shows an entry but it is not connected, it is like this is a cached version of the Modbus TCP EVCS entry in the device list, like that MQTT based on is unable to show up because the Modbus TCP based one is there blocking it?
- things I tried
- reboot GX device
- reboot EVCS
- remove the disconnected EVCS entry in the devices list via the popup option that shows up
- remove MQTT pairing
- start again
- none of these things worked, the device list always did not show the EVCS