-
Notifications
You must be signed in to change notification settings - Fork 90
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
espruino --list returns "Error: No compatible USB Bluetooth 4.0 device found!" #151
Comments
I had the same problem, and I solved it using the issue you linked to. So edit the file in node_modules adding the values used there, and it should work. Obviously that's not a very good solution, so maybe a PR to @abandonware could help? |
If it had worked, then certainly, but ... well I at least can't get it to work xD |
Moving this to the EspruinoTools repo... I think there's a list of supported devices, and you just put your device's USB IDs here: https://github.com/abandonware/node-bluetooth-hci-socket/blob/master/lib/usb.js#L15-L30 A PR to abandonware would be great. Basically the original 'noble' was just totally abandoned so that project sprung up to try and fix the issues with it. Either way, it's not really a great solution since it goes straight to the USB adaptor. Since Windows 10 you can just access BLE devices via API, and you'd hope there would be a node module to handle that. I'm not sure if there is though. I did |
Hi, so I am trying to see my Bangle.js 2 on my pc, I'd rather use VS Code for development than the app, so I am playing around with commandline.
In the web ide I can connect to my bangle with the button in the top left, no issues.
But in commandline I get the following error:
I suspect that the culprit is
bluetooth-hci-socket
is in a folder called@abandonware
and when I went to their page I could see that the last release was 6 years old and the last code edit was 4 years old.So it's likely woefully outdated at this point :(
I did find this
noble/node-bluetooth-hci-socket#118
but it doesn't really seem like a viable solution, and I can't get it working for my self either.
It seems that the @abandonware project is an attempt to save orphaned projects, but it hasn't really helped this one xD
Not sure what the solution is though :/
The text was updated successfully, but these errors were encountered: