-
• #2
If all is going well, in the
journalctl
log you should see something like:Sep 05 07:52:12 frank EspruinoHub[2507]: <Discover> Starting scan... Sep 05 07:52:12 frank EspruinoHub[2507]: <Discover> Scanning started.
If it doesn't (which it isn't in your case) it's probably because node.js doesn't have the right permissions to access Bluetooth LE. Can you try running
which node
, and if that displays a path, can you run:sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)
And see if that helps after you then do
sudo systemctl restart EspruinoHub.service
to restart EspruinoHub? -
• #3
Just to add, in
/status
, you should see a list of the devices it has found right at the end, after the date/time is printed. -
• #4
Thank you! I'm not sure how I messed that up twice but you suggestion to run setcap and systemctl restart fixed it. Now everything is working smoothly.
Hey everyone! I'm having some trouble accessing the Puck.js from the EspruinoHub IDE. After following these steps (RPi3 -> fresh Raspbian lite -> Installation of everything -> Headless Startup) I'm able to access the server at :1888 and Node Red at :1880 but the IDE doesn't give me the option to connect to the Puck.js. It just says "SEARCHING... NO PORTS FOUND".
There's also an error reported in the Chrome developer console when I click on the Connect / Disconnect button that may be related (image attached).
When I visit :1888/status this is what I get:
And when I run
sudo journalctl -f -u EspruinoHub
this is what I get:Bluetooth seems to be working and is detecting the Puck.js if I check it from bluetoothctl:
Am I missing a step or something?
1 Attachment