The status you get from systemctl status bluetooth is exactly what I get on a Pi that works.
systemctl status bluetooth
However EsspruinoHub isn't seeing anything. For instance I get the following:
New History Topic for /ble/presence/59:13:d6:01:be:7a New History Topic for /ble/advertise/59:13:d6:01:be:7a/rssi Scanning stopped. Serving /home/pi/EspruinoHub/www/favicon.ico Thu Aug 16 2018 07:42:01 GMT+0000 (UTC) 5c:99:3b:1b:c2:a4 - ? (RSSI -81) fe9f => [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] c0:03:88:c9:0d:ec - Thingy 0dec (RSSI -96) cc:74:92:24:0d:83 - Tomatoes (RSSI -96) d1:38:c6:91:89:8d - Pixl.js 898d (RSSI -101) f0:98:9e:6c:0c:2f - Pixl.js 0c2f (RSSI -86) 1809 => {"temp":7.87} f9:cf:55:a1:2c:8d - Puck.js 2c8d (RSSI -97) peacelily - Puck.js 7287 (RSSI -94) 1809 => {"temp":16.75} ffff => {"data":38}
So there's stuff after the text.
Can you try running which node, and then if that works:
which node
sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)
That's usually the culprit if Node.js apps aren't seeing any bluetooth devices.
@Gordon started
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
The status you get from
systemctl status bluetooth
is exactly what I get on a Pi that works.However EsspruinoHub isn't seeing anything. For instance I get the following:
So there's stuff after the text.
Can you try running
which node
, and then if that works:That's usually the culprit if Node.js apps aren't seeing any bluetooth devices.