I have installed the last beta version, and I see that the dynamic ess stats flow is not working any more. I’m using it to read out the actual energy price.
Update from my side, installed the last 3.60-48 beta, and stil not working. When I switch back to the stable version it works like it have to.
Some one have a solution for it?
1 Like
Oddly ~46, ~47 & ~48 work as expected on my older Cerbo-S, but a new Cerbo MK2 throws a fit when a node red dashboard is opened. Had it drop wifi and won’t reconnect or even locate the ssid without a reboot. Also on ~46 it won’t connect to TCP-IP device that the Cerbo-S can, haven’t tried the latest yet. Strange, glad I kept the box.
EDIT: attempted to update the new Cerbo MK2 to 3.60~48 and it never came back on the network. I can get to it with Connect on BT. Update failed, it’s still on ~46, and it can see the wifi network but will not connect.
Tried loading 3.54 large and failed to change, same network issue too. I think it’s dropping the network along the way and can’t finish the updates. This is a new device to me which makes it hard to tease out hardware from firmware issues. Loaded 3.54 large from USB, node red & UI work as expected.
Similar issue for me on ~46. Reverted to 3.54 and that fixed it. I just tried to update to ~48 and it failed. I started it again (wouldn’t have if I would have seen your post first) so we’ll see. I like living on the edge 
My older Cerbo-S works fine on ~48, the new MK2 version will not. You can force feed it on USB, but it doesn’t run properly after.
Update. I ended up finishing an upgrade to 3.60~48.
When I open Node-RED now, I get a login screen…
The login button doesn’t work. I’m pretty sure the VRM portal is supposed to bypass this credential screen, but I also did just put a SSH password on the Cerbo, so I suppose it’s possible it has something to do with that.
I tried restarting the Cerbo, but that didn’t help.
I tried logging in directly to Node-RED using :1881, but the same login prompt comes up and no known credentials work.
Next step might be to reset Node-RED, but I hesitate because one of my flows is not backed up, so I’d have to recreate it.
I figured out how to backup my flow by SSHing to my Cerbo and SCPing the flow* files from /data/home/nodered/.node-red folder to my local PC. I then reset Node Red and had high hopes of running it again, but no cigar. Same login screen with the prepopulated VRM credentials that don’t work (“Login failed”). Sad day.
I tried a couple more things but am ready to give up for the day.
I tried manually restoring a default Node-RED settings file from /usr/lib/node_modules/node-red/venus-settings.js to the /data/home/nodered/.node-red/settings.js but that didn’t help. I think it was defaulting to that settings file anyway when it didn’t find one in /data/home/nodered/.node-red.
Also tried multiple Node-RED resets and restarts and running Node-RED in safe mode.
I don’t want to stay on 3.60 without Node-RED, so I’m going back to .54 for now.
– later –
Rebooted back to 3.54 and was dismayed to discover that Node-RED still wants credentials to login. Tried another Node-RED reset, but that didn’t help. I suppose the next step to actually get Node-RED working (unless someone else knows another trick) is a full factory reset of the Cerbo, but I think I’ll go back to the beta (since NR doesn’t work in 54 anyway) and wait for a fix.
I wondered if Node-RED might be prompting for a credential due to some security setting I enabled, though it seemed unlikely. I turned on the Network Security profile and I went to superuser and set an SSH password so I could remote to the device. I tried anyway to turn off Network Security Profile and surprisingly it did have an effect. It didn’t totally let me into Node-RED, but it rendered the UI and even went through the welcome tutorial, but it still showed the login screen and wouldn’t let me do anything until I log in. After a bit of time typing up this recount though and then flipping back to the UI, the login dialog had gone away! I’m back into NR!
I could stay here, but I strongly suspect it was because of the Network Security Profile, so I’m going to go back to the beta (3.60~48) and see if it works with NSP turned off.
In Venus OS when you set “Network Security Profile” to secured you chose a password for this. This then requires a login for Node Red. The Node Red username is “admin” lower case and the password is what you chose for your “Network Security Profile” password.
At least that is how mine works, no SSH password set.
Aha! Thanks so much. I’m sure the admin username is documented somewhere, but I haven’t come across it. I’ll play with turning NSP back on and using that for credentials. Thanks so much, @pwfarnell.
That is documented here: Venus OS Large image: Signal K and Node-RED [Victron Energy]
Awesome. Thank you.
~49 still doesn’t start node red properly. Loses connection to the NR server, UI is unreachable.
The same flow appears to operate in an older Cerbo GX, but not in a new MK2 version. It does operate properly with production firmware.
@MiPaul Do you mind sharing the vrm id and enabling remote support on the device so I can check what the cause is? (you may do that in a DM too).
Yes I can do that. I need to go out and do a power cycle to bring it back online.
Over the weekend I migrated two of my installs (a Cerbo classic and a Pi3 running VenusOS beta) to a new Cerbo MK2 setup so I can’t do a quick test with those right now 
@dfaber I don’t see how to do a DM, what am I missing?
I’m happy to help test this since I saw the same thing @MiPaul did on both 3.60~46 and ~48. Last time I tried to update to ~48 though it kept failing out of the upgrade. I’m sitting quite happy at 3.54 right now, but am willing to try an upgrade to ~49 if it helps solve the problem.
1 Like
After the 49 version update I was hoping that the node red vrm-api also was working again, but it doesn’t. Will it be fixed in the future?