BLE central for Komoot app service setup

RE: BLE central for Komoot app service setup

Edvin — Wed, 02 Jan 2019 08:12:35 GMT

Hello, and happy new year!

Glad to see that you figured it out, and thank you for sharing, as it can be useful for others working with the same app.

Best regards,

Edvin

RE: BLE central for Komoot app service setup

vincent.golle — Tue, 25 Dec 2018 09:56:10 GMT

Hi Edvin,

And no, 93D3 is unrelated.

However the issue is now solved !

Contrary to what Komoot's manual states, there is no need to write the identifier back to the characteristic.

It is enough to read the characteristic upon notification.

If in the future anybody using the nRF wants to use the Komoot app, they can just refer to my code:

https://github.com/vincent290587/ble_services

RE: BLE central for Komoot app service setup

Edvin — Fri, 21 Dec 2018 11:42:58 GMT

Hello,

I see. It is not possible to write anything to the 503D.... characteristic. Only read and notify.

What is in the other service, starting with 89D3...? Anything you can write to there?

BR,

Edvin

RE: BLE central for Komoot app service setup

vincent.golle — Fri, 21 Dec 2018 11:40:00 GMT

The service looks really simple, however i can't understand how I am supposed to transmit this "identifier" to the iPhone...

I am indeed connected and getting the notifications.

Here i get notified with the identifier as notification data (87 6A...).

The rest of the data is read when I to a "sd_ble_gattc_read" (27 bytes).

I also don't understand how and where i have to register the characteristic 128 bits UUID. ( I did register the service base UUID though)

RE: BLE central for Komoot app service setup

Edvin — Fri, 21 Dec 2018 08:03:56 GMT

I suggest that you start with trying to connect to the app with nRF Connect for Desktop, to get familiar with the services and characteristics on the device.

I also suggest you study the softdevice documentation for Generic Attribute Server, and especially the function sd_ble_gatts_value_get().

You did manage to the device and enable the notification for the service, right? So you have the attribute handle which you can use in sd_ble_atts_value_get()?

BR,

Edvin

RE: BLE central for Komoot app service setup

vincent.golle — Thu, 20 Dec 2018 23:20:30 GMT

Here is a chart of the communication:

I am here trying to build the external BLE device (displays the turn by turn information)

I get the notifications and I read the characteristic fine, but komoot states that the read requests must contain a uint32_t identifier which is present in the notification.

Identifier

UInt32 value to identify a single navigation instruction. Use this identifier for sending the read request to the characteristic. If we get a read request without this identifier, we will deliver the last data object.

Could you please help me on that ?

RE: BLE central for Komoot app service setup

Edvin — Thu, 20 Dec 2018 14:16:08 GMT

Hello,

I am sorry, I don't quite understand what you mean.

[quote user=""]However, I am supposed to provide my read requests with a unique identifier (present in the previous notification)[/quote]

Is this a characteristic that you want to read from or write to? Does it use (BLE) notification?

So are you trying to read the next turn, or do you want to input the next turn?

BR,

Edvin

RE: BLE central for Komoot app service setup

vincent.golle — Wed, 19 Dec 2018 21:24:31 GMT

My current code for the service is located here:

github.com/.../ble_komoot_c