Posted at 2018-08-11 by Robin

Sat 2018.08.11

Hello @PapaTech and appreciate the 'New guy alert...' ;-)

re: 'but when I try to connect to the Puck I get 'No ports found''

Although I'm not able to provide insight using the Pi or non-Win10, were you able to resolve accessing the Puck via the IDE?

BTW, the link in #1 above https://www.espruino.com/ide/, returns 404

Are you using a Bluetooth BLE dongle?
Are you using the Native App on Win10 by chance?
What PC O/S is the IDE running on?

https://www.espruino.com/Quick+Start+BLE#puckjs

"Neither the Online IDE espruino.com/ide nor the Chrome Web App will work to access Bluetooth Low Energy devices on Windows unless
you install the polyfill above. Please try the Native IDE first - this is by far the easiest option."

Posted at 2018-08-11 by PapaTech

Robin,
First, thank you for your reply and wink in acknowledging my 'newbie' status.

Perhaps I am misunderstanding how this all works. I installed Espruino Hub with the IDE and Node-RED on the Raspberry Pi and can access both through the web interface of the raspberry pi. The Bluetooth, I thought is running on the Pi since I am basically remotely running the IDE from there. Maybe I am mistaken and need to install more onto my Windows 10 PC to make this work.

Are you suggesting that I need to install more onto the Windows PC since that is not in the instructions that I read.

Thanks again.

Posted at 2018-08-11 by Robin

re: 'Are you suggesting that I need to install more onto the Windows
PC since that is not in the instructions that I read.'

Not necessarily. Just had a thought that as you were able to re-flash firmware, that communication to the Puck via Bluetooth BLE
could be verified using the Native IDE app <-> Puck

In that way, one could confirm that communication/connecting with the Puck was occurring, remove that wonderment from the equation,
then efforts could be focused on just the Pi.

ref from #1: 'Web Bluetooth not enabled'

So, to clarify, the Bluetooth issues were on the Pi only?

Would you be so kind as to provide the link for the 'Espruino Hub' documentation as search didn't provide that detail for me to follow along.

Probably not. Gordon does an excellent job in documenting his tutorials, and I'm going to guess they have been tested a bazillion times,
okay maybe a gazillion?

His availability is sometimes limited on weekends, so thought that providing some pre-power-debug detail would help speed things up, rather than have to re-visit the same questions, once he and others are able to assist early next week.

This is a common error that is seen when attempting to access via Bluetooth BLE and using the wrong IDE. Just wanted to make sure
that the native app flavor was being used, . . . if that were the case.

Posted at 2018-08-11 by PapaTech

Robin,

Thank you so much for working with me on this. I appreciate your thoughts and insights. Here is the link where I found the Espruino Hub information...
https://github.com/espruino/EspruinoHub

Yes I think the issue is with the bluetooth on the Pi since I was able to access the Puck to do the firmware upgrade. I will take a look at installing the Native IDE and see if I can, well... see the Puck.

Thanks

Posted at 2018-08-12 by Robin

PapaTech,

re: 'to install more onto my Windows 10 PC to make this work'

More for information purposes here,

I had a Win10 PC that was supposed to be Bluetooth compatible, but in order to get communications going with the Puck, I eventually had to pick up a Bluetooth BLE dongle as the docs indicate to get that to work. Hope that's not too much of a Buzz-Kill should the same issue occur with the PC the native IDE is installed on.

See: 'Requirements' heading 'For Bluetooth LE you need a . . . '
https://www.espruino.com/Quick+Start+BLE#puckjs

'Tutorials' heading for a few quick start projects
https://www.espruino.com/Puck.js

After a quick perusal, that content is more Pi specific and I'm not going to be able to assist there. Remember I did start out #2 with "Although I'm not able to provide insight using the Pi . . ."

Was hoping someone with Pi experience would have chimed in by now, but may have to wait until the heavy hitters are around earlier in the week.

Looks like you have a fun, but a bit of challenge project ahead of you. I wish you success, with a bit of patience, of course.

Robin

Posted at 2018-08-12 by PapaTech

Robin,
I have a blinking Puck!!!! Using the Standalone IDE and pairing the puck to my pc it comes up and works. Thanks for getting me to that point!

Now at least I can play around a little bit and then hopefully figure out the Rasp Pi usage next week.

Now if I could just figure out how to make it stop blinking... ;-)

Thanks for all your help.

Posted at 2018-08-13 by @gfwilliams

Hi - sorry for the late reply on this... I'm not usually checking the forum at weekends. What you're doing all looks good to me. If you're doing stuff on the Pi there shouldn't be any issue with Windows at all.

Which type of Raspberry Pi did you install EspruinoHub on? Only the Pi 3 and Pi Zero W have Bluetooth built-in...

So when you set up the Pi, did you go to http://raspberrypi.local:1888/ide or http://www.espruino.com/ide to get to the IDE? The first one is the one you want - and could you try doing it in Chrome, in case it's some issue with the browser you're using?

And what happens if you go to http://raspberrypi.local:1888/status ? At the bottom of the page, after the current time, does it show a Puck.js device?

Hope some of that helps!

Posted at 2018-08-13 by PapaTech

Gordon,

No worries on the reply. This is a new project for me so I am pushing through a bunch of hours while working the rest of the project I have for my company.

I was accessing the ide on the raspberry pi 3 and there were signs that the Bluetooth was up and running.

I am not sure if I have to pair the Puck to the Pi or to the PC. I was able to get the standalone IDE to work and find the Puck and have done a couple of quick examples using the magnetometer that way.

Unfortunately I am at the airport headed to Texas (early flight) and won’t be back to the office until Wednesday morning. I will update you once I get back and some more testing.

Thanks for the help. This looks like it might e perfect for our project.

Tom

Posted at 2018-08-13 by @gfwilliams

The Pi 3 should work great with EspruinoHub, so no worries there. I think next step would be to check out that status page.

I am not sure if I have to pair the Puck to the Pi or to the PC.

The Puck needs pairing with the PC to work with the standalone IDE, but it doesn't need pairing with the Pi at all. Only thing to watch out for is you can only have one connection at a time - so if you're connected to the PC then the Pi won't be able to see the Puck... But that wouldn't have been an issue when you first tried.

Posted at 2018-08-13 by PapaTech

That is what I thought. When I get back I will unpair it from the PC and then get more info from the pi status.

Posted at 2018-08-15 by PapaTech

Here is what it says on the status screen at http://raspberrypi:1888/status:

Config loaded
Connecting...
Server is listening on http://localhost:1888
www directory found at /home/pi/EspruinoHub/www. Web server at http://localhost:1888
log directory found at /home/pi/EspruinoHub/log. Enabling logging.
Connected
Serving /home/pi/EspruinoHub/www/ide.html
Serving /home/pi/EspruinoHub/www/paho-mqtt.js
Sat Aug 11 2018 13:07:46 GMT+0000 (UTC) Connection accepted.
Websocket MQTT connected
Websocket MQTT closed (WebSocket)
Websocket MQTT closed (MQTT)
Serving /home/pi/EspruinoHub/www/paho-mqtt.js
Sat Aug 11 2018 13:25:11 GMT+0000 (UTC) Connection accepted.
Websocket MQTT connected
Serving /home/pi/EspruinoHub/www/favicon.ico
Serving /home/pi/EspruinoHub/www/ide.html
Websocket MQTT closed (WebSocket)
Websocket MQTT closed (MQTT)
Serving /home/pi/EspruinoHub/www/paho-mqtt.js
Sat Aug 11 2018 13:49:17 GMT+0000 (UTC) Connection accepted.
Websocket MQTT connected
Websocket MQTT closed (WebSocket)
Websocket MQTT closed (MQTT)
Tue Aug 14 2018 15:37:35 GMT+0000 (UTC) Connection accepted.
Websocket MQTT connected
Serving /home/pi/EspruinoHub/www/favicon.ico
Serving /home/pi/EspruinoHub/www/index.html
Websocket MQTT closed (WebSocket)
Websocket MQTT closed (MQTT)

Wed Aug 15 2018 18:23:38 GMT+0000 (UTC)

Posted at 2018-08-15 by PapaTech

When I run systemctl status bluetooth on the Pi this is what I get.

bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
Active: active (running) since Sat 2018-08-11 05:03:36 UTC; 4 days ago
Docs: man:bluetoothd(8)
Main PID: 467 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─467 /usr/lib/bluetooth/bluetoothd

Aug 11 05:03:36 EspruinoHub systemd[1]: Starting Bluetooth service...
Aug 11 05:03:36 EspruinoHub bluetoothd[467]: Bluetooth daemon 5.43
Aug 11 05:03:36 EspruinoHub systemd[1]: Started Bluetooth service.
Aug 11 05:03:36 EspruinoHub bluetoothd[467]: Starting SDP server
Aug 11 05:03:36 EspruinoHub bluetoothd[467]: Bluetooth management interface 1.14
Aug 11 05:03:36 EspruinoHub bluetoothd[467]: Failed to obtain handles for "Servi
Aug 11 05:03:36 EspruinoHub bluetoothd[467]: Sap driver initialization failed.
Aug 11 05:03:36 EspruinoHub bluetoothd[467]: sap-server: Operation not permitted
...skipping...

Posted at 2018-08-16 by @gfwilliams

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:

 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:

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.

Posted at 2018-08-16 by @gfwilliams

Also try running sudo hcitool lescan and see if it displays anything... That'll check if Linux itself can see any Bluetooth LE devices (then you need to Ctrl-C out of it)

Posted at 2018-08-16 by PapaTech

Thanks for the suggestions Gordon. I ran the which mode line above and nothing seemed to change. I then ran sudo hcitool lescan and got the following:

pi@EspruinoHub:~ $ sudo hcitool lescan
LE Scan ...
3F:4E:22:64:AE:A0 (unknown)
09:EA:10:86:4C:DA (unknown)
CF:8B:E0:99:E5:B9 Puck.js e5b9
CF:8B:E0:99:E5:B9 (unknown)
C3:C9:01:13:06:CD (unknown)
C3:C9:01:13:06:CD Charge 2
53:45:03:DC:09:3C (unknown)
53:45:03:DC:09:3C (unknown)

So at least it is seeing the Puck.js...right?

Posted at 2018-08-17 by @gfwilliams

Did you restart EspruinoHub after running setcap? At least we know the Pi can see Bluetooth devices.

EspruinoHub should have:

Starting scan...
Scanning started.

Near the top of the status screen, and yours doesn't seem to have that so there's been some issue initializing Bluetooth from Node. If it's not the permissions with setcap (which would be the most likely) then it might be how the Node.js library got installed.

Could you try doing:

cd EspruinoHub
rm -rf node_modules
npm install

and see if you get any errors? There will be some warnings about SKIPPING OPTIONAL DEPENDENCY ... xpc-connection at the end, but that's all you should have.

Posted at 2018-08-17 by PapaTech

Thanks...again...
When I run rf -rf node_modules I get an -bash: rf: command not found.

I hate being a noob...but I guess you have to start at the beginning.

Posted at 2018-08-17 by @gfwilliams

Sorry, my bad - it should have been rm:

rm -rf node_modules

I just corrected the original post as well.

Posted at 2018-08-18 by PapaTech

Back on the road this week...might take it along with me. I tried the above and find the same issue. Thinking I might format the SD card and start from scratch.
Have a great weekend.

Posted at 2018-08-20 by @gfwilliams

Argh, shame it's still not going.

So npm install completed without issues (apart from the SKIPPING OPTIONAL DEPENDENCY bit)?

Posted at 2018-09-01 by PapaTech

Well finally got some time to work on this project again. I bought a Pi Zero W and installed everything on it. I can run the software just like before but I still get no ports. I do however get the following when I look at status:

Config loaded
Connecting...
Server is listening on http://localhost:1888
www directory found at /home/pi/EspruinoHub/www. Web server at http://localhost:1888
log directory found at /home/pi/EspruinoHub/log. Enabling logging.
Bleno State poweredOn
Bleno.startAdvertising Success
Bleno.setServices Success
Starting scan...
Scanning started.
NOT CONNECTED AFTER 10 SECONDS

Sat Sep 01 2018 19:54:01 GMT+0000 (UTC)

1d:48:7c:0a:04:d4 - ? (RSSI -60)
60:2c:9e:64:15:f6 - ? (RSSI -88)
c3:c9:01:13:06:cd - Charge 2 (RSSI -95)
180a => [22,4,16,83,3]
c4:72:74:93:c8:0e - Tile (RSSI -89)
cf:8b:e0:99:e5:b9 - Puck.js e5b9 (RSSI -52)

So that is good. Just don't know why I can't connect on the IDE running on the Pi. Really just want to start learning how to program this Puck...

Posted at 2018-09-01 by PapaTech

Here are some errors when I started the service...

sudo systemctl start EspruinoHub.service && sudo journalctl -f -u EspruinoHub
-- Logs begin at Thu 2016-11-03 17:16:43 UTC. --
Sep 01 19:36:03 raspberrypi systemd[1]: Started EspruinoHub BLE -> MQTT bridge.
Sep 01 19:36:04 raspberrypi EspruinoHub[17254]: setterm: $TERM is not defined.
Sep 01 19:36:04 raspberrypi sudo[17266]: pi : TTY=unknown ; PWD=/home/pi/EspruinoHub ; USER=root ; COMMAND=/sbin/setcap cap_net_raw+eip /usr/bin/node
Sep 01 19:36:04 raspberrypi sudo[17266]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 01 19:36:04 raspberrypi sudo[17266]: pam_unix(sudo:session): session closed for user root
Sep 01 19:36:05 raspberrypi EspruinoHub[17254]: Config loaded
Sep 01 19:36:07 raspberrypi EspruinoHub[17254]: Connecting...
Sep 01 19:36:08 raspberrypi EspruinoHub[17254]: Server is listening on http://localhost:1888
Sep 01 19:36:08 raspberrypi EspruinoHub[17254]: www directory found at /home/pi/EspruinoHub/www. Web server at http://localhost:1888
Sep 01 19:36:08 raspberrypi EspruinoHub[17254]: log directory found at /home/pi/EspruinoHub/log. Enabling logging.
Sep 01 19:36:08 raspberrypi EspruinoHub[17254]: Bleno State poweredOn
Sep 01 19:36:08 raspberrypi EspruinoHub[17254]: Bleno.startAdvertising Success
Sep 01 19:36:08 raspberrypi EspruinoHub[17254]: Bleno.setServices Success
Sep 01 19:36:09 raspberrypi EspruinoHub[17254]: Starting scan...
Sep 01 19:36:09 raspberrypi EspruinoHub[17254]: Scanning started.
Sep 01 19:36:17 raspberrypi EspruinoHub[17254]: NOT CONNECTED AFTER 10 SECONDS
Sep 01 19:40:06 raspberrypi EspruinoHub[17254]: Serving /home/pi/EspruinoHub/www/index.html
Sep 01 19:40:07 raspberrypi EspruinoHub[17254]: Serving /home/pi/EspruinoHub/www/favicon.ico
Sep 01 19:40:43 raspberrypi EspruinoHub[17254]: Serving /home/pi/EspruinoHub/www/ide.html
Sep 01 19:40:43 raspberrypi EspruinoHub[17254]: Serving /home/pi/EspruinoHub/www/paho-mqtt.js
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: Sat Sep 01 2018 19:40:46 GMT+0000 (UTC) Connection accepted.
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: events.js:183
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: throw er; // Unhandled 'error' event
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: ^
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: Error: connect ECONNREFUSED 127.0.0.1:1883
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: at Object._errnoException (util.js:992:11)
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: at _exceptionWithHostPort (util.js:1014:20)
Sep 01 19:40:46 raspberrypi EspruinoHub[17254]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
Sep 01 19:40:46 raspberrypi systemd[1]: EspruinoHub.service: Main process exited, code=exited, status=1/FAILURE
Sep 01 19:40:46 raspberrypi systemd[1]: EspruinoHub.service: Unit entered failed state.
Sep 01 19:40:46 raspberrypi systemd[1]: EspruinoHub.service: Failed with result 'exit-code'.
Sep 01 19:40:46 raspberrypi systemd[1]: EspruinoHub.service: Service hold-off time over, scheduling restart.
Sep 01 19:40:46 raspberrypi systemd[1]: Stopped EspruinoHub BLE -> MQTT bridge.
Sep 01 19:40:46 raspberrypi systemd[1]: Started EspruinoHub BLE -> MQTT bridge.
Sep 01 19:40:46 raspberrypi EspruinoHub[17290]: setterm: $TERM is not defined.
Sep 01 19:40:46 raspberrypi sudo[17297]: pi : TTY=unknown ; PWD=/home/pi/EspruinoHub ; USER=root ; COMMAND=/sbin/setcap cap_net_raw+eip /usr/bin/node
Sep 01 19:40:46 raspberrypi sudo[17297]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 01 19:40:46 raspberrypi sudo[17297]: pam_unix(sudo:session): session closed for user root
Sep 01 19:40:48 raspberrypi EspruinoHub[17290]: Config loaded
Sep 01 19:40:49 raspberrypi EspruinoHub[17290]: Connecting...
Sep 01 19:40:50 raspberrypi EspruinoHub[17290]: Server is listening on http://localhost:1888
Sep 01 19:40:50 raspberrypi EspruinoHub[17290]: www directory found at /home/pi/Espruino

Posted at 2018-09-01 by PapaTech

Here is where I did the nmp install

npm install

usb@1.3.3 install /home/pi/EspruinoHub/node_modules/usb
node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://github.com/tessel/node-usb/releases/download/1.3.3/usb_bindings-v1.3.3-node-v57-linux-arm.tar.gz
node-pre-gyp WARN Pre-built binaries not found for usb@1.3.3 and node@8.11.4 (node-v57 ABI, glibc) (falling back to source compile with node-gyp)
make: Entering directory '/home/pi/EspruinoHub/node_modules/usb/build'
CC(target) Release/obj.target/libusb/libusb/libusb/core.o
CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
CC(target) Release/obj.target/libusb/libusb/libusb/io.o
CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
../libusb/libusb/os/linux_udev.c:40:21: fatal error: libudev.h: No such file or directory
#include <libudev.h>
^
compilation terminated.
libusb.target.mk:132: recipe for target 'Release/obj.target/libusb/libusb/libusb/os/linux_udev.o' failed
make: *** [Release/obj.target/libusb/libusb/libusb/os/linux_udev.o] Error 1
make: Leaving directory '/home/pi/EspruinoHub/node_modules/usb/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.14.50+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/pi/EspruinoHub/node_modules/usb/src/binding/usb_bindings.node" "--module_name=usb_bindings" "--module_path=/home/pi/EspruinoHub/node_modules/usb/src/binding" "--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /home/pi/EspruinoHub/node_modules/usb
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/EspruinoHub/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/home/pi/EspruinoHub/node_modules/usb/src/binding --napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack at ChildProcess. (/home/pi/EspruinoHub/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:126:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:925:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
node-pre-gyp ERR! System Linux 4.14.50+
node-pre-gyp ERR! command "/usr/bin/node" "/home/pi/EspruinoHub/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/pi/EspruinoHub/node_modules/usb
node-pre-gyp ERR! node -v v8.11.4
node-pre-gyp ERR! node-pre-gyp -v v0.10.3
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/EspruinoHub/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/home/pi/EspruinoHub/node_modules/usb/src/binding --napi_version=3 --node_abi_napi=napi' (1)

bluetooth-hci-socket@0.5.1 install /home/pi/EspruinoHub/node_modules/bluetooth-hci-socket
node-gyp rebuild

make: Entering directory '/home/pi/EspruinoHub/node_modules/bluetooth-hci-socket/build'
CXX(target) Release/obj.target/binding/src/BluetoothHciSocket.o
../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::poll()’:
../src/BluetoothHciSocket.cpp:251:95: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::String, int, v8::Localv8::Value* ’ is deprecated [-Wdeprecated-declarations]
back(Nan::New(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
^
In file included from ../src/BluetoothHciSocket.cpp:8:0:
../../nan/nan.h:979:46: note: declared here
NAN_DEPRECATED inline v8::Localv8::Value MakeCallback(
^~~~~~~~~~~~
../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::emitErrnoError()’:
../src/BluetoothHciSocket.cpp:275:72: warning: ‘v8::Localv8::Object v8::Function::NewInstance(int, v8::Localv8::Value) const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
Local error = errorConstructor->NewInstance(1, constructorArgs);
^
In file included from /home/pi/.node-gyp/8.11.4/include/node/v8.h:26:0,
from /home/pi/.node-gyp/8.11.4/include/node/node.h:63,
from /home/pi/.node-gyp/8.11.4/include/node/node_buffer.h:25,
from ../src/BluetoothHciSocket.cpp:7:
/home/pi/.node-gyp/8.11.4/include/node/v8.h:3847:31: note: declared here
Local NewInstance(int argc, Local argv[]) const);
^
/home/pi/.node-gyp/8.11.4/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../src/BluetoothHciSocket.cpp:282:93: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::String, int, v8::Localv8::Value ’ is deprecated [-Wdeprecated-declarations]
back(Nan::New(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
^
In file included from ../src/BluetoothHciSocket.cpp:8:0:
../../nan/nan.h:979:46: note: declared here
NAN_DEPRECATED inline v8::Localv8::Value MakeCallback(
^~~~~~~~~~~~
SOLINK_MODULE(target) Release/obj.target/binding.node
COPY Release/binding.node
make: Leaving directory '/home/pi/EspruinoHub/node_modules/bluetooth-hci-socket/build'