Nodes just disappeared

Third party integrations Node-RED
1

I have had 4 or 5 nodes disappear and now it says they are not recognised. I havent changed anything it was working perfectly fine nothing really changed since the last update and it was still working after that.

I tried to rollback to a time when I know it was working fine but the issue is still there.
I cant re add the pallettes it just gives me an error.

Any help would be very much appreciated thank you

edit*
I have fixed by going about 5 days back in my back ups I back up every day.
I had this issue a day or so a go and only went back to the previous day and it fixed it so I have no idea whats causing it to happen but I at least now know what each missing node was doing so I can replace them should it happen again but not being able to install new pallettes has me a bit confused too.

2

Which nodes disappeared?

not being able to install new pallettes has me a bit confused too.

Could you expand on what is happening here. Can you open manage palette? Are there errors in the log after attempting to add a node?

3

So I have currently fixed it by rolling back again and so far so good.
There where logs yes but as i have fixed it for the moment I cant elaborate.
I lost off the top of my head, join-wait, stoptimer3, schedular, scritpt and i think there was one more.
This happened twice in a few days but I was unable to install any palettes when it happened not just the missing ones.
Its been a couple of days and so far its been ok, I have random restarts and even a complete shutdown to figure out but that’s not necessarily node red related or at least at this point I don’t know if it is.

Thank you for the reply though if it happens again I will post as much detail as I can.

4

I am getting the same with some older but reliable nodes - looptimer, simple-queue, etc. Trying to reinstall looptimer from NPM in Node Red gives the log below. I assume the related libraries have been removed.

2024-10-11T03:15:20.050Z Install : node-red-contrib-looptimer 0.0.8

2024-10-11T03:15:20.082Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict [email protected]

2024-10-11T03:15:36.788Z [err] npm warn deprecated [email protected]: this library is no longer supported

2024-10-11T03:15:37.827Z [err] npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.

2024-10-11T03:15:38.148Z [err] npm warn deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

2024-10-11T03:15:38.571Z [err] npm warn deprecated [email protected]: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.

2024-10-11T03:15:46.046Z [err] npm error code E404

2024-10-11T03:15:46.062Z [err] npm error 404 Not Found - GET https://registry.npmjs.org/node-red-contrib-cheerio/-/node-red-contrib-cheerio-1.1.0.tgz - Not found

2024-10-11T03:15:46.063Z [err] npm error 404

2024-10-11T03:15:46.064Z [err] npm error 404 ‘node-red-contrib-cheerio@https://registry.npmjs.org/node-red-contrib-cheerio/-/node-red-contrib-cheerio-1.1.0.tgz’ is not in this registry.

2024-10-11T03:15:46.065Z [err] npm error 404

2024-10-11T03:15:46.065Z [err] npm error 404 Note that you can also install from a

2024-10-11T03:15:46.067Z [err] npm error 404 tarball, folder, http url, or git url.

2024-10-11T03:15:46.085Z [err]

2024-10-11T03:15:46.085Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2024-10-11T03_15_20_864Z-debug-0.log

2024-10-11T03:15:46.191Z rc=1

5

Once I got mine back I went through the nodes and made sure they were all up to date in node red, so far so good.
I’ve removed one or two from my flows but there are a couple I really need so I need to find a good alternatives before it happens again.

I’m inclined to agree with you that the nodes getting removed are old and I had update automatically turned on so that’s likely why they were simply disappearing.

One of mine is the function node for example I use that 92 times so I really need to find an altenative just to protect myself from it dissapearing

6

So its just returned again I lost

  • join-wait
  • stoptimer3
  • wled2
  • string (function)

Tried to install joine-wait and got

2024-10-15T15:46:26.759Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict [email protected]

2024-10-15T15:46:46.187Z [err] npm warn deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at https://github.com/visionmedia/superagent/releases.

2024-10-15T15:46:52.492Z [err] npm error code E404

2024-10-15T15:46:52.500Z [err] npm error 404 Not Found - GET https://registry.npmjs.org/node-red-node-alexa/-/node-red-node-alexa-1.0.13.tgz - Not found

2024-10-15T15:46:52.500Z [err] npm error 404

2024-10-15T15:46:52.501Z [err] npm error 404 ‘node-red-node-alexa@https://registry.npmjs.org/node-red-node-alexa/-/node-red-node-alexa-1.0.13.tgz’ is not in this registry.

2024-10-15T15:46:52.501Z [err] npm error 404

2024-10-15T15:46:52.501Z [err] npm error 404 Note that you can also install from a

2024-10-15T15:46:52.501Z [err] npm error 404 tarball, folder, http url, or git url.

2024-10-15T15:46:52.509Z [err]

2024-10-15T15:46:52.510Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2024-10-15T15_46_27_210Z-debug-0.log

2024-10-15T15:46:52.605Z rc=1

I dont have an alexa pallete tried to install one got the same error

I really need to find a fix for this its getting frustrating now

7

I just tried installing a few that you are missing and I can install without a problem. Idk if a reinstall would help but other than that i don’t have any other suggestions. Backup the addon, then export all your flows and save. Delete the addon, restart the host, and reinstall NR, then restore the flows not the backup.

8

Yeah it makes no sense to me either and I have tried your suggestions previously and it hasnt worked.

Based on the log output im thinking because I restored a back up today some of the pallettes are not downloaded and thats then causing the error with installing.
Im totally guessing here but my thinking is the alexa pallatte it refers to I may have had installed just not using and now for whatever reason trying to reinstall any pallettes is throwing up an error because it wasnt restored properly which might explain why going back a day or in the previous case about 5 days fixed it. It may well be that the amount of days doesnt matter just that on that restore it manage to download everything correctly
As I say I am totally guessing but it make no sense that it broke to start with I was guessing because I had auto update turned on so I turned that off but had to restore a back up today as I changed hardware

Thank you for trying to help though I managed to fix it before i will hopefully fix it again.

edit
So I fixed it this time by uninstalling the addon after backing up the flows of course deleting the addon connecting to samba share and deleting all node red leftovers directories etc. Then I reinstalled it and reinstalled the missing palettes. I wasn’t able to find stoptimer3 so used stoptimer2 but had to replace the missing stoptimer3 nodes in my flows. Thankfully I could guess the times set.
The others installed without an issue.

1 Like