Help with how to update form NR 1.0.3 to 4.x and all other stuff

General
1

Folks, I am about to set off on a journey of getting 1.0.3 to 4.x

So the node.js and npm will also need to be updated.

I thought I had documented the required things, but....
Sod's law: I need the information, I can't find it.

Could someone please help me.

O/S Ubuntu. (Old) 18.04
Thanks in advance.

2

As it is Ubuntu, just run the pi install script with --node20 or --node18 at the end of it and you will get latest node-red with node version of your choosing.

1 Like
3

Alas I have to update the O/S first. :frowning:

4

Might I suggest that you BACKUP your device before you do anything else.

5

Well, after 4 updates from 18.04 to 22.04 and installing NR 4.x all is working.

I just now have to remember how to install the dark theme.

1 Like
6

Wow, the bright screen!

My eyes are burning.

I run midnight red theme on the existing machines.

Alas that has sort of been retired.

I see a node with themes

But it won't install.

Some crazy error.

But I see a lot of dashboard 2.x mentions.

So, I'm stuck.

Do I just unintall the existing original dashboard and then install dashboard 2.x?

EDIT

This is the error as best I can give it.

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: node-red-contrib-ui-led@0.3.1
npm error Found: node-red-dashboard@2.19.4
npm error node_modules/node-red-dashboard
npm error   node-red-dashboard@"~2.19.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer node-red-dashboard@"2.14.x" from node-red-contrib-ui-led@0.3.1
npm error node_modules/node-red-contrib-ui-led
npm error   node-red-contrib-ui-led@"~0.3.1" from the root project
npm error
npm error Conflicting peer dependency: node-red-dashboard@2.14.0
npm error node_modules/node-red-dashboard
npm error   peer node-red-dashboard@"2.14.x" from node-red-contrib-ui-led@0.3.1
npm error   node_modules/node-red-contrib-ui-led
npm error     node-red-contrib-ui-led@"~0.3.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and pote...

(What's happened to the copy function in the debug window/list?)

Screenshot from 2024-06-28 20-58-58
Screenshot from 2024-06-28 20-58-581920Ă—1080 426 KB

7

Looks like not everything is yet updated. Maybe use a command line to:

cd ~/.node-red
npm install node-red-dashboard@latest

Then restart Node-RED and try to update node-red-contrib-ui-led again.

1 Like
8

In progress.

What has happened that I can't copy the debug output any more?

9

SOLVED!

Thanks.

But I'm not sure that is the end of this set of problems.
Mind if I keep this thread open?

10

Of course not. That's what the forum is for. :slight_smile:

11

Um, it's not working.

The node installed, but when I did what I read as what I needed to do, NR won't relaunch.

Hang on, I'll go to the other machine and reply from it so I can show you what I did
:wink:

Ok, the docs for the theme have this part:

editorTheme: {
    theme: "midnight-red"
},

So I open the settings.js file and....

    // Customising the editor
    editorTheme: {
        theme: "midnight-red"
        projects: {
            // To enable the Projects feature, set this value to true
            enabled: false
        }
    },

I'm not sure if I should leave all that other stuff within the { } block.

ARGH!

Sorry. I missed the , at the end of the line - yes?
(Trying anyway)
Yeah, working now. Sorry. Silly me.
Now I'll try to get my head around how to use uibuilder and actually get to work on the actual project.

1 Like
12

Re uibuilder.

Install uibuilder. Go to the Node-RED import, examples, uibuilder and import the "Simple" example:

image
image769Ă—340 20.3 KB

Open the uibuilder node with the red triangle and give it a url.

Click Done and then deploy.

Reopen the node and click on the "Open" button to see the page it has created for you..

Now play with the triggers and then go from there.

1 Like
13

Thanks.

Am about to get there.... :wink:

Got (accidentally caught up with the VNC stuff.)
That is now resolved - kind of / mostly.

14

I'm not understanding something there.

The URL..... So google.com?

I'm not seeing anything on the dashboard side of things.

15

Which URL?

The "url" in a uibuilder node is effectively its name.

If you have a uibuilder node with a url of "test", and your Node-RED instance exposed its D1 page on http://localhost:1880/ui then your page would be on http://localhost:1880/test.

When you don't provide an html file name, the system automatically uses index.html so the full url would really be http://localhost:1880/test/index.html, you just don't need to supply the index file, looks a bit neater.

The uibuilder url is also used as a folder name for the files that are used, so in this case:

cd ~/.node-red/uibuilder/test/

~/.node-red/uibuilder/ is referred to in the documentation as the uibRoot folder and ~/.node-red/uibuilder/test/ is an instance root folder.

1 Like
16

Thanks.

But when I put / it complained that I can't use them.

Screenshot from 2024-06-28 22-07-10

Or am I being too literal?

Ok, saw/got the edit.

Shall try that.

17

Yup! Just put "test" in there. Node-RED and uibuilder work the rest out between them. There are other things that Node-RED or uibuilder may do that might alter the full url.

18

But the first line really throws me.

Cannot contain /

Yeah, sorry... I'll make the test directory and see what happens.

So that is the .node-red/uibuilder/test directory.....

I've made that directory but that warning won't go away.

1 Like
19

a / in a url indicates a sub-location. uibuilder does not let you specify that at the node level. However, you CAN create sub-locations - lets save that for another time though.

20

Confusion overload this end.
(But what's new?)

Back in your post #15.....

I am not seeing what I put in the uibuilder node when it wants a URL.