forked from noble/bleno
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Linux 6.9 support broken #53
Comments
PR here: #54 |
Also see abandonware/node-bluetooth-hci-socket#60 (comment) for the background |
Oh my gosh thank you, I was going crazy on this issue and doing exactly what you were doing with the same hardware. I can confirm this resolved the issue for me as well. |
This fix has merged, is it possible to get an updated npm package? |
I submitted this PR to bump to 0.6.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a raspberry pi 4, which I am using bleno on.
After a fresh install and setup, my app was working fine and broadcasting a BLE peripheral.
After some time, when I didn't make any changes, the stateChange event stopped arriving when I started the app, even though hci0 was up.
I could see in the
DEBUG=* npm run...
output the following:I couldn't repair this by reinstalling the bluetooth tools, rebooting, taking hci0 up/down etc. I ended up rebuilding the entire pi with all dependencies and this fixed it, but unfortunately today the issue reoccurred.
However, as rebuilding the pi is incredibly time consuming, I did some more research and I have discovered noble#482 with associated pull request for mayfield@2644e67
This changes the setSocketFilter buffer size from
14
to16
and I can confirm that this seems to resolve the issue, once changing this locally, the EINVAL goes away and normal service resumesI will raise a new PR on this repo for the issue
The text was updated successfully, but these errors were encountered: