October 2017 - Bluetooth-dev

macOS didModifyServices:
by Nick Brook 14 Oct '17

14 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:to; bh=y3EjPT0gAt5Tb8C5Hi3q9CfBj7DnlIW83TaCGJSCp+A=; b=tiaoFdBmTpE3e+c6J5/CMlDu7rJRaW5iwYRyy14Qyz6AhSuhUGVUWtH9FU3TGHRO4V FrXjabPtMwTb0m31HjaiHnlTUJFoIlxzSlZQbimo3vulqNaYw7XTvoQbOmh2xVXPMnz6 qNWU7qZhJshyzcXdMglN81yIUm6dFqvA+XV4dZpOWBBAF9NQa1rNfTB9jhZjWVj/cUdN +lmqLZh/lMOzCyc5y7pU79NzlYubc9CSN0tt1V6BYcnvqkzwi579XAAn8yd9ngby2NaT jFjiHTu2MG39wSYqUmZfKtrWVqyuwstNHmBwduTepwWn6qJeJ7DScbmATWtckArcBAYo 57+A== After firmware updates my device indicates that all services have been modified through the service changed characteristic in the generic attribute profile. It sends the indication as soon as the client has subscribed for indications. On iOS, I receive ‘didModifyServices’ immediately after connection, before iOS calls didDiscoverServices. This is great. On macOS, I receive didModifyServices a long way (several seconds) into discovery of the device. This causes two problems: If the GATT database structure has changed then I could read/write an invalid attribute and cause a connection timeout due to no response/other errors. If this happens before didModifyServices, macOS can’t connect to this device, as it never gets the indication that services have changed. When didModifyServices is eventually called, I have to throw away all discovery done so far and start again, almost doubling my discovery time This has been the case for a while now. I suppose it’s a bug really, so I will report it. That doesn’t work around the issue for current macOS though. Is there a way to trigger/force macOS to check for modified services immediately? Thanks Nick W: http://nickbrook.me _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Security
by William McAinsh 12 Oct '17

12 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Thread-index: AdNDPMe5cI7WDIAuSECazINef8kncA== Thread-topic: Security Wow, did apple really just send my password in clear text in a welcome email.. WILLIAM McAINSH _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

BLE Manager & Device access
by Philipp Kraus 11 Oct '17

11 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Hello, I’m starting with Bluetooth LE under OSX (10.11) to control Parrots minidrones. I have tested with a BLE scanner the connection between the drones and OSX, so OSX can find any drone component. Parrot create a native C API for controlling, but for discovery I need the OS depended BLE manager device pointer and the BLE device. I have taken a look into the IOBluetooth framework and my question is, how can I create these two pointers? My main goal is a Java native package for controlling the mini drones, but I need the OS specific part in C. A posting on parrots forum shows the example http://forum.developer.parrot.com/t/ble-device-initialization-under-osx/641… <http://forum.developer.parrot.com/t/ble-device-initialization-under-osx/641…> and a description of the Parrot API can be found here https://github.com/Parrot-Developers/libARNetworkAL/blob/master/Includes/li… <https://github.com/Parrot-Developers/libARNetworkAL/blob/master/Includes/li…> Thanks for any help Phil _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com signature.asc

1 0

BLE pairing prompt doesn't always display
by Mike 11 Oct '17

11 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=aGNwXoDz9os1lCKfNQg6wrtbz4n/mhtwbA/cpuMsprE=; b=PUVHCNFps7GHatR0CrUISoMpofV3bJKks29CT5gkXBjzVDdeJJP/zmLmV0UWmh5//M GnjXKcB5ts1EE/qX/y+PQvSqyavh38+a4Kd+tETunpTVqOnF+Wij9t5fgISLiCHN++md 8wxm5NEURMbVIZjkMJJqF+CuuJ85rJytaHxRBzY/fSdwL1sBviTdOJg/7ucS2CwFXXNX v7HMnZqqk9G6arHl/7idMUeMAOORKuIIhgsaFirCk7CkxuMRmnfdbZ01bKRW+fZPWzBQ ArMgkwDxlRXjWLOeWwYmi27dDzZANAmldmQgt2f+cGsCzFrD1MZ/VkrtO9UmzzxtHro9 iUVw== Hi, Testing with iOS 10.3.3. I'm curious why sometimes iOS will prompt to pair and other times attempt to pair without prompt? The basic steps are: 1. Delete BLE pairing and reboot phone 2. Reinstall app that I'm testing 3. App searches for and finds my BLE device 4. App connects and tries to write to a characteristic that requires encryption, device responds with insufficient encryption 5. Sometimes I see the SMP pairing request without iOS prompting to pair, sometimes iOS prompts to pair My device is no input no output, ble 4.2 secure connections only. Thanks, Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Connection Made then Dropped Right Away
by Chip Wachob 11 Oct '17

11 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Hello, New questions now that I've made some progress on the HID side of things... Result: Connection refused - security block (0x0003) Bluetooth monitor ver 5.37 = New Index: 5C:F3:70:77:62:B0 (BR/EDR,USB,hci0) [hci0] 0.536789 = Open Index: 5C:F3:70:77:62:B0 [hci0] 134.237134 <<< snip >>> > ACL Data RX: Handle 11 flags 0x02 dlen 14 [hci0] 265.221184 L2CAP: Configure Response (0x05) ident 4 len 6 Source CID: 64 Flags: 0x0000 Result: Success (0x0000) > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.224186 Num handles: 1 Handle: 11 Count: 2 > ACL Data RX: Handle 11 flags 0x02 dlen 17 [hci0] 265.225185 Channel: 64 len 13 [PSM 1 mode 0] {chan 0} SDP: Service Search Request (0x02) tid 0 len 8 Search pattern: [len 5] Sequence (6) with 3 bytes [8 extra bits] len 5 UUID (3) with 2 bytes [0 extra bits] len 3 Human Interface Device Service (0x1124) Max record count: 21 Continuation state: 0 < ACL Data TX: Handle 11 flags 0x00 dlen 18 [hci0] 265.225349 Channel: 77 len 14 [PSM 1 mode 0] {chan 0} SDP: Service Search Response (0x03) tid 0 len 9 Total record count: 1 Current record count: 1 Record handle: 0x10000 Continuation state: 0 > ACL Data RX: Handle 11 flags 0x02 dlen 23 [hci0] 265.231183 Channel: 64 len 19 [PSM 1 mode 0] {chan 0} SDP: Service Attribute Request (0x04) tid 1 len 14 Record handle: 0x10000 Max attribute bytes: 656 Attribute list: [len 7] Sequence (6) with 5 bytes [8 extra bits] len 7 Unsigned Integer (1) with 4 bytes [0 extra bits] len 5 0x0000ffff Continuation state: 0 < ACL Data TX: Handle 11 flags 0x00 dlen 359 [hci0] 265.231317 Channel: 77 len 355 [PSM 1 mode 0] {chan 0} SDP: Service Attribute Response (0x05) tid 1 len 350 Attribute bytes: 347 Attribute list: [len 344] {position 0} Attribute: Service Record Handle (0x0000) [len 2] 0x00010000 Attribute: Service Class ID List (0x0001) [len 2] UUID (3) with 2 bytes [0 extra bits] len 3 Human Interface Device Service (0x1124) Attribute: Protocol Descriptor List (0x0004) [len 2] Sequence (6) with 6 bytes [8 extra bits] len 8 UUID (3) with 2 bytes [0 extra bits] len 3 L2CAP (0x0100) Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x0011 Sequence (6) with 3 bytes [8 extra bits] len 5 UUID (3) with 2 bytes [0 extra bits] len 3 HIDP (0x0011) Attribute: Browse Group List (0x0005) [len 2] UUID (3) with 2 bytes [0 extra bits] len 3 Public Browse Root (0x1002) Attribute: Language Base Attribute ID List (0x0006) [len 2] Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x656e Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x006a Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x0100 Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2] Sequence (6) with 6 bytes [8 extra bits] len 8 UUID (3) with 2 bytes [0 extra bits] len 3 HIDP (0x0011) Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x0100 Attribute: Additional Protocol Descriptor List (0x000d) [len 2] Sequence (6) with 13 bytes [8 extra bits] len 15 Sequence (6) with 6 bytes [8 extra bits] len 8 UUID (3) with 2 bytes [0 extra bits] len 3 L2CAP (0x0100) Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x0013 Sequence (6) with 3 bytes [8 extra bits] len 5 UUID (3) with 2 bytes [0 extra bits] len 3 HIDP (0x0011) Attribute: Unknown (0x0100) [len 2] Bluez virtual Mouse and Keyboard [len 32] Attribute: Unknown (0x0101) [len 2] Keyboard [len 8] Attribute: Unknown (0x0102) [len 2] Anselm Martin Hoffmeister (GPL v2) [len 34] Attribute: Unknown (0x0200) [len 2] 0x0100 Attribute: Unknown (0x0201) [len 2] 0x0111 Attribute: Unknown (0x0202) [len 2] 0x40 Attribute: Unknown (0x0203) [len 2] 0x00 Attribute: Unknown (0x0204) [len 2] true Attribute: Unknown (0x0205) [len 2] true Attribute: Unknown (0x0206) [len 2] Sequence (6) with 102 bytes [8 extra bits] len 104 Unsigned Integer (1) with 1 byte [0 extra bits] len 2 0x22 String (4) with 98 bytes [8 extra bits] len 100 # #�#�# #� [len 98] Attribute: Unknown (0x0207) [len 2] Sequence (6) with 6 bytes [8 extra bits] len 8 Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x0409 Unsigned Integer (1) with 2 bytes [0 extra bits] len 3 0x0100 Attribute: Unknown (0x020b) [len 2] 0x0100 Attribute: Unknown (0x020e) [len 2] 0x0000 Continuation state: 0 > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.237183 Num handles: 1 Handle: 11 Count: 2 > ACL Data RX: Handle 11 flags 0x02 dlen 12 [hci0] 265.240186 L2CAP: Disconnection Request (0x06) ident 9 len 4 Destination CID: 64 Source CID: 77 < ACL Data TX: Handle 11 flags 0x00 dlen 12 [hci0] 265.240222 L2CAP: Disconnection Response (0x07) ident 9 len 4 Destination CID: 64 Source CID: 77 > HCI Event: Link Key Request (0x17) plen 6 [hci0] 265.250187 Address: 10:D5:42:BB:1F:F5 (Samsung Electronics Co.,Ltd) Address: 10:D5:42:BB:1F:F5 (Samsung Electronics Co.,Ltd) Link key: 04a355b0f7a76da518c012a47f11f622 > HCI Event: Command Complete (0x0e) plen 10 [hci0] 265.255190 Link Key Request Reply (0x01|0x000b) ncmd 1 Status: Success (0x00) Address: 10:D5:42:BB:1F:F5 (Samsung Electronics Co.,Ltd) > HCI Event: Encryption Change (0x08) plen 4 [hci0] 265.279191 Status: Success (0x00) Handle: 11 Encryption: Enabled with E0 (0x01) Handle: 11 > HCI Event: Command Complete (0x0e) plen 7 [hci0] 265.280197 Read Encryption Key Size (0x05|0x0008) ncmd 1 Status: Success (0x00) Handle: 11 Key size: 16 > ACL Data RX: Handle 11 flags 0x02 dlen 12 [hci0] 265.283184 L2CAP: Connection Request (0x02) ident 10 len 4 PSM: 17 (0x0011) Source CID: 79 < ACL Data TX: Handle 11 flags 0x00 dlen 16 [hci0] 265.283260 L2CAP: Connection Response (0x03) ident 10 len 8 Destination CID: 64 Source CID: 79 Result: Connection successful (0x0000) Status: No further information available (0x0000) < ACL Data TX: Handle 11 flags 0x00 dlen 23 [hci0] 265.283265 L2CAP: Configure Request (0x04) ident 5 len 15 Destination CID: 79 Flags: 0x0000 Option: Retransmission and Flow Control (0x04) [mandatory] Mode: Basic (0x00) TX window size: 0 Max transmit: 0 Retransmission timeout: 0 Monitor timeout: 0 Maximum PDU size: 0 > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.287182 Num handles: 1 Handle: 11 Count: 2 > ACL Data RX: Handle 11 flags 0x02 dlen 16 [hci0] 265.289188 L2CAP: Configure Request (0x04) ident 11 len 8 Destination CID: 64 Flags: 0x0000 Option: Maximum Transmission Unit (0x01) [mandatory] MTU: 640 < ACL Data TX: Handle 11 flags 0x00 dlen 18 [hci0] 265.289222 L2CAP: Configure Response (0x05) ident 11 len 10 Source CID: 79 Flags: 0x0000 Result: Success (0x0000) Option: Maximum Transmission Unit (0x01) [mandatory] MTU: 640 > ACL Data RX: Handle 11 flags 0x02 dlen 14 [hci0] 265.290182 L2CAP: Configure Response (0x05) ident 5 len 6 Source CID: 64 Flags: 0x0000 Result: Success (0x0000) < ACL Data TX: Handle 11 flags 0x00 dlen 5 [hci0] 265.290391 Channel: 79 len 1 [PSM 17 mode 0] {chan 0} 15 . < ACL Data TX: Handle 11 flags 0x00 dlen 12 [hci0] 265.290947 L2CAP: Disconnection Request (0x06) ident 6 len 4 Destination CID: 79 Source CID: 64 > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.294206 Num handles: 1 Handle: 11 Count: 2 > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.295200 Num handles: 1 Handle: 11 Count: 2 > ACL Data RX: Handle 11 flags 0x02 dlen 12 [hci0] 265.295210 L2CAP: Connection Request (0x02) ident 12 len 4 PSM: 19 (0x0013) Source CID: 65 < ACL Data TX: Handle 11 flags 0x00 dlen 16 [hci0] 265.295254 L2CAP: Connection Response (0x03) ident 12 len 8 Destination CID: 65 Source CID: 65 Result: Connection pending (0x0001) Status: Authorization pending (0x0002) ~~~ < ACL Data TX: Handle 11 flags 0x00 dlen 16 [hci0] 265.295770 L2CAP: Connection Response (0x03) ident 12 len 8 Destination CID: 65 Source CID: 65 Result: Connection refused - security block (0x0003) Status: No further information available (0x0000) > ACL Data RX: Handle 11 flags 0x02 dlen 12 [hci0] 265.296204 L2CAP: Disconnection Request (0x06) ident 13 len 4 Destination CID: 64 Source CID: 65 < ACL Data TX: Handle 11 flags 0x00 dlen 12 [hci0] 265.296237 L2CAP: Disconnection Response (0x07) ident 13 len 4 Destination CID: 64 Source CID: 79 > ACL Data RX: Handle 11 flags 0x02 dlen 12 [hci0] 265.298197 L2CAP: Disconnection Response (0x07) ident 6 len 4 Destination CID: 79 Source CID: 64 > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.300183 Num handles: 1 Handle: 11 Count: 2 > HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 265.502203 Num handles: 1 Handle: 11 Count: 1 < HCI Command: Disconnect (0x01|0x0006) plen 3 [hci0] 269.303096 Handle: 11 Reason: Remote User Terminated Connection (0x13) > HCI Event: Command Status (0x0f) plen 4 [hci0] 269.306107 Disconnect (0x01|0x0006) ncmd 1 Status: Success (0x00) > HCI Event: Disconnect Complete (0x05) plen 4 [hci0] 269.379094 Status: Success (0x00) Handle: 11 Reason: Connection Terminated By Local Host (0x16) @ Device Disconnected: 10:D5:42:BB:1F:F5 (0) reason 2 -- Chip Wachob Design Engineer Allen Organ _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com I've been able to look at the Bluetooth traces on the HID side of my connection and I keep coming across the following. I'm sure that this message is more meaningful to those who wrote the Bluez stack, but I'm not having any luck finding out what it really means and how to 'fix' it. I'm hoping that someone on the list is able to give me a pointer as to what this message is trying to tell me. What I am observing is that I can try to connect to my HID device from external sources (I've tried many different devices with the same results). The connection will appear to be made, then within seconds will be dropped. The external devices that I try to connect indicate that they are 'paired' with the HID device after this. My gut is telling me that it may have something to do with the attributes or the pairing configuration on the HID side, but I don't have a clue as to where to start looking. I've tried turning SSP on and off, likewise with Auth and Encrypt. I can't say that I've tried every possible combination of the three yet, but adding each of them one at a time didn't seem to make any difference. The same "Connection refused" message comes up. Thank you in advance for your help, below is the btmon dump, I'm sorry that it is so long. I've marked the entry in question with ~~~ below. [The mailing list came back and told me that the message was too long, so I'm removing part of the log file in hopes that it will pass the monitor] < HCI Command: Link Key Request Reply (0x01|0x000b) plen 22 [hci0] 265.250223 < HCI Command: Read Encryption Key Size (0x05|0x0008) plen 2 [hci0] 265.279237

1 0

Bluetooth device pairing (and working) with multiple phones
by Jan Lübeck 06 Oct '17

06 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fyrastudio-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=6NXgTOZKfU4H/vla14933Ou1ImeUJLRVWqAcYTXHFRE=; b=f+jEDBJ/cRyP36MkwwRK4iPHmkXpyZIefNs1LwGgMmLI1Bib01kRHqUuS2NgkFHIeV x1av+mtNH1vdOdFIwUgTQv4XdU/tJtqKnWYdWWcVOkdZTjZSeTdtskCfz3YBBOYUwfuy QvxNLdWB1GSzZiHQaPRR8VrS8wO8ge3NffQdw7KMUiEGZOuQ1OltMDT5TfawfbIs0A9a El8ss5YHMRvn9Xzqey7pNhHF6KDR0HpNq4r6IHpyxaT3bVqUhDzBOGXrGVgTMc58Fb1u FN/k/AKOPVJGJYGRwu6xu4QPgvszdWwz/xK84gRCezhFYtsvpeRAADTU8bBgFsBJHZoB iZkg== Is it possible for a bluetooth device to actually pair and work simultaneously across several phones?? Every consumer BT device I´ve used, although you can pair to multiple phones, it only works with a single one at a time. Just wondering if that is by design or a technical impossibility. Thank you! *_____**_* Jan Lübeck Chief Technology Officer fyrastudio.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Fwd: Requirements for a Connection
by Matthias Ringwald 04 Oct '17

04 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluekitchen-gmbh.com; s=default; h=Date:To:References:Message-Id:Subject: Mime-Version:Content-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VsPJEANkLMY4u9ys8vIwDwNFtViND7wQse/5myzKc+c=; b=prdUquGMC23Umx3l8vaHwAhdJP Lc7BLZ+ktP+7RjoIDQE+iMoCKLvZ/U4p6hrzCPc2OnaazjDWLi0ZfA6SDNfxXRjCAbvIxFd9mpG8o 1ssKdjYiJOtb/yjD4UCP6g236EJ7XHtPMq3+gnRQVe31v0nCopYoLVWaEHyEpyMZcGhn7DqrExvku LxdwXbbHh/rGQOekMDjKIEW951QDbVhJvB0GW7VRQITit5xH7EDQSx7lcoklWWEKhnG4+I9Xt2XOb ipwxchr/gXCaaG8jrocEZaiJ/LG/bNrL2XdA2XO2H0kQvz90uwl+MK9/elp92urntiH1TPcgly4nm UDyRBd+w==; Hi Chip In Bluetooth Classic (BR/EDR), the HID Host has to announce an HID Service via SDP and accept L2CAP connections if it wants to accept incoming connections, e.g. a connection initiated by the keyboard (which is implemented most Bluetooth keyboards). Cheers Matthias — Dr. sc. Matthias Ringwald Co-founder BlueKitchen GmbH, Zurich https://bluekitchen-gmbh.com <https://bluekitchen-gmbh.com/> > On 4 Oct 2017, at 19:39, Chip Wachob <cw(a)allenorgan.com > <mailto:cw@allenorgan.com>> wrote: > > Matthias, > > Thank you for the information and the link. > > Does this also apply to non-LE applications? > > Chip Wachob > Design Engineer > Allen Organ > 150 Locust St. > Macungie, PA 18062 > V 610.966.2200 > F 610.966.4684 > > Walking on water and writing software to specification is easy if they're > frozen. > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain confidential and/or privileged material. Any review, > retransmission, dissemination > or other use of, or taking of any action in reliance upon, this information > by persons or entities > other than the intended recipient is prohibited. If you received this in > error, please contact the > sender and delete the material from any computer. > > On 10/2/2017 7:54 AM, Matthias Ringwald wrote: >> Hi Chip >> >> The client of an LE HID Device (HID-over-GATT), the HID Host, does not need >> to implement or advertise any services. >> The HID Device can reconnect and send new notifications if needed. >> >> Feel free to browse the specification: >> https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141 >> <https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141> >> >> Cheers >> Matthias >> >> — >> Dr. sc. Matthias Ringwald >> Co-founder BlueKitchen GmbH, Zurich >> https://bluekitchen-gmbh.com <https://bluekitchen-gmbh.com/> >> >> >>> On 29 Sep 2017, at 14:42, Chip Wachob <cw(a)allenorgan.com >>> <mailto:cw@allenorgan.com>> wrote: >>> >>> Hello again, >>> >>> I realize that this is an Apple specific list, but everyone here seems >>> friendly enough that I think I can ask this more general question without >>> being flamed... >>> >>> Can someone please confirm or correct my understanding about making a >>> connection with BT? >>> >>> As I understand it, for two devices to be able to connect they must both >>> have the same Service UUID (and Service Class UUID). >>> >>> Say, for example, a BT keyboard. Keyboards are usually handled under the >>> HID group, so the keyboard must advertise that it supports HID and a >>> keyboard. Likewise, on the other side of the connection, the other device >>> needs to also have a identical UUID so that the two devices know that they >>> can 'talk' on the same "port". >>> >>> Did I read this right? >>> >>> I presume there's no way around this requirement if the device that you >>> want to connect the keyboard to does not advertise that capability... >>> >>> Thank you, >>> -- >>> Chip Wachob >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com >>> <mailto:Bluetooth-dev@lists.apple.com>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/bluetooth-dev/matthias%40bluekitche… >>> >>> <https://lists.apple.com/mailman/options/bluetooth-dev/matthias%40bluekitche…> >>> >>> This email sent to matthias(a)bluekitchen-gmbh.com >>> <mailto:matthias@bluekitchen-gmbh.com> >> > _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Requirements for a Connection
by Chip Wachob 04 Oct '17

04 Oct '17

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Matthias, Thank you for the information and the link. Does this also apply to non-LE applications? Chip Wachob Design Engineer Allen Organ 150 Locust St. Macungie, PA 18062 V 610.966.2200 F 610.966.4684 Walking on water and writing software to specification is easy if they're frozen. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. On 10/2/2017 7:54 AM, Matthias Ringwald wrote: Hi Chip The HID Device can reconnect and send new notifications if needed. Cheers Matthias — Dr. sc. Matthias Ringwald Co-founder BlueKitchen GmbH, Zurich https://bluekitchen-gmbh.com Hello again, Did I read this right? Thank you, -- Chip Wachob _______________________________________________ Do not post admin requests to the list. They will be ignored. Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/matthias%40bluekitche… This email sent to matthias(a)bluekitchen-gmbh.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com The client of an LE HID Device (HID-over-GATT), the HID Host, does not need to implement or advertise any services. Feel free to browse the specification: https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141 On 29 Sep 2017, at 14:42, Chip Wachob <cw(a)allenorgan.com <mailto:cw@allenorgan.com>> wrote: I realize that this is an Apple specific list, but everyone here seems friendly enough that I think I can ask this more general question without being flamed... Can someone please confirm or correct my understanding about making a connection with BT? As I understand it, for two devices to be able to connect they must both have the same Service UUID (and Service Class UUID). Say, for example, a BT keyboard. Keyboards are usually handled under the HID group, so the keyboard must advertise that it supports HID and a keyboard. Likewise, on the other side of the connection, the other device needs to also have a identical UUID so that the two devices know that they can 'talk' on the same "port". I presume there's no way around this requirement if the device that you want to connect the keyboard to does not advertise that capability... Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com <mailto:Bluetooth-dev@lists.apple.com>)

1 0