Unknown and un-configured nodes

When I start up node-red it loads 181 nodes, where are these?

My flow is empty, yes I did previously had a few flows but deleted them.


Windows 10


Welcome to Node-RED

30 Jul 22:52:37 - [info] Node-RED version: v3.0.1
30 Jul 22:52:37 - [info] Node.js  version: v14.17.1
30 Jul 22:52:37 - [info] Windows_NT 10.0.16299 x64 LE
30 Jul 22:52:38 - [info] Loading palette nodes
Initializing chat-platform lib, you should see this only once
Running at: C:\Users\Johan\.node-red\node_modules\chat-platform Version: 1.0.13

node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. internal\modules\cjs\loader.js:1085:14
30 Jul 22:52:41 - [info] RedBot version: 0.18.15 (node-red-contrib-chatbot)
30 Jul 22:52:43 - [info] +-----------------------------------------------------
30 Jul 22:52:43 - [info] | uibuilder initialised:
30 Jul 22:52:43 - [info] |   root folder: \Users\Johan\.node-red\uibuilder
30 Jul 22:52:43 - [info] |   version . .: 2.0.8
30 Jul 22:52:43 - [info] |   packages . : vue,bootstrap,bootstrap-vue,jquery,socket.io
30 Jul 22:52:43 - [info] +-----------------------------------------------------
30 Jul 22:52:44 - [info] Worldmap version 2.3.8
30 Jul 22:52:44 - [info] Dashboard version 2.20.0 started at /ui
30 Jul 22:52:44 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
30 Jul 22:52:44 - [warn] ------------------------------------------------------
30 Jul 22:52:44 - [warn] [node-red-node-serialport/serialport] Error: The module '\\?\C:\Users\Johan\.node-red\node_modules\@serialport\bindings\build\Release\bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 72. This version of Node.js requires
NODE_MODULE_VERSION 83. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
30 Jul 22:52:44 - [warn] [node-red-contrib-ttn/ttn-app] Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: node-v83-win32-x64-unknown
Found: [node-v72-win32-x64-unknown]
This problem can often be fixed by running "npm rebuild" on the current system
Original error: Cannot find module 'C:\Users\Johan\node_modules\grpc\src\node\extension_binary\node-v83-win32-x64-unknown\grpc_node.node'
Require stack:
- C:\Users\Johan\node_modules\grpc\src\grpc_extension.js
- C:\Users\Johan\node_modules\grpc\src\client_interceptors.js
- C:\Users\Johan\node_modules\grpc\src\client.js
- C:\Users\Johan\node_modules\grpc\index.js
- C:\Users\Johan\node_modules\ttn\dist\discovery\discovery.js
- C:\Users\Johan\node_modules\ttn\dist\discovery\index.js
- C:\Users\Johan\node_modules\ttn\dist\handler\handler.js
- C:\Users\Johan\node_modules\ttn\dist\handler\index.js
- C:\Users\Johan\node_modules\ttn\dist\index.js
- C:\Users\Johan\node_modules\node-red-contrib-ttn\ttn-app\ttn-app.js
- C:\Users\Johan\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\loader.js
- C:\Users\Johan\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\index.js
- C:\Users\Johan\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\nodes\index.js
- C:\Users\Johan\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\index.js
- C:\Users\Johan\AppData\Roaming\npm\node_modules\node-red\lib\red.js
- C:\Users\Johan\AppData\Roaming\npm\node_modules\node-red\red.js
30 Jul 22:52:44 - [warn] [node-red-contrib-automation-hat/automation-hat-generic] Error: 'C:\Users\Johan\.node-red\node_modules\node-red-contrib-automation-hat\nodes/../library/automationhatlink' must be executable (755)
30 Jul 22:52:44 - [warn] ------------------------------------------------------
30 Jul 22:52:44 - [info] Settings file  : \Users\Johan\.node-red\settings.js
30 Jul 22:52:44 - [info] Context store  : 'default' [module=memory]
30 Jul 22:52:44 - [info] User directory : \Users\Johan\.node-red
30 Jul 22:52:44 - [warn] Projects disabled : editorTheme.projects.enabled=false
30 Jul 22:52:44 - [warn] Flows file name not set. Generating name using hostname.
30 Jul 22:52:44 - [info] Flows file     : \Users\Johan\.node-red\flows_JohanLaptop.json
(node:14380) Warning: Accessing non-existent property 'defaultContainer' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
30 Jul 22:52:44 - [info] Creating new flow file
30 Jul 22:52:44 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

30 Jul 22:52:44 - [info] Server now running at
30 Jul 22:52:44 - [info] Starting flows
30 Jul 22:52:44 - [info] Started flows

Have you looked for any Configuration nodes ?

From the side panel dropdown menu


or in the Dashboard tab ? maybe Tabs / groups / spacer are counting as nodes ?

run npm rebuild from your .node-red install location.

Those are the nodes exisitng the in palette. Even if your flow is empty the editor will load those nodes to make them available for you. You can disable them with the manage palette option in the menu.


Thank you for the response.

MY actual problem is that some where in the back ground (if I can call it that) there are a MQTT connection still active and I need to delete it.

I don't have any there.

Thank s tried that.

Sorry forgot that, thank for the reminder.

Do they show up if you ctrl+f and search mqtt in your Node-RED editor?

Thanks for the response, no they don't.

do those connections show up in the startup log of this node-red ? For Example:

31 Jul 21:23:24 - [info] [mqtt-broker:ef59a3b8.aa554] Connected to broker: mqtt://

Thank you for he response.

No I don't see it.

How do you know that you have active MQTT connections ?
i doubt that they are coming from this Node-red .. because there is nothing left

maybe these mqtt connections are from other devices in your network ?

Perhaps you are retaining messages with the MQTT broker outside of Node-RED?