Node-red dashboard nodes is not appearing

#1

Hi Guys I installed node-red dashboard from gitHub and the specifics nodes from node-red-dashboards is not appearing in the node-red framework.

install procedure: sudo npm Install node-red/node-rede-dashboard
all those files were included in the node-modules.

Somebody have an idea whats is happening?

Best Regards,
Alex

#2

You may need to restart node red and/or reload the page in the browser.

#3

You should not really use sudo - and that path will install the development version - not the release version. You also need to be in your node-red directory - usually ~/.node-red - so:

cd ~/.node-red
npm i node-red-dashboard

then restart Node-RED - should be all you need.
Or use the Manage Palette option in the menu to install it.
But you may need to clean up your existing install.
Also you don't mention which version of nodejs you are currently using.

#4

Hi Myplacedk and Dceejay I did it before. I have use "sudo" to install and restart node-red. But I uninstall and install again, and restar node-rede, using the establish version as Dceejay advise me. You can see the commands below:

But the dashboard nodes still not appearing In the node-red palette.

pi@raspberrypi:~ cd .node-red/ pi@raspberrypi:~/.node-red sudo npm i node-red-dashboard
node-red-dashboard@2.11.0 node_modules/node-red-dashboard
β”œβ”€β”€ serve-static@1.13.2 (escape-html@1.0.3, encodeurl@1.0.2, parseurl@1.3.2, send@0.16.2)
└── socket.io@2.1.1 (socket.io-adapter@1.1.1, has-binary2@1.0.3, socket.io-parser@3.2.0, debug@3.1.0, engine.io@3.2.1, socket.io-client@2.1.1)
pi@raspberrypi:~/.node-red $ sudo node-red restart

They have another idea?

#5

Assuming you're on a normal install on the Pi, that isn't how you restart Node-RED.

You should run:

node-red-stop
node-red-start
#6

Hi Guys, I stoped node-red and see that the node-red portal is not stoping. My node red running well. I have a project running well, but I don't know whats happening w/ node-red-dashboard.
I did it a few times and see the same behavior. I see during star and stop a few errors as you see below:

sudo node-red stop
19 Nov 10:30:35 - [info]

Welcome to Node-RED

19 Nov 10:30:35 - [info] Node-RED version: v0.19.4
19 Nov 10:30:35 - [info] Node.js version: v8.11.1
19 Nov 10:30:35 - [info] Linux 4.14.71-v7+ arm LE
19 Nov 10:30:40 - [info] Loading palette nodes
19 Nov 10:30:47 - [info] Settings file : /root/.node-red/settings.js
19 Nov 10:30:47 - [info] Context store : 'default' [module=memory]
19 Nov 10:30:47 - [info] User directory : /root/.node-red
19 Nov 10:30:47 - [warn] Projects disabled : editorTheme.projects.enabled=false
19 Nov 10:30:47 - [info] Flows file : /root/.node-red/stop
19 Nov 10:30:48 - [info] Creating new flow file
19 Nov 10:30:48 - [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.

19 Nov 10:30:48 - [info] Starting flows
19 Nov 10:30:48 - [info] Started flows
19 Nov 10:30:48 - [error] Unable to listen on http://127.0.0.1:1880/
19 Nov 10:30:48 - [error] Error: port in use

**[quote="aargollo, post:1, topic:5010, full:true"]
Hi Guys I installed node-red dashboard from gitHub and the specifics nodes from node-red-dashboards is not appearing in the node-red framework.

install procedure: sudo npm Install node-red/node-rede-dashboard
all those files were included in the node-modules.

Somebody have an idea whats is happening?

Best Regards,
Alex
[/quote]

No**v 10:31:03 - [info]

Welcome to Node-RED

19 Nov 10:31:03 - [info] Node-RED version: v0.19.4
19 Nov 10:31:03 - [info] Node.js version: v8.11.1
19 Nov 10:31:03 - [info] Linux 4.14.71-v7+ arm LE
19 Nov 10:31:09 - [info] Loading palette nodes
19 Nov 10:31:16 - [info] Settings file : /root/.node-red/settings.js
19 Nov 10:31:16 - [info] Context store : 'default' [module=memory]
19 Nov 10:31:16 - [info] User directory : /root/.node-red
19 Nov 10:31:16 - [warn] Projects disabled : editorTheme.projects.enabled=false
19 Nov 10:31:16 - [info] Flows file : /root/.node-red/start
19 Nov 10:31:16 - [info] Creating new flow file
19 Nov 10:31:16 - [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.

19 Nov 10:31:16 - [info] Starting flows
19 Nov 10:31:16 - [info] Started flows
19 Nov 10:31:16 - [error] Unable to listen on http://127.0.0.1:1880/
19 Nov 10:31:16 - [error] Error: port in use
pi@raspberrypi:~ $

#7

Hi Guys, in additional my recently post I did those commands and get success to stop node-red portal and nothing have changed. I didn't see dashboard nodes in the node-red portal.

udo systemctl stop nodered
udo systemctl start nodered

Somebody have an idea to fix it?

Best Regards
Alex

#8

You may have a version of NR already running which would cause this message.

From the command line run 'top -u pi' and see if node-red shows in the list (type 'q' to quit out of top'

#9

Hi guys, sorry for my mistake. I forgot to include "-" after node-red in the command. Now can stop and start node-red (sudo node-red-stop / node-red-start). I have only one stance working. But I still didn't see node-red-dashboard nodes in the portal.

I still trying to fix it.

Best Regards
Alex

#10

When you use node-red-start that starts node red with the systemd service file so it doesn't make any difference whether you use sudo or not. Post the log here that you see after running node-red-start. You can copy from the terminal using Ctrl-Shift-C. Also note that by using sudo to install nodes locally you will have created files with root permissions in your home folder, which will likely give you problems at some point.

#11

Hi Colin, I canΒ΄t find find an explanation for the problem. I already installed another tool and I didn't have the same problem!
I understood your concern about install node using root permission with sudo.

As you see bellow all those files and folders have the same owner!

Do you have another idea how to fix it?

tks
Alex

pi@raspberrypi:~ $ ls -lt
total 52
drwxr-xr-x 2 pi pi 4096 Nov 19 23:04 myScripts
drwxr-xr-x 3 pi pi 4096 Nov 19 22:55 node_modules
drwxr-xr-x 11 pi pi 4096 Nov 5 09:20 pyusb
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Desktop
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Documents
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Downloads
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Music
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Pictures
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Public
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Templates
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Videos
drwxr-xr-x 2 pi pi 4096 Oct 9 12:31 MagPi
drwxr-xr-x 2 pi pi 4096 Oct 9 12:31 python_games

#12

Do a ls -al to show the hidden files too

#13

You haven't posted the log I asked for.

#14

Hi Colin, sorry i dindt see your request. Would you see below the node-red-log:

Hi zenofmud, Would you see the "ls -al" result below:

I did stop and start to include it in the log.
Stopping Node-RED graphical event wiring tool...
20 Nov 10:05:21 - [info] Stopping flows
20 Nov 10:05:21 - [info] serial port /dev/ttyUSB0 closed
20 Nov 10:05:21 - [info] Stopped flows
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
20 Nov 10:05:50 - [info]
Welcome to Node-RED
===================
20 Nov 10:05:50 - [info] Node-RED version: v0.19.4
20 Nov 10:05:50 - [info] Node.js version: v8.11.1
20 Nov 10:05:50 - [info] Linux 4.14.71-v7+ arm LE
20 Nov 10:05:55 - [info] Loading palette nodes
20 Nov 10:06:03 - [info] Settings file : /home/pi/.node-red/settings.js
20 Nov 10:06:03 - [info] Context store : 'default' [module=memory]
20 Nov 10:06:03 - [info] User directory : /home/pi/.node-red
20 Nov 10:06:03 - [warn] Projects disabled : editorTheme.projects.enabled=false
20 Nov 10:06:03 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
20 Nov 10:06:03 - [info] Server now running at http://127.0.0.1:1880/
20 Nov 10:06:03 - [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.
---------------------------------------------------------------------
20 Nov 10:06:03 - [info] Starting flows
20 Nov 10:06:04 - [info] Started flows
20 Nov 10:06:04 - [info] serial port /dev/ttyUSB0 opened at 115200 baud 8N1
20 Nov 10:06:04 - [info] [debug:43313881.a42ee8]
<Buffer 01 80 02 10 02 10 02 15 4d 02 10 81 02 10 49 02 10 03>

/home/pi
pi@raspberrypi:~ $ ls -la
total 152
drwxr-xr-x 23 pi pi 4096 Nov 19 23:04 .
drwxr-xr-x 3 root root 4096 Oct 9 11:50 ..
-rw------- 1 pi pi 19373 Nov 20 03:02 .bash_history
-rw-r--r-- 1 pi pi 220 Oct 9 11:50 .bash_logout
-rw-r--r-- 1 pi pi 3523 Oct 9 11:50 .bashrc
drwxr-xr-x 5 pi pi 4096 Nov 2 21:11 .cache
drwx------ 8 pi pi 4096 Nov 2 21:11 .config
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Desktop
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Documents
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Downloads
drwx------ 3 pi pi 4096 Nov 2 21:11 .gnupg
drwxr-xr-x 3 pi pi 4096 Oct 9 12:31 .local
drwxr-xr-x 2 pi pi 4096 Oct 9 12:31 MagPi
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Music
drwxr-xr-x 2 pi pi 4096 Nov 19 23:04 myScripts
drwxr-xr-x 3 pi pi 4096 Nov 2 23:42 .node-gyp
drwxr-xr-x 3 pi pi 4096 Nov 19 22:55 node_modules
drwxr-xr-x 4 pi pi 4096 Nov 19 23:15 .node-red
drwxr-xr-x 121 pi pi 4096 Nov 19 22:55 .npm
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Pictures
-rw-r--r-- 1 pi pi 675 Oct 9 11:50 .profile
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Public
drwxr-xr-x 2 pi pi 4096 Oct 9 12:31 python_games
-rw------- 1 pi pi 74 Nov 8 22:33 .python_history
drwxr-xr-x 11 pi pi 4096 Nov 5 09:20 pyusb
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Templates
drwxr-xr-x 3 pi pi 4096 Nov 2 21:11 .themes
drwxr-xr-x 2 pi pi 4096 Nov 2 21:11 Videos
-rw------- 1 pi pi 56 Nov 18 20:43 .Xauthority
-rw------- 1 pi pi 4133 Nov 18 20:43 .xsession-errors
-rw------- 1 pi pi 4133 Nov 12 09:05 .xsession-errors.old

/home/pi/node_modules
pi@raspberrypi:~/node_modules $ ls -la
total 12
drwxr-xr-x 3 pi pi 4096 Nov 19 22:55 .
drwxr-xr-x 23 pi pi 4096 Nov 19 23:04 ..
drwxr-xr-x 5 pi pi 4096 Nov 19 22:55 node-red-dashboard

thanks guys!!
Best Regards
Alex

#15

That is the wrong folder, your local modules are stored in the .node-red folder so you want

cd ~/.node-red
ls -al
cd ~/.node-red/node_modules
ls -al
#16

Which explains why they are not appearing, as you were not in the .node-red directory when you installed them.

The easiest way to install them is to use the "Manage Palette" option within Node-RED

1 Like
#17

Hi Ukmoose.
The dashboard nodes in the node read web application is not avaialable. I seen only default nodes and HID Usb that i recently installed.

best Regards,
Alex

#18

Hi Guys,
I uninstalled node-red-dashboard via shell, that i installed before, and trying to install it node-red "Manage Palette. But i get error during install procedure, as they can see in the PIC attached.

#20

Please dio this
stop node-red - from a terminal type node-red-stop
go to the node-red directory cd $HOME/.node-red/node_modules
remove the dashboard if it exists rm node-red-dashboard -rf
change back to the .node-red directory cd $HOME/.node-red
install the dashboard npm install node-red-dashboard
restart node-red node-red-start
check to see if the dashboard nodes exist.

#21

Now, what was that I said earlier about getting access problems at some point due to using sudo to install nodes locally?

cd   ~/.node-red
sudo   chown  -R  pi:pi  .

Don't miss the dot on the end. That should set everything in that folder back to being owned by pi as it should be.