-
Notifications
You must be signed in to change notification settings - Fork 52
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
Disconnecting instantly after sucessful connection #30
Comments
I had the same problem. Is anyone know how to fix it? |
Are you running stock raspberrian? |
can you try earlier version and bissec it? |
What do you mean by this? |
find where regression has been introduced good luck |
what? |
well yes, but this isn't a versioning issue |
(earlier version doesn't work) |
Would appreciate any help, as although I know about bluez, the custom implementation is all brand new to me and I'm struggling to realise where this starts. |
While I prefer the interface in this library, if anyone else is having a similar issue another similar library exists at |
Yes, I tested several Raspberry Pi OS (from 2018 to latest release), all have the same issue. Although bleno works fine on PC with USB BLE dongle. I guess it's not Raspberry Pi OS issue. It's a bug on node-bluetooth-hci-socket v0.5.3-8. (https://github.com/abandonware/node-bluetooth-hci-socket/pull/32] I rollback to v0.5.3-7, everything works fine for me.
|
Thanks @xuminready - this fix also worked for me when using FortiusANT on RPi0. Greatly appreciated! |
Currently running dietpi.
Everything works, except when I try to connect; It works for ~3s and disconnects.
Btmon shows this as a Remote User Terminated Connection
Any idea how I can find out what is giving this disconnect request?
Logs are running the echo example.
Bleno Debug=* enviroment dump
https://pastebin.com/PiMkBNH8
btmon dump
https://pastebin.com/EUnikR9E
Any help would be greatly appreciated, been at a loss for a very long time now, and it seems google does not contain any solutions.
The text was updated successfully, but these errors were encountered: