Node.js version v18.20.6
NPM version 10.8.2
O/S and last reboot Raspbian GNU/Linux 10 (buster)
2025-06-05 21:55:47
O/S install DT
Node-red last started Mon 2025-08-25 19:57:07 AEST
N/R version 4.0.9
Sorry, but what do I need to do?
Go into your .node-red folder and run
npm remove node-red-node-rbe
and restart node red and refresh the browser.
You don't need it any more as it is included in core as the filter node. Your flows will not be affected.
Sorry for slow reply.
OTHER PROBLEMS.... 
pi@TimePi:~ $ cd .node-red
pi@TimePi:~/.node-red $ npm remove node-red-node-rbe
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: node-red-contrib-ui-led@0.4.8
npm error Found: node-red-dashboard@3.6.6
npm error node_modules/node-red-dashboard
npm error node-red-dashboard@"~3.6.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
npm error node_modules/node-red-contrib-ui-led
npm error node-red-contrib-ui-led@"~0.4.8" from the root project
npm error
npm error Conflicting peer dependency: node-red-dashboard@2.30.0
npm error node_modules/node-red-dashboard
npm error peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
npm error node_modules/node-red-contrib-ui-led
npm error node-red-contrib-ui-led@"~0.4.8" 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 potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-debug-0.log
Above my pay grade.
Ok, sorry, the log file:
pi@TimePi:~/.node-red $ cat /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-debug-0.log
0 verbose cli /usr/bin/node /usr/bin/npm
1 info using npm@10.8.2
2 info using node@v18.20.6
3 silly config load:file:/usr/lib/node_modules/npm/npmrc
4 silly config load:file:/home/pi/.node-red/.npmrc
5 silly config load:file:/home/pi/.npmrc
6 silly config load:file:/usr/etc/npmrc
7 verbose title npm remove node-red-node-rbe
8 verbose argv "remove" "node-red-node-rbe"
9 verbose logfile logs-max:10 dir:/home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-
10 verbose logfile /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-debug-0.log
11 silly packumentCache heap:248512512 maxSize:62128128 maxEntrySize:31064064
12 silly logfile start cleaning logs, removing 1 files
13 silly logfile done cleaning log files
14 silly idealTree buildDeps
15 silly fetch manifest node-red-dashboard@^2.23.3
16 silly packumentCache full:https://registry.npmjs.org/node-red-dashboard cache-miss
17 http fetch GET 200 https://registry.npmjs.org/node-red-dashboard 2418ms (cache revalidated)
18 silly packumentCache full:https://registry.npmjs.org/node-red-dashboard set size:549868 disposed:false
19 verbose stack Error: could not resolve
19 verbose stack at PlaceDep.failPeerConflict (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:503:25)
19 verbose stack at new PlaceDep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:157:21)
19 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:917:18)
19 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7)
19 verbose stack at async Promise.all (index 1)
19 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5)
19 verbose stack at async Uninstall.exec (/usr/lib/node_modules/npm/lib/commands/uninstall.js:51:5)
19 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9)
19 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5)
20 error code ERESOLVE
21 error ERESOLVE could not resolve
22 error
23 error While resolving: node-red-contrib-ui-led@0.4.8
23 error Found: node-red-dashboard@3.6.6
23 error node_modules/node-red-dashboard
23 error node-red-dashboard@"~3.6.6" from the root project
23 error
23 error Could not resolve dependency:
23 error peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
23 error node_modules/node-red-contrib-ui-led
23 error node-red-contrib-ui-led@"~0.4.8" from the root project
23 error
23 error Conflicting peer dependency: node-red-dashboard@2.30.0
23 error node_modules/node-red-dashboard
23 error peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
23 error node_modules/node-red-contrib-ui-led
23 error node-red-contrib-ui-led@"~0.4.8" from the root project
23 error
23 error Fix the upstream dependency conflict, or retry
23 error this command with --force or --legacy-peer-deps
23 error to accept an incorrect (and potentially broken) dependency resolution.
24 error
24 error
24 error For a full report see:
24 error /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-eresolve-report.txt
25 silly unfinished npm timer reify 1756207488568
26 silly unfinished npm timer reify:loadTrees 1756207488597
27 silly unfinished npm timer idealTree:buildDeps 1756207490719
28 silly unfinished npm timer idealTree:node_modules/node-red-contrib-ui-led 1756207490770
29 verbose cwd /home/pi/.node-red
30 verbose os Linux 5.10.103-v7+
31 verbose node v18.20.6
32 verbose npm v10.8.2
33 verbose exit 1
34 verbose code 1
35 error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-debug-0.log
Again, above my pay grade.
Sorry.
Oh and on the second last line of the first one the log file:
pi@TimePi:~/.node-red $ cat /home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-eresolve-report.txt
'Log files:
/home/pi/.npm/_logs/2025-08-26T11_24_46_392Z-debug-0.log
# npm resolution error report
While resolving: node-red-contrib-ui-led@0.4.8
Found: node-red-dashboard@3.6.6
node_modules/node-red-dashboard
node-red-dashboard@"~3.6.6" from the root project
Could not resolve dependency:
peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
node_modules/node-red-contrib-ui-led
node-red-contrib-ui-led@"~0.4.8" from the root project
Conflicting peer dependency: node-red-dashboard@2.30.0
node_modules/node-red-dashboard
peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
node_modules/node-red-contrib-ui-led
node-red-contrib-ui-led@"~0.4.8" from the root project
Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.
Nothing to do with this node.
I told you what to do about that yesterday Google's text to speech node - stuck with weird problems - #3 by Colin
Yes, and if I was wanting to update any, all good.
I can't update any.
So I am kinda stuck.
I am sure I tried updating the dashboard and it wouldn't.
The LED... Well... If the dashboard won't, what chance has it?
Dunno.
Won't it let you update the led node?
I haven't tried.
I know that an update messed up things with it.
I'll give it a go when I get more time. (Late here now)
I have also been down a deep rabbit hole with remote log in on a RasPi and found a doozy of a problem.
That took me a lot of time and help from Mr GPT.
But we got it worked out.
(That was on the machine in question)
It is the LED node that it is complaining about. It says that the current dashboard version is too new for it. The latest version of the led node allows for dashboard v3+
If you ever get stuck in dependency hell. Sometimes the quickest and safest solution is to manually delete the ~/.node-red/node_modules/ folder and then do an npm install.
cd ~/.node-red/
rm -R node_modules
npm install
(stop node-red before doing that and then start it again afterwards.
2 Likes
Yes, if updating the led node, and then any other nodes that can be updated, doesn't do it, then follow Julian's advise. Note though that on a low spec pi it can take a long time to reinstall all the nodes. Significant fractions of an hour.
I haven't found it necessary to stop node-red first, I just restart when it is all done.
3 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
