Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

emotive — Wed, 14 Oct 2020 21:40:02 GMT

SOLUTION AT LAST!

(Since it appears that this thread has been relegated to the dust bin....)

// 1. After a determined effort, here is what I was able to do with the Thingy:52

// Make sure you have gatttool installed via apt or pip if you are on the Pi.

// 2. IMPORTANT to enable this first...
pisys1@piSys1:~$ sudo btmgmt le on

pisys1@piSys1:~$ sudo gatttool -t random -b yo:ur:ma:c:ad:rs -I
[yo:ur:ma:c:ad:rs][LE]> connect
Attempting to connect to yo:ur:ma:c:ad:rs
Connection successful

[yo:ur:ma:c:ad:rs][LE]>

// 3. Display all the characteristics of the Thingy52...
[yo:ur:ma:c:ad:rs][LE]> characteristics
handle: 0x0002, char properties: 0x02, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0004, char properties: 0x02, char value handle: 0x0005, uuid: 00002a01-0000-1000-8000-00805f9b34fb
handle: 0x0006, char properties: 0x02, char value handle: 0x0007, uuid: 00002a04-0000-1000-8000-00805f9b34fb
handle: 0x0008, char properties: 0x02, char value handle: 0x0009, uuid: 00002aa6-0000-1000-8000-00805f9b34fb
handle: 0x000b, char properties: 0x20, char value handle: 0x000c, uuid: 00002a05-0000-1000-8000-00805f9b34fb
handle: 0x000f, char properties: 0x0a, char value handle: 0x0010, uuid: ef680101-9b35-4933-9b10-52ffa9740042
handle: 0x0011, char properties: 0x0a, char value handle: 0x0012, uuid: ef680102-9b35-4933-9b10-52ffa9740042
handle: 0x0013, char properties: 0x0a, char value handle: 0x0014, uuid: ef680104-9b35-4933-9b10-52ffa9740042
handle: 0x0015, char properties: 0x0a, char value handle: 0x0016, uuid: ef680105-9b35-4933-9b10-52ffa9740042
handle: 0x0017, char properties: 0x0a, char value handle: 0x0018, uuid: ef680106-9b35-4933-9b10-52ffa9740042
handle: 0x0019, char properties: 0x02, char value handle: 0x001a, uuid: ef680107-9b35-4933-9b10-52ffa9740042
handle: 0x001b, char properties: 0x0a, char value handle: 0x001c, uuid: ef680108-9b35-4933-9b10-52ffa9740042
handle: 0x001d, char properties: 0x0a, char value handle: 0x001e, uuid: ef680109-9b35-4933-9b10-52ffa9740042
handle: 0x0020, char properties: 0x10, char value handle: 0x0021, uuid: ef680201-9b35-4933-9b10-52ffa9740042
handle: 0x0023, char properties: 0x10, char value handle: 0x0024, uuid: ef680202-9b35-4933-9b10-52ffa9740042
handle: 0x0026, char properties: 0x10, char value handle: 0x0027, uuid: ef680203-9b35-4933-9b10-52ffa9740042
handle: 0x0029, char properties: 0x10, char value handle: 0x002a, uuid: ef680204-9b35-4933-9b10-52ffa9740042
handle: 0x002c, char properties: 0x10, char value handle: 0x002d, uuid: ef680205-9b35-4933-9b10-52ffa9740042
handle: 0x002f, char properties: 0x0a, char value handle: 0x0030, uuid: ef680206-9b35-4933-9b10-52ffa9740042
handle: 0x0032, char properties: 0x0a, char value handle: 0x0033, uuid: ef680401-9b35-4933-9b10-52ffa9740042
handle: 0x0034, char properties: 0x10, char value handle: 0x0035, uuid: ef680402-9b35-4933-9b10-52ffa9740042
handle: 0x0037, char properties: 0x10, char value handle: 0x0038, uuid: ef680403-9b35-4933-9b10-52ffa9740042
handle: 0x003a, char properties: 0x10, char value handle: 0x003b, uuid: ef680404-9b35-4933-9b10-52ffa9740042
handle: 0x003d, char properties: 0x10, char value handle: 0x003e, uuid: ef680405-9b35-4933-9b10-52ffa9740042
handle: 0x0040, char properties: 0x10, char value handle: 0x0041, uuid: ef680406-9b35-4933-9b10-52ffa9740042
handle: 0x0043, char properties: 0x10, char value handle: 0x0044, uuid: ef680407-9b35-4933-9b10-52ffa9740042
handle: 0x0046, char properties: 0x10, char value handle: 0x0047, uuid: ef680408-9b35-4933-9b10-52ffa9740042
handle: 0x0049, char properties: 0x10, char value handle: 0x004a, uuid: ef680409-9b35-4933-9b10-52ffa9740042
handle: 0x004c, char properties: 0x10, char value handle: 0x004d, uuid: ef68040a-9b35-4933-9b10-52ffa9740042
handle: 0x0050, char properties: 0x10, char value handle: 0x0051, uuid: ef680302-9b35-4933-9b10-52ffa9740042
handle: 0x0053, char properties: 0x0a, char value handle: 0x0054, uuid: ef680301-9b35-4933-9b10-52ffa9740042
handle: 0x0055, char properties: 0x0a, char value handle: 0x0056, uuid: ef680303-9b35-4933-9b10-52ffa9740042
handle: 0x0058, char properties: 0x0a, char value handle: 0x0059, uuid: ef680501-9b35-4933-9b10-52ffa9740042
handle: 0x005a, char properties: 0x04, char value handle: 0x005b, uuid: ef680502-9b35-4933-9b10-52ffa9740042
handle: 0x005c, char properties: 0x10, char value handle: 0x005d, uuid: ef680503-9b35-4933-9b10-52ffa9740042
handle: 0x005f, char properties: 0x10, char value handle: 0x0060, uuid: ef680504-9b35-4933-9b10-52ffa9740042
handle: 0x0063, char properties: 0x12, char value handle: 0x0064, uuid: 00002a19-0000-1000-8000-00805f9b34fb
handle: 0x0067, char properties: 0x28, char value handle: 0x0068, uuid: 8ec90003-f315-4f60-9fb8-838830daea50
[yo:ur:ma:c:ad:rs][LE]>

// Notice all of the offsets shown and specifically 'handle: 0x0063 and handle 0x0064' for the
// characteristic 00002a19, e.g. The Battery Characteristic.
// Note that for the battery service, the characteristic is displayed as a full UUID,
// NOT the service 0x180F as a full UUID.

// Read the battery service characteristic value
[yo:ur:ma:c:ad:rs][LE]> char-read-uuid 00002a19-0000-1000-8000-00805f9b34fb 0x0063 0x0066
handle: 0x0064 value: 60 // <-- Expected 1 byte

// Lo and behold, the elusive battery value has finally been read!

// Enable notify on Temperature value
[yo:ur:ma:c:ad:rs][LE]> char-write-req 0x0022 0100
Characteristic value was written successfully
Notification handle = 0x0021 value: 17 18 // <-- Expected 2 bytes
Notification handle = 0x0021 value: 17 0f
Notification handle = 0x0021 value: 17 16
Notification handle = 0x0021 value: 17 1c
Notification handle = 0x0021 value: 17 0f
Notification handle = 0x0021 value: 17 21
Notification handle = 0x0021 value: 17 25

// Disable notify on Temperature value
[yo:ur:ma:c:ad:rs][LE]> char-write-req 0x0022 0000
Characteristic value was written successfully

// Read the name value
[yo:ur:ma:c:ad:rs][LE]> char-read-uuid ef680101-9b35-4933-9b10-52ffa9740042 0x000f 0x0010
handle: 0x0010 value: 54 68 69 6e 67 79 32 // <-- Expected 5 bytes(Thingy2)

So... if this helps anyone, pls comment. Maybe a bit obsessive, but I knew that one should be able to get at all these characteristics using low level linux tools.

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

emotive — Thu, 08 Oct 2020 18:55:53 GMT

Well?

From the last post, it is clear that the Battery is a GSS (Standard service) and not a GATT service.

So, can anyone in the Nordic Dev Group look into a solution?

How does one read the value for the Battery Service without writing a full C program?

How does one take advantage of the basic tools built into linux in order to work with the bluetooth stack graciously provided by Nordic?

Thank you again.

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

emotive — Tue, 06 Oct 2020 21:38:46 GMT

Some additional findings:

Using btmon (A bluetooth monitor)
I launched btmon from one terminal session (#1)
I launched bluetoothctl from another terminal session (#2)

From (#2) issue

[bluetoothctl]# connect xx:18:81:32:yy:B0

[Thingy2]#

To read the attribute info, one must first go into the GATT submenu

[Thingy2]# menu gatt

On connection executed by (#2), the following is reported by #1 (condensed version)

#23 [hci0] 526.473447
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: xx:18:81:32:yy:B0 (Static)
Data length: 30
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
128-bit Service UUIDs (partial): 1 entry
Vendor specific (ef680100-9b35-4933-9b10-52ffa9740042)
Name (complete): Thingy2
RSSI: -42 dBm (0xd6)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2

#43 [hci0] 527.519266
ATT: Read By Group Type Response (0x11) len 13
Attribute data length: 6
Attribute group list: 2 entries
Handle range: 0x0001-0x0009
UUID: Generic Access Profile (0x1800)
Handle range: 0x000a-0x000d
UUID: Generic Attribute Profile (0x1801)
< ACL Data TX: Handle 64 flags 0x00 dlen 9

#51 [hci0] 527.812983
ATT: Read By Group Type Response (0x11) len 101
Attribute data length: 20
Attribute group list: 5 entries
Handle range: 0x000e-0x001e
UUID: Vendor specific (ef680100-9b35-4933-9b10-52ffa9740042)
Handle range: 0x001f-0x0030
UUID: Vendor specific (ef680200-9b35-4933-9b10-52ffa9740042)
Handle range: 0x0031-0x004e
UUID: Vendor specific (ef680400-9b35-4933-9b10-52ffa9740042)
Handle range: 0x004f-0x0056
UUID: Vendor specific (ef680300-9b35-4933-9b10-52ffa9740042)
Handle range: 0x0057-0x0061
UUID: Vendor specific (ef680500-9b35-4933-9b10-52ffa9740042)
< ACL Data TX: Handle 64 flags 0x00 dlen 11

#58 [hci0] 527.910473
ATT: Read By Group Type Response (0x11) len 13
Attribute data length: 6
Attribute group list: 2 entries
Handle range: 0x0062-0x0065
UUID: Battery Service (0x180f)
Handle range: 0x0066-0xffff
UUID: Nordic Semiconductor ASA (0xfe59)
< ACL Data TX: Handle 64 flags 0x00 dlen 9

Now we try to correlate the btmon 'Handle range:' with the service../char.. values

// bluetoothctl list report (#2):
[NEW] Primary Service (Handle 0xf000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f
ef680200-9b35-4933-9b10-52ffa9740042
Vendor specific

[NEW] Characteristic (Handle 0xaf90)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char002f
ef680206-9b35-4933-9b10-52ffa9740042
Vendor specific

// btmon report:
Handle range: 0x001f-0x0030
UUID: Vendor specific (ef680200-9b35-4933-9b10-52ffa9740042)

// Another one...

// bluetoothctl list report (#2):
[NEW] Primary Service (Handle 0xf000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031
ef680400-9b35-4933-9b10-52ffa9740042
[NEW] Characteristic (Handle 0xaf90)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0032
ef680401-9b35-4933-9b10-52ffa9740042
...
[NEW] Characteristic (Handle 0xaf90)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char004c
ef68040a-9b35-4933-9b10-52ffa9740042
Vendor specific
[NEW] Descriptor (Handle 0x4a70)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char004c/desc004e
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration

// btmon report:
Handle range: 0x0031-0x004e
UUID: Vendor specific (ef680400-9b35-4933-9b10-52ffa9740042)

// The clues:
1.1 The above suggests that btmon shows the vendor specific service for the
200 series service with a range of 0x001f-0x0030

The [bluetoothctl]# list report corresponds with:

service001f //<-- The offset
service001f/char002f //<-- The last characteristic offset

And the next service listed has
HandleRange: 0x0031 to 0x004e

The [bluetoothctl]# list report corresponds with:

/service0031 //<-- The offset
and the last charactersitic's description at
/service0031/char004c/desc004e //<-- The last characteristic offset

1.2 Maybe the battery can be found at:

Handle range: 0x0062-0x0065
UUID: Battery Service (0x180f)
service0062/

[Thingy2:/service0066/char0067]# select-attribute /org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067/desc0069

Notice the prompt changes only when the attribute is valid:

[Thingy2:/service0066/char0067/desc0069]# read

A Legitimate read operation producers results:

Attempting to read /org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067/desc0069
[CHG] Attribute /org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067/desc0069 Value:
00 00 ..
00 00

Notice the attempt to read what should be the battery offset:

And notice that the prompt does not change indicating attribute is not valid:

[Thingy2:/service0066/char0067/desc0069]# select-attribute /org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0062/char0063

[Thingy2:/service0066/char0067/desc0069]#

Again no joy. So, battery service is present and has an offset but is not a GATT service and therefore cannot be found under the GATT menu.

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

emotive — Tue, 06 Oct 2020 17:23:40 GMT

Thank you again for the quick response.

The link you provided is one that I have used.(At least the command order)

If there is a specific memory offset from 0000fe59-... would you let me know what the offset is?

Or, is it necessary to pair with the thingy in order to even see the battery service?

I have connected to the thingy many times with

[bluetoothctl]# connect <mac adrs here>

Each time as included above, I get a list of services with their tiered characteristics and descriptions (partially included here)

Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066
0000fe59-0000-1000-8000-00805f9b34fb
Nordic Semiconductor ASA
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067
8ec90003-f315-4f60-9fb8-838830daea50
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067/desc0069
00002902-0000-1000-8000-00805f9b34fb

...

However, the one that is never shown is the battery service.

Using the [bluetoothctl]# list (after having connected to the thingy, not paired)

I get a list which includes the UUID for the battery service as shown above and repeated here for clarity:

...

UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb) // <------

...

The Bluetooth spec lists the battery service as type GSS.

However, on completion of the above 'connect' command under bluetoothctl, the device/service/characteristic path is not found and does not exist for the battery service.

This says that the battery service is not enumerated under bluetoothctl?

So, are there specific offsets from the 0000fe59 location that I missed in the documentation?

The benefit (supposed) to using bluetoothctl is that it is 'standardized' with Bluez under linux.

This means that much of the software stack that would have to be handwritten/cut-pasted/ etc is already done and optimized for the linux kernel.

There are older tools which have bee deprecated hcitool and gatttool and those were rolled into bluetoothctl.

If anyone in your group has insights as to how to get at this ever-elusive battery service under bluetoothctl please let me know.

Thank you again...

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

Hung Bui — Tue, 06 Oct 2020 13:33:26 GMT

As I mentioned, I'm not very familiar with Linux environment. I will try to forward your question to some one that has more experience with Linux here.

But as I mentioned, please try to test with a simple application first before you go straight to the thingy application.

In my case, when checking with nrf Connect app, the battery service is located right above 0000fe59-0000-1000-8000-00805f9b34fb DFU service.

Please note again, regarding question on 3rd party platform, please try to ask on other support channels in addition to posting the question here, as we don't have any control over how bluetoothctl works.

I did a quick search and in this doc, the battery service is discovered in the example and you have a path to access it:

https://core.docs.ubuntu.com/en/stacks/bluetooth/bluez/docs/reference/gatt-services

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

emotive — Mon, 05 Oct 2020 18:44:45 GMT

With utmost respect for your knowledge, 'bluetoothctl' under linux is 'the' current standard. It is implemented through Bluez. So one purpose in providing the commands I used (which are basically 4) is so that you or anyone in your group could run the same test on any Ubuntu Linux based system (Current ver 20.xx Ubuntu Mate on Rasberry Pi 4). I would guess that you all have multiple linux based systems for development and test.

Since this is not something you are familiar with (and again I say this with respect for your position and knowledge), perhaps another engineer could quickly verify whether the service is or is not accessible under bluetoothctl and or bluez?

Since the other service 1801 is accessible, I do not yet see an explanation as to why 180F would not also be accessible as well?

I have even read posts that state that the standard bluetooth daemon loads a plugin which blocks the 'battery service'? And running systemctl with the correct args can stop this plugin from being loaded. (-P battery or --property --value=battery) as in

systemctl daemon-reload

systemctl start bluetooth --property --value=battery

Well, I tried all that and still no joy.

Since the Battery service is not under GAP or GATT, but a standard Bluetooth SIG service...

Can anyone reading this or in your group determine why or how one reads the battery level using the service 180F and the attribute 2A19 by implementing command line bluetoothctl or bluez?

Thank you.

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

Hung Bui — Mon, 05 Oct 2020 09:49:16 GMT

Hi,

I'm afraid that I'm not very familiar with Bluez, so I don't know how I can help you.
You may want to post your question at other forum/portal that more specifically to BlueZ stack.

My suggestion for you is to try to test on one of our example so that the attribute table is smaller and easier to handle than go straight to the Thingy52.

The battery service is not under GAP or GATT service. It's a Bluetooth SIG standard service.

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

emotive — Fri, 02 Oct 2020 23:02:49 GMT

Thank you for your quick response. Yes 0x180F is the battery service. When I execute a [bluetoothctl]# list as below, I do see the battery service. Is the battery service a gatt service?

After bluetoothctl establishes a connection, it lists all the available gatt services. That 'process' assigns the path to the characteristic so one can then use the attribute-select and list-attribute commands. (I am sure you already know all this)

So, I still do not know how to read the value of the battery service using bluetoothctl since no path to the characteristic is shown even when going into the gatt submenu of bluetoothctl and executing a list-attributes on the device Thingy:52 as shown below (sorry for the whole 250 line dump, I thought it might be useful to see the actual output)

Unfortunately I do not have a DK to use a sniffer on?

I can see the battery value under this bus command after running the following:

sudo dbus-send --print-reply=literal --system --dest=org.bluez /org/bluez/hci0/dev_xx_18_81_32_yy_B0 org.freedesktop.DBus.Properties.GetAll string:"org.bluez.Battery1"

array [

dict entry(

Percentage variant byte 98

)

]

Below is a complete dump and even though the service is listed under info, it is not listed in the gatt service menu, as in there is no path to the service/char as there is for the other services and their characteristics.

So you have any idea how to read the value of the battery using bluetoothctl?

I see no way to list the gatt 'path' to the battery service.

[Thingy2]# info
Device xx:18:81:32:yy:B0 (random)
Name: Thingy2
Alias: Thingy2
Paired: no
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Nordic Semiconductor ASA (0000fe59-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (ef680100-9b35-4933-9b10-52ffa9740042)
UUID: Vendor specific (ef680200-9b35-4933-9b10-52ffa9740042)
UUID: Vendor specific (ef680300-9b35-4933-9b10-52ffa9740042)
UUID: Vendor specific (ef680400-9b35-4933-9b10-52ffa9740042)
UUID: Vendor specific (ef680500-9b35-4933-9b10-52ffa9740042)

[Thingy2]# menu gatt

[Thingy2]# list-attributes xx_18:81:32:yy:B0

Primary Service (Handle 0xfbd4)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000a
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000a/char000b
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000a/char000b/desc000d
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e
ef680100-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char000f
ef680101-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char0011
ef680102-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char0013
ef680104-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char0015
ef680105-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char0017
ef680106-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char0019
ef680107-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char001b
ef680108-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service000e/char001d
ef680109-9b35-4933-9b10-52ffa9740042
Vendor specific
Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f
ef680200-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0020
ef680201-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0020/desc0022
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x5230)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0023
ef680202-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0023/desc0025
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x6b90)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0026
ef680203-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0026/desc0028
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x7b50)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0029
ef680204-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char0029/desc002b
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x9a90)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char002c
ef680205-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char002c/desc002e
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0xaa30)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service001f/char002f
ef680206-9b35-4933-9b10-52ffa9740042
Vendor specific
Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031
ef680400-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0032
ef680401-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0034
ef680402-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0034/desc0036
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0xd180)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0037
ef680403-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0037/desc0039
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0xdf80)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char003a
ef680404-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char003a/desc003c
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0xed10)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char003d
ef680405-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char003d/desc003f
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x0170)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0040
ef680406-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0040/desc0042
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x0f20)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0043
ef680407-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0043/desc0045
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x23c0)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0046
ef680408-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0046/desc0048
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x3c10)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0049
ef680409-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char0049/desc004b
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x49c0)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char004c
ef68040a-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0031/char004c/desc004e
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service004f
ef680300-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service004f/char0050
ef680302-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service004f/char0050/desc0052
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x5ec0)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service004f/char0053
ef680301-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x5ec0)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service004f/char0055
ef680303-9b35-4933-9b10-52ffa9740042
Vendor specific
Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057
ef680500-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057/char0058
ef680501-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057/char005a
ef680502-9b35-4933-9b10-52ffa9740042
Vendor specific
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057/char005c
ef680503-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057/char005c/desc005e
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x9af0)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057/char005f
ef680504-9b35-4933-9b10-52ffa9740042
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0057/char005f/desc0061
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Primary Service (Handle 0xacdc)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066
0000fe59-0000-1000-8000-00805f9b34fb
Nordic Semiconductor ASA
Characteristic (Handle 0x0240)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067
8ec90003-f315-4f60-9fb8-838830daea50
Vendor specific
Descriptor (Handle 0x0000)
/org/bluez/hci0/dev_xx_18_81_32_yy_B0/service0066/char0067/desc0069
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration

RE: Unable to read battery level from battery characteristic on Thingy:52 using bluetoothctl on linux

Hung Bui — Fri, 02 Oct 2020 11:47:02 GMT

Hi Emotive,

Are you sure 0x1801 is battery service ?
Battery service is defined as 0x180F here.

And you can find the battery level characteristic (0x2A19) listed here.

0x1801 is the GAP service , that include the service changed characteristic you may have mistakenly enabled.

I would also suggest to capture a sniffer trace in addition to the log just to double check if the communication was correct.