I’m currently traveling and won’t be back to have a proper look a this until early next week.
In the meantime can you see if there are any useful BLE advertising braodcasts, and if they changes in manufacturerdata or servicedata with the wind speed - best to test with a constant fan or similar.
Did some decoding ,
Wind speed reading on the gauge jumps a lot, could not register the reading on time.
but i think i got the reading
packet: aabb1005372020302e30304d2f533430800462
is formated like that:
aabb10053720 20302e3030 4d2f533 43 08 00462
first is constant aabb10053720
second is reading (hex to text) 20302e3030 → 0,00
third is unit (hex to text) 4d2f533 → M/S
fourth 43 → C …maybe a temperature unit
fifth 08 and 00 when battery full , 0c when battery low
I don’t understand the last one.
{
"id": "E8:D0:3C:51:8D:D3",
"mac_type": 0,
"adv_type": 0,
"name": "UT363BT",
"manufacturerdata": "aabb1005372020302e30304d2f533430800462",
"rssi": -73
}
aabb10053720 20322e3130 4d2f533 430800465 1,9 wind speed m/s 21,1 temp C
aabb10053720 20322e3638 4d2f533 430800472 2,5 21,0
aabb10053720 20322e3638 4d2f533 430800472 2,5 20,9
aabb10053720 20322e3333 4d2f533 43080046a 2,3 20,8
aabb10053720 20312e3938 4d2f533 430800474 1,8 20,9
aabb10053720 20312e3837 4d2f533 430800472 1,8 20,8
aabb10053720 20312e3430 4d2f533 430800467 1,4 20,9
aabb10053720 20302e3830 4d2f533 43080046a 1,0 20,9
aabb10053720 20312e3532 4d2f533 43080046a 1,5 20,9
aabb10053720 20312e3035 4d2f533 430800468 1,0 20,9
aabb10053720 20322e3333 4d2f533 43080046a 2,6 20,9
aabb10053720 20332e3033 4d2f533 430800468 2,9 20,9
aabb10053720 20332e3935 4d2f533 430800473 3,9 20,6
aabb10053720 20342e3330 4d2f533 430800469 4,1 20,7
aabb10053720 20342e3635 4d2f533 430800471 4,5 20,7
aabb10053720 20342e3838 4d2f533 430800476 5,0 20,8
aabb10053720 20342e3737 4d2f533 430800474 4,8 20,8
aabb10053720 20352e3635 4d2f533 430800472 5,6 20,8
aabb10053720 20392e3334 4d2f533 430800472 9,0 21,0
aabb10053720 20362e3538 4d2f533 430800475 6,5 21,1
aabb10053720 20352e3739 4d2f533 430800477 5,7 21,1
aabb10053720 20392e3437 4d2f533 430800476 9,5 21,2
aabb10053720 31302e3237 4d2f533 43080047c 10, 21,2
aabb10053720 20312e3837 4d2f533 430800472 1,8 19,2
aabb10053720 20312e3837 4d2f533 430800472 1, 20,0
aabb10053720 20312e3735 4d2f533 43080046f 1, 20,2
aabb10053720 20312e3735 4d2f533 43080046f 1,7 20,4
aabb10053720 20362e3035 4d2f533 430c004ad 5, 21,8 3,3v
aabb10053720 20352e3030 4d2f533 430c004a7 5, 21,7 2,9v
aabb10053720 20352e3236 4d2f533 430c004af 5,2 21,6 2,9v
aabb10053720 20352e3236 4d2f533 430c004af 5, 21,4 2,7v
aabb10053720 20352e3739 4d2f533 430c004b7 5, 21,2 2,7v
aabb10053720 20352e3030 4d2f533 430c0 04a7 5,0 21,2 2,7v
aabb10053720 20352e3030 4d2f533 43 08 00467 5,0 20,7 3,4v
aabb10053720 20342e3838 4d2f533 43 08 00476
aabb10053720 20342e3838 4d2f533 43 0c 004b6 4,8 20,7 temp C 3,3v
aabb10053720 20342e3838 4d2f533 43 0c 004b6
aabb10053720 20352e3030 4d2f533 43 0c 004a7
aabb10053720 20342e3737 4d2f533 43 08 00474 4,0 8,5 temp C
aabb10053720 20342e3432 4d2f533 43 08 0046c
aabb10053720 20342e3838 4d2f533 43 08 00476 4,8 11,8 temp C 4,8v
aabb10053720 20312e3131 4d2f533 43 00 203e7
aabb10053720 20312e3134 4d2f533 43 00 203ea
aabb10053720 20312e3239 4d2f533 43 00 803f6
aabb10053720 20312e3430 4d2f533 43 00 803ef
aabb10053720 20312e3430 4d2f533 43 00 803ef
aabb10053720 20312e3239 4d2f533 43 00 003ee
aabb10053720 20312e3239 4d2f533 43 00 003ee
aabb10053720 20302e3030 4d2f533 43 00 203e4
aabb10053720 20312e3934 4d2f533 43 00 203f2
Nice decoding work! HEX to TEXT, ok for the M/S I suppose, but for encoding the actual speed number, that’s a new one. We’ll have to see if and what issues that might cause further down the controller line.
Just a few amendments
first is constant aabb10053720
second is reading (hex to text) 20302e3030 → 0,00
I think the last 20 octet from the fist chunk belongs to the beginning of the second, as an additional leading space, to allow for 3 digit values
aabb100537 2020312e3532 4d2f533 43080046a
20 20 31 2E 35 32 = _ _1.52
third is unit (hex to text) 4d2f533 → M/S
octet bytes should not be split up, so the trailing single 3 at the end here can go, as the three octets 4d 2f 53 are enough to have M/S encoded in them.
So the manufacturerdata split up will be
aabb100537 2020322e3638 4d2f53 3430800472
Could you cycle through the different units the device allows for and post some sample messages. Then we will see which additional octets might be required for longer unit text, and which will remain to dig more into the temperature and possible battery level/voltage?
I changed the unit on the device, but the data is still sent in m/s, one number changes in the package with unit change
all samples : wind 1.4 temp 20
I think that temperature is not sent
aabb1005372020312e35324d2f533 4 300003ea unit m/s and temp C
aabb1005372020312e35324d2f533 4 300003ea unit m/s and temp F
aabb1005372020312e34304d2f533 5 300003e8 unit km/s and temp C
aabb1005372020312e35324d2f533 6 300003ec unit ft/min and temp C
aabb1005372020312e35324d2f533 7 300003ed unit knots and temp C
aabb1005372020312e34304d2f533 8 300003eb unit mph and temp C
aabb1005372020312e34304d2f533 8 300003eb unit mph and temp F
aabb1005372020312e34304d2f533 4 300003e7 unit m/s and temp C
Correctly reformatted with the octets, this is
aabb100537 2020312e3532 4d2f53 34 300003ea unit m/s and temp C
aabb100537 2020312e3532 4d2f53 34 300003ea unit m/s and temp F
aabb100537 2020312e3430 4d2f53 35 300003e8 unit km/s and temp C
aabb100537 2020312e3532 4d2f53 36 300003ec unit ft/min and temp C
aabb100537 2020312e3532 4d2f53 37 300003ed unit knots and temp C
aabb100537 2020312e3430 4d2f53 38 300003eb unit mph and temp C
aabb100537 2020312e3430 4d2f53 38 300003eb unit mph and temp F
aabb100537 2020312e3430 4d2f53 34 300003e7 unit m/s and temp C
with the octet after the 4d2f53 - M/S indicating which wind speed unit is selected on the device itself, even if the actual speed is always broadcasts in m/s:
34 - m/s
35 - km/s
36 - ft/min
37 - knots
38 - mph
Not sure if this would actually be relevant to include4 in a decoder, as the broadcast m/s can then always be auto-converted in any controller.
If the remaining changing last two octets have any decoding relevance is unsure, as they con’t seem to be indicating the steady temperature, nor any up and down battery level.
It seems that the unit is not important because wind speed is always sent in m/s. rather confusing
how can i install this to openmqtt gateway on esp32?
It is included in the development version of OpenMQTTGateway