# 🎉 Node-RED 2.0.0-beta.1 Released

**URL:** <https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990>\
**Category:** News\
**Created:** [10 June 2021 15:21 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990 "2021-06-10T15:21:18Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [13 June 2021 11:28 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/82 "2021-06-13T11:28:17Z")

</div>

Node removed, issue persists

---

<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:** [13 June 2021 11:33 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/83 "2021-06-13T11:33:10Z")

</div>

Hi Steve

Yes. It is all working now. I will move the zigbee devices to standard MQTT.

Still, be interesting to know WHY that node affects the editor

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [13 June 2021 12:20 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/84 "2021-06-13T12:20:19Z")

</div>

> [@Buckskin](#):
>
> node-red-contrib-zigbee2mqtt

I now have that node set installed on my test system (have always had it installed on one of my production servers), and in use, and I see the same thing. I can open - for example - a function node but can not enter any text in the editor.

I see this in the devtools console as soon as I try to type in the editor window:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/7/57e48619b85e944dea1b7f41bb602bbbbc939194.png)

Removing that palette, and then restarting node-red, fixes it. Doesn't fix it until a restart of node-red, though.

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [13 June 2021 12:25 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/85 "2021-06-13T12:25:10Z")

</div>

> [@JoseGodinho](#):
>
> Node removed, issue persists

Did you reboot/restart node-red after removing that palette? You need to restart before it will be fixed - if that is your original issue, of course.

---

<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:** [13 June 2021 12:52 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/86 "2021-06-13T12:52:51Z")

</div>

@Buckskin & @Botched1 - thank you - your posts have lead me to the cause (though I dont understand the exact reason why it breaks)

In short, `node-red-contrib-zigbee2mqtt` uses an old jQuery add-in called "multiple-select". If I disable that or update it, the editor does not break.

@Botched1, @Buckskin, @JoseGodinho If you wouldnt mind verifying my findings, please try the following...

1. Open `\node-red-contrib-zigbee2mqtt\static\js\multiple-select.min.js` in a text editor and replace the contents with [this updated version](https://raw.githubusercontent.com/wenzhixin/multiple-select/develop/dist/multiple-select.min.js) - then save & close the file.
2. Open `\node-red-contrib-zigbee2mqtt\static\css\multiple-select.css` in a text editor and replace the contents with [this updated version](https://raw.githubusercontent.com/wenzhixin/multiple-select/develop/dist/multiple-select.css) - then save & close the file.
3. Stop / re-start node-red
4. Refresh browser

Please let me know if this works for you and I will update the [github issue](https://github.com/andreypopov/node-red-contrib-zigbee2mqtt/issues/41) I raised

---

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [13 June 2021 16:21 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/87 "2021-06-13T16:21:25Z")

</div>

I did that !

---

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [13 June 2021 16:25 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/88 "2021-06-13T16:25:31Z")

</div>

Steve

I have removed the zigbee mentioned node and the problem persist.  
I have node test instance with a lot of nodes, could be that some other node causes a similar issue.

---

<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:** [13 June 2021 16:27 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/89 "2021-06-13T16:27:51Z")

</div>

> [@JoseGodinho](#):
>
> could be that some other node causes a similar issue

Possibly.

could you list the contrib nodes you have installed please?

---

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [13 June 2021 16:48 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/90 "2021-06-13T16:48:55Z")

</div>

Here you go .... I said a lot!!!

node-red-contrib-alexa-home-skill  
node-red-contrib-alexa-remote2  
node-red-contrib-array-permutations  
node-red-contrib-array-splitter  
node-red-contrib-boolean-logic-ultimate  
node-red-contrib-button-interpreter  
node-red-contrib-collector  
node-red-contrib-config  
node-red-contrib-cpu  
node-red-contrib-daikin-ac  
node-red-contrib-dashboard-average-bars  
node-red-contrib-dashboard-sum-bars  
node-red-contrib-deconz  
node-red-contrib-delta  
node-red-contrib-device-stats  
node-red-contrib-ewelink  
node-red-contrib-filter  
node-red-contrib-flow-combine  
node-red-contrib-fs  
node-red-contrib-hue-tunable-white  
node-red-contrib-image-output  
node-red-contrib-influxdb  
node-red-contrib-influxdb-backup  
node-red-contrib-interval  
node-red-contrib-linux-memory  
node-red-contrib-literal-utils  
node-red-contrib-logger  
node-red-contrib-match  
node-red-contrib-modbus  
node-red-contrib-moment  
node-red-contrib-mytimeout  
node-red-contrib-netatmo-dashboard  
node-red-contrib-nuki  
node-red-contrib-play-audio  
node-red-contrib-pushstaq  
node-red-contrib-remote  
node-red-contrib-samsung-automation-studio-nodes  
node-red-contrib-schedex  
node-red-contrib-simple-gate  
node-red-contrib-simple-message-queue  
node-red-contrib-simpletime  
node-red-contrib-solar-power-forecast-plus  
node-red-contrib-sonos-plus  
node-red-contrib-spotify  
node-red-contrib-string  
node-red-contrib-sun-position  
node-red-contrib-tfjs-coco-ssd  
node-red-contrib-time-range-switch  
node-red-contrib-toggle  
node-red-contrib-ui\_list  
node-red-contrib-ui-artless-gauge  
node-red-contrib-ui-clock  
node-red-contrib-ui-contextmenu  
node-red-contrib-ui-digital-display  
node-red-contrib-ui-led  
node-red-contrib-ui-level  
node-red-contrib-ui-multistate-switch  
node-red-contrib-ui-svg  
node-red-contrib-ui-value-trail  
node-red-contrib-uibuilder  
node-red-contrib-virtual-smart-home  
node-red-contrib-web-babylonjs  
node-red-contrib-xiaomi-sensors

---

<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:** [13 June 2021 17:08 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/91 "2021-06-13T17:08:21Z")

</div>

Wow, yes, a lot 😲

could you please help me prioritise / narrow this down somewhat?

Which of those nodes have a code editor (like the function node, infuxdb node, and the DB node in the samsung nodes? )

### EDIT

Never mind - I believe it is exactly the same issue as the `node-red-contrib-zigbee2mqtt` node.

The following packages all have an old version of the offending jQuery package **"multiple-select"** embedded in their src package (instead of using the npm version)

- [node-red-contrib-deconz-test-zehir](https://www.npmjs.com/package/node-red-contrib-deconz-test-zehir) - [issue raised](https://github.com/deconz-community/node-red-contrib-deconz/issues/140)
- [node-red-contrib-defaro](https://www.npmjs.com/package/node-red-contrib-defaro) - [issue raised](https://github.com/bkorda/node-red-contrib-defaro/issues/1)
- [node-red-contrib-zigbee2mqtt](https://www.npmjs.com/package/node-red-contrib-zigbee2mqtt) - [issue raised](https://github.com/andreypopov/node-red-contrib-zigbee2mqtt/issues/41)
- [node-red-contrib-wirenboard](https://www.npmjs.com/package/node-red-contrib-wirenboard) - [issue raised](https://github.com/andreypopov/node-red-contrib-wirenboard/issues/2)
- [node-red-contrib-deconz](https://www.npmjs.com/package/node-red-contrib-deconz) - [Issue raised](https://github.com/deconz-community/node-red-contrib-deconz/issues/140) - author is working on it 🙂
- [node-red-contrib-zway](https://www.npmjs.com/package/node-red-contrib-zway) - [Issue raised](https://github.com/bkorda/node-red-contrib-zway/issues/9)
- [node-red-contrib-spruthub](https://www.npmjs.com/package/node-red-contrib-spruthub) - [Issue raised](https://github.com/andreypopov/node-red-contrib-spruthub/issues/3)

---

<div class="post-metadata">

**Author:** ![JoseGodinho](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)\
**Post date:** [13 June 2021 17:48 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/92 "2021-06-13T17:48:44Z")

</div>

You are correct, just deleted deconz and its working

---

<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:** [13 June 2021 17:52 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/93 "2021-06-13T17:52:42Z")

</div>

If you (or anyone) does need the deconz node, the fix I posted before also works for that node...

1. Open `\node-red-contrib-deconz\static\js\multiple-select.min.js` in a text editor and replace the contents with [this updated version](https://raw.githubusercontent.com/wenzhixin/multiple-select/develop/dist/multiple-select.min.js) - then save & close the file.
2. Open `\node-red-contrib-deconz\static\css\multiple-select.css` in a text editor and replace the contents with [this updated version](https://raw.githubusercontent.com/wenzhixin/multiple-select/develop/dist/multiple-select.css) - then save & close the file.
3. Stop / re-start node-red
4. Refresh browser

But the author is aware and does intend on fixing the deconz nodes.

---

<div class="post-metadata">

**Author:** ![Botched1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/botched1/32/21190_2.png) [@Botched1](https://discourse.nodered.org/u/Botched1)\
**Post date:** [13 June 2021 18:58 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/94 "2021-06-13T18:58:51Z")

</div>

I can confirm that for me, making those two changes in the zigbee2mqtt node's js & css (then restarting node-red) fixes the editor issue where you can not enter new data.

---

<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:** [13 June 2021 19:48 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/95 "2021-06-13T19:48:02Z")

</div>

Checking the filter/rbe node in the palette, I'm seeing a warning - 'Type already registered'.  
I'm guessing it's because the node has 2 names and the warning can be disregarded.

![rbe](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/4/a4ba2c9c762ddf43c4d0cad684fc1a4f72aaa698.jpeg)

---

<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:** [13 June 2021 20:13 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/96 "2021-06-13T20:13:42Z")

</div>

We moved the rbe into core and relabelled it as filter. The “old” existing rbe node will still be there unless you remove it so yes it will create a warning.

---

<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:** [13 June 2021 20:35 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/97 "2021-06-13T20:35:30Z")

</div>

> [@dceejay](#):
>
> unless you remove it

Thanks.  
I've removed the filter node, and again installed `node-red@next` which has re-installed the filter node again as part of core.  
All good 👍

---

<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:** [13 June 2021 21:16 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/98 "2021-06-13T21:16:14Z")

</div>

Hi Steve

I can confirm that the `monaco` editor works with those changes. Thank you, saves me a bit of messing around.

---

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [14 June 2021 03:36 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/99 "2021-06-14T03:36:07Z")

</div>

In 2.0.0beta1, even if you access FlowEditor from a Chrome / Firefox browser whose language setting is Japanese, the display will be in English. It was possible to switch by selecting Japanese in User Settings-\> View.

---

<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:** [14 June 2021 06:13 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/100 "2021-06-14T06:13:16Z")

</div>

> [@utaani](#):
>
> if you access FlowEditor from a Chrome / Firefox browser whose language setting is Japanese, the display will be in English

Did you F5 refresh the browser after changing language?

---

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [14 June 2021 06:59 UTC](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/101 "2021-06-14T06:59:28Z")

</div>

> [@Steve-Mcl](#):
>
> Did you F5 refresh the browser after changing language?

My Chrome browser is set to Japanese, but it is still displayed in English no matter how many times I F5 with the "Browser default" setting.  
Then, if you set Language to Japanese in User Settings and then press F5, the display will be in Japanese. (This is as expected)

(The thing that I find problematic is that Browser default is displayed in English even though it is in Japanese.)

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

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