# 🎉 Node-RED 3.1.0-beta.2 released

**URL:** <https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192>\
**Category:** News\
**Created:** [6 March 2023 18:06 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192 "2023-03-06T18:06:24Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [7 March 2023 12:18 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/21 "2023-03-07T12:18:05Z")

</div>

@Steve-Mcl Yes - in FireFox and Chrome - it does seem like it only works the first time for any one node until you refresh then it will again only work once - noter a deploy doesn't change it only the page refresh does, And as I said, in Safari, some of the nodes never seem to work while others do.

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [7 March 2023 13:04 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/22 "2023-03-07T13:04:38Z")

</div>

On a Mac, ctrl-cmd-f triggers the search instead of going full screen.

And ctrl-click on the workspace brings up the context menu on top of the quick-add dialog.

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

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [7 March 2023 14:59 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/23 "2023-03-07T14:59:24Z")

</div>

The JSONata Expression Editor test is having problems

Example message

```auto
{
    "topic": "alexa/Oregon Sensor 01/Temperature/Update"
}

```

Error message

```auto
Invalid example JSON message:
  SyntaxError: Expected double-quoted property name in JSON at position 60

```

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [7 March 2023 15:02 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/24 "2023-03-07T15:02:22Z")

</div>

> [@mbonani](#):
>
> On a Mac, ctrl-cmd-f triggers the search instead of going full screen.

What version of macOS are you running? For me on Ventura ctrl-cmd-f takes me to full screen while on Mojave the first time I do ctrl-cmd-f it brings up the search panel and it I do it again, it goes full screen

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [7 March 2023 15:08 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/25 "2023-03-07T15:08:36Z")

</div>

> [@zenofmud](#):
>
> on Mojave the first time I do ctrl-cmd-f it brings up the search panel and it I do it again, it goes full screen

I'm on Ventura, and I see this same behavior.

---

<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 March 2023 15:16 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/26 "2023-03-07T15:16:19Z")

</div>

Similar errors in Chrome on Windows.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/8/783e6db365f4a895bd69b96c7f9dac5650e747a2.png)

Seems that the expression is not re-evaluated unless there is a syntax error in the Example message part

---

<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 March 2023 17:01 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/27 "2023-03-07T17:01:32Z")

</div>

- Search button in palette popover only works once - now fixed in git
- JSONata Expression tester - now fixed in git

---

<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:** [7 March 2023 17:19 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/28 "2023-03-07T17:19:09Z")

</div>

Is anyone else seeing problems with link call nodes? After the upgrade some(all?) of my link call nodes are showing the red triangle. I haven't had time to work out why yet.

---

<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:** [7 March 2023 17:31 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/29 "2023-03-07T17:31:03Z")

</div>

I saw a problem with link calls too.  
Think it went away after opening the node config for each one.

---

<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:** [7 March 2023 17:35 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/30 "2023-03-07T17:35:16Z")

</div>

> [@jbudd](#):
>
> Think it went away after opening the node config for each one.

Yes, you are right. After the upgrade, existing link call nodes show the error. Opening the node and clicking Done removes the error and the Deploy button is enabled.

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [7 March 2023 19:32 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/32 "2023-03-07T19:32:38Z")

</div>

I just learned that Apple changed the global keyboard shortcut for "Enter Full Screen" to fn-f in Monterey.

It partially works on Chrome. It goes full screen and then shows the search dialog.

On Safari, it brings up the search. It goes full screen if I hit fn-f a second time.

---

<div class="post-metadata">

**Author:** ![tve](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tve/32/59475_2.png) [@tve](https://discourse.nodered.org/u/tve)\
**Post date:** [8 March 2023 02:31 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/33 "2023-03-08T02:31:18Z")

</div>

> [@knolleary](#):
>
> Yes. However that is only useful if the user knows the help tab is there, and there is no direct link between the two.

I was just looking at the new help button and IMHO the little icon button at the bottom is quite useless. If you don't know it's there it's really hard to see. I don't see it at all unless I go looking for it. The value of the "HELP" button at the top is that it's in the field of view of a relatively new user that is a bit lost and directs them to "hey, maybe this is a good moment to read the help text for this node". I don't think the button at the bottom does that. Just my 2 cents...

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [8 March 2023 11:33 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/34 "2023-03-08T11:33:23Z")

</div>

Could I re-raise my request from the last beta to have a "remove and reconnect" in the right-context menu please

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

---

<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:** [11 March 2023 16:57 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/35 "2023-03-11T16:57:43Z")

</div>

Suspect this isn't a 3.1 issue but just spotted anyway.

In the JSONata editor:

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

Says that `msg` is referenced in the JSONata code but it most certainly isn't (the bits you can't see are the same pattern as what you can see).

This is in a change node

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/8/18e52363f545b8e4e4358d68ff2c266a4963d761.png)

Presumably because the text `msg` appears in a comment.

---

<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:** [11 March 2023 17:18 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/36 "2023-03-11T17:18:23Z")

</div>

Oh! Found one thing, then found another! This one I think IS v3.1 related.

Trying to add a title to a group and it would not process the "Done" button. Checked the console and saw this:

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

This is the flow

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

The inner group headings still edit OK, it is just this outer heading that will not update. I tried just updating one of the colours and had the same error.

Strangely, I can edit the heading on another compound group and it works fine. But it had been created before I upgraded to the beta.

PS: Full flow is available here: [uibuilder dynamic SVG example - no framework needed (flow) - Node-RED (nodered.org)](https://flows.nodered.org/flow/89487d20c635d54d9b98d963656ce429#)

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [11 March 2023 17:51 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/37 "2023-03-11T17:51:43Z")

</div>

Not sure if is just me; when inserting a` junction` it appears at seemingly random locations, certainly NOT under the cursor.

---

<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:** [11 March 2023 19:41 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/38 "2023-03-11T19:41:05Z")

</div>

> [@TotallyInformation](#):
>
> this isn't a 3.1 issue

Correct. This has been the behaviour ever since JSONata was introduced. It is doing simple regex checking to see if msg is mentioned, rather than a full syntactically parse.

---

<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:** [11 March 2023 19:41 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/39 "2023-03-11T19:41:57Z")

</div>

> [@Buckskin](#):
>
> seemingly random locations

Do you mean "offset by a few pixels" or entirely different flow tabs/locations etc? A screenshot would be helpful

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [11 March 2023 23:01 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/40 "2023-03-11T23:01:00Z")

</div>

Same flow tab, but more than a few pixels

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/6/c6e5056e5ed298c3f12a7d7cf826b536d513e55a.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:** [11 March 2023 23:46 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192/41 "2023-03-11T23:46:55Z")

</div>

That looks like you have zoomed out? Is that correct? Exactly what method of adding a junction node are you using?

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

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