Error When Updating OL Connect Automate

[Sharne]

Hi,

I see Automate is now at version 1.0. (Last forum notice was “New release: OL Connect Automate 0.9.19”). When trying to update it I get the following error:

2025-11-27T13:11:01.168Z Install : @objectif-lune/node-red-contrib-connect 1.0.0

2025-11-27T13:11:01.429Z npm.cmd install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @objectif-lune/node-red-contrib-connect@1.0.0
2025-11-27T13:11:10.053Z [err] npm
2025-11-27T13:11:10.055Z [err]  WARN config production Use `--omit=dev` instead.
2025-11-27T13:11:22.318Z [err] npm
2025-11-27T13:11:22.319Z [err]  ERR! code EBADENGINE
2025-11-27T13:11:22.320Z [err] npm
2025-11-27T13:11:22.320Z [err]  ERR! engine Unsupported engine
2025-11-27T13:11:22.320Z [err] npm ERR! engine Not compatible with your version of node/npm: @objectif-lune/node-red-contrib-connect@1.0.0
2025-11-27T13:11:22.320Z [err] npm ERR! notsup Not compatible with your version of node/npm: @objectif-lune/node-red-contrib-connect@1.0.0
2025-11-27T13:11:22.320Z [err] npm ERR! notsup Required: {"node":">=20.19.5"}
2025-11-27T13:11:22.320Z [err] npm ERR! notsup Actual:   {"npm":"10.1.0","node":"v20.9.0"}
2025-11-27T13:11:22.321Z [err] 
2025-11-27T13:11:22.321Z [err] npm 
2025-11-27T13:11:22.322Z [err] ERR! A complete log of this run can be found in: C:\Users\xxx\AppData\Local\npm-cache\_logs\2025-11-27T13_11_10_003Z-debug-0.log
2025-11-27T13:11:22.338Z rc=1

This error occurs on my laptop but when updating Automate on my PC running Workflow etc., it updates fine.

Please advise.

Regards,
S

[Erik]

Hi Sharne,

I suspect the issue is caused by your system running an older version of Node.js (likely from an OL Connect Automate beta installation). I’d suggest downloading Node.js v20.19.6 (LTS), which is the version officially recommended for Node-RED: Node.js — Download Node.js®

Install it in the following location (which is the default path for OLCA):

C:\Program Files\Objectif Lune\OL Connect Automate\nodejs

After installation, the version should appear in the OLCA Prompt. If you want to verify manually, run the following command in a command prompt: node -v

Hope this solves things for you,

Erik

[Sharne]

Hi Erik,

That made it worse. Now Automate refuses to load. When selecting “Start Node-RED service”, in task manager I see:

But in Task Manager Services it’s paused and wont allow me to start:

If I select Open Services and stop Node-Red, then restart I get this error:

I did try uninstalling Node-red and reinstalling to no avail.

Regards,
S

[Erik]

Hi S,

Could you run the following test.

1. Start CMD as administrator and navigate to the following directory:

C:\Program Files\Objectif Lune\OL Connect Automate\node-red

2. Run:

node-red --settings "C:\ProgramData\Objectif Lune\OL Connect Automate\settings.js" --userDir "C:\ProgramData\Objectif Lune\OL Connect Automate"

[Sharne]

Hi Erik,

Been a bit busy. I ran the command and get the below error.

Error loading settings file: C:\ProgramData\Objectif Lune\OL Connect Automate\settings.js

There is no settings file there but there are other directories: nodejs, node-red and nssm.

Regards,
S

[Erik]

That doesn’t sound right, these I would expect in:

C:\Program Files\Objectif Lune\OL Connect Automate

So in Program Files not ProgramData. Do you have any OLCA related folders in Program Files? It is a bit hard to tell from a post and I cannot judge the setup of your environment but perhaps it makes sense to delete the folder in ProgramData and in Program Files and try a reinstall. I suggest to keep the default locations from the installer and validate the above folders after the install.

In case you already developed a flow make sure to backup your flows.json file and perhaps keep a backup the settings file.

[Sharne]

Hi Erik,

I did as you suggested. Uninstalled Automate, downloaded the 1.0.0 installer, default paths (as before) and get this error:

Not sure what to do about that

Regards,
S

[Erik]

Could you try running the installer again? It looks like there was a Cloudflare outage earlier today.(fyi we are working on an offline installer which does not require an internet connection, no eta yet).

[Sharne]

Thanks Erik, that was the issue. Installed successfully.

Regards,
S

[Erik]

Good to hear!!!

Erik