with the latest beta the problem with the EVCS (NS) still exists.
–> The device is no longer available via the stored service path. Please (re)select the device from the dropdown and deploy again.
Measurement is gone and also not selectable.
Have you tried deleting the EVCS node from the flow and dragging a new copy in ?
This refreshes some cached information and maybe a changed instance ID.
Needless to say the EVCS should be connected to the network and recognized by the GX before it can be used in Node Red.
The file system is RO. Same on v3.65. I assume this has been RO with all previous releases as well. So, count his one as a user error (PEBCAK) on my side…
v3.65 is up and running. So far, so good.
Root filesystem should always be RO.
If I’m not mistaken a VenusOS version was released where it accidentally wasn’t, but that was an exception.
Maybe you just happened to be on that one.
Enabling SuperUser mode and setting a root password normally should remount the root filesystem as RW by the way.
If you’re using a public key for SSH login, then this isn’t needed.
Yes, PEBCAK. No problem.
And no Venus OS version was released by accident where that wasn’t the case, @BartChampagne , you’re referring to another device, Venus GX where it was never read only, by mistake indeed, but pretty harmless, until recently.
Anyway: back to v3.65, thanks for installing that and looking forward to hear your results. Next week Monday we’ll have the first go / no-go moment wrt official release for v3.65. Lots of testing was done on Node-RED internally.
And, for some reason, looking at this thread, the amount of people that ran into this Not connected to D-Bus error, or any other Node-RED issues on v3.64, for that matter, is quite low. Number of systems out there running Node-RED is huge 
!
1 Like
Then that might explain it. I started out with ssh using username/password. Later (hours, not days), I switched to public key. The file system was already set to RW by then.
I do see that it isn’t working correctly on your system. Not sure (yet) on the cause. I was suspecting the #-sign in the custom name of your EV charger, but tested that on another system and that doesn’t seem to be causing problems.
v3.65 is running just fine. No issues for me. :)
Edit: v3.65~3 that is. Running on a Cerbo GX MK2.
1 Like
I know, I know: A product is only ready when it’s ready. 
But… Can you tell us anything? I could really use some extra grunt (cpu and memory and drivespave)