Update Node.js and Node-RED

Updates of the OL Connect Automate nodes are available through the Node-RED palette manager, accessed from the upper right menu.

The following explains how to update Node.js and Node-RED manually, without a new installer from Objectif Lune.

Note: If manually updating Node-RED, we recommend you do not update to a new major version. New major versions of Node-RED may contain changes that affect the operation of OL Connect Automate or OL Connect nodes. New major versions of Node-RED are usually incorporated in the next release of OL Connect Automate. Manual updates of Node-RED to new minor versions (i.e. going from 4.2 to 4.3) or patch releases generally will not conflict with your existing OL Connect Automate version.

Update Node.js

To manually update Node.js:

  1. Download the installer of the latest LTS (long-term support) version of Node.js from nodejs.org.

Note: OL Connect Automate requires at least Node.js 20.19.5 (LTS for Windows). To run Node-RED 5, Node.js 22 is required, and Node.js 24 is recommended/

  1. Delete all files in the node.js folder. This is a sub-folder of the OL Connect Automate folder.

  • By default, the OL Connect Automate installer set the <OL Connect Automate> folder path to:

    \Program Files\Objectif Lune\OL Connect Automate\

    however, during installation, a different folder may have been selected.

  1. Install the new version of Node.js into the node.js folder.

The version of Node.js can be verified from the command line, after installation, through the following command:

node -v

Update Node-RED

To manually update Node-RED from the command line:

  1. Stop the Node-RED service.
  2. Update Node.js if necessary (see note above).

  3. Open the command prompt in administrator mode, in the node.js folder.

  4. Run the following command:

    Copy 
    .\npm install -g --unsafe-perm --prefix "<OL Connect Automate install folder>\node-red" node-red@latest

    5. If you want a specific Node-RED version, replace @latest with @theVersionNumber (e.g., @4.0.1).

  5. Restart the Node-RED service.