EVCS - repeated occurrence of incorrect values over MQTT

[motylu]

Hello,
I am running Home Assistant on RPi and use it for collecting data, controlling and doing automations - heat pump (over eBUS using data converter eBUS/USB and integration eBUSd), IP cameras, … , and also Victron PV system with EVCS (over MQTT).

After upgrade to the latest Venus OS v3.42 on Cerbo GX and EVCS to beta FW v2.00-beta-04, I see repeated occurrence of incorrect values related to EVCS over MQTT from Cerbo GX on daily basis. Sometimes over night but today also during charging over day.

Mode and status is defined in HA like this:

And repeatedly mode and status are suddenly set to “Unkown” state for a while and then back to previous value. But not only mode and status, but more parameters related to EVCS - set charging current for manual mode, counter for charged energy to EV and others…

Has anyone experinced the same behaviour?

[motylu]

Still the same behaviour with final EVCS FW v2.00.

I will see after update Cerbo GX to the latest FW v3.50.

[Nicolas]

Hi @motylu. Please check EVCS-Modbus-TCP-register-list. You can find it here EV Charging Station NS - Victron Energy . It seems you have to extend the definitions of statuses and modes in HS as EVCS has new ones.

[motylu]

Hello @Nicolas , I don’t have NS version of EVCS, but TCP registers should be the same I suppose for both EVCS versions.
Below is definition for status in HA. It seems that is complete according to excel sheet.

    value_template: >
      {% if value_json.value == 0 %}
        Disconnected
      {% elif value_json.value == 1 %}
        Connected
      {% elif value_json.value == 2 %}
        Charging
      {% elif value_json.value == 3 %}
        Charged
      {% elif value_json.value == 4 %}
        Wait for sun
      {% elif value_json.value == 5 %}
        Wait for RFID
      {% elif value_json.value == 6 %}
        Wait for start
      {% elif value_json.value == 7 %}
        Low SOC
      {% elif value_json.value == 8 %}
        Ground test err
      {% elif value_json.value == 9 %}
        Weld. contacts err
      {% elif value_json.value == 10 %}
        CP test err
      {% elif value_json.value == 11 %}
        Residual current
      {% elif value_json.value == 12 %}
        Undervoltage
      {% elif value_json.value == 13 %}
        Overvoltage
      {% elif value_json.value == 14 %}
        Overheating
      {% elif value_json.value == 20 %}
        Charging limit
      {% elif value_json.value == 21 %}
        Start charging
      {% elif value_json.value == 22 %}
        Switch to 3 phase
      {% elif value_json.value == 23 %}
        Switch to 1 phase
      {% elif value_json.value == 24 %}
        Stop charging
      {% else %}
        {{ value_json.value }}
      {% endif %}

Under EVCS mode I know, that “Scheduled” mode is missing in definition, but this mode I don’t use…

From yesterday I am on the latest FW v3.50 in Cerbo GX without problem for now. But very suspicious is that problem is related only with EVCS data - mode, status, set charging current, … Another topics on MQTT from Cerbo GX related to another devices (Multis, MPPT, …) are not affected.

[Vilcek]

Hi @motylu quick question, did you find out how to read date from MQTT for grid return from multiplus? I am not able to do find it and then import to HA

[motylu]

@Vilcek , I don’t know what you exactly mean. Do you mean information about actual power fed-in back to grid?
Lots of info is described on github here: https://github.com/victronenergy/venus/wiki/dbus, and also best for this is to use MQTT Explorer for deeper investigation :–)