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

Third party integrations Node-RED
42

This happened to me today.

I did take the time time read the release notes for the new Node Red update within Home Assistant.

I know software releases for the wider public are extremely difficult (impossible) to make flawless for every single individual, and hence this comment is no criticism on anyone, however, @frenck seemed to be the person who signed off the changelog message shown from within Home Assistant, so he must have had some saying in the release.

Having said that, in my case the error shown within Node Red after upgrading the add-on from Home Assistant was :

Flows stopped due to missing node types.

    ui_base

Node Red showed me the pop up, searched the node, but it led me nowhere.

Then opened up the "Configuration Nodes" panel on the left (using the gear icon at the bottom right of the UI) and at the bottom of my configuration nodes, one with a long hexadecimal number showed up. Deleted it and off we go!!!

Note prior to upgrading I had doubts because I did not understand or know what the v1 Dashboard was, but once I looked into the video for the new version, I was positively sure that I never ever created any dashboards in Node Red. So the lingering node may occur due to something else, maybe, a dependency of some previously installed Node Red package , which I since deleted but left the node around?

Either case now my flows are working again.

Hope this helps.

43

Thank you for the solution

I agree not giving a heads up of this happening and a solution could have been handled a LOT better!

44

Thanks @sjthespian I saw the upgrade note but didn't think I was using ui_base , I hadn't realised it was a global include. Removed and finally upgraded successfully.

45

This. There's no reason for unused nodes to break anything in flows not even containing the nodes. The correct thing to do would be disable problematic flows at worst. After clear warnings. What a shitshow.

The fact that the node red ui is unusable and you actually have to have a computer or tablet with access to your home assistant system to even see or search for the nodes just adds insult to injury.

46

For anyone trying to fix this here is what I did:
Before upgrading (might work after, not sure)
click on search flows
search for "dashboard"
double click on Node-red Dashboard at the end of the list and select delete
deploy
update Node-Red

47

Appreciate man ! That works for me !!

48

Not for me, please help :wink:

2026-07-14T09:35:54.443Z Install : @flowfuse/node-red-dashboard 1.30.2


2026-07-14T09:35:54.497Z /usr/bin/node /opt/node_modules/npm/bin/npm-cli.js install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict -- @flowfuse/[email protected]

2026-07-14T09:35:58.907Z [err] npm error code EBADENGINE

2026-07-14T09:35:58.907Z [err] npm error engine Unsupported engine

2026-07-14T09:35:58.907Z [err] npm error engine Not compatible with your version of node/npm: [email protected]

2026-07-14T09:35:58.908Z [err] npm error notsup Not compatible with your version of node/npm: [email protected]

2026-07-14T09:35:58.908Z [err] npm error notsup Required: {"node":"^18 || ^20 || ^22"}

2026-07-14T09:35:58.908Z [err] npm error notsup Actual:   {"node":"v24.16.0","npm":"11.16.0"}

2026-07-14T09:35:58.910Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2026-07-14T09_35_54_612Z-debug-0.log

2026-07-14T09:35:59.013Z rc=1
49

Although you are attempting to install the FlowFuse dashboard, your problem has nothing to do with the original post issue.

When installing node modules using the palette manager, Node-RED uses npm (node package manager), which as part of any install will always do a full dependency check on everything.

You have installed, somewhere, hap-nodejs, which is something to do with the HomeKit Accessory Protocol, and for some reason you have version 0.12.3 [out of date]. This old version locks in a dependency on nodeJS up to v22. As you are now on nodeJS v24, naturally npm complains because one of your nodes is insisting on a prior version of nodeJS. Hence BAD ENGINE. Install stops.

To find out what module depends on this (ie what got hap-nodejs into your node_modules directory in the first place) you need to run, from the .node-red user directory,

npm list

or

npm list hap-nodejs

to list dependencies .

You can use the ‘exec’ node to run this command quite easily.

PS.
It almost goes without saying that, if you are not using any Node-RED dashboards (and hardly anyone other than a few of us do so) you do not need to add the FlowFuse dashboard in the first place.

50

This was very helpful ! I find out some unused home kit nodes. Removed them, after that the flowfuse installation is working fine .
Needed this dashboard for the “Gast777” zendure Proxy (home battery)

51

The FlowFuse alternative dashboard is supported and is mostly comparable. It is however not directly compatible. There is a tool that can perform node translation, but I reworked my two key dashboards by hand, which took several days. My biggest problem was a graph that required a complete rebuild of the feed data.

A big issue for me is that the old dashboard was accessible via the Node-RED Dashboard integration, so I was able to see my NR Dashboard using NabuCasa when away, but now cannot as the NR Dashboard integration now points to the wrong dashboard exposure url. The dashboards use https, which is also not available in a webpage / iframe when viewed over NabuCasa.

As you have upgraded, there is no issue with re-installing back the original node-red-dashboard as well. Both dashboards can operate side by side. I have not (yet) upgraded, but installed FlowFuse and ran both so I could see both as I converted each dashboard.