If you go into that folder in the container shell again, and run
npm install
It should install all the nodes you had installed, as defined by your package.json file.
Did you restart node red and refresh the browser page showing the editor?
Hi Colin,
I spoke too soon, so far only the BigTimer has installed and that wad the only one I installed via the console and then via the pallet. When I try to install any of the other this is what I get….
2023-09-21T20:16:00.454Z Install : node-red-dashboard 3.6.0
2023-09-21T20:16:00.168Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-dashboard@3.6.0
2023-09-21T20:16:00.931Z [err] npm
2023-09-21T20:16:00.931Z [err] WARN config
2023-09-21T20:16:00.932Z [err] production Use --omit=dev instead.
2023-09-21T20:16:04.431Z [out]
2023-09-21T20:16:04.431Z [out] changed 1 package in 4s
2023-09-21T20:16:04.445Z rc=0
I tried the nom install command, it did not fail but it said this…
p to date, audited 301 packages in 2s
42 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
npm notice
npm notice New major version of npm available! 8.19.4 -> 10.1.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.1.0
npm notice Run npm install -g npm@10.1.0 to update!
npm notice
~ $
…no packages were re-inslalled, I did the restart and etc but it makes no difference. My package.json looks intact..
{
"name": "node-red-project",
"description": "A Node-RED Project",
"version": "0.0.1",
"private": true,
"dependencies": {
"node-red-contrib-alexa-home-skill": "~0.1.19",
"node-red-contrib-alexa-local": "~0.3.24",
"node-red-contrib-alexa-remote2-v2": "~3.10.5",
"node-red-contrib-apple-find-me": "~1.1.8",
"node-red-contrib-apple-findme-reloaded": "~0.1.8",
"node-red-contrib-apple-tv-x": "~1.0.3",
"node-red-contrib-bigtimer": "~2.8.5",
"node-red-contrib-boolean-logic": "0.0.3",
"node-red-contrib-chatgpt": "~0.1.0",
"node-red-contrib-crypto-js-dynamic": "~0.1.22",
"node-red-contrib-example-wibble": "file:node-red-contrib-wibble",
"node-red-contrib-mikrotik": "~0.7.0",
"node-red-contrib-moving-average": "~1.3.0",
"node-red-contrib-os": "~0.2.1",
"node-red-contrib-pythonshell": "~1.5.4",
"node-red-contrib-remote": "~1.5.0",
"node-red-contrib-ring-central": "~0.0.6",
"node-red-contrib-ringdoorbell": "~2.0.0",
"node-red-contrib-simple-crypto": "~1.0.1",
"node-red-contrib-simple-gate": "~0.5.2",
"node-red-contrib-spotify": "~0.1.4",
"node-red-contrib-switch-break": "~1.0.2",
"node-red-contrib-timerswitch": "~1.4.0",
"node-red-contrib-tuya-local": "0.0.5",
"node-red-contrib-tuya-smart-device": "~5.2.0",
"node-red-contrib-ui-artless-gauge": "~0.3.12",
"node-red-contrib-ui-button_state": "~0.2.2",
"node-red-contrib-ui-digital-display": "~1.0.3",
"node-red-contrib-ui-led": "~0.4.11",
"node-red-contrib-ui-level": "~0.1.46",
"node-red-contrib-ui-ping": "~1.0.0",
"node-red-contrib-ui-thermostat": "~1.0.0",
"node-red-contrib-ui-time-scheduler": "~1.17.2",
"node-red-contrib-uibuilder": "~6.4.1",
"node-red-contrib-unifi": "~0.2.14",
"node-red-contrib-web-worldmap": "~2.37.4",
"node-red-dashboard": "~3.6.0",
"node-red-node-email": "~2.0.1",
"node-red-node-mysql": "~1.0.3",
"node-red-node-openweathermap": "~0.5.1",
"node-red-node-random": "~0.4.1",
"node-red-node-ui-iframe": "~0.2.1",
"node-red-node-ui-table": "~0.4.3",
"thingzi-logic-timers": "~1.2.5"
}
}
…I’m going to try another package via the console install then pallet and see if it works that way again.
Thanks again for your help with this, I feel like I’m making some progress.
Nigel R
That means it was already installed, and it upgraded something. Run
npm list
from the flows directory and it will tell you what nodes and modules are installed.
I think you need to find the node-red startup log, the one starting Welcome to Node Red, but I don't know how you see that in docker.
Hi Colin,
I have used npm now to re-install everything I needed and it’s all working!!!
I cannot thank you enough, I was about to chuck it all away as unreliable crap and you gave me the pointer I needed brilliant!
It’s still a mystery as to why the V3 upgrade removed all of the pallet nodes but at least I know how to recover it all if it happens again.
Many thanks,
Nigel R
1 Like
I'll just report that I'm successfully running Node-RED 3.1.0 w/ Node.js v18 on RaspPi4B 64bit Bullseye.
2 Likes
I'm very reliant on the Ctrl-Enter shortcut as well. I understand this was a problem when Monaco was released into Node-RED and was subsequently solved - looks like the issue is back.
I have raised an issue here, hopefully I got the details correct.
2 Likes
yes you are right, thank you for bringing this issue up
Shame there's no video! I look forward to those!
Very useful! Thanks for the info! I need it for writing documentation.
How can I roll back? My install self updated and it appears to have broken a HTTPS Get from MyEnergi.
"TypeError: node.config.pgPool.connect is not a function"
postgresql config error application.
in version 3.0.2 my application worked normally.
My database configuration is by external variable.
After updating to 3.1 I am receiving this error.
Can someone help me?
Can you explain exactly what / how?
So are these env vars still set?
Put the exact same env vars into an inject node & send it to a debug - are the values still present?
the values are being printed normally in debug
Did you also upgrade nodejs? Do you know what version nodejs you had before and what version you have now?
Which postgres node are you using?
node-red-contrib-postgresql version 0.14
