# Flows stopped due to missing nodetypes after reinstall

**URL:** <https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005>\
**Category:** General\
**Created:** [11 September 2025 05:46 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005 "2025-09-11T05:46:50Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![warnert](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/warnert/32/108132_2.png) [@warnert](https://discourse.nodered.org/u/warnert)\
**Post date:** [11 September 2025 05:46 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/1 "2025-09-11T05:46:50Z")

</div>

My development pi3b sd card got bad so I reinstalled my system. I had a backup of all the flows but then the nodes were not installed. So I managed to get almost all things to get working except for ui\_base, ui\_link, ui\_spacer and so on till ui\_dropdown and ui\_colour\_picker. So I installed noder-red-dashboard, although deprecated, and then the error did not go away. In the manage palette screen there is a strange error: in the node-red-dashboard palette it saia 19x [object Object] where the last one had a yellow triangle in front with a ! in it. And then it says 21 nodes.

What to do to get things working again?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2025 06:23 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/2 "2025-09-11T06:23:13Z")

</div>

Assuming that you used the recommended pi install script, go into your .node-red folder and run  
`npm remove node-red-dashboard`  
`npm install node-red-dashboard`  
And post the full output from that.

Then restart node red using  
`node-red-stop`  
`node-red-start`  
If you still have the problem then post the full output from the stop/start.

---

<div class="post-metadata">

**Author:** ![warnert](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/warnert/32/108132_2.png) [@warnert](https://discourse.nodered.org/u/warnert)\
**Post date:** [11 September 2025 07:54 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/3 "2025-09-11T07:54:27Z")

</div>

pi@rbpi3b1:~ $ npm remove node-red-dashboard

up to date in 3s  
pi@rbpi3b1:~ $ npm install node-red-dashboard  
npm error code EINTEGRITY  
npm error errno EINTEGRITY  
npm error Invalid response body while trying to fetch [https://registry.npmjs.org/node-red-dashboard:](https://registry.npmjs.org/node-red-dashboard:) sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== integrity checksum failed when using sha512: wanted sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== but got sha512-2+Vr+gtlIxcjKlJq6+uIb54xIRLRWzLI7cUTUVGCG7k4ks3MOpqIaIoGf7yrSRX4qFzpdOpvaXoj+ggUOkH2JQ==. (549868 bytes)  
npm error A complete log of this run can be found in: /home/pi/.npm/\_logs/2025-09-11T07\_53\_25\_126Z-debug-0.log  
pi@rbpi3b1:~ $

---

<div class="post-metadata">

**Author:** ![warnert](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/warnert/32/108132_2.png) [@warnert](https://discourse.nodered.org/u/warnert)\
**Post date:** [11 September 2025 08:00 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/4 "2025-09-11T08:00:05Z")

</div>

pi@rbpi3b1:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at [http://192.168.17.71:1880](http://192.168.17.71:1880)  
On Pi Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED  
Use node-red-start to start Node-RED again  
Use node-red-log to view the recent log output  
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot  
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to [http://flows.nodered.org](http://flows.nodered.org)

# Starting as a systemd service.

Started nodered.service - Node-RED graphical event wiring tool.  
11 Sep 08:56:48 - [info]  
Welcome to Node-RED

11 Sep 08:56:48 - [info] Node-RED version: v4.1.0  
11 Sep 08:56:48 - [info] Node.js version: v20.19.4  
11 Sep 08:56:48 - [info] Linux 6.12.34+rpt-rpi-v8 arm64 LE  
11 Sep 08:56:49 - [info] Loading palette nodes  
11 Sep 08:56:54 - [warn] ------------------------------------------------------  
11 Sep 08:56:54 - [warn] [node-red-contrib-zigbee2mqtt/server] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_base] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_button] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_dropdown] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_switch] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_slider] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_numeric] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_text\_input] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_date\_picker] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_colour\_picker] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_form] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_text] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_gauge] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_chart] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_audio] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_toast] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_ui\_control] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_template] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_link] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] [node-red-dashboard/ui\_spacer] SyntaxError: Invalid or unexpected token  
11 Sep 08:56:54 - [warn] ------------------------------------------------------  
11 Sep 08:56:54 - [info] Settings file : /home/pi/.node-red/settings.js  
11 Sep 08:56:54 - [info] Context store : 'default' [module=memory]  
11 Sep 08:56:54 - [info] User directory : /home/pi/.node-red  
11 Sep 08:56:54 - [warn] Projects disabled : editorTheme.projects.enabled=false  
11 Sep 08:56:54 - [info] Flows file : /home/pi/.node-red/flows.json  
11 Sep 08:56:54 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
11 Sep 08:56:54 - [warn] Using unencrypted credentials  
11 Sep 08:56:55 - [info] Waiting for missing types to be registered:  
11 Sep 08:56:55 - [info] - ui\_base  
11 Sep 08:56:55 - [info] - ui\_link  
11 Sep 08:56:55 - [info] - ui\_spacer  
11 Sep 08:56:55 - [info] - ui\_button  
11 Sep 08:56:55 - [info] - ui\_switch  
11 Sep 08:56:55 - [info] - ui\_date\_picker  
11 Sep 08:56:55 - [info] - ui\_form  
11 Sep 08:56:55 - [info] - ui\_chart  
11 Sep 08:56:55 - [info] - ui\_slider  
11 Sep 08:56:55 - [info] - ui\_text  
11 Sep 08:56:55 - [info] - ui\_gauge  
11 Sep 08:56:55 - [info] - ui\_text\_input  
11 Sep 08:56:55 - [info] - ui\_numeric  
11 Sep 08:56:55 - [info] - ui\_dropdown  
11 Sep 08:56:55 - [info] - ui\_colour\_picker

---

<div class="post-metadata">

**Author:** ![warnert](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/warnert/32/108132_2.png) [@warnert](https://discourse.nodered.org/u/warnert)\
**Post date:** [11 September 2025 08:03 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/5 "2025-09-11T08:03:57Z")

</div>

After the remove command noderedstart keeps complaining about node-red-dashboard.

So it seems not to be removed.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [11 September 2025 08:16 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/6 "2025-09-11T08:16:14Z")

</div>

Is this on a new SD card or are you reinstalling on the one which failed?

Your `npm install node-red-dashboard` command failed. Try it again.  
You may need to run `npm install node-red-contrib-zigbee2mqtt` too.

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [11 September 2025 08:20 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/7 "2025-09-11T08:20:42Z")

</div>

```auto
11 Sep 08:56:55 - [info] Waiting for missing types to be registered:
11 Sep 08:56:55 - [info] - ui_base
11 Sep 08:56:55 - [info] - ui_link
11 Sep 08:56:55 - [info] - ui_spacer
....

```

These messages mean that the Node-RED dashboard nodes are still present in your flow, but the node is not installed.

```auto
pi@rbpi3b1:~ $ npm install node-red-dashboard
npm error code EINTEGRITY
npm error errno EINTEGRITY
npm error Invalid response body while trying to fetch https://registry.npmjs.org/node-red-dashboard: sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== integrity checksum failed when using sha512: wanted sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== but got 
...

```

Implies that there was a problem when you tried to reinstall it. The error implies the tgz file that npm downloaded didn't match the hash it was given (it was changed or corrupted in transfer).

Best suggestion is to use the Node-RED palette manager to try and reinstall node-red-dashboard again, if the errors persist after reinstall, then you have a much bigger problem, something is messing with your traffic from the internet.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2025 09:18 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/8 "2025-09-11T09:18:48Z")

</div>

> [@hardillb](#):
>
> Best suggestion is to use the Node-RED palette manager to try and reinstall node-red-dashboard again

I prefer to use the command line in cases like this as it is easier to see what the problem is. @warnert did not notice the error when he initially installed using the palette manager, whereas it is clear to see when installing via the command line.

But yes, @warnert appears to have a major issue of some sort with his internet access.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2025 09:21 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/9 "2025-09-11T09:21:20Z")

</div>

> [@warnert](#):
>
> pi@rbpi3b1:~ $ npm install node-red-dashboard

Also, you have not gone into your .node-red folder before installing, as I instructed.

---

<div class="post-metadata">

**Author:** ![warnert](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/warnert/32/108132_2.png) [@warnert](https://discourse.nodered.org/u/warnert)\
**Post date:** [11 September 2025 09:22 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/10 "2025-09-11T09:22:01Z")

</div>

I installed a lot of other nodes and that all went well. Only this one fails.  
But (later) I will fire-up another PI3 and do, as I did with this one on a new sd-card, a clean install.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2025 09:25 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/11 "2025-09-11T09:25:53Z")

</div>

Note that if you are moving an node red system from one machine another, after installing node red, restore the full .node-red folder from the old machine _except_ for the node\_modules folder and the file package-lock.json. The go into the .node-red folder and run  
`npm install`  
That will automatically install all the extra nodes that you had previously installed.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [11 September 2025 13:41 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/12 "2025-09-11T13:41:21Z")

</div>

An alternative take on the issue might be a corrupted npm cache? Might be sensible to force clear the cache.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2025 13:50 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/13 "2025-09-11T13:50:49Z")

</div>

> [@TotallyInformation](#):
>
> Might be sensible to force clear the cache.

Good idea. @warnert, in your .node-red folder run  
`npm cache clean --force`  
and re-try the install.

---

<div class="post-metadata">

**Author:** ![warnert](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/warnert/32/108132_2.png) [@warnert](https://discourse.nodered.org/u/warnert)\
**Post date:** [11 September 2025 14:01 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/14 "2025-09-11T14:01:09Z")

</div>

I have done a fresh install on an other sd-card and there it worked.  
So I copied the .node-red directory from the new system to the old one (after a rename from the original one) without the node\_modules map and did the npm install.

After that the problem was solved, I could install all the modules I needed.

So maybe the cache was corrupt?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [10 December 2025 14:02 UTC](https://discourse.nodered.org/t/flows-stopped-due-to-missing-nodetypes-after-reinstall/99005/15 "2025-12-10T14:02:09Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.