read-hn | A Bayesian ML recommendation engine for HackerNews stories | Machine Learning library

As a side note, gatttool is deprecated and the current supported tool for doing this is bluetoothctl.

GATT UUID's with the format 0000xxxx-0000-1000-8000-00805f9b34fb mean they have been adopted by the Bluetooth SIG and you can look up what they represent in the 16-bit UUID Numbers Document

There are also generic Bluetooth Low Energy scanning and exploration tools such as nRF connect that can be helpful exploring a device.

From the GATT information you posted, I could only see generic content that needs to be included and not anything specific about temperature.

The advertising data is including Manufacturer Data which can (as maybe the name suggests) be anything that the manufacturer wants. From the Core Specification Supplement

This means you need to get the information from the manufacturer or work backwards from what you think the data is saying. As you have not shared any information about the device broadcasting, it seems like you are heading in the right direction.

Most Bluetooth data is little endian so having to swap the bytes around is not unexpected. Beacon formats like iBeacon and Eddystone tend to be big endian but they are the exception rather than the rule.

You will probably want to use the D-Bus API if you want to get the data into some kind of code. There are D-Bus bindings for most languages and the BlueZ API you will need is documented at:

• https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/adapter-api.txt
• https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/device-api.txt

The temperature measurement follows the following rules:

• it’s in little endian format so you first need to switch it to read as 0x092e

• you convert that to decimal and you get (9x256+2x16+14) = 2350

• then the value has an implied decimal exponent of -2, which means you take the value and divide by 100

This means the value read in this case is 23.50 Celsius

The output of primary is telling you which services your device supports, e.g.: the first segment of uuid: 00001800-0000-1000-8000-00805f9b34fb is 00001800 which is the Generic Access service (org.bluetooth.service.generic_access, 0x1800).

The output of primary does not list the Battery Service (org.bluetooth.service.battery_service, 0x180F):

I was thinking of subclassing pexpect.spawn and providing an expect_before(p,c) method that would save a list of patterns p and callback functions c, then override expect(p2) to prefix the list p onto the list p2 of that call before calling the real spawn.expect function.

If the real function then returns a match index i that is within the size of the list p, we can call function c[i] and loop again. When the index is beyond that list, we adjust it to be an index in list p2 and return from the call. Here's an approximation: