# 🎉 Node-RED 1.0 Released
**URL:** https://discourse.nodered.org/t/node-red-1-0-released/16091
**Category:** News
**Created:** [30 September 2019 13:19 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091 "2019-09-30T13:19:05Z")
**Posts on this page:** 20
**Page:** 3
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 October 2019 20:29 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/41 "2019-10-01T20:29:07Z")
> [@dceejay](#):
>
> Start uses - sudo systemctl start nodered
> Stop uses - sudo systemctl stop nodered
> Restart uses - sudo systemctl restart nodered
>
> so it is hardly "not the same"
Just one final post to explain the difference. `node-red-start` leaves the log running in the console. `node-red-restart` does not, it just restarts the service. So one has to do `node-red-restart && node-red-log` to achieve the same thing.
---
### Author:  [@krambriw](https://discourse.nodered.org/u/krambriw)
#### Post date: [2 October 2019 04:45 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/42 "2019-10-02T04:45:28Z")
> [@Colin](#):
>
> Interestingly I think the problem would not have shown itself (in this flow) in previous versions of node-red as the original message would have worked its way down the chain before the Join node got the chance to modify it.
Isn't this the same kind of symptom we experienced earlier with other parts? Like node.send in function nodes?
Is like throwing a handful of coins up in the air, you do not know in what order they will land but you better know how to sort them once they are picked up again
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [2 October 2019 06:07 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/43 "2019-10-02T06:07:38Z")
> [@krambriw](#):
>
> Isn't this the same kind of symptom we experienced earlier with other parts? Like node.send in function nodes?
But it also illustrates the good reason for changing the way NR works doesn't it? This _was_ a bug but wouldn't have shown itself except in a rare edge case, now it is obvious.
---
### Author:  [@krambriw](https://discourse.nodered.org/u/krambriw)
#### Post date: [2 October 2019 06:16 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/44 "2019-10-02T06:16:15Z")
Yeah, I do not argue against, it's just that you have to know what you are doing and the way it was before "allowed" for things maybe showing up as "surprises". The way it worked, as what I think is meant by the term flow, one after the other, maybe also made you think too much serial
---
### Author:  [@abajolle](https://discourse.nodered.org/u/abajolle)
#### Post date: [2 October 2019 06:37 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/45 "2019-10-02T06:37:04Z")
Thanks Nick and all the team involved in reaching this milestone, right on time 👍 !
Kudos !!!
---
### Author:  [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)
#### Post date: [2 October 2019 17:12 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/46 "2019-10-02T17:12:04Z")
Is anyone else missing the copy path / copy value icons in the debugger window with v1.0.0?
Update: they are missing in latest version of Chrome but they are working in the latest versions of Safari & Firefox.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [2 October 2019 17:33 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/47 "2019-10-02T17:33:02Z")
> [@dudleyjosh](#):
>
> Is anyone else missing the copy path / copy value icons in the debugger window with v1.0.0?
Any errors in the browser console? They work fine for me in all browsers.
---
### Author:  [@ghayne](https://discourse.nodered.org/u/ghayne)
#### Post date: [2 October 2019 17:53 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/48 "2019-10-02T17:53:46Z")
Working fine here with the latest Chrome on Manjaro Linux.
---
### Author:  [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)
#### Post date: [2 October 2019 18:41 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/49 "2019-10-02T18:41:29Z")
> [@knolleary](#):
>
> Any errors in the browser console? They work fine for me in all browsers.
There were no console errors.
It's working fine in Chrome now after a Command+Shift+R on the tab running Node-RED... I am assuming it was some sort of browser cache issue?
---
### Author:  [@tilleul](https://discourse.nodered.org/u/tilleul)
#### Post date: [2 October 2019 18:49 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/50 "2019-10-02T18:49:58Z")
Using Chrome v77.0.3865.90 here on Windows 10, copy path/value icons are present and working ...
---
### Author:  [@softy2k](https://discourse.nodered.org/u/softy2k)
#### Post date: [4 October 2019 06:16 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/51 "2019-10-04T06:16:09Z")
Working fine with Firefox 69.0.2 (Windows 7).
---
### Author:  [@snowjimmy](https://discourse.nodered.org/u/snowjimmy)
#### Post date: [5 October 2019 04:49 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/52 "2019-10-05T04:49:37Z")
Since I update nodered whith this release, one of my flows doesn't work anymore 😢
I reproduce the problem with few nodes and code:
As you can see on the debug console, the payload array disappear 🤔
I already remove and re-install nodered....
Thanks for your help
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [5 October 2019 09:43 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/53 "2019-10-05T09:43:33Z")
can you let us know the name of that extra node (node-red-contrib-???) and provide your test flow ([read this first](https://discourse.nodered.org/t/how-to-share-code-or-flow-json/506))
---
### Author:  [@snowjimmy](https://discourse.nodered.org/u/snowjimmy)
#### Post date: [5 October 2019 10:25 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/54 "2019-10-05T10:25:16Z")
This is the green extra node: node-red-node-snmp.snmp subtree
And my test flow:
```auto
[{"id":"e728b9ae.b7a4c8","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"df9eed44.3844f","type":"inject","z":"e728b9ae.b7a4c8","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":350.0187683105469,"y":297.0249938964844,"wires":[["4f276b88.c15e04"]]},{"id":"4dd8063b.257c78","type":"debug","z":"e728b9ae.b7a4c8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","x":947.024772644043,"y":188.9937162399292,"wires":[]},{"id":"c6f76aa9.9c9a58","type":"function","z":"e728b9ae.b7a4c8","name":"just returning msg","func":"\nreturn msg;","outputs":1,"noerr":0,"x":901.0249786376953,"y":307.0187187194824,"wires":[["4dd8063b.257c78"]]},{"id":"4f276b88.c15e04","type":"snmp subtree","z":"e728b9ae.b7a4c8","host":"localhost","community":"public","version":"2c","oids":"1.3.6.1.2.1.1.3","timeout":5,"name":"srv-pi001 sysUpTime","x":589.6187362670898,"y":299.8562717437744,"wires":[["c6f76aa9.9c9a58","4dd8063b.257c78"]]}]
```
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [5 October 2019 13:38 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/55 "2019-10-05T13:38:54Z")
> [@snowjimmy](#):
>
> node-red-node-snmp.snmp subtree
[edit]?? how did you install it? where did you get it from? never mind, I see it is part of node-red-node-snmp - let me take a look
[update] ok, sorry I can't help since I don't have and SNMP knowledge 🥴
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [5 October 2019 14:05 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/56 "2019-10-05T14:05:53Z")
Can you try adding this cloning function node on the output of your node SNMP node and see what happens?
---
### Author:  [@snowjimmy](https://discourse.nodered.org/u/snowjimmy)
#### Post date: [5 October 2019 15:08 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/57 "2019-10-05T15:08:32Z")
@zenofmud : I installed it with the GUI palette manager, and that work fine before updating release 1.0.0.
@cymplecy : I add the cloning function, and the twice nodes returns [empty] 😟
I try another flow test: the two function nodes are exactly the same (`return msg;`), and the result is really bizarre 🧐:
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [5 October 2019 15:12 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/58 "2019-10-05T15:12:39Z")
> [@snowjimmy](#):
>
> I add the cloning function, and the twice nodes returns an empty array
Do you mean both messages in the debug node are empty?
---
### Author:  [@snowjimmy](https://discourse.nodered.org/u/snowjimmy)
#### Post date: [5 October 2019 15:15 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/59 "2019-10-05T15:15:24Z")
> [@cymplecy](#):
>
> > [@snowjimmy](#):
> >
> > I add the cloning function, and the twice nodes returns an empty array
>
> Do you mean both messages in the debug node are empty?
yes, like on debug console: msg.payload : array[0] -\> [empty]
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [5 October 2019 15:21 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/60 "2019-10-05T15:21:31Z")
This is going to need @dceejay or @knolleary to sort out I think - something seems to be going wrong if the message is cloned
[Previous page](https://discourse.nodered.org/t/node-red-1-0-released/16091.md?page=2)
[Next page](https://discourse.nodered.org/t/node-red-1-0-released/16091.md?page=4)