If I reboot the Cerbo, most of the times, my node-red flow for the EVCS ends up with unavailable nodes. Path does not exist. For only 1 of the 2 EVCSs. If I remember correctly it’s always the first EVCS.
All I need to do to fix it is disable node-red, wait for a bit and start it again. All “unavailable nodes” will come to life and the flow works like it has for over a year now.
I did not experience this issue < 3.60 but am not sure which beta release introduced this behaviour.
I haven’t seen that behaviour before, so that will needs some investigation to reproduce. Mind enabling remote support or sharing your flow so I can take a closer look at what might be causing this?
Remote Support enabled.
Cerbo is very busy right now keeping all consumers safe so cannot reboot.
I did the install of the latest beta this morning. And I also needed to stop and start node-red again right after. So the logs from this morning should still be fresh. The nodes that are failing are from the EVCS NS01 nodegroup on the EVCS Dual tab:
NS01_ChargeCurrent
NS01_Status
NS01_Mode
NS01_StartStop
All from the Victron EV Charger node.
Thanks. Unfortunately the logging isn’t showing anything that might give me a clue, so this will need some more digging to get reproducible and fixed.
I will find some time later tonight to reboot. First figure out if behaviour is consistent every reboot or only happens during an upgrade to a new beta.
One thing is certain. I did not experience this before 3.60 beta series. And I have been using this particular flow for a long long time to control priority between the 2 chargers and between the chargers and DESS charge windows.
Reboot. All still good. Will wait for next beta, update and report back in this thread.
Applied most recent beta, all still good. Apparently it only happens 2 times 
Will continue monitoring. May be related to unavailability of the EVCS during reboot of the Cerbo or some other corner case.
Can you update to 3.60~80? That might very well fix that for you.
In that case it’ll have to wait for the next round of beta’s. I like the new switches, have no issues, and an update will remove them. Will stop and start Node-Red till then.
So will post my results once the new beta round will be released.
@sega: Mind enabling remote support so I can take a look at what is causing this?
