-
Notifications
You must be signed in to change notification settings - Fork 253
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
Dual GATT server running on different hci #103
Comments
I guess you are saying you have 2 different services rather than 2 different servers, the server is implemented by bluetoothd, also for bluetoothd all it matter is that the D-Bus connection and path are unique, if it is not the it will assume it is the same instance, so this suggests the problem is the application side. |
So, currently it is not possible to run two Gatt python server example in separate threads in the same python script ? The wired thing here is if I'm quick enough then sometime it works and sometime it doesn't. |
You may need to create different connection if you are running just different threads since for the daemon identify based on the connection id if python just reuses the same connection it won't work, or run as separate process, anyway this is on the client side and there is nothing we can do if the connection ID and path clashes with othe instances. |
Hey,
so I try to run 2 GATT python servers at the same time on two different dongles (hci0, hci1). I have a main python script in which I start both GATT server in their own thread. But as soon as the second GATT server needs to be launched. I always get the following error message:
I check the agent manager to be different:
Why is it still saying
Already Exists
Has someone an idea ?
The text was updated successfully, but these errors were encountered: