BLE UUID for the Battery Service on the thing52?

[jimm58]

I'm writing an app to that talks to the Thing52 over BLE, and using this as a reference: nordicsemiconductor.github.io/.../firmware_architecture.html For Battery Services, the Service UUID isn't listed - just the characteristic UUID.  What's the service UUID?

[Bjørn Kvaale]

I agree with you on first look, however it seems that the battery service does actually have this UUID. In ble_srv_common.h in the Thingy SDK, you can see the battery service UUID defined:

#define BLE_UUID_BATTERY_SERVICE                                 0x180F     /**< Battery service UUID. */

[jimm58]

Ok, I found a charastic of Batty level in one of the header files - 0x2A19 - but that doesn't seem to be correct or work.

[Bjørn Kvaale]

I am certain that is the correct characteristic value. You can see how the characteristic value is added in the battery_level_char_add() function inside ble_bas.c:

[jimm58]

Did a bit more debugging on the app I'm using to talk to the thingy, and it actually seems I'm seeing a problem with the service itself (0x180f).  Per the phone app, the thingy has the 2.1.0 FW, but could it be I need different FW?

[Bjørn Kvaale]

Maybe, but I don't think so. Are you able to connect to the battery service (0x180F) via nRF Connect for Mobile? If you click on the service, you should be able to see the battery level characteristic (0x2A19) & read the battery value. Also, are you able to see the battery level in the Thingy mobile app? That would suggest that reading from the characteristic works like it should.

[jimm58]

OK!  It's working!  It gets back to the documentation I mentioned in the initial post.  I was using the same base UUID as for the other services like env and motion (as none was mentioned),  Using the base UUID for the DFU service got things going

[Bjørn Kvaale]

Great to hear that you got it working!