# 🎉 Node-RED 3.1.1 released

**URL:** <https://discourse.nodered.org/t/node-red-3-1-1-released/83318>\
**Category:** News\
**Created:** [30 November 2023 18:58 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318 "2023-11-30T18:58:47Z")\
**Posts on this page:** 20\
**Page:** 1

<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:** [30 November 2023 18:58 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/1 "2023-11-30T18:58:48Z")

</div>

Node-RED 3.1.1 is now available.

This is mostly a maintenance release with a number of fixes for issues reported against 3.1.0.

Full details in the changelog. The docker images are rebuilding as I type - will be available shortly.

> **[Release 3.1.1: Maintenace Release · node-red/node-red](https://github.com/node-red/node-red/releases/tag/3.1.1)**
>
> 3.1.1: Maintenance Release
> Editor
> 
> Fix debug filter (#4461) @knolleary
> Fix various issues with debug pop-out window (#4459) @knolleary
> Ensure subflow instances keep track of their groups (#4457) @k...

---

<div class="post-metadata">

**Author:** ![softy2k](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/softy2k/32/23707_2.png) [@softy2k](https://discourse.nodered.org/u/softy2k)\
**Post date:** [30 November 2023 20:56 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/2 "2023-11-30T20:56:54Z")

</div>

Finally, after some time. Thanks...

---

<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:** [30 November 2023 21:26 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/3 "2023-11-30T21:26:51Z")

</div>

Great, thanks.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [30 November 2023 23:38 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/4 "2023-11-30T23:38:17Z")

</div>

Thanks Nick and the team 😀

---

<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:** [1 December 2023 14:12 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/5 "2023-12-01T14:12:02Z")

</div>

I am seeing a number of nodes indicating a config error after the upgrade from 3.1.0, which is cleared by opening the node and closing it again. In particular for JSON nodes, if I export a node while it is showing the error then I see

```auto
[
    {
        "id": "442220a6.87889",
        "type": "json",
        "z": "c6d29a39.8cded",
        "name": "",
        "x": 347,
        "y": 386,
        "wires": [
            [
                "4e6acaf1.dd68fc"
            ]
        ]
    }
]

```

On one of the nodes that has been opened and closed I see

```auto
[
    {
        "id": "d2192921.3b1a58",
        "type": "json",
        "z": "c6d29a39.8cded",
        "name": "",
        "property": "payload",
        "action": "",
        "pretty": false,
        "x": 391,
        "y": 113,
        "wires": [
            [
                "805553da.d481c8",
                "71035c91.4658d4"
            ]
        ]
    }
]

```

So I guess that 3.1.1 does not cope with the missing properties.  
I also see a similar thing on filter (rbe) nodes, where

```auto
[
    {
        "id": "e4d9fae4.b7c7a8",
        "type": "rbe",
        "z": "9d3f7d2b.521328",
        "name": "",
        "func": "rbe",
        "gap": "",
        "start": "",
        "inout": "out",
        "property": "payload",
        "x": 100,
        "y": 350,
        "wires": [
            [
                "d9114c18.ab36d"
            ]
        ]
    }
]

```

goes to

```auto
[
    {
        "id": "e4d9fae4.b7c7a8",
        "type": "rbe",
        "z": "9d3f7d2b.521328",
        "name": "",
        "func": "rbe",
        "gap": "",
        "start": "",
        "inout": "out",
        "septopics": true,
        "property": "payload",
        "topi": "topic",
        "x": 100,
        "y": 350,
        "wires": [
            [
                "d9114c18.ab36d"
            ]
        ]
    }
]

```

and a Range node where `"property": "payload",` is added.

---

<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:** [1 December 2023 21:03 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/7 "2023-12-01T21:03:45Z")

</div>

Ah yes. We added improved validation of lots of node fields which were otherwise going ignored. I didn't take into account cases where older nodes don't have a particular properly set. Will revisit.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [1 December 2023 21:08 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/8 "2023-12-01T21:08:34Z")

</div>

This is why I wanted to add the type validator (typeField), so that the user updates his node and repair the changed property

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [4 December 2023 17:14 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/9 "2023-12-04T17:14:57Z")

</div>

> [@knolleary](#):
>
> The docker images are rebuilding as I type - will be available shortly.

The update I pulled from nodered/node-red:latest still shows 3.1.0 both in the log at startup and in the Editor side panel. Not only has NR been restarted, but the host has been rebooted as well. And the browser cache has been cleared.

Seems this happened to me a year or so ago too but I can't recall if the issue was the Docker image or something I did wrong/missed.

---

<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:** [5 December 2023 10:57 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/10 "2023-12-05T10:57:25Z")

</div>

> [@knolleary](#):
>
> I didn't take into account cases where older nodes don't have a particular properly set. Will revisit.

Is there likely to be a re-release within a week or so, or should I bite the bullet and open and close the 20 or so nodes that are complaining?

---

<div class="post-metadata">

**Author:** ![mickym2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mickym2/32/36128_2.png) [@mickym2](https://discourse.nodered.org/u/mickym2)\
**Post date:** [5 December 2023 14:01 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/11 "2023-12-05T14:01:12Z")

</div>

Will there be another maintenance release with correct validation of the nodes? Currently I am waiting and will not upgrade my production system.

---

<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:** [5 December 2023 14:05 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/12 "2023-12-05T14:05:43Z")

</div>

Yes, will revisit this week.

---

<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:** [5 December 2023 14:36 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/13 "2023-12-05T14:36:43Z")

</div>

Excellent, thanks.

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [7 December 2023 02:35 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/14 "2023-12-07T02:35:03Z")

</div>

> [@LosinIt](#):
>
> latest still shows 3.1.0

I'm the only one???

---

<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:** [7 December 2023 06:15 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/15 "2023-12-07T06:15:05Z")

</div>

> [@LosinIt](#):
>
> > [@LosinIt](#):
> >
> > latest still shows 3.1.0
> 
> I'm the only one??

Where?  
Have you performed an upgrade?

---

<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:** [7 December 2023 09:13 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/16 "2023-12-07T09:13:43Z")

</div>

> [@LosinIt](#):
>
> I'm the only one???

Hi @LosinIt

I've just pulled `nodered/node-red:latest` from docker and can confirm it is 3.1.1.

If you run `docker inspect nodered/node-red` you'll get a big blob of JSON. At the start is an `Id` field that will begin `"sha256:...."` - can you share that as well as the `RepoDigests` entry?

---

<div class="post-metadata">

**Author:** ![dan90ned](https://avatars.discourse-cdn.com/v4/letter/d/dbc845/32.png) [@dan90ned](https://discourse.nodered.org/u/dan90ned)\
**Post date:** [7 December 2023 11:08 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/17 "2023-12-07T11:08:41Z")

</div>

Hi all,  
I think I find an issue:  
If you have a nested group inside of a subflow like in the picture, after you make the update to 3.1.1 the start-up will stuck in "Starting flows"

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

---

<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:** [7 December 2023 11:21 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/18 "2023-12-07T11:21:43Z")

</div>

Hi @dan90ned

Thanks for reporting - I can recreate it locally. Am investigating.

---

<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:** [7 December 2023 11:50 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/19 "2023-12-07T11:50:07Z")

</div>

Fixed via [Ensure nested groups inside subflows have their g props remapped by knolleary · Pull Request #4472 · node-red/node-red · GitHub](https://github.com/node-red/node-red/pull/4472)

I'll do a 3.1.2 this afternoon.

---

<div class="post-metadata">

**Author:** ![dan90ned](https://avatars.discourse-cdn.com/v4/letter/d/dbc845/32.png) [@dan90ned](https://discourse.nodered.org/u/dan90ned)\
**Post date:** [7 December 2023 12:01 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/20 "2023-12-07T12:01:24Z")

</div>

Thank you very much for that!

---

<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:** [7 December 2023 14:34 UTC](https://discourse.nodered.org/t/node-red-3-1-1-released/83318/21 "2023-12-07T14:34:03Z")

</div>

3.1.2 is now available - [🎉 Node-RED 3.1.2 Released](https://discourse.nodered.org/t/node-red-3-1-2-released/83499)

[Next page](https://discourse.nodered.org/t/node-red-3-1-1-released/83318.md?page=2)