I have a similar setup (Win 7 x64) and I am seeing very similar results where windows can see the puck via BLE but the native application does not. The console log shows these errors at the beginning:
We have chrome.serial - not using 'serialport' module
'noble' module couldn't be loaded, no node.js Bluetooth Low Energy Error: LIBUSB_ERROR_NOT_SUPPORTED
'winnus' module not found, no Windows Bluetooth Low Energy Error: The specified module could not be found. \?\C:\Users\t44a8l2\AppData\Local\Temp\nw10628_25245\node_modules\winnus\build\Release\winnus.nod
And then later:
Connecting...
Set Slow Write = true
BT> ERROR: NotFoundError: User cancelled the requestDevice() chooser.
ERROR: [notify_error] Connection Failed.
Connection Failed.
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.
I have a similar setup (Win 7 x64) and I am seeing very similar results where windows can see the puck via BLE but the native application does not. The console log shows these errors at the beginning:
We have chrome.serial - not using 'serialport' module
'noble' module couldn't be loaded, no node.js Bluetooth Low Energy Error: LIBUSB_ERROR_NOT_SUPPORTED
'winnus' module not found, no Windows Bluetooth Low Energy Error: The specified module could not be found. \?\C:\Users\t44a8l2\AppData\Local\Temp\nw10628_25245\node_modules\winnus\build\Release\winnus.nod
And then later: