Confirm TPMS Decoding is working

I have 4 TPMS devices sitting out on my driveway. Using MQTT Explorer I can see that there are a lot of devices detect, but not decoded. Are my TPMS devices among them?

I read a post that implied the decoders were logged as they were loaded. Where is the Decoder logging (and the logging for the Gateway for that matter). I think the problem lies with the devices and it would be nice to be able to confirm that the Decoder is not seeing them.
Thanks in advance
Gary

  1. try to figure the devices’s MAC addresses, for instance with nRF Connect/Android or the app the sensors came with
  2. set the pubadvdata flag : BLE ESP32 gateway | OpenMQTTGateway v1.7.0
  3. post some recordings from your sensors including the advertising data

I have seen 3 different advertising formats of TPMS sensors in the wild - you might have hit a fourth one

Michael

tried nRF Connect, but it didn’t detect anything. Finally managed to get one of the sensors open to check the battery, flat as a pancake. So now waiting for new batteries to arrive.

1 Like

these TPMS sensors typically have very long reporting intervals when not pressurized to save power

if you have a chance expose them to varying pressure
for instance using a pressure air pump which should make report them right away

however I observed the ones I have reply to an active scan pretty much immediately

1 Like

Well, replaced the batteries and they all work, connect to a small display that came with them and report reasonable values (first goal achieved).

However, they are not recognized by the decoder and I cant see any possibilities in the MQTT explorer output (I am assuming the first three hexadecimal pairs of the id are linked to a company in the same way MAC addresses are). I switched off the display and hoped this disconnects the sensors and then they would/should become visible in the explorer, but no change.

I think I set the pubadvdata flag but I saw no obvious change in the explorer output. I have no idea how to record data from my sensors.

I am way out of my depth now. I still haven’t found any logging generated by the gateway and/or the decoder. Even chatgpt couldn’t help!

Hi @garynl

Yes, that would be the advertising data we’d need to be able to add a decoder for any new device like your TPMS. Don’t you see any additional manufacturerdata or servicedata in the MQTT output then?? You might need to look in the history of the messages, as these might not be included with every single message.

If you never see any manufacturerdata or servicedata with pubadvdata set to true, it won’t be possible to create a decoder for it, as it likely means that the pressure can only be retrieved by connecting to your model of TPMS, also possible with the READ command of OpenMQTTGateway, but you’d need to find out first with service/characteristic you would need to read from and how the pressure might be encoded there, best investigated with the nRF Connect app for your phone.

example output with pubadvdata set:

{
    "id": "D4:15:5C:77:56:68",
    "mac_type": 1,
    "adv_type": 0,
    "name": "Ruuvi 5668",
    "manufacturerdata": "99040510604f43c42a004000140400ac56db728dd4155c775668",
    "rssi": -65,
    "brand": "Ruuvi",
    "model": "RuuviTag",
    "model_id": "RuuviTag_RAWv2",
    "type": "ACEL",
    "track": true,
    "tempc": 20.96,
    "tempf": 69.728,
    "hum": 50.7275,
    "pres": 1002.18,
    "accx": 0.062763,
    "accy": 0.019613,
    "accz": 1.004201,
    "volt": 2.978,
    "tx": 4,
    "mov": 219,
    "seq": 29325,
    "mac": "D4:15:5C:77:56:68"
}

manufacturerdata is what we need to see

Oh I see manufacturerdata and servicedata, but undecoded.

This is typical output, my mifloras, my neighbours TV and the rest unknown.

I see far fewer devices in nRF Connect, but also a couple I dont see at all in the Explorer.

Ah yes, I see something similar in the ‘value’ pane of the Explorer, but only for devices the Decoder recognises. (See my reply to DigiH).

Could you copy and paste these messages here, instead of just posting a screenshot? Makes it a lot easier for me to copy and paste then to try and create a new decoder, but glancing at all the above messages, it seems that the 8 device messages’ servicedata (two cars?) are all identical to the car/TMPS type per car, so that likely the pressure might not actually be encoded in the freely broadcast advertising data. In the actual TMPS app, do you see the same pressure for all the tires, or are they different?

Hi, sorry, I didnt think. Obviously cant give you the same data as the screenshot, but here is something similar.

There might be a 2nd set of TPMS sensors. I have a spare set (long story), but the batteries in them are > 6 years old!

(The ELK-BLEDOB is a led strip).
thanks Gary

BE6088002FFF = {“manufacturerdata”: “3132333435363738393031”, “name”: “ELK-BLEDOB”, “id”: “BE:60:88:00:2F:FF”, “rssi”: -66}

64E7D86D2949 = {“manufacturerdata”: “7500420401806e64e7d86d294966e7d86d294801b24dc7000000”, “name”: “[TV] Samsung Q700 Series (55)”, “id”: “64:E7:D8:6D:29:49”, “rssi”: -70, “mfr”: “Samsung Electronics Co. Ltd.”}

6AAB6BF7D514 = {“manufacturerdata”: “e0004466ca66469c”, “id”: “6A:AB:6B:F7:D5:14”, “rssi”: -70, “servicedatauuid”: “fe9f”, “servicedata”: “0253494d313032577162366300000192bfd4161c”, “mfr”: “Google”}

5C623BE2D18D = {“id”: “5C:62:3B:E2:D1:8D”, “rssi”: -55, “servicedatauuid”: “fe2c”, “servicedata”: “0090c2158802545182909111b3135f”}

C47C8D6710F0 = {“name”: “Flower care”, “id”: “C4:7C:8D:67:10:F0”, “rssi”: -53, “brand”: “Xiaomi/VegTrug”, “model”: “MiFlora”, “model_id”: “HHCCJCY01HHCC”, “type”: “PLANT”, “lux”: 35, “mac”: “C4:7C:8D:67:10:F0”}

C47C8D65A8A1 = {“name”: “Flower care”, “id”: “C4:7C:8D:65:A8:A1”, “rssi”: -55, “brand”: “Xiaomi/VegTrug”, “model”: “MiFlora”, “model_id”: “HHCCJCY01HHCC”, “type”: “PLANT”, “moi”: 0, “mac”: “C4:7C:8D:65:A8:A1”}

80EACA890B1B = {“name”: “Flower care”, “id”: “80:EA:CA:89:0B:1B”, “rssi”: -70, “brand”: “Xiaomi/VegTrug”, “model”: “MiFlora”, “model_id”: “HHCCJCY01HHCC”, “type”: “PLANT”, “moi”: 31, “mac”: “80:EA:CA:89:0B:1B”}

E3E28C5E7FBF = {“manufacturerdata”: “eff0e3e28c5e7fbf”, “name”: “C18”, “id”: “E3:E2:8C:5E:7F:BF”, “rssi”: -68, “servicedatauuid”: “feea”, “servicedata”: “51444203010010”}

7E3D30C57196 = {“id”: “7E:3D:30:C5:71:96”, “rssi”: -52, “servicedatauuid”: “fe2c”, “servicedata”: “0090c2158802545182909111b3135f”}

47776F3E89C8 = {“manufacturerdata”: “e0004466ca66469c”, “id”: “47:77:6F:3E:89:C8”, “rssi”: -74, “servicedatauuid”: “fe9f”, “servicedata”: “0256785f457435495f4a714d00000192bfe6659c”, “mfr”: “Google”}

5577D94AF196 = {“id”: “55:77:D9:4A:F1:96”, “rssi”: -53, “servicedatauuid”: “fe2c”, “servicedata”: “0090c2158802545182909111b3135f”}

5D0CA4F199E1 = {“manufacturerdata”: “e0004466ca66469c”, “id”: “5D:0C:A4:F1:99:E1”, “rssi”: -74, “servicedatauuid”: “fe9f”, “servicedata”: “02526a32305f72626d316f4500000192bfef8d5c”, “mfr”: “Google”}

48D4FAABBDFA = {“manufacturerdata”: “e0004466ca66469c”, “id”: “48:D4:FA:AB:BD:FA”, “rssi”: -74, “servicedatauuid”: “fe9f”, “servicedata”: “02373133676a336c43697a5500000192bff8b51c”, “mfr”: “Google”}

67B1B3A214EB = {“id”: “67:B1:B3:A2:14:EB”, “rssi”: -49, “servicedatauuid”: “fe2c”, “servicedata”: “0090c2158802545182909111b3135f”}

:arrow_forward:

All these just appeared in the list at the same time. curious,
728F956DD37F = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “72:8F:95:6D:D3:7F”, “rssi”: -52}

6DDCAF81B4E0 = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “6D:DC:AF:81:B4:E0”, “rssi”: -51}

5F15AD0AF4F3 = {“manufacturerdata”: “e8be5a94d613242424242424242424242424242424242424242424”, “id”: “5F:15:AD:0A:F4:F3”, “rssi”: -54}

526C6A68106D = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “52:6C:6A:68:10:6D”, “rssi”: -54}

6C13EFDBFF9F = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “6C:13:EF:DB:FF:9F”, “rssi”: -48}

542469C0FB6F = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “54:24:69:C0:FB:6F”, “rssi”: -51}

532E994FB286 = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “53:2E:99:4F:B2:86”, “rssi”: -50}

4D073F9AD599 = {“manufacturerdata”: “e8be5b95d712252525252525252525252525252525252525252525”, “id”: “4D:07:3F:9A:D5:99”, “rssi”: -51}

7D4A6144248C = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “7D:4A:61:44:24:8C”, “rssi”: -51}

61F11454AF33 = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “61:F1:14:54:AF:33”, “rssi”: -50}

5A0177F56C71 = {“manufacturerdata”: “e8be5997d51059202224d8d82737c8272727272727272727272727”, “id”: “5A:01:77:F5:6C:71”, “rssi”: -53}

5F92703A3A90 = {“manufacturerdata”: “e8be5c92d015222222222222222222222222222222222222222222”, “id”: “5F:92:70:3A:3A:90”, “rssi”: -55}

70E0733F5F33 = {“manufacturerdata”: “e8be5d93d1145d24262023dc2333cc232323232323232323232323”, “id”: “70:E0:73:3F:5F:33”, “rssi”: -55}

6462AAD05F58 = {“manufacturerdata”: “e8be5e90d217202020202020202020202020202020202020202020”, “id”: “64:62:AA:D0:5F:58”, “rssi”: -50}

64B81BB8ACE2 = {“manufacturerdata”: “e8be5d93d1145d24262023dc2333cc232323232323232323232323”, “id”: “64:B8:1B:B8:AC:E2”, “rssi”: -52}

528ECDECFD53 = {“manufacturerdata”: “e8be5d93d1145d24262023dc2333cc232323232323232323232323”, “id”: “52:8E:CD:EC:FD:53”, “rssi”: -51}

58CF5613F5AC = {“manufacturerdata”: “e8be5d93d1145d24262023dc2333cc232323232323232323232323”, “id”: “58:CF:56:13:F5:AC”, “rssi”: -49}

7B00CBCCDA49 = {“manufacturerdata”: “e8be5d93d1145d24262023dc2333cc232323232323232323232323”, “id”: “7B:00:CB:CC:DA:49”, “rssi”: -52}

7BF0346A49CD = {“manufacturerdata”: “e8be5d93d1145d24262023dc2333cc232323232323232323232323”, “id”: “7B:F0:34:6A:49:CD”, “rssi”: -51}

:arrow_forward:homeassis

Do you know if any of these with servicedata and/or manufacturerdata only are definitely your TPMS devices, and if so which with which MAC/id? And that they are definitely BLE TPMSs and not 433 MHz RF ones?

If this can be established by taking out the battery of one of them and reinserting itwhile monitoring the messages, then concentrating on this single one device with it’s raw data.

I bought them on AliExpress: (“Jansite TY02S TPMS” still finds them, the solar powered set), and reading the specifications again, they dont say if they are BT or RF but they do give a frequency, 433.92MHz±38KHz. I hadn’t realised they could be either.

I have never been sure if they are among the detected devices (and was surprised not to find 4 devices with similar MAC/id.

I’ll try removing a battery this evening.

thx
gary

Well I removed one of the batteries, but noticed no change in the message list in the explorer so I stopped the explorer, started it again and put the battery back in. No messages arrived immediately (apart from the LED strip), scans were set to every minute. Over the next 30mins the messages below arrived.

45886EEE171F = {“manufacturerdata”: “e0004466ca66469c”, “id”: “45:88:6E:EE:17:1F”, “rssi”: -77, “servicedatauuid”: “fe9f”, “servicedata”: “0230696570647062372d434900000192c3dea200”, “mfr”: “Google”}

75041CA9F2B0 = {“manufacturerdata”: “e0004466ca66469c”, “id”: “75:04:1C:A9:F2:B0”, “rssi”: -73, “servicedatauuid”: “fe9f”, “servicedata”: “023064785f5a48343648783400000192c3fa1940”, “mfr”: “Google”}

59A850A006B3 = {“manufacturerdata”: “e0004466ca66469c”, “id”: “59:A8:50:A0:06:B3”, “rssi”: -76, “servicedatauuid”: “fe9f”, “servicedata”: “026c475568526974356b6b6700000192c4034100”, “mfr”: “Google”}

500CE2D5451A = {“manufacturerdata”: “e0004466ca66469c”, “id”: “50:0C:E2:D5:45:1A”, “rssi”: -79, “servicedatauuid”: “fe9f”, “servicedata”: “024a44586e46764c6e75636300000192c40c68c0”, “mfr”: “Google”}

As they all have a “mfr” set to Google, I think they may have been the phones of people walking past the house. (At about 17:45 to 18:15 there was an explosion of similar messages (people walking from the bus stop?))

If you think they are RF sensors and cant be read for that reason, I dont want you to spend any more time trying to get a better answer for me, I’ll manage without the data, I have a little display showing the values!
thanks
Gary

Well, searching for the model “Jansite TY02S TPMS” you stated above, these are 433MHZ RF TPMS devices, which do have a decoder in rtl_433

[123]* Jansite TPMS Model TY02S

so they definitely won’t be able to be picked up by a Bluetooth OMG gateway with Theengs Decoder.

Even the rtl_433 port of OpenMQTTGateway rtl_433_ESP has not ported this particular decoder (yet?), possibly due to the fact that is also is disabled by default in the upstream rtl_433 for whatever reason, but can be enabled there. So any rtl_433 reception you can have, possibly with a RTL-SDR stick, will be able to pick up your Jansite TY02S TPMS.

1 Like