Node-Red Whereabouts

[Peter Scargill]

I have a new BeagleBone Green - which came with Node-Red installed - I would normally take the lot out and re-install but they have a number of GROVE nodes specifically for that hardware in place and I don't want to lose them.

which node-red returns /usr/local/bin/node-red

I tried installing sudo npm install -g node-red-admin

All worked - but on restarting node-red no sign of it  - so within the "debian" user - I created a .node-red directory any in there I installed npm install node-red-contrib-bigtimer

Still nothing. In /home/debian/.node-red is the expected node-modules directory and my bigtimer - but neither are appearing in the node-red installation.

Can someone put me out of my misery - as I've always installed node-red myself - I've no idea how to get the various nodes to appear in this version as my normal installs are not working.

Pete.

[Nicholas O'Leary]

I'm not familiar with how the BeagleBone preinstall has been set up.

Are you running node-red manually? If so, what does it report as the "User directory" on start up?

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+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.
For more options, visit https://groups.google.com/d/optout.

[Peter Scargill]

It starts up automatically and was installed as part of the image – so I have no way to know how it is setup. The only reason I don’t scrap it and start again is that they have a load of hardware nodes setup and I don’t want to lose them.

 

Stopping the service and starting it manually…. It says

 

18 May 22:13:54 - [info] Node-RED version: v0.13.4

18 May 22:13:54 - [info] Node.js  version: v0.12.13

18 May 22:13:54 - [info] Linux 4.4.8-ti-r23 arm LE

18 May 22:13:54 - [info] Loading palette nodes

18 May 22:14:13 - [warn] ------------------------------------------

18 May 22:14:13 - [warn] Failed to register 2 node types

18 May 22:14:13 - [warn] Run with -v for details

18 May 22:14:13 - [warn] ------------------------------------------

18 May 22:14:13 - [info] Settings file  : /usr/local/lib/node_modules/node-red/settings.js

18 May 22:14:13 - [info] User directory : /home/debian/.node-red

18 May 22:14:13 - [info] Flows file : /home/debian/.node-red/flows_beaglebone.json

18 May 22:14:13 - [info] Creating new flow file

18 May 22:14:13 - [info] Starting flows

18 May 22:14:13 - [info] Started flows

18 May 22:14:13 - [info] Server now running at http://127.0.0.1:1880/

 

With –v I get in addition

 

18 May 22:15:07 - [warn] ------------------------------------------

18 May 22:15:07 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node

18 May 22:15:07 - [warn] [bbb] VError: Write to CapeMgr slots failed: EACCES, permission denied '/sys/devices/platform/bone_capemgr/slots'

18 May 22:15:07 - [warn] ------------------------------------------

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/zcpwv6G4UVU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

[Nicholas O'Leary]

So /home/debian/.node-red is the right place to run the npm installs of new nodes.

Next, check to see if the npm install has put the node in the right place. We have seen cases where if there is no node_modules directory in the directory you run the command, but there is one in the directory above, the node will get installed in the parent one.

If you find that /home/debian/node_modules/node-red-contrib-bigtimer exists and /home/debian/.node-red/node_modules/node-red-contrib-bigtimer does not exist, then move it over and restart.

Nick

[Peter Scargill]

/home/debian/.node-red/node-modules exists (I had to create .node-red directory – and in there I ran the install for bigtimer) – and there is no node-modules directory in /home/debian…

 

But no sign of bigtimer in the node-red installation after restarting node-red… and no sign of the node-red-admin tab…

 

Got me completely lost this one…

[Nicholas O'Leary]

How are you restarting Node-RED?

[Peter Scargill]

Service node-red stop

 

(and it stops)

 

Service node-red start