Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Trapping "No compatible USB Bluetooth 4.0 device" error?

See original GitHub issue

Hi!

I have a project that uses Noble as one of a few different connection options (BLE, USB Serial, TCP/IP) - however I’m finding that on Windows 10 I get No compatible USB Bluetooth 4.0 device errors on some devices which closes my application.

That’s fine - I know some devices won’t have BLE dongles that work with Noble. However I’d like to be able to trap the error gracefully and carry on without Noble regardless.

On Linux, I get stateChange -> poweredOff without any devices, so that’s easy.

I have tried:

  var noble = undefined;
  try {
    noble = require('noble');
  } catch (e) {
   ...
  }

But that doesn’t seem to be able to trap the error that occurs on Windows 10 as it appears it’s coming from a callback that’s been scheduled at some later point.

Error: No compatible USB Bluetooth 4.0 device found!
at BluetoothHciSocket.bindUser (C:\Users\name\AppData\Roaming\npm\node_modules\espruino\node_modules\bluetooth-hci-socket\lib\usb.js:70:11)
at BluetoothHciSocket.bindRaw (C:\Users\name\AppData\Roaming\npm\node_modules\espruino\node_modules\bluetooth-hci-socket\lib\usb.js:28:8)
at Hci.init (C:\Users\name\AppData\Roaming\npm\node_modules\espruino\node_modules\noble\lib\hci-socket\hci.js:101:35)
at NobleBindings.init (C:\Users\name\AppData\Roaming\npm\node_modules\espruino\node_modules\noble\lib\hci-socket\bindings.js:82:13)
at Noble.<anonymous> (C:\Users\name\AppData\Roaming\npm\node_modules\espruino\node_modules\noble\lib\noble.js:57:24)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3

Is there any way I can trap it nicely? About the only thing I can think right now is uncaughtException but that seems like overkill.