# 🎉 Node-RED 3.1.0-beta.4 released

**URL:** <https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091>\
**Category:** News\
**Created:** [26 July 2023 16:33 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091 "2023-07-26T16:33:51Z")\
**Posts on this page:** 20\
**Page:** 3

<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:** [21 August 2023 13:30 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/43 "2023-08-21T13:30:34Z")

</div>

dashboard 3.5.0.

---

<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:** [21 August 2023 13:30 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/44 "2023-08-21T13:30:41Z")

</div>

I think I have got it.  
Somehow the problematic mqtt config node has acquired a new option in flows.json  
`"autoUnsubscribe": true,`  
Deleting those lines from flows.json and restarting node-red clears the problem, at least until they re-appear.

I will raise an issue.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [21 August 2023 13:33 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/45 "2023-08-21T13:33:06Z")

</div>

Yes, as you describe

---

<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:** [21 August 2023 13:33 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/46 "2023-08-21T13:33:57Z")

</div>

Do you see the autoUnsubscribe line(s) in flows.json? And are you definitely on 3.0.2?

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [21 August 2023 13:35 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/47 "2023-08-21T13:35:26Z")

</div>

That's above my pay grade. But later today I will try to see if it's there,

---

<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:** [21 August 2023 13:38 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/48 "2023-08-21T13:38:44Z")

</div>

Are you definitely running 3.0.2?

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [21 August 2023 13:44 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/49 "2023-08-21T13:44:25Z")

</div>

Yes definitely

---

<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:** [21 August 2023 13:56 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/50 "2023-08-21T13:56:46Z")

</div>

See issue [autoUnsubscribe option in mqtt broker node causing red triangles in editor · Issue #4291 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/4291)

---

<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:** [21 August 2023 15:22 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/51 "2023-08-21T15:22:52Z")

</div>

> [@gerry](#):
>
> That's above my pay grade. But later today I will try to see if it's there,

If you are using an editor to look in the flows file then make a copy of the file first, in case you accidentally mess it up. Make sure you use a straight text editor, not something like Word which will mess it up.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [21 August 2023 20:08 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/52 "2023-08-21T20:08:15Z")

</div>

Did a global search on both of my sick machines and did not find that entry

---

<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:** [21 August 2023 20:42 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/53 "2023-08-21T20:42:49Z")

</div>

In that case I think you have a different problem.

Maybe start a new thread (as your issue is not to do with the beta), describe the problem you are seeing in your own words, and we can try and sort it out.

---

<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:** [21 August 2023 21:35 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/54 "2023-08-21T21:35:36Z")

</div>

Is there a timeframe for the v3.1.0 release?

I note that node.js v16 is now already in maintenance mode and expires in September - does this mean that the baseline node.js version will move to v18?

---

<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:** [21 August 2023 22:40 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/55 "2023-08-21T22:40:30Z")

</div>

> [@TotallyInformation](#):
>
> Is there a timeframe for the v3.1.0 release

It has been pencilled for release for some time. All I can say is it is imminent. Almost everything is in place (tour guide updated, i18n updated etc). Time is the only enemy at the moment. But soon. Real soon.

> [@TotallyInformation](#):
>
> does this mean that the baseline node.js version will move to v18?

No. It is to follow the plan. However, the tests run against 16 & 18 so there is not really any reason to stay in 16

---

<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:** [21 August 2023 22:42 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/56 "2023-08-21T22:42:07Z")

</div>

> [@TotallyInformation](#):
>
> I note that node.js v16 is now already in maintenance mode and expires in September

In fairness, node 16 was [cut short by 7 months](https://nodejs.org/en/blog/announcements/nodejs16-eol)

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [22 August 2023 19:06 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/57 "2023-08-22T19:06:33Z")

</div>

In all fairness to the developers, I really don't care if I have to deploy twice. I can live with it and maybe somewhere down the line it gets fixed as part of something else.

---

<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:** [22 August 2023 19:28 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/58 "2023-08-22T19:28:30Z")

</div>

> [@gerry](#):
>
> In all fairness to the developers, I really don't care if I have to deploy twice.

Assuming that you are talking about your problem with MQTT then it is unlikely to get fixed as your problem is different to the one with the beta release. As far as we know you are the only one suffering from it.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [22 August 2023 20:18 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/59 "2023-08-22T20:18:10Z")

</div>

The question becomes, is it really worth the developers efforts since it's only me and it could be some quirk in how my systems are setup.

---

<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:** [22 August 2023 20:40 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/60 "2023-08-22T20:40:32Z")

</div>

I does not necessarily need developer's effort. The community is here to help.  
**[Edit]** And if it is a bug then they want to know as others will fall over it at some point.

---

<div class="post-metadata">

**Author:** ![paulkeates](https://avatars.discourse-cdn.com/v4/letter/p/9de053/32.png) [@paulkeates](https://discourse.nodered.org/u/paulkeates)\
**Post date:** [23 August 2023 02:47 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/61 "2023-08-23T02:47:46Z")

</div>

Hi,

I think I've come across a bug when using 3.1.0-beta.4.  
I'm currently on node v18.16.1.  
Windows 10.

I use subflows a lot (roughly 150 of them in this project) and this issue was not happening until my recent changes. The recent change is I started using the "Catch" node with the new beta "Group" option:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/c/acfc0a6ecc7d87be911169c591c23ad8f86e003e.png)  
This is a really cool and convenient feature - but it (perhaps) has broken my project.  
Maybe in conjunction with subflows?

On startup I see the following errors (TypeError: node.scope.map is not a function.  
This is repeated maybe 20 times:

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

Any help would be much appreciated.

Cheers,

Paul

---

<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:** [23 August 2023 07:53 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/62 "2023-08-23T07:53:23Z")

</div>

I am seeing the same issue. This flow shows it. The error appears in the log when node-red is restarted and the flow does not work.

```auto
[{"id":"039005d502896edb","type":"subflow","name":"Subflow 1","info":"","in":[{"x":50,"y":30,"wires":[{"id":"7662deb88cab3cbe"}]}],"out":[{"x":800,"y":140,"wires":[{"id":"7662deb88cab3cbe","port":0}]},{"x":800,"y":200,"wires":[{"id":"6f18a6e32a2f8def","port":0}]}]},{"id":"7662deb88cab3cbe","type":"function","z":"039005d502896edb","g":"9a74e2979cb28746","name":"function 5","func":"//let x=0\n//x.fred = 1\nnode.warn(\"in f5\")\nnode.error(\"oops\",msg)\nreturn msg;","outputs":1,"timeout":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":440,"y":140,"wires":[[]]},{"id":"6f18a6e32a2f8def","type":"catch","z":"039005d502896edb","g":"9a74e2979cb28746","name":"","scope":"group","uncaught":false,"x":450,"y":200,"wires":[[]]},{"id":"9a74e2979cb28746","type":"group","z":"039005d502896edb","style":{"stroke":"#2e333a","stroke-opacity":"1","fill":"#383c45","fill-opacity":"0.5","label":true,"label-position":"nw","color":"#dddddd"},"nodes":["6f18a6e32a2f8def","7662deb88cab3cbe"],"x":354,"y":99,"w":192,"h":142},{"id":"72cab79983d3f248","type":"subflow:039005d502896edb","z":"bdd7be38.d3b55","name":"","x":580,"y":2500,"wires":[["8c2483a1f0e6b663"],["458d6034cefdf45e"]]},{"id":"ed21d62cce182ca3","type":"inject","z":"bdd7be38.d3b55","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":380,"y":2500,"wires":[["72cab79983d3f248"]]},{"id":"8c2483a1f0e6b663","type":"debug","z":"bdd7be38.d3b55","name":"debug 100","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":750,"y":2500,"wires":[]},{"id":"458d6034cefdf45e","type":"debug","z":"bdd7be38.d3b55","name":"debug 101","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":750,"y":2560,"wires":[]}]

```

[Previous page](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091.md?page=2)

[Next page](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091.md?page=4)