-
Notifications
You must be signed in to change notification settings - Fork 54
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
Assertion failure #64
Comments
Do you have two bluetooth controllers? Usually there is only hci0. |
Yeah I do. I have a little USB ble device that I'm using for another application. For some reason the onboard Bluetooth gets assigned hci1 |
Please run "sudo btmon" in another tab and then start flicd and post the output. |
Done. Doesn't look very helpful, but maybe it will make more sense to you! Started btmon, started flicd, started my client library and it crashed shortly afterwards
|
To add, it also gets the assertion failed error even if I don't start a client. It eventually just crashes |
It seems you have some other Bluetooth application running that interferes with flicd. Please shutdown that. |
Thanks Emill, I'll check it out but the other app should be ustilising hci0 |
I've stopped the other app that uses the other bluetooth controller but the issue still persists |
Well all I can say is that it's definitely not the flicd program that sends out the command
Have you really checked all processes running? What does "ps aux" say? |
/facepalm. Yep Sorry. there was a rogue process not managed by systemd and I had previously looked under Thanks for you help! Hopefully this can serve to anyone else getting this error. Make sure to check that there is not another process using the same bluetooth controller as flic! |
Getting this error on a raspberry pi 3, running latest raspbian, using onboard Bluetooth. Connecting to it via the node client library. Is there anything else I can do to help trouble shoot this one? I previously was running this on a C.H.I.P with no issues (2 releases behind)
The text was updated successfully, but these errors were encountered: