# 🎉 Node-RED 2.0 Released

**URL:** <https://discourse.nodered.org/t/node-red-2-0-released/48647>\
**Category:** News\
**Created:** [20 July 2021 10:45 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647 "2021-07-20T10:45:29Z")\
**Posts on this page:** 18\
**Page:** 3

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [21 July 2021 09:53 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/41 "2021-07-21T09:53:11Z")

</div>

I would say that if you need to build flows for 1.3.x then you should just keep a local copy of 1.3.x around to build them one, that way you don't have to worry about things changing.

Anything else is just leaving you open to things working locally and breaking when deployed to the machines you have limited access to, making it even harder to debug/fix.

---

<div class="post-metadata">

**Author:** ![get\_joe](https://avatars.discourse-cdn.com/v4/letter/g/35a633/32.png) [@get\_joe](https://discourse.nodered.org/u/get_joe)\
**Post date:** [21 July 2021 09:56 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/42 "2021-07-21T09:56:00Z")

</div>

These error messages are getting spammed in the browser-console when opening the function editor, @Steve-Mcl.

```auto
TypeError: e[Symbol.iterator] is not a function
    at Object.e.first (editor.js:1)
    at Object.getCommand (editor.js:5)
    at Mn.executeCommand (editor.js:5)
    at Object.type (editor.js:5)
    at $e.type (editor.js:5)
    at editor.js:5
    at c.fire (editor.js:1)
    at HTMLTextAreaElement.<anonymous> (editor.js:5)
    at editor.js:1
editor.js:1 Uncaught Error: e[Symbol.iterator] is not a function

```

```auto
debug-utils.js:479 Uncaught TypeError: Cannot read property 'length' of undefined
    at HTMLDivElement.<anonymous> (debug-utils.js:479)
    at HTMLDivElement.handle (vendor.js:2)
    at HTMLDivElement.dispatch (vendor.js:2)
    at HTMLDivElement.v.handle (vendor.js:2)
(anonymous) @ debug-utils.js:479
handle @ vendor.js:2
dispatch @ vendor.js:2
v.handle @ vendor.js:2

```

---

<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:** [21 July 2021 10:01 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/43 "2021-07-21T10:01:49Z")

</div>

This is a known issue with an prototype polution caused by other nodes.

See this thread: [🎉 Node-RED 2.0.0-beta.1 Released - #84 by Botched1](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/84)

Do you have any of these nodes installed...

- [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) - fixed in v1.3.3
- [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) - fixed in v0.6.9
- [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) - fixed in v3.5.1
- [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) - fixed in v1.3.3
- [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) - fixed in v1.0.0
- [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) - fixed in v1.0.4

See here for workaround...

> [@tada Node-RED 2.0.0-beta.1 Released](https://discourse.nodered.org/t/node-red-2-0-0-beta-1-released/46990/93):
>
> If you (or anyone) does need the deconz node, the fix I posted before also works for that node... 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. 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. Stop / re-start node-red Refresh browser But the author is aware and does int…

---

<div class="post-metadata">

**Author:** ![spants](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@spants](https://discourse.nodered.org/u/spants)\
**Post date:** [21 July 2021 10:05 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/44 "2021-07-21T10:05:15Z")

</div>

I have a problem when docker updated to V2 - the node-red-contrib-enocean node v0.8.5 fails to load. I logged a comment testing the beta on his github but does anyone have a pointer on how to fix?

(loving the monaco editor and other bells and whistles!)

> 14 Jul 13:11:40 - [info] Flows stopped in safe mode. Deploy to start.  
> 14 Jul 13:11:40 - [info] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
> 14 Jul 13:12:54 - [info] Installing module: node-red-contrib-enocean, version: 0.8.5  
> 14 Jul 13:13:25 - [info] Installed module: node-red-contrib-enocean  
> 14 Jul 13:13:25 - [info] Added node types:  
> 14 Jul 13:13:25 - [info] - node-red-contrib-enocean:enocean-config-node : SyntaxError: Cannot use import statement outside a module  
> 14 Jul 13:13:25 - [info] - node-red-contrib-enocean:enocean-in  
> 14 Jul 13:13:25 - [info] - node-red-contrib-enocean:enocean-actor : SyntaxError: Cannot use import statement outside a module  
> 14 Jul 13:13:25 - [info] - node-red-contrib-enocean:enocean-out : SyntaxError: Cannot use import statement outside a module  
> 14 Jul 13:13:25 - [info] - node-red-contrib-enocean:enocean-btn  
> 14 Jul 13:14:42 - [info] Stopping flows

---

<div class="post-metadata">

**Author:** ![Deon](https://avatars.discourse-cdn.com/v4/letter/d/67e7ee/32.png) [@Deon](https://discourse.nodered.org/u/Deon)\
**Post date:** [21 July 2021 10:26 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/45 "2021-07-21T10:26:55Z")

</div>

There is a small issue with the delay node when set to rate limit and sending a msg.reset message throwing the error:

> "TypeError: Cannot read property 'hasOwnProperty' of undefined"

```auto
[{"id":"49c5f93c6e9995b4","type":"inject","z":"8ae02d5f.40148","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":920,"y":1140,"wires":[["2e22d894ed0e714c"]]},{"id":"2e22d894ed0e714c","type":"change","z":"8ae02d5f.40148","name":"","rules":[{"t":"set","p":"reset","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":1080,"y":1140,"wires":[["644d0a36bf3c0011"]]},{"id":"644d0a36bf3c0011","type":"delay","z":"8ae02d5f.40148","name":"","pauseType":"rate","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"allowrate":false,"x":1250,"y":1140,"wires":[[]]}]

```

---

<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:** [21 July 2021 10:27 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/46 "2021-07-21T10:27:23Z")

</div>

Hi @Deon

please raise an issue.

---

<div class="post-metadata">

**Author:** ![get\_joe](https://avatars.discourse-cdn.com/v4/letter/g/35a633/32.png) [@get\_joe](https://discourse.nodered.org/u/get_joe)\
**Post date:** [21 July 2021 11:01 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/47 "2021-07-21T11:01:27Z")

</div>

Updated the deconz node, and seems to be working now. Thanks!

---

<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:** [21 July 2021 17:31 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/48 "2021-07-21T17:31:04Z")

</div>

> [@knolleary](#):
>
> I'll make the change unless you have a PR on the way?

Have you done this Nick or do you want a PR?

---

<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:** [21 July 2021 17:40 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/49 "2021-07-21T17:40:49Z")

</div>

It's already fixed. 2.0.2 will be released tomorrow.

---

<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:** [21 July 2021 20:11 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/50 "2021-07-21T20:11:07Z")

</div>

I hate those nerve-wracking hours after a big release!

---

<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:** [22 July 2021 20:48 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/51 "2021-07-22T20:48:25Z")

</div>

I assume this is related to the RBE to Filter change... is there a way to clean up this notice manually?

 ![Screen Shot 2021-07-22 at 16.43.02](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/b/2b4f4078793b2c95eff07d56bb8eecfb9a63cd6c.png)

---

<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:** [22 July 2021 22:06 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/52 "2021-07-22T22:06:16Z")

</div>

See this : [Node-red-node-rbe in Manage Palette - #2 by knolleary](https://discourse.nodered.org/t/node-red-node-rbe-in-manage-palette/48724/2)

---

<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:** [23 July 2021 14:17 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/53 "2021-07-23T14:17:29Z")

</div>

@Steve-Mcl thanks!

---

<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:** [23 July 2021 18:17 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/54 "2021-07-23T18:17:47Z")

</div>

v2.0.3 has been released to address these issues - [🎉 Node-RED 2.0.3 Released](https://discourse.nodered.org/t/node-red-2-0-3-released/48816)

---

<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:** [23 July 2021 18:17 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/55 "2021-07-23T18:17:55Z")

</div>

Closed on 23 July 2021 18:17 UTC



---

<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:** [23 July 2021 18:47 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/56 "2021-07-23T18:47:45Z")

</div>

Opened on 23 July 2021 18:47 UTC



---

<div class="post-metadata">

**Author:** ![Per2J](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@Per2J](https://discourse.nodered.org/u/Per2J)\
**Post date:** [13 August 2022 18:28 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/57 "2022-08-13T18:28:56Z")

</div>

This saved me, I had a naughty deconz node installed on my Home Assistant setup. Thanks a lot for the list of "bad" nodes 🙂

---

<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 August 2022 19:45 UTC](https://discourse.nodered.org/t/node-red-2-0-released/48647/58 "2022-08-13T19:45:44Z")

</div>

Closed on 13 August 2022 19:45 UTC



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