After updating to v3.60 71 my Nodered installion is not accessable any more
Error: remote installation does not seem to have a running Node Red service.
All Setting s are ok - going back to v3.60 69 it works
Which dashboard version are you running (if any) ?
I just updated my Labo Pi3 to v3.60~71 and NodeRed runs just fine.
Hi All,
Just to confirm. I have exactly the same problem as Dirk. No node red for version 71. It is running on a Cerbo GX on a boat so do not have (D)ESS. Back to 69 and all ok.
Note 1: I also have a raspberry PI upgraded to 71 and runs perfectly.
Note 2: No GUIMods or something like that. Add-ons modules (Tailscale etc) are the same for the Cerbo and PI and work on both in 71. Just Node Red is not available at all on the Cerbo.
i´m using guiv2
Alex, did you have any of the new virtual devices in your flows?
When I switched to ~71, back to ~69, then back to ~71, I lost dark mode on both of my Cerbo.
Paul, no I do not have any virtual devices in my flows.
I want to in the future with the Virtual Switch but not in there yet.
I do not know why you lost Dark mode, I have a test Pi running ver. 71 in Dark mode and works perfect on remote console via VRM. By the way this Pi does include the Virtual Switch device.
Thanks, I see we both lost node red going to ~71. Maybe it doesn’t like one of my palettes?
Switching back to ~71 from a previous version triggered the loss of dark mode.
EDIT: Factory reset node red, installed palettes, imported flow. Lost connection with the NR server right after deployment. I feels like a ~71 issue.
EDIT:
Cerbo GX HQ2044 Node red okay, virtual switches work. Although loss of NR switch control after manually moving the switch issue persists to ~71.
Cerbo GX-S HQ2225 factory reset Cerbo to get dark mode back. Factory reset NR, simple flow kills the NR server. No external mods. ~71
Hi,
Just installed 3.60~71 on my various devices :
Ekrano GX => Node RED OK ! Started and Dashboard OK
Cerbo GX MK I => Node Red not started/unreachable
Venux GX => Node Red running.
Xabi.
Same issue as others with Node red, “This installation does not appear to have a Node-Red service running”. Cerbo mk1, Node-RED as it comes with Venus OS, no mods. I went back to ~69 removed the virtual switch and batteries then swapped back to ~71 and Node-Red would still not work.
Hi,
just updated a Venus GX => Node Red OK, but not tested the Ve-direct with this installation.
Did the ve-direct lost has been corected too ? (If yes, I can updae an other Venus GX device with ve-direct used )
Xabi
Quick reminder to those reporting bugs:
- Please specify on what hardware you are running Venus OS (since the latest Node Red bug seems to be hardware specific)
- Please create a new topic to report your bug or reply to / upvote an existing topic if it describes (roughly) the same bug you’re experiencing.
Thanks !
2 Likes
Hi,
I do not test on my Cerbo GX MK II as this RV is far from my actual place and do not want to be in trouble 
For the other device I use to have, Venus GX & Ekrano GX who are OK !
Xabi
Same behavior on my cerbo ugrading from v3.60~60 to v3.60~71.
Reverting to v3.60~60 brings node-red back to life.
running on Cerbo on New UI.
Can you share a vrm id (the number in the url) on a system that isn’t starting Node-RED and enable remote support, so I can take a look at the actual cause (and fix it)?
Message sent
It seems to be caused by flows writing to services that don’t (yet) exist, which doesn’t get properly caught by the system. Figured that out by looking at the system of @pwfarnell (thanks!).
This is a side-effect of removing the polling of the dbus, but not too hard to fix. I’ll make a new version of the node-red-contrib-victron code now and have it part of the next beta.
Meanwhile, you could either stick to ~69 or start node-red in safe mode and disable writing to non-existing services (e.g. a switched off inverter).
A post was merged into an existing topic: Venus OS v3.60~71 available for public testing
Hey all, this is fixed per the latest beta version.
Can you confirm that it works ok for you?
The changes made recently were the last large planned changes to Node-RED: it would be great if it can be tested as much as possible - so its asap stable and ready for release.
Further expected changes still worked on for v3.60 are mostly related to the new virtual switch feature.
in my case Nodered is working with v3.60 72 now but the naming and grouping will not be kept after reboot
2 Likes
Yes, Node-RED restarted OK even with the inverteroff which caused the previous problems, but as noted elsewhere settings on virtual switches are not retained on reboot.
1 Like