You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2021/02/02 13:12:02 UTC
[GitHub] [mynewt-nimble] codewitch-honey-crisis opened a new issue #909: No "Class of Device" (CoD) setter, getter found in API?
codewitch-honey-crisis opened a new issue #909:
URL: https://github.com/apache/mynewt-nimble/issues/909
I need to get the CoD so I can determine if the devices I'm finding are the specific devices I created.
Class of Device is how you do this, no?
bluedroid has this
BluetoothClass
and it gets me that information.
There is no equivalent here from the looks of things, either for setting it (server) or getting it (client)
I'm looking for a different lightweight library. What would you have me do, connect by name and manufacturer? I am uncomfortable with this without checking the device class.
Or maybe it is here, and the documentation doesn't make it clear.
Either way, it's a problem.
Best regards
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [mynewt-nimble] codewitch-honey-crisis commented on issue #909: No "Class of Device" (CoD) setter, getter found in API?
Posted by GitBox <gi...@apache.org>.
codewitch-honey-crisis commented on issue #909:
URL: https://github.com/apache/mynewt-nimble/issues/909#issuecomment-771633823
I'm sorry. I'm still new to this, and I thought CoD was how you did it.
Thanks!
On Tue, Feb 2, 2021 at 5:26 AM Andrzej Kaczmarek <no...@github.com>
wrote:
> There's no CoD in BLE, it's only used in Bluetooth classic which NimBLE
> does not support.
> If you want to filter devices during discovery you can use either
> Appearance value or Services UUIDs, both can be present in advertising data.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/mynewt-nimble/issues/909#issuecomment-771632903>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AD5ICVK4SIUMV67OESQS3MDS474QJANCNFSM4W6TPQMA>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [mynewt-nimble] andrzej-kaczmarek commented on issue #909: No "Class of Device" (CoD) setter, getter found in API?
Posted by GitBox <gi...@apache.org>.
andrzej-kaczmarek commented on issue #909:
URL: https://github.com/apache/mynewt-nimble/issues/909#issuecomment-771632903
There's no CoD in BLE, it's only used in Bluetooth classic which NimBLE does not support.
If you want to filter devices during discovery you can use either Appearance value or Services UUIDs, both can be present in advertising data.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [mynewt-nimble] sjanc closed issue #909: No "Class of Device" (CoD) setter, getter found in API?
Posted by GitBox <gi...@apache.org>.
sjanc closed issue #909:
URL: https://github.com/apache/mynewt-nimble/issues/909
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [mynewt-nimble] andrzej-kaczmarek commented on issue #909: No "Class of Device" (CoD) setter, getter found in API?
Posted by GitBox <gi...@apache.org>.
andrzej-kaczmarek commented on issue #909:
URL: https://github.com/apache/mynewt-nimble/issues/909#issuecomment-771632903
There's no CoD in BLE, it's only used in Bluetooth classic which NimBLE does not support.
If you want to filter devices during discovery you can use either Appearance value or Services UUIDs, both can be present in advertising data.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [mynewt-nimble] codewitch-honey-crisis commented on issue #909: No "Class of Device" (CoD) setter, getter found in API?
Posted by GitBox <gi...@apache.org>.
codewitch-honey-crisis commented on issue #909:
URL: https://github.com/apache/mynewt-nimble/issues/909#issuecomment-771633823
I'm sorry. I'm still new to this, and I thought CoD was how you did it.
Thanks!
On Tue, Feb 2, 2021 at 5:26 AM Andrzej Kaczmarek <no...@github.com>
wrote:
> There's no CoD in BLE, it's only used in Bluetooth classic which NimBLE
> does not support.
> If you want to filter devices during discovery you can use either
> Appearance value or Services UUIDs, both can be present in advertising data.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/mynewt-nimble/issues/909#issuecomment-771632903>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AD5ICVK4SIUMV67OESQS3MDS474QJANCNFSM4W6TPQMA>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org