Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cloned noble did not work with npm install #553

Open
OwenBrotherwood opened this issue Feb 13, 2017 · 6 comments
Open

cloned noble did not work with npm install #553

OwenBrotherwood opened this issue Feb 13, 2017 · 6 comments

Comments

@OwenBrotherwood
Copy link

OwenBrotherwood commented Feb 13, 2017 •
edited

I cloned nobel to continue with understanding bluetooth.
I had previously cloned node-bluetooth-hci-socket, which did not complain about missing pre-req or bluetooth adapter.

However, with npm install followed by node examples\advertisement-discovery.js, I got a

throw new Error('No compatible USB Bluetooth 4.0 device found!');

npm install ..\node-bluetooth-hci-socket and another attempt gave me

peripheral discovered (dff5a5ec431b with address <df:f5:a5:ec:43:1b, random>, connectable true, RSSI -67:
        hello my local name is:
                Puck.js 431b
        can I interest you in any of the following advertised services:
                ["6e400001b5a3f393e0a9e50e24dcca9e"]

Hello dear puck, where do we go now: windows 10 with Zandig and noble are working.

Edit:
I had the same experience with https://github.com/NordicSemiconductor/secure-dfu-web-bluetooth and solved with same method
and this https://github.com/NordicSemiconductor/secure-dfu-web-bluetooth
@OwenBrotherwood OwenBrotherwood mentioned this issue Feb 14, 2017
Closed
@OwenBrotherwood
Copy link
Author

OwenBrotherwood commented Feb 14, 2017 •
edited

And with espruino/EspruinoWebIDE
espruino/EspruinoWebIDE#168

@OwenBrotherwood OwenBrotherwood mentioned this issue Feb 15, 2017
Open
@sandeepmistry
Copy link
Collaborator

What adapter are you using? I haven't done a node-bluetooth-hci-socket release in a while, so master is not in sync with what's on npm.

@OwenBrotherwood
Copy link
Author

Intel Wireless Bluetooth 7265 0x8087 0x0a2a

@OwenBrotherwood
Copy link
Author

OwenBrotherwood commented Feb 18, 2017 •
edited

espruino/EspruinoWebIDE#168 (comment) Windows 10 success with Gordons https://github.com/espruino/winnus in a bluetooth only with no usb scenario.

usb is proving to be a nasty for me and has caused a downgrade of node and nw.js because of node-usb/node-usb#163

Gordons IDE and node-usb issue gives the following setup that I will now try to achieve a positive result on and then go back to Windows 7 testing.
node 6.8.1 https://nodejs.org/download/release/v6.8.1/
nw.js https://nwjs.io/blog/v0.18.2/ (based on node 6.8.1)
Github clones from Gordons IDE and from nobel and node-bluetooth-hci-socket

I believe I have mismatch with the current LTS node so I am downgrading to the node 6.8.1 and work on it "now".

I will edit this comment with results

node-usb/node-usb#158 (comment)

quick link to npm status https://www.npmjs.com/package/bluetooth-hci-socket

@sandeepmistry
Copy link
Collaborator

Intel Wireless Bluetooth 7265 0x8087 0x0a2a

Support for this was added in noble/node-bluetooth-hci-socket@ae33b4f (Jan 15) which has not been published to npm yet. The current version published on npm is 0.5.1 which was published Sept 6th, 2016.

This should be resolved with the next npm release of node-bluetooth-hci-socket

@OwenBrotherwood OwenBrotherwood mentioned this issue Feb 23, 2017
Closed
@fedyfausto
Copy link

i get the same prolem but i can not fix with the Zadig

Intel Wireless Bluetooth 8265 | 0x8087 | 0x0a2b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@OwenBrotherwood @sandeepmistry @fedyfausto