[New Sensor]: Kpro Beacon

[barkdadof4]

Sensor Description

KKM K6

Additional information

Mac address dd340206d06c kpro

Here's their iOS SDK: https://github.com/kkmhogen/kbeaconlib2
Specifically, check out this file for parsing the advertisement packet w/ temp and humidity: https://github.com/kkmhogen/kbeaconlib2/blob/df34f4bfeb80d9793e098f3e5b57382bf6a38ea4/kbeaconlib2/Classes/KBAdvPacketSensor.swift

I am not smart enough to write the python code from the above information
dump.txt
.

BLE advertisements

04 3E 24 02 01 04 01 6C D0 06 02 34 DD 18 09 16 80 20 6D 01 
  00 00 00 00 0D 09 4B 42 50 72 6F 5F 32 31 34 38 31 30 D3

[Ernst79]

0d094b4250726f5f323134383130 = name (KBPro_214810)
091680206d0100000000 = data

09 = length
16 = manufacturer specific data
8020 = UUID
6d0100000000 = data

Can you also send some new data along with the temperature and humidity at the time you took the measurement?

[barkdadof4]

New dump file Temp is 21.25 Humidity is 33.2
dump.txt
5

[barkdadof4]

Sorry pushed the wrong button

[barkdadof4]

When using Wireshark I have notice the each device sends two advertisements one with the device name and one without the device name. I think the one without the name is where the data is.

[Ernst79]

hmmm, I also found a google UUID (and length). Normally, UUID is a fixed value according to the Bluetooth specs. But this sensor seems to be sending two UUID's

Google UUID
1216aafe21010f0e07192a224ffffcffec03eb

12 = length
16 = manufacturer specific data
aafe = UUID (0xFEAA = Google LLC)
21010f0e07192a224ffffcffec03eb = data

Unknown UUID
091680206d0100000000

09 = length
16 = manufacturer specific data
8020 = UUID (not officially registered at the Bluetooth organization)
6d0100000000 = data

[Ernst79]

I'm trying to make some sense out of it, but still failing.

If I understand the link you gave correctly, we have

version 1 byte?
battery level/voltage 2 bytes
temperature 2 bytes
humidity 2 bytes
acceleration x-axis 2 bytes
acceleration y-axis 2 bytes
acceleration z-axis 2 bytes

1216AAFE 2101 0F0E 0719 3022 CBFF F5FF EF03 FB C6
1216AAFE 2101 0F0E 0719 2A22 4FFF FCFF EC03 EB D3
1216AAFE 2101 0F0E 0719 3022 CBFF F9FF E803 E9 D1

Bytes normally have to be read backwards, so 0F0E has to be read as 0x0E0F, after conversion from hex to dec, this is equal to 3599. But I can't make sense of the numbers, they don't seem to match with 2125 (0x084D) or 212 (0x00D4) for example.

In the link you gave, I don't see any conversion (integers are always numbers without digits, so normally there is some formula somewhere, e.g. temperature / 100, to get the number of digits.

[barkdadof4]

I have some other docs to share

KBeaconPro download resource link (2).pdf
K6 (1).pdf
.

This device also has the ability to advertise with different protocols.

Thanks

[Ernst79]

Thanks, following your link, I get

1216AAFE 21 01 0F 0E071930 22CB FFF9 FFE8 03E9 D1

12 = length
16= adv type manufacture specific data
AAFE = UUID (google llc)
21 = version
01 = version tag (always 01)
0F = Sensor Mask
0E07 = voltage = 3591 mV
1930 = temperature = 25.48°C
22CB = humidity = 34.203%
FFF9 = acceleration x = -7 mG
FFE8 = acceleration x = -24 mG
03E9 = acceleration z = 1001 mG
D1 = ???

Temperature is a little higher than you said, but I guess this is ok.

I will update the parser with this.

[barkdadof4]

Great thanks can you share the math used to get Temp and humidity. I seem to be missing something.

[Ernst79]

first byte is the number before the point, second byte is number after the point.

So, 1930
--> 19 in hex is 25 in dec
--> 30 in hex = 48 in dec
--> 25.48

[barkdadof4]

My bad I was not doing them individually. I was trying to convert 1930.

Again thanks for your help.