# 🎉 Node-RED 5 beta 2 now available

**URL:** <https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208>\
**Category:** News\
**Tags:** docker\
**Created:** [21 January 2026 14:30 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208 "2026-01-21T14:30:16Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [3 February 2026 21:09 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/21 "2026-02-03T21:09:03Z")

</div>

> [@Colin](#):
>
> > [@Steve-Mcl](#):
> >
> > Sounds like a candidate for a `good-first-issue` label!
> 
> Actually it would be my 39th issue on the core.

🤣 🤣 🤣

Colin. I am very much aware you raise issues on core (and dashboard and...) (and I/we are VERY thankful 👼).

To clear up my post, `good-first-issue` is a common theme on GH where users seeking to get experienced in coding on open source hunt for issues tagged as "good-first-issue" - see here: [good-first-issue · GitHub Topics · GitHub](https://github.com/topics/good-first-issue).  
Typically these are small tasks perfect for beginners to make contributions.  
The Label helps them find such issues. And with a sprinkle of luck, they land on this one and fix it 😉

---

<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:** [3 February 2026 21:17 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/22 "2026-02-03T21:17:54Z")

</div>

Oh yes, I should have realised.

---

<div class="post-metadata">

**Author:** ![kitwar](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kitwar/32/55008_2.png) [@kitwar](https://discourse.nodered.org/u/kitwar)\
**Post date:** [3 February 2026 21:57 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/23 "2026-02-03T21:57:03Z")

</div>

There could be a small 500ms delay or maybe a wait for "key up", or maybe the deletion would only trigger on "key up" (as opposed to "key down"). The key up thing is much better. Both actually are quite necessary. The delay should be represented by the highlight.

There is also Ctrl+Z, so accidents would not be that big a deal.

---

<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:** [4 February 2026 13:25 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/24 "2026-02-04T13:25:21Z")

</div>

It seems I had completely misunderstood what is happening when an unused config node is deleted. It is not that the next unused node, that is under the mouse, is selected, it is just that when the mouse is hovered over a node it is highlighted and looks exactly the same as a selected node, but since it is not actually selected then hitting delete does nothing.

---

<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:** [4 February 2026 14:44 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/25 "2026-02-04T14:44:08Z")

</div>

This isn't new to v5 but it would be nice if it could be alleviated for v5.

I'm trying to find the flow which handles sensor data from my DS18B20 experiments.  
Search DB18B20 returns this

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/3/b36c2df1a06fe26ee58cd87b099148db36345a3b.png)

It would be useful if the search returned ui nodes assigned to DS18B20 tab or group.

I appreciate it implies recursion because the tabs & group are referenced by ID not name.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [4 February 2026 14:48 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/26 "2026-02-04T14:48:41Z")

</div>

@jbudd please raise as a separate feature request topic, otherwise this topic becomes a mix of actual feedback on the beta and other new ideas that could be done any time.

@Colin similarly with the config nodes feedback - if you have thoughts on improving the UX of the config sidebar (I have many such thoughts...), please raise a dedicated topic.

---

<div class="post-metadata">

**Author:** ![Aaqu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/aaqu/32/101407_2.png) [@Aaqu](https://discourse.nodered.org/u/Aaqu)\
**Post date:** [6 February 2026 13:08 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/27 "2026-02-06T13:08:06Z")

</div>

Is the new beta dropping soon? 👀

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 February 2026 13:09 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/28 "2026-02-06T13:09:39Z")

</div>

Depends if I can fix all the things I've broken this week. To be realistic, unlikely today.

---

<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:** [7 April 2026 13:10 UTC](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208/29 "2026-04-07T13:10:26Z")

</div>

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

[Previous page](https://discourse.nodered.org/t/node-red-5-beta-2-now-available/100208.md?page=1)