I may need to update NR on my 3 RasPis.
They have NR 3.0.2
They need 3.1.5 so they are the same version as this machine.
Sorry, how would I do that?
Run the official installer script
But won't that install the latest version?
I don't do this enough to confidently do it.
Sorry.
The script supports parameters one of them being --nodered-version e.g script --nodered-version="3.1.5"
Although not sure why you wouldn't go with latest (4.0.3) or even the latest 3.x which is 3.1.12!
I agree so much.
But I fear (correctly or otherwise) that incompatibilities will creep in.
I don't want to move stuff between machine and have problems with versions.
And in light of the other thread: I'm not sure I need to update.
But I'll keep it in mind if I do decide to update.
Incompatibilities are often due to leaving it too long.
Neglecting for a minute the security issues and bugs that have been fixed since 3.1.5 was released - if you are going to the efforts of updating, go to the latest. Get ahead of the curve. Don't choose an older version because (tightly out wobbly etc) ....
Remember this: when you update node-red you aren't just updating node-red you are updating hundreds of dependencies. Many of them have security issues and bugs that have been fixed.
1 Like
Yeah, you are right.
And I am (maybe) being stubborn.
Just I have had this code which I THOUGHT worked for years.
For reasons unknown it is starting to fail and I am getting a lot of alerts which are not real.
I am sitting down rewriting a LOT OF CODE on the big machine - testing it.
It looks good but when I move it to the other machine/s it doesn't.
I would like to get this problem resolved - bad/poor programming.
Hey, I'll cop it. I'll put it down to not really understanding what was happening and my poor testing.
As you see I have a few threads open as I am being blind sided by these ..... idiosyncratic things that I can't see the cause for them failing.
Not sure where you are at on this Andrew - i think your main machine is a Windows PC ? If so - look at one of the Virtual Machine managers and setup a couple of Virtual Machines on there - then move your code through each virtual machine and test it on different versions of Node Red to see if amything obvious breaks - this is the way i do it.
Clone the existing production machine, Change its IP to something new and disable all Input/Output (so it can not affect any live systems) (i have all my MQTT in/out nodes on a single page linked to everywhere that uses them so i can simply disable that flow and all MQTT traffic is stopped)
I then upgrade that new VM to whatever version of NR i want and check if all the nodes work OK - if not i can remediate until finally ready to test in production.
Craig
If you distribute to devices that are running Raspbian, I would also develop on a similar
Hey Craig.
No, the main machine is a NUC with Ubuntu 22.04
I once did have a VM on this but disc space kinda killed it. 
500GB only goes so far.
You really only need 20GB (or Less) for a headless VM for NR
Craig
Ah, 20 gig. 
Ok, I have 40G free just now.
But that was after a lot of cleaning up.
Thanks. But....
Just now I am out of my depth with these weird things happening to me.
(See other threads)
I won't go on about it, but it is really confusing.
