Just upgraded from 2.1.x to 2.2.2 on RaspberryPi using the script on Node-Red site. Upgrade went normally except at the end, I got a message informing me that my settings.js did not match the format of the new settings.js format located in /usr/lib/node_modules/node-red/ folder. After inspecting a…

I've just bumped up your level so you can try uploading the settings.js file BUT before you do, try starting nee-red with node-red --safe and see if it starts. It's possible you have a syntax error in the file.

[image] GasTurbineMan: I made the needed changes in the new settings.js You don't need to make any changes. The message is to inform you that there are additional features in the new source file. Did you get the impression from the message that it was necessary to update it? I believe the …

@Colin , you are correct in the exact message I was given. It is just after I examined both old and new settings.js files that I thought the prudent thing to do would be to get my settings.js file closer to the current default file. If you are implying that my old settings.js file is still OK, then…

Your old file should be fine. The purpose in adding the new options is just in case you want to enable the new features. I would have expected the new stuff to be mostly just comments. Can you post the output of the diff command?

I see the problem, because the settings file was completely re-organised recently the diff is not much short of useless. What would be more useful would be to be able to see the changes one has made to settings.js in order to apply them to the new file. @dceejay I am not sure the message as curren…

indeed - folk asked to to be told if they were out of date... so i have done that... I don't know of any automatic diff way that can handle a complete re-org - apart from telling people to go read the upgrade readme/change log... and we know how good people are at that...

ORIGsettings.js.txt (13.0 KB) NEWsettings.js.txt (20.0 KB) Attached are my ORIG and NEW settings.js files. Agree most lines are commented out in both files; however, there is something in the NEW file that is preventing my flows from loading. I will look at the change log to see if I can figure …

Perhaps it would be better just to tell users about the fact that there is a new version and tell them where it is, but also that there is no need to do anything if they don't want to.

Ahh finally you provide what I asked for. You have two lines: flowFile: 'flows_RPi4b.json', and nodesDir: '/home/rgl/.node-red/node_modules', that you used single quotes. Change them to double quotes and see if it works. And make sure they are not ‘smart’ quotes.

Well I thought the warning did just that. The diff just being a way to see them both at the same time. But yes suggestions always welcome

Settings.js issue after upgrading to 2.2.2

General

GasTurbineMan 13 March 2022 19:45 13

Changed single to double quotes as suggested. Same issue. From within the browser, looking at More Tools->Developer Tools I am seeing the attached error.

Flow load error

Topic		Replies	Views
Updating node-RED - settings.js General	12	1504	8 September 2020
Updating settings.js General	5	1369	11 March 2020
Amending settings.js file after NR update General	6	228	9 January 2024
When enabled projects node-red wont start and there is problems with the settings.js file General	10	2052	19 December 2021
Error loading settings file: \Users\kingf\.node-red\settings.js General	17	2165	5 September 2021

Settings.js issue after upgrading to 2.2.2

Related topics