# 🎉 Node-RED 1.0.0-beta.2 released

**URL:** <https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504>\
**Category:** News\
**Created:** [24 May 2019 13:15 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504 "2019-05-24T13:15:39Z")\
**Posts on this page:** 20\
**Page:** 2

<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:** [27 May 2019 20:29 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/21 "2019-05-27T20:29:57Z")

</div>

All reported issues fixed:

- ✅ TypedInput is broken for Boolean type
- ✅ Pinned Debug message background
- ✅ TreeList Children api
- ✅ Status icon not being drawn

Thanks for the feedback - keep it coming.

---

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [28 May 2019 00:59 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/22 "2019-05-28T00:59:39Z")

</div>

> [@knolleary](#):
>
> keep it coming.

I am not sure if I am doing something wrong or this could be really something to look at...

1 - Build the most bassic flow  
2- try to export to library

Nothing happens when clicking buttom `Export to library`

I tried in a windows machine as well as on a Raspberry.

---

<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:** [28 May 2019 06:41 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/23 "2019-05-28T06:41:12Z")

</div>

> [@Andrei](#):
>
> Nothing happens when clicking buttom `Export to library`

Any errors in the browser log?

---

<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:** [28 May 2019 09:10 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/24 "2019-05-28T09:10:18Z")

</div>

Same happened to me and then I realised we have to click on local before clicking on export

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

---

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [28 May 2019 12:49 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/25 "2019-05-28T12:49:46Z")

</div>

@knolleary, yes Nick. See below:

 ![t-02](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/455967dd74f21936c2a2083517c6375c887bd045.png)

but it works as @cymplecy well noted (tks Simon).

---

<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:** [28 May 2019 12:57 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/26 "2019-05-28T12:57:39Z")

</div>

Fixed:

- ✅ Library browser now auto-selects first entry in the list to avoid that error

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [28 May 2019 14:56 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/27 "2019-05-28T14:56:54Z")

</div>

Hi Nick,  
Just wondering when you say the various 'issues' have been 'fixed'...  
Do I have to wait for the next beta release to get them??

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [28 May 2019 15:07 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/28 "2019-05-28T15:07:49Z")

</div>

Don't know if it has been fixed together with "Library browser now auto-selects first entry" fix so

Export editor if trying to Download the flow, error in browser and no functionality.

![error](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/6/65e2869014693570b1d643ab5eac8d4103a9e231.jpeg)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/d2ef418496e37d59bf7ce4ef05f9c339acd75bce.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:** [28 May 2019 15:10 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/29 "2019-05-28T15:10:56Z")

</div>

Thanks for reporting - fixed:

- ✅ Library export download button

---

<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:** [28 May 2019 15:30 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/30 "2019-05-28T15:30:32Z")

</div>

> [@dynamicdave](#):
>
> Just wondering when you say the various 'issues' have been 'fixed'...  
> Do I have to wait for the next beta release to get them??

Yes. You don't get the fixes until we release them. We'll be refreshing the beta once a week (or there abouts).

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [30 May 2019 12:39 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/31 "2019-05-30T12:39:12Z")

</div>

I've upgraded to Node-RED v1.0.0-beta.2  
I am seeing strange dropdown rendering behavior using the UDP in / out and TCP in/out/request nodes. I tested my local flow in both Firefox and Chrome and see the blank dropdown fields in both browsers. I have reinstalled node-red-bluemix-nodes v1.1.10 and still see the issue.

 ![udp-node-rendering](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/7/73250624dd28f925134c6c848803288177c2db66.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:** [30 May 2019 13:21 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/32 "2019-05-30T13:21:41Z")

</div>

Thanks for reporting @johnwalicki. That is odd; I don't think we've seen that with other modules that provide their own i18n messages. Will investigate.

---

<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:** [30 May 2019 13:42 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/33 "2019-05-30T13:42:48Z")

</div>

do we have udp and tcp on bluemix ? If so they would be their own nodes so may never have been i18n

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [30 May 2019 13:46 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/34 "2019-05-30T13:46:59Z")

</div>

Yes - The UDP / TCP nodes render correctly on IBM Cloud (running Node-RED v0.20-5). I have not tried to install Node-RED v1.0 Beta on IBM Cloud yet.

---

<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 May 2019 14:22 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/35 "2019-05-30T14:22:24Z")

</div>

Does that mean you have installed `node-red-bluemix-nodes` locally? That module is not really intended for local use as a lot of the nodes assume they are running in the IBM Cloud environment. Did the module work locally prior to 1.0?

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [30 May 2019 15:00 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/36 "2019-05-30T15:00:16Z")

</div>

Yes, node-red-bluemix-nodes works locally. I only mention it because that's what provides the UDP and TCP nodes. I need the UDP node to control the drone. I can roll back to Node-RED v0.20 to test again.

---

<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 May 2019 15:01 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/37 "2019-05-30T15:01:52Z")

</div>

> [@johnwalicki](#):
>
> I only mention it because that's what provides the UDP and TCP nodes

Well no - the core node-red palette includes UDP/TCP nodes. You do not need bluemix-nodes installed to have them available. The bluemix-nodes module provides custom versions of those nodes for the IBM Cloud environment - and the bluemix-settings.js file is configured to block loading of the core tcp/udp nodes so they don't clash.

---

<div class="post-metadata">

**Author:** ![pvanklink](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@pvanklink](https://discourse.nodered.org/u/pvanklink)\
**Post date:** [30 May 2019 15:39 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/38 "2019-05-30T15:39:24Z")

</div>

Hi i installed node-red version v 0.20.5 on a raspberry pi 3b+ with the latest raspbian stretch desktop  
with this command:  
bash \<(curl -sL [https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered](https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered))

When i enter to upgrade to the latest beta:  
sudo npm install -g --unsafe-perm node-red@next  
i get: sudo: npm: opdracht niet gevonden

i read that i had to specify @next, do i have to type something else, so what?

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [30 May 2019 15:59 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/39 "2019-05-30T15:59:29Z")

</div>

Interesting! I didn't know there were two versions of the UDP/TCP nodes. Independent of my v1.0 bug report, on my local instance, I'll flip back to the core Node-RED palette nodes. Regardless, it looks like a rendering / i18n bug in node-red-watson-nodes with Node-RED v1.0

---

<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:** [30 May 2019 17:35 UTC](https://discourse.nodered.org/t/node-red-1-0-0-beta-2-released/11504/40 "2019-05-30T17:35:28Z")

</div>

> [@pvanklink](#):
>
> opdracht niet gevonden

That says that the npm command isn't found which is a bit odd if the bash install script ran OK.  
what does `node -v` report ?

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

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