Node Red v0.19.5 modbus serial rs 485 can not be installed

#1

Hello After updating node red ı can not install again node red Modbus Serial Rs 485 again

0 Likes

#2

I moved your question into general as “Core development” is, as per the description, the place for questions if you are helping to code the node-red application.

Please post the log file you get when you start Node-RED.
What machine you are running Node-RED on as well as any errors when you try to install the node.

0 Likes

#3

Node Red is running on raspberry pi It is giving 'Failed to install:node-red-contrib-serial-modbus
Error:Installed failed
Check the log for more information

0 Likes

#4

I would suggest you check the log then.

As well as supplying the other information I asked for…

1 Like

#5

Which node is it that you are trying to install? (node-red-something).

0 Likes

#6

Colin, I think this gives you the information you asked for

0 Likes

#7

Oh yes, I missed that.
@Hasan as well as providing the information asked for by @ukmoose, in a terminal run

cd ~/.node-red
npm install node-red-contrib-serial-modbus

and copy/paste the result here.

0 Likes

#8

msg : string[74734]

"npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/debug failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443↵npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.↵↵> serialport@4.0.7 install /home/pi/.node-red/node_modules/node-red-contrib-serial-modbus/node_modules/serialport↵> node-pre-gyp install --fallback-to-build↵↵node-pre-gyp info it worked if it ends with ok↵node-pre-gyp verb cli [ '/usr/bin/node',↵node-pre-gyp verb cli '/home/pi/.node-red/node_modules/node-red-contrib-serial-modbus/node_modules/serialport/node_modules/.bin/node-pre-gyp',↵node-pre-gyp verb cli 'install',↵node-pre-gyp verb cli '--fallback-to-build' ]↵node-pre-gyp info using node-pre-gyp@0.6.32↵node-pre-gyp info using node@10.14.1 | linux | arm↵node-pre-gyp verb command install []↵node-pre-gyp info check checked for "/home/pi/..."

14/12/2018, 11:58:28msg : string[42]

0 Likes

#9

you still haven’t posted the startup log for node-red which contains the details of what version of node-red what version of nodejs and what operating system you are running on.
It was also be useful to know what platform you are running this on

0 Likes

#10

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.168.77:1880
On Pi Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.
Started Node-RED graphical event wiring tool.
14 Dec 14:43:24 - [info]
Welcome to Node-RED

14 Dec 14:43:24 - [info] Node-RED version: v0.19.5
14 Dec 14:43:24 - [info] Node.js version: v10.14.1
14 Dec 14:43:24 - [info] Linux 4.14.34-v7+ arm LE
14 Dec 14:43:25 - [info] Loading palette nodes
14 Dec 14:43:32 - [info] Settings file : /home/pi/.node-red/settings.js
14 Dec 14:43:32 - [info] Context store : 'default' [module=memory]
14 Dec 14:43:32 - [info] User directory : /home/pi/.node-red
14 Dec 14:43:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Dec 14:43:32 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
14 Dec 14:43:32 - [warn]

Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

14 Dec 14:43:32 - [info] Starting flows
14 Dec 14:43:32 - [info] Started flows
14 Dec 14:43:32 - [info] Server now running at http://127.0.0.1:1880/
14 Dec 14:43:32 - [info] serial port /dev/ttyUSB0 opened at 9600 baud 7N1

0 Likes

#11

If you google the error it suggests that it is a DNS error so you pi cannot connect to npmjs.org
which it would need to download and install the package.

Check that you can access npmjs.org and then try again

0 Likes