EVCS options missing in nodered since 3.70

Updated to 3.70 on friday and thought i would just check everything is ok with nodered.

Our EVCS is missing 90% of the options it had before.

There were some regressions in 3.70 that are addressed in the beta and soon to be 3.71.

Just reporting, that the problem mentioned by OP is still present in VenusOS 3.72.

It looks like the state of the configuration/EVCS nodes depend heavily on the state of the charger itself. My observation from the past 24 hours:

  • yesterday, all the EVCS Node-Red nodes reported that the device is disconnected, BUT, it was normally connected and displayed on the Cerbo (in VRM, I could access EVCS web interface, the “connection Check” in the EVCS settings was successful, etc.)
    • I restarted the Node-Red service (from SSH console), and it seems that helped. I have seen what was expected, the device was identified by its name (i.e., EVCS-HQ22…)
  • today, EVCS is charging, and when I open any Node-Red EVCS node, the device is identified by “com.victronenergy.evcharger/40” (see screenshot below), and some (sub-)options are missing:
    • 1 hour ago, I saw only “Start/Stop charging (manual mode)”
    • then I changed the “max charge current” settings via EVCS web interface, and now, I can see also “Set charge current (manual mode) (A)” and “Maximum charge current (A)” (see screenshot below)
  • also, in the “EV Charger node”, there seem to be only ‘Measurements’ that are somehow currently available on the device. I am charging EV via 2-phase charger, and I can see only L1 power and L2 power in the drop-down (not L3 power as I should also). See the Screenshot 2 below.

Soo, something is still “fishy” in Venus 3.72 (NodeRed v4.1.1, @victronenergy/node-red-contrib-victron: 1.6.63 (and it can NOT be updated – the Update button is not wisible, see Screenshot 3 & 4)

I hope this report can help finding the “magic” bug and to resolve it soon.

Screenshot 1:

Screenshot 2:

Screenshot 3:

Screenshot 4:

This happens when you originally installed some packages manually.
Most, if not all, of this is fixed in the current beta.

I am not aware of installing any node-red packages “manually” :thinking: I have installed a few packages via “Manage palette”, as I believed this is expected way howto get additional plugins in. Also, I can remember that, for example, the @flowfuse/node-red-dashboard offered the “Update” button on the palette when there as an update in the repository.

So, what advice would you give to fix it?

  • is there any procedure I can do?
  • or shall I wait until Venus OS 3.8 is out, and that would fix the situation automatically?

Thanks a lot for any advice.

The beta should automatically fix the issues. No idea when it is GA.

When will this be fixed? 3.73 and the evcs is still constantly offline in node red.