Flows stopped due to missing node types. App version: 22.0.0

Third party integrations Node-RED
1

Hi, just update Node-Red to App version: 22.0.0 and now getting the following errors.

Not sure what to do?

Flows stopped due to missing node types.

  • ui_base
  • ui_tab
  • ui_group
-----------------------------------------------------------

App: Node-RED

Flow-based programming for the Internet of Things

-----------------------------------------------------------

App version: 22.0.0

You are running the latest version of this app.

System: Home Assistant OS 17.3 (amd64 / generic-x86-64)

Home Assistant Core: 2026.6.2

Home Assistant Supervisor: 2026.05.1

-----------------------------------------------------------

Please, share the above information when looking for help

or support in, e.g., GitHub, forums or the Discord chat.

-----------------------------------------------------------

s6-rc: info: service base-addon-banner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service base-addon-log-level: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service base-addon-log-level successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-nginx: starting

s6-rc: info: service init-customizations: starting

s6-rc: info: service init-customizations successfully started

s6-rc: info: service init-nodered: starting

s6-rc: info: service init-nginx successfully started

up to date, audited 50 packages in 835ms

15 packages are looking for funding

run `npm fund` for details

found 0 vulnerabilities

s6-rc: info: service init-nodered successfully started

s6-rc: info: service nodered: starting

s6-rc: info: service nodered successfully started

s6-rc: info: service nginx: starting

s6-rc: info: service nginx successfully started

s6-rc: info: service legacy-services: starting

[08:43:34] INFO: Starting Node-RED...

s6-rc: info: service legacy-services successfully started

> start

> node node_modules/node-red/red.js --settings /etc/node-red/config.js

11 Jun 08:43:34 - [info]

Welcome to Node-RED

===================

11 Jun 08:43:34 - [info] Node-RED version: v5.0.0

11 Jun 08:43:34 - [info] Node.js version: v24.16.0

11 Jun 08:43:34 - [info] Linux 6.12.85-haos x64 LE

11 Jun 08:43:35 - [info] Loading palette nodes

11 Jun 08:43:35 - [info] Node-RED Contrib Theme Collection version: v5.0.1

11 Jun 08:43:36 - [info] node-red-contrib-home-assistant-websocket v0.80.3 nodes initialized

11 Jun 08:43:36 - [info] Settings file : /etc/node-red/config.js

11 Jun 08:43:36 - [info] Context store : 'default' [module=memory]

11 Jun 08:43:36 - [info] User directory : /config/

11 Jun 08:43:36 - [warn] Projects disabled : editorTheme.projects.enabled=false

11 Jun 08:43:36 - [info] Flows file : /config/flows.json

11 Jun 08:43:36 - [info] Server now running at http://127.0.0.1:46836/

11 Jun 08:43:36 - [info] Waiting for missing types to be registered:

11 Jun 08:43:36 - [info] - ui_base

11 Jun 08:43:36 - [info] - ui_tab

11 Jun 08:43:36 - [info] - ui_group

[08:43:36] INFO: Starting NGinx...

11 Jun 08:55:29 - [info] Stopping flows

11 Jun 08:55:29 - [info] Stopped flows

11 Jun 08:55:29 - [info] Updated flows

11 Jun 08:55:29 - [info] Waiting for missing types to be registered:

11 Jun 08:55:29 - [info] - ui_base

11 Jun 08:55:29 - [info] - ui_tab

11 Jun 08:55:29 - [info] - ui_group

11 Jun 09:54:45 - [info] Stopping flows

11 Jun 09:54:45 - [info] Stopped flows

11 Jun 09:54:45 - [info] Waiting for missing types to be registered:

11 Jun 09:54:45 - [info] - ui_base

11 Jun 09:54:45 - [info] - ui_tab

11 Jun 09:54:45 - [info] - ui_group

Could anyone help me with a fix?

2

The latest release of the HA Node-RED app has just landed.

There are a couple of breaking changes. This means that, when/if you update, things will break.

Breaking changes

Node-RED Dashboard (v1) is no longer bundled. The classic node-red-dashboard has been unmaintained upstream for a while, and on top of that it kept claiming the dashboard route and colliding with the newer FlowFuse Dashboard 2. So it had to go. Do you still rely on it? You can add it back yourself through the extra options.

Even better, this is a great moment to move over to its maintained successor, @flowfuse/node-red-dashboard.

Your specific issue is that NR Dashboard V1 has gone, so the dashboard configuration nodes (if used) will be missing.

The release note not only has the breaking changes, but also explains how to address the change.

I quote from the release notes...

Please give the notes below a quick read before you hit that update button.

Extra notes [updated] :

You can edit [or delete] the affected nodes to disable them (they are in the config tab in the debug window) and that should stop the error message. It will also stop any NR Dashboard you have, so worth disabling the part of any flow that uses a dashboard as well. Quick fix.

You can add back the missing nodes [use palette manager to re-install the original node-red-dashboard], if you still have active dashboards. Short term fix.

Longer term, anyone using a Node-RED dashboard now needs to move to using the FlowFuse Dashboard. This is not directly compatible, so I think that we can only have the new nodes installed when the old ones are removed first, or only use either dashboard version but not both at the same time. There is a bit of work required to transition, so I am slowly removing my unwanted dashboard tabs before changing any that I wish to keep.

The FlowFuse Dashboard details can be found on Github with documentation.

https://github.com/FlowFuse/node-red-dashboard

If you have an active Node-RED dashboard [and please note, this has nothing to do with the editor and any changes to the editor UI made going to NR version 5]

  • the FlowFuse dashboard can be loaded from the palette manager
  • you can have both the original and the new version at the same time
    • the original nodes are in the list under "dashboard"
    • the configuration nodes are called ui_base, ui_tab, ui_group
    • the FlowFuse nodes are under "dashboard 2"
    • the new configuration nodes are called ui-base, ui-tab, ui-group
  • getting at either dashboard requires using http://homeassistant.local:1880/endpoint/ui/ for the original dashboard and http://homeassistant.local:1880/endpoint/dashboard/ for the new one
    • use a new dashboard as webpage with the above link to access either dashboard directly from the HA menu
3

Hi, I have installed @flowfuse/node-red-dashboard.

Now what to do?

4

You either need to re-install the old version nodes to keep your old dashboards working (for now) or you need to change all your dashboards to use the new FlowFuse version.

The FlowFuse Dashboard is (significantly) different in how it all works, so this is not an update that can be done without additional work.

5

yep, and sometimes if you even don't use ui element right now there might be a left over (currently unused) configuration node which then leads to thrown error. Delete that node and you're done.

6

Thanks,
I have reverted back to the old dashboard, least all my flows are working now.
FlowFuse Dashboard is a project for another day.

7

Follow this, I had a similar issue a while back. This may fix your problem.

8

While I greatly appreciate the effort that goes into advancing HA and its Apps, I wonder if I am the only one who feels this could have been handled better?

This appears to require a dramatic overhaul with a significant impact to flows that people rely on. Similar overhauls of HA have given people warnings for months before actual changes were implemented, allowing time to address any issues. The Breaking Changes seems to provide very little detail on what to do and I have also reverted and am looking to Chat GPT for details on the necessary steps. If it is right, I would suggest those steps should have been called to our attention months ago.

9

Repairs apply to Home Assistant.

Node-Red is not Home Assistant.

Node-Red is an independent, open-source software project.

It has its own community forum.

I encountered the same problem you did, googled it, and followed the suggestions (delete the missing node types).

10

We are discussing the Node-Red App/Add-on within Home Assistant, not Node Red independently. Are you suggesting this is not the correct place for that? The issue appears to pertain directly to the Node Red third-party integration.

And yes, there is a simple fix easily found on Google. However, it would seem that that is not the ideal fix and that the best fix is a potentially larger project, as another respondent to the thread commented. I am pleased to carry out any significant improvement to the system. However, as I suggested, I feel that this could have been handled better.

11

The node red app is node red with the ha nodes already installed, configured to play nice with home assistant's OS. This particular change was made by node red. They decided how and when to do it.

Home Assistant had no say in this matter. If you want to address those responsible for the change, the node red forum would be the place to do it.

12

:warning: Breaking changes

Node-RED Dashboard (v1) is no longer bundled. The classic node-red-dashboard has been unmaintained upstream for a while, and on top of that it kept claiming the dashboard route and colliding with the newer FlowFuse Dashboard 2. So it had to go. Do you still rely on it? You can add it back yourself through the extra options.

Even better, this is a great moment to move over to its maintained successor, @flowfuse/node-red-dashboard.

I am having trouble interpreting this the same way. My bad.

13

Exactly, a classic Home Assistant upgrade. Breaking all your automations without any serious warning. Easy to call it a NodeRed upgrade and you need to go over there to read the changes while it is fully integrated in their system. Such upgrades should be handled way better.

14

Can anyone give a step by step walk through to get this resolved? I have installed the new dashboard in Node Red but what is the next step? Does the new dashboard automatically takeover? After installing the new dashboard, I still get the unknown node type errors and all of my flows stopped working.

I read the breaking changes before upgrading, but I didn't think it would be this complicated to get everything back up and running.

15

The app is a containerized version of Node-Red; it simply makes it easier to install Node-Red on Home Assistant OS.

The maintainer of the Node-Red app is under no obligation to list all of Node-Red's enhancements or how they may, or may not, affect your use of it. The bare minimum is provided as a convenience. The details are in the product's own documentation.

You, the user of Node-Red, remain responsible for understanding what you are installing and how it may have changed since the previous version.

Except it was not a Home Assistant upgrade. It was a Node-Red upgrade; a separate and independent software product.

Exactly. It's a completely separate software product (like Zigbee2MQTT). It's maintained and documented by a completely separate team of volunteers.

You don't have to install anything (I didn't). Just delete the unknown nodes and then click Deploy. That's all I had to do to rectify the issue.

16

I'm running into the same issues as folks above. I'm not sure what the new dashboard even is, from reading the docs it sounds like it's a tool for building dashboard in Node-RED -- which I'm not even doing.

In my case, it's flagging ui_base as missing after the upgrade. This is all of my HA MQTT nodes and every single Home Assistant node. And the "fix" isn't as simple as installing the new dashboard npm module, there is something else missing.

I get it, this is a major upgrade and it's likely to break things. But like some of the other comments above, I'm a bit surprised at the lack of documentation as to just what needs to be done. The docs seem to imply that everyone using this is a Node-RED guru -- and I'm betting very few of us actually are.

I'm an engineer by day -- I get paid to deal with problems like this. But most of the time when there are incompatible upgrades there is a bit more guidance on just what needs to be done to fix it.

18

So did you then manually add every one of those nodes back? In my case the nodes that need to be deleted are 120+ HA nodes. It's flagging every single HA-specific node in my flows -- every device, every event, etc.

That's more than a breaking change, it's a "completely break all functionality" change.

19

I installed nothing.

The unknown nodes are remnants of the old version of the dashboard. The new dashboard version (which requires no installation step; it's part of Node-Red 5.0) no longer employs those nodes, which is why they are now "unknown" and need to be deleted.

Here is how Copilot explains it:

Why ui_base is missing

  • In Dashboard 1.x, ui_base was an internal node that handled the base UI configuration.
  • In Dashboard 2.x (used in Node-RED 5), the architecture changed — it’s now a separate module (node-red-dashboard-2) and ui_base is not used.
  • If you import old flows from Dashboard 1.x, they may still reference ui_base, causing a "unknown node type: ui_base" error.

FWIW, the Node-Red community forum is a good place to get help for Node-Red. For example:
:tada: Node-RED 5 now available - News - Node-RED Forum

20

So in my case the nodes that have to be deleted are things like "turn porch light on" or "send an MQTT message to XXX". Are you saying that if we upgrade Node-RED to v22 we can no longer control HA devices? Or does every one of these nodes have to be replaced with some new node? (that I don't see in the node sidebar -- the only MQTT that comes up for example are the same ones I'm using now -- that get flagged with the same error if I try and add them).

Or do we just nuke all of our flows from orbit and restoration an exported json file? I would think that would have the same issues if the nodes themselves are the problem.

21

Short answer: No (to all questions).

Long answer: I posted what I did above (deleted three ui-related nodes that are now unknown because they are leftovers from the old dashboard). That's it, that's all. If that's insufficient, I suggest asking the question in the Node-Red community forum; it's populated by very knowledgeable users.