That is what I see on my old pc
That is what I get on my new computer:
Top left => no hamburger Icon to use the tabs
Wrong color
in score bord no buttons
If I go to dashboard and change theme, nothing is happening.
In what file is dashboard theme saved? Perhaps it is written in a different map?
what versions are the old and new installations:
| Old computer | New computer | |
|---|---|---|
| NodeJS | ? | ? |
| Node-RED | ? | ? |
| node-red-dashboard | ? | ? |
Are there any errors in the dashboard console?
Try opening editing (but not changing anything) on every item in the dashboard sidebar (be sure to click "Update" button, not the "Cancel" button) - this can sometimes fix-up any nodes that have old/wrong properties - then do a FULL deploy.
old computer
C:\Users\hom assistant mini>node-red --version
Node-RED v4.0.4
Node.js v20.12.2
Windows_NT 10.0.22631 x64 LE
new computer
C:\Users\benny>node-red --version
Node-RED v4.0.5
Node.js v22.11.0
Windows_NT 10.0.22621 x64 LE
now I see there is a difference
do I have to update node-red first on my old pc before I tranfer the files?
No, don't do that.
thats fine. However, since you have an issue with dashboard AND i asked for dashboard version, that is of more interest but you didnt provide it!
Can you get text instead of screenshot?
Use CTRL-SHIFT-P -> system info
what about these...
I did'nt see some errors after deploy,.
This is my old computer
{
"report": "diagnostics",
"scope": "basic",
"time": {
"utc": "Sat, 02 Nov 2024 13:08:00 GMT",
"local": "2/11/2024, 14:08:00"
},
"intl": {
"locale": "en-BE",
"timeZone": "Europe/Brussels"
},
"nodejs": {
"version": "v20.12.2",
"arch": "x64",
"platform": "win32",
"memoryUsage": {
"rss": 104169472,
"heapTotal": 88588288,
"heapUsed": 79379056,
"external": 21336449,
"arrayBuffers": 18524179
}
},
"os": {
"containerised": false,
"wsl": false,
"totalmem": 16946954240,
"freemem": 12387692544,
"arch": "x64",
"loadavg": [
0,
0,
0
],
"platform": "win32",
"release": "10.0.22631",
"type": "Windows_NT",
"uptime": 73692.953,
"version": "Windows 11 Pro"
},
"runtime": {
"version": "4.0.4",
"isStarted": true,
"flows": {
"state": "start",
"started": true
},
"modules": {
"node-red": "4.0.4",
"node-red-contrib-mqtt-broker": "0.2.9",
"node-red-contrib-play-audio": "2.5.0",
"node-red-contrib-ui-actions": "0.1.8",
"node-red-contrib-uibuilder": "7.0.4",
"node-red-dashboard": "3.6.5",
"node-red-node-ui-table": "0.4.4"
},
"settings": {
"available": true,
"apiMaxLength": "UNSET",
"disableEditor": false,
"contextStorage": {},
"debugMaxLength": 1000,
"editorTheme": {
"palette": {},
"projects": {
"enabled": false,
"workflow": {
"mode": "manual"
}
},
"codeEditor": {
"lib": "monaco",
"options": {}
},
"markdownEditor": {
"mermaid": {
"enabled": true
}
}
},
"flowFile": "flows.json",
"mqttReconnectTime": 15000,
"serialReconnectTime": 15000,
"socketReconnectTime": "UNSET",
"socketTimeout": "UNSET",
"tcpMsgQueueSize": "UNSET",
"inboundWebSocketTimeout": "UNSET",
"runtimeState": {
"enabled": false,
"ui": false
},
"adminAuth": "UNSET",
"httpAdminRoot": "/",
"httpAdminCors": "UNSET",
"httpNodeAuth": "UNSET",
"httpNodeRoot": "/",
"httpNodeCors": "UNSET",
"httpStatic": "UNSET",
"httpStaticRoot": "UNSET",
"httpStaticCors": "UNSET",
"uiHost": "SET",
"uiPort": "SET",
"userDir": "SET",
"nodesDir": "UNSET"
}
}
}
This is my new computer
{
"report": "diagnostics",
"scope": "basic",
"time": {
"utc": "Sat, 02 Nov 2024 13:05:58 GMT",
"local": "2/11/2024, 14:05:58"
},
"intl": {
"locale": "en-BE",
"timeZone": "Europe/Brussels"
},
"nodejs": {
"version": "v22.11.0",
"arch": "x64",
"platform": "win32",
"memoryUsage": {
"rss": 160387072,
"heapTotal": 99647488,
"heapUsed": 94913376,
"external": 40600784,
"arrayBuffers": 36893050
}
},
"os": {
"containerised": false,
"wsl": false,
"totalmem": 16946950144,
"freemem": 11593740288,
"arch": "x64",
"loadavg": [
0,
0,
0
],
"platform": "win32",
"release": "10.0.22621",
"type": "Windows_NT",
"uptime": 3520.968,
"version": "Windows 11 Pro"
},
"runtime": {
"version": "4.0.5",
"isStarted": true,
"flows": {
"state": "start",
"started": true
},
"modules": {
"node-red": "4.0.5",
"node-red-contrib-mqtt-broker": "0.2.9",
"node-red-contrib-play-audio": "2.5.0",
"node-red-contrib-ui-actions": "0.1.8",
"node-red-contrib-aedes": "0.6.0",
"node-red-contrib-uibuilder": "7.0.4",
"node-red-dashboard": "3.6.5",
"node-red-node-ui-table": "0.4.4"
},
"settings": {
"available": true,
"apiMaxLength": "UNSET",
"disableEditor": false,
"contextStorage": {},
"debugMaxLength": 1000,
"editorTheme": {
"palette": {},
"projects": {
"enabled": false,
"workflow": {
"mode": "manual"
}
},
"codeEditor": {
"lib": "monaco",
"options": {}
},
"markdownEditor": {
"mermaid": {
"enabled": true
}
},
"multiplayer": {
"enabled": false
}
},
"flowFile": "flows.json",
"mqttReconnectTime": 15000,
"serialReconnectTime": 15000,
"socketReconnectTime": "UNSET",
"socketTimeout": "UNSET",
"tcpMsgQueueSize": "UNSET",
"inboundWebSocketTimeout": "UNSET",
"runtimeState": {
"enabled": false,
"ui": false
},
"adminAuth": "UNSET",
"httpAdminRoot": "/",
"httpAdminCors": "UNSET",
"httpNodeAuth": "UNSET",
"httpNodeRoot": "/",
"httpNodeCors": "UNSET",
"httpStatic": "UNSET",
"httpStaticRoot": "UNSET",
"httpStaticCors": "UNSET",
"uiHost": "SET",
"uiPort": "SET",
"userDir": "SET",
"nodesDir": "UNSET"
}
}
}
ok, so not so many differences. thats good.
difficult to say what is going on TBH.
you wont see client side errors in node-reds console. You will need to open the dashboard (new computer) then open the browsers dev-tools console and look see if there are errors in there.
PS, it might be time to ditch old dashboard - since it is no longer being actively developed. perhaps it is time to switch to the replacement @flowfuse/node-red-dashboard AKA dashboard 2.0
the websocket failure is a big clue.
firewall?
browser plug in issue?
I'am using exactly the same windows pc for the old and the new pc. The old pc, I started beginning this year with a copy of node red from raspberry pi. And now I try to make a copy on a new pc that is exactly the same.
What I can do is making an image from the old computer and transfer this to my new computer.
If the new device is using the same platform as the old, then - ASSUMING A "STANDARD" INSTALL OF Node-RED - you can:
- Check what version of node.js you have installed - install the same version on the new device.
- Check what GLOBAL npm packages you have installed, what version as well. Install those on the new device.
- Check whether the user id's are the same on both devices and whether they have (and whether the system has if running as a service) the same permissions.
- Copy all of your userDir folder (
~/.node-redif using PowerShell) to the new PC - this will be a long process because you are including all of the installed modules. You can exclude anynode_modulesfolder at any level and donpm installfor each folder that contains a package.json if you prefer. - Start node-red on the new device exactly how you started it on the old one.
That should be it.
Note that if transferring between different platforms (e.g. Pi to PC or Intel PC to ARM PC, etc), then things are more complex.
Sensibly, you would probably want to bring the old PC up to current install/patch levels for Windows, node.js, Node-RED and all globally and locally installed npm packages.
I do notice that your old computer is using Node.js v20.12.2 while your new computer is using Node.js v22.11.0
You might want to try downgrading the new computer to Node.js v20.12.2 and see if that changes anything.
You can always upgrade it back if it doesn't change anything.
Thanks to all for the help.
I made an image of my old pc and put it on my new computer. I bought 2 the same mini n100 pc's. Now it is working perfect on my new pc.
