# 🎉 Node-RED 1.0.0-beta.4 released

**URL:** <https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577>\
**Category:** News\
**Created:** [16 September 2019 14:48 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577 "2019-09-16T14:48:42Z")\
**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:** [16 September 2019 14:48 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/1 "2019-09-16T14:48:42Z")

</div>

We have published the final beta of Node-RED 1.0.

This release sweeps up a number of bug fixes and brings us very close to the final release.

### Cloning messages

Following the feedback on the last beta, some more changes were needed to help minimise the impact the move to asynchronous message passing brings.

This release, as I described on the [blog last week](https://nodered.org/blog/2019/09/13/cloning-messages), changes the default behaviour of the Function node to always clone messages passed to `node.send()`.

If you didn't follow the discussion in the last beta release thread, have a read of the [blog post](https://nodered.org/blog/2019/09/13/cloning-messages) to find out what has changed.

### Removed Nodes (again)

**We have removed some _more_ nodes from the default palette.**

In additional to the other nodes we removed in the last beta, the **Sentiment** nodes is no longer installed by default. It is now in its own npm module and can be installed separately.

## Installing the beta

If you want to try out the beta, you will need specify node-red@next when you use npm to update. Without the `@next` you'll still get 0.20.x.

So on a Pi you'd do:

```auto
sudo npm install -g --unsafe-perm node-red@next

```

## Reporting problems

If you hit any problems, please report them either as a reply on this topic, or in the #dev slack channel. Please do not post new topics to the forum regarding the beta as that could confuse users who are not using the beta.

## Outstanding work

We had intended beta.3 to be the final beta before the full release, but we wanted to get the message cloning change into the hands of beta testers - we didn't want to leave that until the final release.

Good progress is being made on the various other things we need in place for the release and we're on track for releasing 1.0 on .... well, lets not spoil that surprise just yet.

---

<div class="post-metadata">

**Author:** ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)\
**Post date:** [16 September 2019 14:55 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/2 "2019-09-16T14:55:07Z")

</div>

Great news! I will update my test installation shortly.

Thank you for your hard work! 😀

---

<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:** [16 September 2019 18:37 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/3 "2019-09-16T18:37:51Z")

</div>

I still have an issue with node-red-contrib-static-markdown.

The Editor tells me it isn't installed:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/0/0829922fbbd7a9e98c32ae337bc68a67728663e2.png)  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/c/c02c702cf2c84a19e3fff82d1e7d06f85ad106d2.png)

The palette manager tells me it kind of is but kind of isn't:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/9/911cd7ba9a318499756557760a4d6ea0855a1459.png)

The console tells me it is:

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

And it _is_ serving things up:

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

I'm confused. I've tried removing and re-adding it from the command line (when NR isn't running).

---

<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:** [16 September 2019 18:42 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/4 "2019-09-16T18:42:24Z")

</div>

I'd contact the author of the node for clarification 😉

PS - just installed it locally and all fine for me....

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/e/e54188a77b1954000264733ea90caa24ea57e609.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:** [16 September 2019 18:47 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/5 "2019-09-16T18:47:28Z")

</div>

I would do but he is a lunatic who likes shouting abuse at me so I do my best to avoid him 🤓

Any other suggestions?

---

<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:** [16 September 2019 18:49 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/6 "2019-09-16T18:49:06Z")

</div>

nope - it's working here...

---

<div class="post-metadata">

**Author:** ![phantom](https://avatars.discourse-cdn.com/v4/letter/p/e0b2c6/32.png) [@phantom](https://discourse.nodered.org/u/phantom)\
**Post date:** [17 September 2019 07:33 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/7 "2019-09-17T07:33:39Z")

</div>

Upgraded to 1.0.0-beta.4 and seeing this.  
Using nodes from node-red-contrib-modbus in a PLC-HMI application.  
This is the error from the console:

(node:7245) UnhandledPromiseRejectionWarning: TypeError: a is not a function  
at activateSending (/home/pi/.node-red/node\_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:577:20)  
at process.\_tickCallback (internal/process/next\_tick.js:68:7)

Down-graded to 1.0.0-beta.2 and problem goes away.  
Has anyone else seen this issue?

---

<div class="post-metadata">

**Author:** ![elch](https://avatars.discourse-cdn.com/v4/letter/e/4af34b/32.png) [@elch](https://discourse.nodered.org/u/elch)\
**Post date:** [17 September 2019 22:10 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/8 "2019-09-17T22:10:52Z")

</div>

I am running V1.0 beta 4 since yesterday. I thought I had messed up as I can confirm on android 9 I am running node-red ui ok and switching tabs, BUT  
+++++++ I cannot get get node-red flow.  
I get title Node-red on black background with thw red signature for it with a blank screen

Pete Scargill has similar problem cannot tab when using Android  
NR tabs editor don’t work in Android chrome.

On Android 9 flows  
So by firefox does not work.  
By Chrome does not work

Windows still works with ui and flow on firefox and chrome  
All works on windows 7 as normal

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [19 September 2019 19:24 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/9 "2019-09-19T19:24:18Z")

</div>

> [@knolleary](#):
>
> sudo npm install -g --unsafe-perm node-red@next

Correct - sorry I was on holiday and could not really write much. On my Android tablet - I tried going into the Node-Red editor to update the Alexa code in a function attached to node-red-contrib-alexa-echo. I normally do sush function coding on a PC. In Node-Red I could use the arrows at the top of the screen to switch from tab to tab but could not actually SELECT any of the tabs so I gave up. As I normally work on a PC (and only use NR DASHBOARD on Android) I had no idea if this was a new problem or not.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [19 September 2019 19:58 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/10 "2019-09-19T19:58:25Z")

</div>

> [@scargill](#):
>
> On my Android tablet... (wanted to) switch from tab to tab but could not actually SELECT any of the tabs so I gave up

@elch @scargill - Yes, it's an outstanding problem for which Nick is aware of.

It appears that there is no touch handling code (or it's not working as it should).  
The work around is a but fiddly though -  
Tap the tab that you want to select, then immediately drag it to one side - just a little bit, and release.  
You should find the focus will then move to that tab.

I got caught out with that when I was also away from home, and needed to make a flow change.

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [19 September 2019 21:05 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/11 "2019-09-19T21:05:06Z")

</div>

Hey thanks for that – would a usb mouse do the job until they fix it?

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [19 September 2019 21:19 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/12 "2019-09-19T21:19:47Z")

</div>

> [@scargill](#):
>
> would a usb mouse do the job...until they fix it?

I assume so because it's the 'touch' handler that's not working.

Although not a great solution, the 'touch, drag, release' work-around does work, and once that you have selected the tab, most other edit functions do work to enable the flow to be edited.

---

<div class="post-metadata">

**Author:** ![elch](https://avatars.discourse-cdn.com/v4/letter/e/4af34b/32.png) [@elch](https://discourse.nodered.org/u/elch)\
**Post date:** [21 September 2019 14:01 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/13 "2019-09-21T14:01:38Z")

</div>

hello Paul-Reed

Thanks for the quick answer will try your temp soloution

regards elch

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [24 September 2019 19:49 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/14 "2019-09-24T19:49:20Z")

</div>

I just ran into what is seemingly a bug with the "Complete" node.

When I exported a flow containing a "Complete" node, and imported it to another Pi also running v1.0.0b4, the link between the "Complete" node and the node it was watching was broken and had to be re-established.

I was able to replicate the issue multiple times.

---

<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:** [24 September 2019 20:05 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/15 "2019-09-24T20:05:17Z")

</div>

> [@dudleyjosh](#):
>
> When I exported a flow containing a "Complete" node, and imported it to another Pi also running v1.0.0b4, the link between the "Complete" node and the node it was watching was broken and had to be re-established.

Good spot - thanks for reporting. Now fixed in git.

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [24 September 2019 20:18 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/16 "2019-09-24T20:18:39Z")

</div>

Wow, thanks for the quick work!

One other thought on this... for the "Complete", "Status" & "Catch" nodes, it would be really handy if they had the same "invisible" connection lines like the "Link" nodes show.

---

<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:** [24 September 2019 20:22 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/17 "2019-09-24T20:22:25Z")

</div>

> [@dudleyjosh](#):
>
> it would be really handy if they had the same "invisible" connection lines like the "Link" nodes show.

Yup, that thought has occurred to us. It's a post-1.0 thought though. The link nodes are handled as a special case in the view code - it needs to be refactored to make it easier for other node types to be able to make use of it.

---

<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:** [24 September 2019 20:58 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/18 "2019-09-24T20:58:31Z")

</div>

needs lots of thinking through though... (so as Nick says not until after 1.0)... such as where on other nodes would it connect to - as lots of them don't have output connectors and some do... so would a virtual connector be added or ... etc.. not going to think about it now.

---

<div class="post-metadata">

**Author:** ![kazuhitoyokoi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kazuhitoyokoi/32/621_2.png) [@kazuhitoyokoi](https://discourse.nodered.org/u/kazuhitoyokoi)\
**Post date:** [27 September 2019 02:00 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/19 "2019-09-27T02:00:13Z")

</div>

I tried Node-RED v1.0.0-beta.4 on Internet Explorer 11 on Windows 10. I found that "Selection to subflow" doesn't work correctly. For example, after converting the template node to subflow, the subflow newly emerges but the template node still remains on the workspace. (As we know, the template node needs to be removed because the subflow node contains the template node.) After this operation, some nodes cannot connect to other nodes.

![ie](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/5/56b5de1cbda92e368370a384a2ff78ed6be4d4c3.gif)

Additionally, I found that there're other non-critical problems as follows.

(1) The logo name is just "Node-".  
(2) Node icons don't appear in the workplace.  
(3) Icon size in typedInput is too large.

I think that BrowserStack is useful to check UI on multi-browsers...(Safari from Windows or Internet Explorer from Mac)

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [27 September 2019 07:39 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-4-released/15577/20 "2019-09-27T07:39:39Z")

</div>

@knolleary on iOS (13) the node-red editor does not load, is this a bug ?

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