Can't enable newly installed node (node-red-contrib-noble)

[Scott Chapman]

So I have a new Rasp-Pi installation (all up to date, though I haven't run the "update-nodejs-and-nodered" command yet).

I've installed the node-red-contrib-noble (since I want to do bluetooth scanning). And I can see that the node is there installed, but I am not able to enable it...

Any ideas?

[Nick O'Leary]

Any errors in the node-red log when it starts 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+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/b99242f9-a75b-4572-9a55-fa396f738444%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott Chapman]

I do see that I get:

[noble] Error: Cannot find module 'bluetooth-hci-socket'

Going to blow away the node_modules folder in /root/.node-red and trying to re-install the contrib.

I know I need to run this as root, so I assume that is the right action?

On Tuesday, June 6, 2017 at 11:10:43 AM UTC-4, Nick O'Leary wrote:

Any errors in the node-red log when it starts up?

Nick

On 6 June 2017 at 15:56, Scott Chapman <scotted...@gmail.com> wrote:

So I have a new Rasp-Pi installation (all up to date, though I haven't run the "update-nodejs-and-nodered" command yet).

I've installed the node-red-contrib-noble (since I want to do bluetooth scanning). And I can see that the node is there installed, but I am not able to enable it...

Any ideas?

--
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.

[Colin Law]

Which version of raspbian are you using? Could it be this problem?
https://github.com/sandeepmistry/noble/issues/253

Colin

> https://groups.google.com/d/msgid/node-red/ac57998f-f6c7-4a85-8452-622d7ce82d91%40googlegroups.com.

[Scott Chapman]

Fresh install and just updated

[Scott Chapman]

Well... OK... appears to be hung here:

[              ....] \ extract:noble: verb gentlyRm don't care about contents; nuking /root/.node-red/node_modules/.staging/noble-292694d5/node_modules

I checked and that folder doesn't exist...

On Tuesday, June 6, 2017 at 12:30:06 PM UTC-4, Scott Chapman wrote:

Fresh install and just updated

[Scott Chapman]

OK, got further (eventually). Got some error about not having permissions in /root/.node-gyp. Not sure how that happened, but blew it away, and running again.

[Scott Chapman]

gak. so OK. getting:

root@pizero:~/.node-red# npm install node-red-contrib-noble
> u...@1.2.0 install /root/.node-red/node_modules/usb
> node-pre-gyp install --fallback-to-build
sh: 1: node-pre-gyp: Permission denied

Now I am stuck again... any ideas? 

[Dave C-J]

you may need the --unsafe-perm flag on the command

    npm i --unsafe-perm node-red-contrib-noble

as when it calls out to node-gyp it drops it's privs to nobody thaht then may not have access to what it needs...

[Julian Knight]

Why are you doing this as root? I did previously note I think - when I was playing with noble - that the instructions say you can only use it as root, but that is not true as all you need to do is correct the default permissions on your bluetooth dev files.

[Scott Chapman]

I think when I first tried to set it up I was getting access errors with noble. I assumed that it was a protected device (not sure why I assumed that) and that I needed to be root.

What's the process for fixing that exactly? 

[Julian Knight]

Instructions are in the readme for noble:

Running without root/sudo

Run the following command:

sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)

This grants the node binary cap_net_raw privileges, so it can start/stop BLE advertising.

Note: The above command requires setcap to be installed, it can be installed using the following:

• apt: sudo apt-get install libcap2-bin
• yum: su -c \'yum install libcap2-bin\'