Hi, thanks for help, I would uninstall this node but it’s in use, there is no sign of it in any flow, I’ve disabled and restarted NR, still in use. Maybe it’s a buggy node, how then can I force clean it? Unfortunately NR doesn’t let me the chance to delete it or identify its location.
Thank you for help!
I went to node red folder and I manually removed it (waited some time) sucessfully
C:\Users\Admin.node-red>npm uninstall node-red-contrib-tuya-devices
Now NR doesn’t start, 1 Sep 00:45:01 - [info] Waiting for missing types to be registered:
1 Sep 00:45:01 - [info] - tuya-local-device
1 Sep 00:45:01 - [info] - tuya-project
1 Sep 00:45:01 - [info] - tuya-cloud
I guess I need to remove manyally from the flow file? THere is any way to fix this probelm in a clean way?
Start Node-red in safe mode node-red --safe.
Find the offending node[s] (it's quite likely to be a config node) and delete it/them.
Deploy and Node-red will restart the flows.
1 Like
whare can I find config nodes? they aren’t in the flows
Under Configuration Nodes in the drop-down menu. Click Unused at the top and it will show the ones you can delete. Click each one and use delete key
1 Like
Thank you, I would suggest to add an option to force eliminate/clean nodes, inside the palette. Chances are, it happens often we try different modules to reach our goals, some are old, some not well written, we just want to move to the next one and forget about it. To foce clean these modules is not dangerous, since we are just testing them.
But how can the system differentiate between test modules and ones you might actually want/need to keep? Forcing removal of unused config nodes is not something to do lightly.
You can use search normally to find node types. Also, if you do a deploy, it will tell you if you have unused config nodes.
because on flows.json I can indentify the module on each node it is involved, and I clean everything inside { }, so I guess it’s easy to implement a function that clean completely and exactly all related to that module. Am I wrong?
It isn't so hard to be able to clean things out. What is hard is whether something should clean them out. If I select a bunch of nodes on a flow and delete them, ideally, if that would result in a configuration node being left orphaned, I would be asked if I wanted to delete it. It shouldn't happen automatically.
You don’t catch me 
I’m talking about palette>Nodes only,
consider you there have a grayed out button “in use” and you don’t have solutions to remove it deleting nodes and eventually hided/orphans config nodes, but it still there because the node is buggy, old, or something went wrong. You already lost some time to try clean on flows, now you have the only option to open flows.json, search all about that module and delete it manually, risking to delete what you shouldn’t, for example a “,”.
It woul be good to have next to “use” button a “wipe out” button, when pressed NR will delete everything related to it on flows and inside the flows.json, and reload the flow.
In my opinion useful, and worth to create it. Thank you for your attention.
PS: a remove module’s files should be also considered, mabe to include on wipe button too
I think what might be useful is if, on the Manage Palette page, if a node is unused except for (unused) config nodes then perhaps an option 'Delete config nodes and Remove' were available. That would solve a common problem reported here, that of being unable to remove an apparently unused node.
1 Like
