# 🎉 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:** 2

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

</div>

Just noticed a small issue.

The status display now seems to be forced to have a white background instead of transparent:

On the beta:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/e/fe35b5b59b4d8ded184d22177d8f51094d5942c4.png)

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

---

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

</div>

Is that a theme issue or should the css not have changed?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 August 2023 17:47 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/23 "2023-08-06T17:47:21Z")

</div>

They are meant to be semi opaque (I think) This was a change to improve the look when wires cross under the status area.

---

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

</div>

More `opaque` than `semi` it would seem. 🙂

Not the end of the world, I'm sure I can adjust the theme if needed. I use a darker background on my dev PC to reduce the contrast. Helps with my aging eyes!

---

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

</div>

Which theme are you using? It is ok for me with midnight-red and dark, from @node-red-contrib-themes/theme-collection, and with the default theme. This is midnight-red

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/9/196029bbf2c7ea378d7b69014a4bbbf26fc08732.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:** [6 August 2023 20:41 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/26 "2023-08-06T20:41:16Z")

</div>

Just something I hacked together. I didn't like any of the dark themes and I only needed to adjust a few things.

---

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

</div>

We can create a new theme that suits your needs. 😉

---

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

</div>

I'd love that. Mostly I need something that is like the standard theme just with the contrast toned down so that it doesn't burn out my eyes when working in a low-light room.

I've currently got this:

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

Instead of:

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

Doesn't look as dramatic as pics as it does on a 27" hi-def screen. I already put my screens into lower brightness in the evenings but the white and light grey of the default theme is still eye watering.

---

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

</div>

I just sent you a DM.

---

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

</div>

Got a strange one - don't seem able to add any code into a function node

I don't get any cursor appearing and nothing appears when I type anything  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/f/af3b8f3dbebc4d6d8990ecfc8c4eefb891e2d765.png)

Win11, Vivaldi  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/4/740edee00d02cdae0c1bb8bd51b4057683632890.png)

Found this out while testing out in this thread

> [@How to get lengthy values out of the editor?](https://discourse.nodered.org/t/how-to-get-lengthy-values-out-of-the-editor/80421/3):
>
> You can send the value to console in the debug node config, were it will not be truncated . Or Here is a [subflow](https://discourse.nodered.org/t/pausing-the-debug-window/76815/5) where you can send the msg or any property of it to a separarte browser window, where you can copy it if you wish.

---

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

</div>

@cymplecy most likely due to a node you've recently installed causing a clash of some sort. I've been mostly offline this last week, but I think I saw a similar issue was reported and fixed in our (FlowForge) dashboard nodes. If you have that installed, please make sure you've updated to the lastest (0.0.9 at the time of writing).

---

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

</div>

updating the new FF dashboard to 0.0.9 fixed the editing/no-code appearing issue 🙂

---

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

</div>

I am seeing an occasional problem with mqtt nodes, but I have not been able to replicate it. I do have the new flowforge dashboard installed, but I think it is unlikely that is related. The symptom is that when I try to deploy it says that a set of my mqtt nodes are misconfigured. To make the error go away I have to open the mqtt config node and click Done, then it will deploy ok. One time it happened I told it to deploy anyway, then opened the config node and when I clicked done it said I needed to deploy, but when I did that the flows file was exactly as it was before.

As I said I have not been able to work out what is triggering the issue, and it may be nothing to do with the beta release, but I thought I should mention it in case others have seen it.

---

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

</div>

Would be good if you could get a repro down please Colin 🤞

---

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

</div>

I have the same issue with MQTT. [https://discourse.nodered.org/t/when-i-restart-node-red-mqtt-broker-nodes-show-error/79081](https://discourse.nodered.org/t/when-i-restart-node-red-mqtt-broker-nodes-show-error/79081)

In that thread I said the problem went away when I reinstalled the entire OS, but it's back now on the same Raspberry Pi Zero 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:** [20 August 2023 23:22 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/36 "2023-08-20T23:22:43Z")

</div>

To chime in I see it too  
[edit]  
Pi 4, all the updates ver 3.02

---

<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 07:47 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/37 "2023-08-21T07:47:47Z")

</div>

> [@jbudd](#):
>
> I have the same issue with MQTT

It does look like the same problem, after reading your post I realise that opening the config node, clicking Update and deploying makes the error disappear, if I then refresh the browser they come back.

As both you and @gerry are seeing it on 3.02 it isn't a 3.1 beta problem so I will re-open your thread and carry on over there. If anyone has any ideas how to diagnose what is going on then please join us at [When I restart Node-red, or refresh the browser, MQTT broker & nodes show error](https://discourse.nodered.org/t/when-i-restart-node-red-mqtt-broker-nodes-show-error/79081)

---

<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 08:44 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/40 "2023-08-21T08:44:42Z")

</div>

Well to clarify, the machine I see it on is running 3.1.0-beta.4.

To further confuse things: yesterday it was misbehaving, today all seems OK.

Restarting Node-red, rebooting the NR device and clearing the browser cache do not currently trigger the errors.

As I mentioned in the other thread but can't currently confirm, messages do still flow through the MQTT nodes marked with the red triangle.  
Does that suggest the problem is with the code which identifies a bad connection rather than actual mqtt processing?

---

<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 12:36 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/41 "2023-08-21T12:36:25Z")

</div>

> [@gerry](#):
>
> To chime in I see it too

Hi @gerry, can you confirm that you are seeing the same problem? Refreshing the browser brings up the red triangles, opening the config node and clicking Update and Deploy clears it, but another refresh brings them back? Meanwhile the flow continues to work correctly.

---

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

</div>

> [@jbudd](#):
>
> Well to clarify, the machine I see it on is running 3.1.0-beta.4.

Oh yes, I had missed that.  
Do you have the new dashboard installed?

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

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