Are you wanting to cancel the import or ignore the install of missing nodes?
Good question.
Generally I would want to cancel the import but the other is an equally valid choice.
A slight gap between highlighted node and the blue line does look better than the v4 highlight.
If you inject to a node which is already highlighted, the blue surround is not immediately expanded
The line crowds the status message slightly.
The blue line does disappear behind the input and output connectors. Maybe it should be behind the status message too?
I thought that was handled... it was something I definitely remember working on.. will take a look.
I'm looking at v5.0.0 beta 6
Best to install the released version.
Just chucking in my unasked for 2 penny worth, I like the blue highlight like it is.
That's a good point. And with longer status messages, they end up overlapping that area anyway, so you still get the text quite close to the blue line.
A post was split to a new topic: Language in the code editor context menu is incorrect
I guess that's about the only REAL fix possible 
/s
But honestly, I'd take adding a long name as a fix since I don't really know what the "cron-plus" node is triggering. Perhaps a better title would be "trigger every X minutes to update Y" ... same with the mqtt producer.
My answer is only half in jest!
I have this version newly installed on Home Assistant.
It seems that Homekit Bridge and AppleTV nodes cannot be installed,
-----------------------------------------------------------
2026-06-21T10:02:01.769Z Installer : node-red-contrib-homekit-bridged 1.7.3
2026-06-21T10:02:01.868Z /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 -- node-red-contrib-homekit-bridged@1.7.3
2026-06-21T10:02:09.577Z [err] npm error code EBADENGINE
2026-06-21T10:02:09.577Z [err] npm error engine Unsupported engine
2026-06-21T10:02:09.579Z [err] npm error engine Not compatible with your version of node/npm: hap-nodejs@0.12.3
2026-06-21T10:02:09.583Z [err] npm error notsup Not compatible with your version of node/npm: hap-nodejs@0.12.3
2026-06-21T10:02:09.583Z [err] npm error notsup Required: {"node":"^18 || ^20 || ^22"}
2026-06-21T10:02:09.583Z [err] npm error notsup Actual: {"node":"v24.16.0","npm":"11.16.0"}
2026-06-21T10:02:09.595Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2026-06-21T10_02_02_325Z-debug-0.log
2026-06-21T10:02:09.781Z rc=1
I run another instance on a Mac and there is no problem.
Is it due to this update ?
This is an issue with the node, not with Node-RED. Please contact the author(s).
Thanks, I'll try to update in HA terminal. I thought that all necessary packages were installed when using the HA Node-Red integration
Did that install nodejs 24? For node-red-contrib-homekit-bridged you need to stick to 22, until the node is modified to use the latest version of hap-nodejs.
v2 of that node is currently under development. This new version will support NodeJS v24. You just need to wait a little longer or install the beta version of v2 or an older version of NodeJS.
Thanks, I think Iāll wait for this node to be updated and use my old instance in the meantime
Thanks I'll wait
I can still not wrap my head around the panel behaviour, when i drag a panel, I lose the debug panel and it decides to show another panel instead.
Is this just me ? The behaviour is not natural from a user experience.
Can someone explain in simple terms how this exactly works ?
Do you mean this:
Which can be used to adjust the location of the debug panel, either top or bottom on the left (or if dragged to the right, top or bottom right side - not shown).
Node-RED 5 basically has four separate side bars with each of them having a choice of different plugins/sidebars that can be shown. The drag shown in the animation is the placement of those the sidebars. It only happens if clicking on the the top bar of the sidebar.
