What is the recommended procedure to upgrade my Atrium Gateway to Node Red 4.1? I am assuming I will need to upgrade node.js as well and wasn’t sure how the Atrium/React will be affected? Also, wondering why this wasn’t done prior, as this gateway relatively new and updated versions have been out for a while? Thanks!
I can look into and test later versions of Node-Red and NodeJS on the Gateway but could you note why you would like to update it?
I have nodes that I need to install from the Palette that require the newer versions.
Any updates available on this topic?
@Jacob can you provide an update on running later versions of NodeJS/Node Red on the Atrium Gateways?
Thank you,
Travis
I’ve created a script to update nodejs and node-red for better compatibility. You will need the Gateway to have internet access and to SSH into the Gateway. If you connect to the WiFi AP of the Gateway you can use this command to do so from powershell on Windows or terminal on Mac:
ssh ncdio@192.168.0.1
You will be prompted for a password which will be the default unless its been changed:
ncdB3ast
Once you’re SSHd in you can run this command and wait for it to complete:
curl -sSL https://raw.githubusercontent.com/ncd-io/NCD-Edge-CR/main/configuration/scripts/update-nodejs-node-red-rebuild.sh | bash
You will be prompted for the password again which will be ncdB3ast again.
Let me know if you have any questions or encounter any issues.
Thank you Jacob, that worked perfectly!
I have a few non Atrium Gateways that I need to do the same updates to. Potentially dumb question, but would this work for them, or would it require a different script?
Hi,
I just ran a single test, but yes the same method works on the Enterprise Gateways. I would say maybe wait til Monday before running it in case there’s an issue it won’t bring a Gateway down over the weekend and we can jump on a call to resolve it. So far though its 100% reliable between both versions of the Gateway, there’s always the concern though that since we grant admin privileges to users there was a user change implemented that could interfere, but its pretty unlikely.
I’ll have to run a few more tests before I change our official update documentation, but I prefer this method as we at NCD have more control over what actually happens during the update.
Awesome, thank you Jacob! I have an extra gateway that I would be willing to test this on, as it is not deployed just yet. Let me know if you come across anything during testing and I’ll send updates as well.
Thanks, Ryan