Github Devices Community Docs Blog

How to help to integrate/support new BLE child themometer

Hi there community and developers.
Firs of all GREAT DIY solution.
I am using it from several weeks, (have my attention from second release)
I want to ask you , how could I help to integrate new (not in compatible sheet) device - an XIAOMI CHILD THERMOMETHER.
The device is BLE enabled and I can see true MQTT that it is discovered and some data are read from it, but does now how/have any idea how to proceed forwards.
I am able to send/post all data read from the device or any other info from it if you need it .
My idea for it is that if my child have high temperature (lets say in the middle of the night) true OMG and HASS the lights to be switched on.
Bit again I cannot read/decode the data.
Point of directions to start ??
P.S. Am I writing in the correct sub-forum/topic?

Here is the MQTT message send to the server

Thanks in the name of all the contributors :slightly_smiling_face:

Yes perfect

The idea is to note the service data and the sensors values in the mean time. Once done of at least 5 different values, you try to find the changing part of the service data. Usually it is by set of 4 bytes. By converting the 4 bytes (reversed 2 by 2) you can convert it to decimal and see if you fall back on your feets.
Once done you can post the results and I will continue the guidance.

Great, I will gether the data later tonight.
Not sure will I be able to log the data presented in the stock reading app with those from the OMG simultaneously but I will try.

Unfortunately I was unable to log simultaneously the data from the mi home app (miaomioace app) and the OMG ble data.
But I logged only ble data when not connected to phone/app
The range should be between 35.50-36.00 degrees Celsius.
Here is the data:

Now you can extract the service data on a spreadsheet or text editor, align them and check the changing parts.
When you determine the changing parts try to convert it to decimal by group of 2.
Example if you see : ad3c on service data.

You can try to convert 3cad in decimal (15533 ) and see if with some division it corresponds to a sensor value you ve retrieved.

Something like that?
7122 db00 2fb1 ade8 2291 b005 0023 0562 0c9c 0b1d
7122 db00 4ab1 ade8 2291 b005 0023 059e 0c1d 0c1d
7122 db00 63b1 ade8 2291 b005 0023 05c7 0c6b 0c1d
7122 db00 7eb1 ade8 2291 b005 0023 05ea 0c9e 0c1d
7122 db00 9fb1 ade8 2291 b005 0023 052e 0dfc 0c1d
7122 db00 07b1 ade8 2291 b005 0023 056a 0d63 0d1d
7122 db00 37b1 ade8 2291 b005 0023 056d 0d3b 0d1d
The bold ones are the only close to a real reading. Maybe some conversions in place.

1 Like

Yes like that, now reverse them 2 by 2 and you can try to convert it to decimal.

Unfortunately is not “reversing” successfully .
I will continue testing and I hope I get it.
Some other advice from you?

And if you take:
7122 db00 2fb1 ade8 2291 b005 0023 0562 0c9c 0b1d -> 3170
instead of :
7122 db00 2fb1 ade8 2291 b005 0023 0562 0c9c 0b1d
is ti more corresponding to real values?