Node-RED 0.16.1 released

[Nicholas O'Leary]

Hi,

we did a small maintenance release today to tidy up some small things that had cropped up in 0.16:

Amongst the changes are:

 - we now explicitly warn if you are running on an unsupported version of node.js. This warning appears both in the console log and in the editor so you cannot miss it.

 - the -v option to enable verbose mode works again

 - certain types of node error weren't appearing in the debug pane

And as a bonus, if a node property is recognised as a hex colour value (ie #ff7700), we'll display a little colour swatch next to it.

Full release notes - https://github.com/node-red/node-red/releases/tag/0.16.1

Nick

[Mark Setrem]

"This warning appears both in the console log and in the editor so you cannot miss it." LOL I bet someone will ;-)

[hello world]

Thanks for all the nice new features and improvements!

Would it be possible to extend the object to the width of the debug window.  After 5, the "..." appears.

Cheers!

[Joey Langan]

I updated a few days ago to v16.0 (from 14.6?) using the update-nodejs-and-nodered script as user pi.  (I ran it (twice) with no issues (permission or install) and it added serial and my custom modules back in).  When I went to run to update to version 16.1 today, it told me I didn't have permission, and sure enough I didn't have execute

I did a sudo chmod 755 on the file.  Then (successfully) ran the update-node-js-and-nodered as user pi.  The file was changed back after going to 16.1 to where I don't have permission again ... is this by design?

-rw-r--r-- 1 root root       15458 Jan 17 18:05 update-nodejs-and-nodered

after running updating to the latest 16.1 from 16.0

One other question - what version of node.js should I be using on a Raspberry PI 3?  This script has me at v4.7.2 of node.js - but I see others with higher versions.  I'd like to use a newer version of node.js - I guess I expected the the script to install something like 6.9.4.

Thanks,

Joey

[Dave C-J]

Hi 

well node.js 4 is an LTS version - so I don't to force people off that just because...

If you want to get to node 6 - you can    sudo rm /etc/apt/sources.list.d/nodesource.list

and then re-run the update script - which should then go and get node 6 .

or   bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

[Colin Law]

Is the comment shown at the start a little awry, in that it says "This
script will remove any pre-installed versions of node.js and Node-RED
and replace them with node.js 6.x LTS (boron) and ..."?

Colin

> --
> http://nodered.org
>
> Join us on Slack to continue the conversation: http://nodered.org/slack
> ---
> You received this message because you are subscribed to the Google Groups
> "Node-RED" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to node-red+u...@googlegroups.com.
> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/node-red/CACXWFwKLQk7%3DVRF9RK2wv%3DzYa3tXrG3PSqK10erE-mnO1T1mTA%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.

[MaJoo]

Hello everybody,

My embedded system is an Odroid XU4 with Octa core, 2GB RAM and Debian.
I've been using Node-Red for a very long time. My flow.json is 1024kb big. Node-Red must work a lot.


I have updated from Node-Red 0.16.0 to 0.16.1 with the bash-Script. "curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered"

According to Script everything was OK.

___________________________________________________________
This can take 20-30 minutes on a Pi 1 - please wait.

  Stop Node-RED ✔
  Remove old version of Node-RED ✔
  Remove old version of node.js ✔
  Install node.js LTS ✔ Node v6.9.4 Npm 3.10.10
  Clean npm cache ✔
  Install Node-RED core ✔ 0.16.1
  Install extra nodes ✔
  Install serialport node ✔
  Npm rebuild existing nodes ✔
  Add menu shortcut ✔
  Update systemd script ✔
  Update update script ✔

Any errors will be logged to /var/log/nodered-install.log
____________________________________________________________


When I started Node-Red, it took an extremely long time until it ran.
Working with Node-Red was not possible.
Also the Dashboard did not work and got Connection lost.

With "apt-get purge nodejs" I removed nodejs v6.9.4 and installed with  "curl -sL https://deb.nodesource.com/setup_4.x | Bash -" + "apt-get install nodejs "the nodejs v4.7.2



After restarting Node-Red, it ran with the nomal speed. :-)

nodejs v6.9.4  slows down Node-Red ?




best regards

MaJoo

[Dave C-J]

Interesting,

Not heard of that anywhere else - but if anyone else has please shout.

certainly npm3 is slower than npm2 - but that is just installing nodes, not the runtime.

No problem with Node.js 4.x - it's an LTS version we like.

(in fact if you re run the script now it should leave 4.7.2 there and just upgrade Node-RED... but no need just yet... as you are now on 16.1)

[Paul Smith]

Hi Guys,

I've just updated NR to 16.1. I'm running it on a raspberry pi. It has been working fine. After the update / restart. It complained about missing node-red-node-serialport so i installed that.

However it keeps now crashing and looking in the log file i see the following. 

Jan 21 13:27:06 raspberrypi Node-RED[22553]: 21 Jan 13:27:06 - [error] [owfs:Airing] No usable messages received, but no error returned.

Jan 21 13:27:53 raspberrypi Node-RED[22553]: <--- Last few GCs --->

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 186266 ms: Mark-sweep 114.9 (148.5) -> 114.7 (148.5) MB, 2125.6 / 0 ms [allocation failure] [GC in old space requested].

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 188387 ms: Mark-sweep 114.7 (148.5) -> 114.8 (148.5) MB, 2120.8 / 0 ms [allocation failure] [GC in old space requested].

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 190514 ms: Mark-sweep 114.8 (148.5) -> 114.7 (148.5) MB, 2126.4 / 0 ms [last resort gc].

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 192661 ms: Mark-sweep 114.7 (148.5) -> 114.7 (148.5) MB, 2147.5 / 0 ms [last resort gc].

Jan 21 13:27:53 raspberrypi Node-RED[22553]: <--- JS stacktrace --->

Jan 21 13:27:53 raspberrypi Node-RED[22553]: ==== JS stack trace =========================================

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 2: arguments adaptor frame: 1->2

Jan 21 13:27:53 raspberrypi Node-RED[22553]: Security context: 0x46f6d639 <JS Object>

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 3: destroy [net.js:513] [pc=0x38a4ce80] (this=0x2fd68439 <a Socket with map 0x5165fe19>,exception=0x46f080dd <undefined>)

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 4: arguments adaptor frame: 0->1

Jan 21 13:27:53 raspberrypi Node-RED[22553]: 5: socketErrorListener [_http_client.js:287] [pc=0x25ce6e10] (this=0x2fd68439 <a Socket with map 0x5165fe19>,err=0x5dfdffcd <an Error with map 0x5165fffd>)

Jan 21 13:27:54 raspberrypi Node-RED[22553]: 6: emit [events.js:~117] [pc=0x4f07ab...

Jan 21 13:27:54 raspberrypi Node-RED[22553]: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

Jan 21 13:27:54 raspberrypi systemd[1]: nodered.service: main process exited, code=killed, status=6/ABRT

Jan 21 13:27:54 raspberrypi systemd[1]: Unit nodered.service entered failed state.

Jan 21 13:27:54 raspberrypi systemd[1]: nodered.service holdoff time over, scheduling restart.

Jan 21 13:27:54 raspberrypi systemd[1]: Stopping Node-RED graphical event wiring tool....

Jan 21 13:27:54 raspberrypi systemd[1]: Starting Node-RED graphical event wiring tool....

Jan 21 13:27:54 raspberrypi systemd[1]: Started Node-RED graphical event wiring tool..

Jan 21 13:27:57 raspberrypi Node-RED[22595]: 21 Jan 13:27:57 - [info]

Jan 21 13:27:57 raspberrypi Node-RED[22595]: Welcome to Node-RED

Jan 21 13:27:57 raspberrypi Node-RED[22595]: ===================

Jan 21 13:27:57 raspberrypi Node-RED[22595]: 21 Jan 13:27:57 - [info] Node-RED version: v0.16.1

Jan 21 13:27:57 raspberrypi Node-RED[22595]: 21 Jan 13:27:57 - [info] Node.js  version: v4.7.0

Jan 21 13:27:57 raspberrypi Node-RED[22595]: 21 Jan 13:27:57 - [info] Linux 4.4.34-v7+ arm LE

Jan 21 13:27:59 raspberrypi Node-RED[22595]: 21 Jan 13:27:59 - [info] Loading palette nodes

Jan 21 13:28:06 raspberrypi Node-RED[22595]: 21 Jan 13:28:06 - [info] Dashboard up and running

Jan 21 13:28:12 raspberrypi Node-RED[22595]: 21 Jan 13:28:12 - [info] Dashboard version 2.2.1 started at /ui

Jan 21 13:28:15 raspberrypi Node-RED[22595]: 21 Jan 13:28:15 - [info] Settings file  : /home/pi/.node-red/settings.js

Jan 21 13:28:15 raspberrypi Node-RED[22595]: 21 Jan 13:28:15 - [info] User directory : /home/pi/.node-red

Jan 21 13:28:15 raspberrypi Node-RED[22595]: 21 Jan 13:28:15 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json

Jan 21 13:28:15 raspberrypi Node-RED[22595]: 21 Jan 13:28:15 - [info] Server now running at https://127.0.0.1:1880/

Jan 21 13:28:17 raspberrypi Node-RED[22595]: 21 Jan 13:28:17 - [info] Starting flows

Can anyone tell me whats going on.

Regards

Paul

[Nick O'Leary]

Hi Paul,

the "process out of memory" line is the clue.

Do you have any websocket nodes in your flow? Specifically, websocket client nodes (ones that connect out, rather than accept inbound connections)? We've just fixed a memory leak in that node which we'll release later today.

If not, can you give a run down of what nodes you are using?

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/1ebb67ff-807b-40a2-8bc5-5ca1da2fbce0%40googlegroups.com.

[Paul Smith]

Hi Nick,

Thanks for the speedy response, Yes I do have some outbound WS to Kodi boxes around the house. How do you know WS is the problem from my log file or is it just coincidence.

Regards

Paul

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

[Nick O'Leary]

Hi Paul,

I don't know for a fact you've hit this problem, but the WebSocket memory issue is the first such issue we've had for a very long time. Whilst you could have hit another new memory issue,  I'd like to think that you've hit the one we know about.

If you wanted to try the fix out, here's the change: https://github.com/node-red/node-red/commit/0ffeb0c5afa98371b892c49a27b1f1cc313db88c to the file  node-red/nodes/core/io/22-websocket.js

Will get the fix out later today.

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/f1e5fae9-c255-4f39-99a1-eaaccbb12856%40googlegroups.com.

[Paul Smith]

Hi Nick,

Ok, I made the changes to the file, and now when i restart NR i get ....

Jan 21 14:05:57 raspberrypi Node-RED[23391]: Welcome to Node-RED

Jan 21 14:05:57 raspberrypi Node-RED[23391]: ===================

Jan 21 14:05:57 raspberrypi Node-RED[23391]: 21 Jan 14:05:57 - [info] Node-RED version: v0.16.1

Jan 21 14:05:57 raspberrypi Node-RED[23391]: 21 Jan 14:05:57 - [info] Node.js  version: v4.7.0

Jan 21 14:05:57 raspberrypi Node-RED[23391]: 21 Jan 14:05:57 - [info] Linux 4.4.34-v7+ arm LE

Jan 21 14:05:59 raspberrypi Node-RED[23391]: 21 Jan 14:05:59 - [info] Loading palette nodes

Jan 21 14:06:06 raspberrypi Node-RED[23391]: 21 Jan 14:06:06 - [info] Dashboard up and running

Jan 21 14:06:12 raspberrypi Node-RED[23391]: 21 Jan 14:06:12 - [info] Dashboard version 2.2.1 started at /ui

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [warn] ------------------------------------------------------

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [warn] [websocket] SyntaxError: Unexpected token )

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [warn] ------------------------------------------------------

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [info] Settings file  : /home/pi/.node-red/settings.js

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [info] User directory : /home/pi/.node-red

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json

Jan 21 14:06:15 raspberrypi Node-RED[23391]: 21 Jan 14:06:15 - [info] Server now running at https://127.0.0.1:1880/

Jan 21 14:06:17 raspberrypi Node-RED[23391]: 21 Jan 14:06:17 - [info] Waiting for missing types to be registered:

Jan 21 14:06:17 raspberrypi Node-RED[23391]: 21 Jan 14:06:17 - [info]  - websocket-client

Jan 21 14:06:17 raspberrypi Node-RED[23391]: 21 Jan 14:06:17 - [info]  - websocket in

Jan 21 14:06:17 raspberrypi Node-RED[23391]: 21 Jan 14:06:17 - [info]  - websocket out

Is this what you expect.

Regards

Paul

[Nick O'Leary]

Jan 14:06:15 - [warn] [websocket] SyntaxError: Unexpected token )

Suggests you've not applied the fix cleanly.

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/a40e7f49-2735-432d-93f8-608abca6b12b%40googlegroups.com.

[Paul Smith]

Hi Nick,

I've just download that whole file rather than manually updating it and it looks to be ok.

Thanks.

Regards

Paul

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/a40e7f49-2735-432d-93f8-608abca6b12b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---

You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/QcfUHJCxAls/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3Dvhqd22wMNMz1DeE-bnRgQ3Z3rPXqEiSKQthbY4axMZ-FyyA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Paul Smith

Your Local Computer Specialist, Supporting Your Business When You Need It Most

We also now do Portable Appliance Testing, if you would like to know more please drop us a line.

Tel:-  0845 009 6226 

This email and any attachments may be confidential and/or privileged.  Everything is intended for use of the addressee only. If you receive this message in error then you must not print it or pass it on to anyone else or use the information it contains.  Please inform Phoenix Technology UK  of the error by email or by telephoning (+44)(0)845 009 6226.  Please then delete all copies from your system.
If you are not the intended recipient then you must not use the information in the message or attachments or allow anyone else to do so.