-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Secondary Services #58
Comments
Hi, there is currently no support for that but it should be easy to add. I've never had a request for it or even seen this used anywhere before. |
A few of the standard BLE services say they can be or should be implemented as secondary services. are a few of the one's I've encountered. Right now, I'm specifically looking at Object Transfer Service. I've implemented a scaled down version of that (Connection Oriented Channels aren't supported on the ESP32 as far as I can tell, so I had to improvise a bit). I have another, distinct set of objects that I might want to throw this on top of. In that case, I want both services to be secondary services included in separate primary services. |
Thanks for the info, I guess bluetooth had to have a reason for secondary services somewhere and I haven't seen those before.
I believe they are, there are options in menuconfig for them (for NimBLE I thought I saw them at least). |
There's a config for "max number of CoCs", but I couldn't find the APIs to actually access them. Nor could I find any examples. Maybe I just didn't look hard enough... |
Sorry, I didn't actually answer your question. I think maybe just something like |
Thanks, I'll have a look at adding this. NimBLE internals might dictate a different interface but I'll see what I can do. |
I've created PR #59, If you could test it and provide feedback it would be greatly appreciated 😄 |
@justintconroy Any feedback on this yet? |
Is there any way to add a secondary service? It looks like I can only add primary services. I may need to reuse a secondary service as part of another primary service on the same device.
The text was updated successfully, but these errors were encountered: