# Node-red-node-serialport 0.6.8 not working (0.4.2 do)
**URL:** https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007
**Category:** General
**Created:** [18 November 2018 17:11 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007 "2018-11-18T17:11:33Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [18 November 2018 17:11 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/1 "2018-11-18T17:11:33Z")
Sorry about that generally topic, but i do not really know how to ask.
I have a heatpump system with an USB-Interface which sends and receives simple Strings like "13 1234"
Want ro read/write this strings.
With my Device A it works
Device B not works (no data in or out), but i have no idea why.
When i Install the older version of the node-red-node-serialport node it works fine. But what can i try, that i can use newer version?
THANK YOU
Device A:
Hardware NanoPi NEO2
Ubuntu core 16.04 LTS 4.11.2
Linux 4.11.2 arm64 LE
Node.js version: v4.2.6
Node-RED version: v0.16.2
-\> node-red-node-serialport 0.4.2
Device B:
Hardware NanoPi NEO2
Ubuntu core 16.04 LTS 4.14.52
Linux 4.14.52 arm64 LE
Node.js version: v4.2.6
Node-RED version: v0.19.5
-\> node-red-node-serialport 0.6.8
--\> After installing node-red-node-serialport 0.4.2 the serial port works fine
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [18 November 2018 18:24 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/2 "2018-11-18T18:24:37Z")
You are using a very old version of nodejs that is out of nodejs support. While v0.19 of Node-RED supports it, it will be the last version that does. [https://nodered.org/blog/2018/08/14/version-0-19-released](https://nodered.org/blog/2018/08/14/version-0-19-released)
node-red-node-serialport relies on the serialport package. That package only supports Active Maintenence and LTS version of nodejs.
My guess is the v0.19.5 of Node-RED is requesting the latest version of serialport which doesn't support nodejsV4.
Have you tried updating nodejs to v8 or v10 and then trying?
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [18 November 2018 19:24 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/3 "2018-11-18T19:24:08Z")
My System is tested and stable since years, but you are right. Maybe this will solve my problem.
The image vor the nanopi neo2 is on ubuntu 16.04. I hope nodeJS 10 works well on that system.
I will try ...
Thank you.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 November 2018 22:30 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/4 "2018-11-18T22:30:19Z")
> [@KirchnerAlex](#):
>
> My System is tested and stable since years, but you are right. Maybe this will solve my problem.
> The image vor the nanopi neo2 is on ubuntu 16.04. I hope nodeJS 10 works well on that system
I'm afraid that you really can't rest on your laurels when it comes to computers. You need to keep patching and updating.
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [18 November 2018 22:46 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/5 "2018-11-18T22:46:16Z")
Thats what i mean:
The newer version gives me tonnes of errors:
Ubuntu core 16.04 LTS
Linux 4.14.52
npm -v 6.4.1
node -v 8.12.0 LTS
Node-RED version: v0.19.5
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
....
node-pre-gyp ERR! Tried to download(404):
....
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute ....
....
node-red-node-serialport 0.6.8
> > not possible to install
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 November 2018 22:48 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/6 "2018-11-18T22:48:11Z")
> [@KirchnerAlex](#):
>
> node-pre-gyp ERR! Tried to download(404):
> ....
> node-pre-gyp ERR! build error
> node-pre-gyp ERR! stack Error: Failed to execute ....
Do you have build tools installed? Looks like you are missing something that Gyp needs.
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [18 November 2018 22:51 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/7 "2018-11-18T22:51:54Z")
I have done exactly that, nothing else
sudo apt install curl
curl -sL [https://deb.nodesource.com/setup\_8.x](https://deb.nodesource.com/setup_8.x) | sudo bash -
sudo apt-get install nodejs
sudo npm install -g --unsafe-perm node-red node-red-admin
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [18 November 2018 23:13 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/8 "2018-11-18T23:13:15Z")
You need to
```
sudo apt-get install build-essential python-dev
```
Then retry the node-red serialport imstall
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [18 November 2018 23:39 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/9 "2018-11-18T23:39:02Z")
> [@dceejay](#):
>
> sudo apt-get install build-essential python-dev
I have done that and after that i was able to install "serial-node" via the pallette in node-red.
Serial Interface now works (not to forget to put the user into the group "dialout" π
What i am not understand is, why there ar so many errors in Node-Red, when i follow the "official" insallation manual. There are important files which are missing to download etc.
I need to install abput 100 Raspi and i want to have a good feeling on stability, but it is not that easy.
Anyway!
Thank you for helping me out!
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [18 November 2018 23:43 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/10 "2018-11-18T23:43:52Z")
> bcrypt@2.0.1 install /usr/lib/node\_modules/node-red/node\_modules/bcrypt
> node-pre-gyp install --fallback-to-build
node-pre-gyp ERR! Tried to download(404): [https://github.com/kelektiv/node.bcrypt.js/releases/download/v2.0.1/bcrypt\_lib-v2.0.1-node-v57-linux-arm64-glibc.tar.gz](https://github.com/kelektiv/node.bcrypt.js/releases/download/v2.0.1/bcrypt_lib-v2.0.1-node-v57-linux-arm64-glibc.tar.gz)
node-pre-gyp ERR! Pre-built binaries not found for bcrypt@2.0.1 and node@8.12.0 (node-v57 ABI, glibc) (falling back to source compile with node-gyp)
make: Entering directory '/usr/lib/node\_modules/node-red/node\_modules/bcrypt/build'
CXX(target) Release/obj.target/bcrypt\_lib/src/blowfish.o
make: g++: Command not found
bcrypt\_lib.target.mk:101: recipe for target 'Release/obj.target/bcrypt\_lib/src/blowfish.o' failed
make: \*\*\* [Release/obj.target/bcrypt\_lib/src/blowfish.o] Error 127
make: Leaving directory '/usr/lib/node\_modules/node-red/node\_modules/bcrypt/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node\_modules/npm/node\_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:198:12)
gyp ERR! System Linux 4.14.52
gyp ERR! command "/usr/bin/node" "/usr/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/usr/lib/node\_modules/no de-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node" "--module\_name=bcrypt\_lib" "--module\_path=/usr/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding" " --napi\_version=3" "--node\_abi\_napi=napi"
gyp ERR! cwd /usr/lib/node\_modules/node-red/node\_modules/bcrypt
gyp ERR! node -v v8.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module= /usr/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node --module\_name=bcrypt\_lib --module\_path=/usr/lib/node\_modules/node-red/node\_modules/b crypt/lib/binding --napi\_version=3 --node\_abi\_napi=napi' (1)
node-pre-gyp ERR! stack at ChildProcess. (/usr/lib/node\_modules/node-red/node\_modules/bcrypt/node\_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:126:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)
node-pre-gyp ERR! stack at maybeClose (internal/child\_process.js:915:16)
node-pre-gyp ERR! stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:209:5)
node-pre-gyp ERR! System Linux 4.14.52
node-pre-gyp ERR! command "/usr/bin/node" "/usr/lib/node\_modules/node-red/node\_modules/bcrypt/node\_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/lib/node\_modules/node-red/node\_modules/bcrypt
node-pre-gyp ERR! node -v v8.12.0
node-pre-gyp ERR! node-pre-gyp -v v0.9.1
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/node /usr/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/lib/node\_modules/node-red/ node\_modules/bcrypt/lib/binding/bcrypt\_lib.node --module\_name=bcrypt\_lib --module\_path=/usr/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding --napi\_versio n=3 --node\_abi\_napi=napi' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@2.0.1 (node\_modules/node-red/node\_modules/bcrypt):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@2.0.1 install: `node-pre-gyp install --fallback-to-build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
- node-red@0.19.5
added 319 packages from 308 contributors in 207.105s
0.19.5
npm WARN deprecated bcrypt@0.8.7: bcrypt \< v2.0.0 is susceptible to bcrypt wrap-around bug. Upgrade to bcrypt \>= v2.0.0 for improved support for newer bcrypt hashes
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated boom@2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated hoek@2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles@2.0.5: This version is no longer maintained. Please upgrade to the latest version.
> bcrypt@0.8.7 install /home/pi/.node-red/node\_modules/bcrypt
> node-gyp rebuild
make: Entering directory '/home/pi/.node-red/node\_modules/bcrypt/build'
CXX(target) Release/obj.target/bcrypt\_lib/src/blowfish.o
make: g++: Command not found
bcrypt\_lib.target.mk:101: recipe for target 'Release/obj.target/bcrypt\_lib/src/blowfish.o' failed
make: \*\*\* [Release/obj.target/bcrypt\_lib/src/blowfish.o] Error 127
make: Leaving directory '/home/pi/.node-red/node\_modules/bcrypt/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node\_modules/npm/node\_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:198:12)
gyp ERR! System Linux 4.14.52
gyp ERR! command "/usr/bin/node" "/usr/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/.node-red/node\_modules/bcrypt
gyp ERR! node -v v8.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@0.8.7 (node\_modules/bcrypt):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@0.8.7 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [19 November 2018 08:47 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/11 "2018-11-19T08:47:55Z")
HI,
the clue is near the top of the first error
So you still don't have quite enough pre-reqs.
As it happens these are only warnings - as they end with `npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1` - so in fact it should now work and be ok... - However the lack of g++ may well cause issues moving forwards, - as with serialport - and maybe other extra modules, so it would be best to fix.
Most full fat (ie default installs) come with the necessary pre-reqs which is probably why we missed them from the list. - Normally `sudo apt get install build-essential` should be all that is needed - but maybe not in Ubuntu core...
Also note that we do now have a snap version of Node-RED available via their snap store.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [19 November 2018 09:38 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/12 "2018-11-19T09:38:40Z")
Hmm- just had a look at Ubuntu core... - that is not exactly a standard Linux install - so no wonder we don't have docs for it π - Would be happy to receive some docs if you or anyone are willing ?!?
But please note there is still an outstanding issue with snaps and usb serial ports - [[Announce] Node-RED snap 0.19.5 available](https://discourse.nodered.org/t/announce-node-red-snap-0-19-5-available/4715)
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [19 November 2018 17:41 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/13 "2018-11-19T17:41:24Z")
Thank you for your thoughts!!! Now I begin to understand!
I love to write docs, but i can do it about topics i anderstand. Linux is not one of these.
Be happy to build a system where i can test my ideas ...
This snap-thing is very interesting, i anyway want to try.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [19 November 2018 18:06 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/14 "2018-11-19T18:06:19Z")
Indeed. But being the first to try this (publically) under core makes you the expert ! π
Let know how you get on.
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [19 November 2018 19:48 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/15 "2018-11-19T19:48:57Z")
WOW - easy living!
Hardware: Nanopi-NEO2 from FriendlyARM
[http://wiki.friendlyarm.com/wiki/index.php/NanoPi\_NEO2](http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2)
Burn a fresh SD-Card with Win32diskImager:
-\> nanopi-neo2\_sd\_friendlycore-xenial\_4.14\_arm64\_20181011.img
-\> this is Ubuntu 16.04 Core with 4.14 Kernel
Start the Pi and log in via putty
-\> user "pi" and password "pi" (standard)
Install snap
$ sudo apt update
$ sudo apt install snapd
Install node (Node-RED recommend V8 on their Website (2018-11-19))
$ sudo snap install node --channel=8/stable --classic
Install Node-RED:
$ sudo snap install node-red
Reboot the PI
$ sudo reboot now
Wait for 30 Seconds
Go to your browser and try
[http://nanopi-neo2:1880](http://nanopi-neo2:1880)
or find out the ip-address of yor pi ond try
[http://ip-address:1880](http://ip-address:1880)
Really Great!
Comments π
Node-Red runs as a service and start up with ubuntu - GREAT!
serial I/O node is installed and works perfect! - GREAT!
Install Dashboard-Nodes via Menue -\> Manage palette -\> node-red-dashboard
-\> works perfect (maybe the numbers in the msg.payloay tell you nothing, but they are fine)
π§
Node-Red is running under root
-\> is this save?
-\> i have no idea.
You find the settings.js in /root/snap/node-red/current
"current" is just a link to the "real" directory (in my case "157")
Over all a great and very easy solution to install nodejs and node-red!
**Great Job! Big "thank you" to the devs.**
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [19 November 2018 20:21 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/16 "2018-11-19T20:21:28Z")
Create Password hash for node-RED Admin:
Install bcryptjs:
$ sudo npm install bcryptjs
$ node -e "console.log(require('bcryptjs').hashSync(process.argv[1], 8));" your-password
-\> gives you the hash for your-password back
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [19 November 2018 21:12 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/17 "2018-11-19T21:12:00Z")
Ideally you don't run in "classic" mode as that does indeed then give you full access - but as per the issues USB serialport is not fully (easily) supported in confined mode - so yes classic is probably the way to go for serial for now...
So yes root is a concern - but depends what the risk profile for your devices and their operation is.
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [19 November 2018 22:41 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/18 "2018-11-19T22:41:13Z")
What does "confined" mean for the USB-serialport. Is it only the group "dialout" or is it more to do? I don't try that mode.
Do you have a link, where i can read all that stuff about "classic" and "confined"?
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [19 November 2018 23:31 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/19 "2018-11-19T23:31:56Z")
> **[Demystifying Snap Confinement | Snapcraft](https://snapcraft.io/blog/demystifying-snap-confinement)**
>
> Snaps introduce some new concepts to the Linux ecosystem which developers can take advantage of, and snap users need to appreciate. When installing a snap, itβs important to understand what parts of the system the application wants access to. Itβs up...
---
### Author:  [@KirchnerAlex](https://discourse.nodered.org/u/KirchnerAlex)
#### Post date: [9 December 2018 20:19 UTC](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007/20 "2018-12-09T20:19:39Z")
In most Howtos you can read that the User who runs node-Red must be in the user group "dialout" like "/dev/ttyUSB0"
**BUT!**
I found out, that Node-RED also has to run under "root" like "/dev/ttyUSB0".
Than you have no problems at all.
[Next page](https://discourse.nodered.org/t/node-red-node-serialport-0-6-8-not-working-0-4-2-do/5007.md?page=2)