Support for Bluetooth low energy TPMS

[psoukal-nonms]

Could you kindly look to support BLE (Bluetooth 5 low energy) tyre pressure devices. They use 8 digit hexadecimal identifiers and are normally paired over Bluetooth rather than by scanning a QR code and are paired one by one.

Here are 2 sample IDs, note they aren’t ordered 1,2,3,4 like those already supported.

FD2F46B2 95365F44

Thanks!

[VincentMasselis]

Hello and thanks for submitting and issue !

Could you provide me a link where I can show which kind of sensor you're talking about ? I've 2 packs a sensors which uses BLE 5 and both of them are working correctly with TPMS Advanced.

[psoukal-nonms]

Bluetooth 5.0 2/3/4 TPMS Sensors Motorcycle Car Tire Pressure Monitoring System 0-100PSI Tyre https://a.aliexpress.com/_mLq6ziA

Regards, Peter

On Mon, 28 Aug 2023 at 8:14 PM, Vincent Masselis @.***> wrote:

Hello and thanks for submitting and issue !

Could you provide me a link where I can show which kind of sensor you're talking about ? I've 2 packs a sensors which uses BLE 5 and both of them are working correctly with TPMS Advanced.

— Reply to this email directly, view it on GitHub https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1695243068, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWA6QBIE5PFEJJEQ5X2W6JDXXRHOPANCNFSM6AAAAAA377WTOY . You are receiving this because you authored the thread.Message ID: @.***>

[VincentMasselis]

It's strange, theses sensors looks exactly the same than the one I already own.

I need some additional information to understand what are the returned data by theses sensors, could you install the app nRF Connect, open it, click on the button "Scan" in the top right corner and search for your sensor in the list.

Then, click on the button Raw in the sensor's cell:

Then, click on the Copy icon in the top right corner of the dialog, It will copy into your phone clipboard the current data returned by your sensor:

Once copied, paste the data here, in this issue, I will analyse if this data is something I know or something new for the app. The best thing to do is copy/paste a returned data for each of your sensor, It will help me.

Regards

[psoukal-nonms]

Here’s the data you requested. I think these are from two of my TPMS.

Let me know what you find.

Regards, Peter

On Thu, 31 Aug 2023 at 8:00 PM, Vincent Masselis @.***> wrote:

It's strange, theses sensors looks exactly the same than the one I already own.

I need some additional information to understand what are the returned data by theses sensors, could you install the app nRF Connect https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en&gl=US, open it, click on the button "Scan" in the top right corner and search for your sensor in the list.

Then, click on the button Raw in the sensor's cell: [image: Screenshot_20230831-091802] https://user-images.githubusercontent.com/6769250/264575541-ee6b6206-6513-40ba-96c3-427b2aa3c3e6.png

Then, click on the Copy icon in the top right corner of the dialog, It will copy into your phone clipboard the current data returned by your sensor: [image: Screenshot_20230831-091811] https://user-images.githubusercontent.com/6769250/264575700-5c133c25-aa74-4fdc-8631-ea18093a5281.png

Once copied, paste the data here, in this issue, I will analyse if this data is something I know or something new for the app. The best thing to do is copy/paste a returned data for each of your sensor, It will help me.

Regards

— Reply to this email directly, view it on GitHub https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1700551486, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWA6QBOQ6CK2J7T7MPEJHLLXYBABFANCNFSM6AAAAAA377WTOY . You are receiving this because you authored the thread.Message ID: @.***>

[VincentMasselis]

Unfortunately I can't see any data in your response. Could you consider using the github website directly instead of using mails please ?

[psoukal-nonms]

Here's the data froimages, apologies they didn't come through to you.

DC:A5:73:92:8D:DB NOT BONDED CONNECT 7-106 dBm # 2005 ms Device type: UNKNOWN Advertising type: Legacy Flags: GeneralDiscoverable, BrEdrNotSupported Complete list of 16-bit Service UUIDs: OxFEED Service Data: UUID: OxFEED Data: Ox0200E14CEA12AE41634C

DC:A5:73:92:8D:DB NOT BONDED CONNECT 7-106 dBm # 2005 ms Device type: UNKNOWN Advertising type: Legacy Flags: GeneralDiscoverable, BrEdrNotSupported Complete list of 16-bit Service UUIDs: OxFEED Service Data: UUID: OxFEED Data: Ox0200E14CEA12AE41634C

Regards, Peter

On Tue, 5 Sep 2023 at 1:10 AM, Vincent Masselis @.***> wrote:

Unfortunately I can't see any data in your response. Could you consider using the github website directly instead of using mails please ?

— Reply to this email directly, view it on GitHub https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1705249864, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWA6QBKQ5YEUDVQVYV3B42TXYXHNFANCNFSM6AAAAAA377WTOY . You are receiving this because you authored the thread.Message ID: @.***>

[VincentMasselis]

Theses data are unusual, TPMS Advanced used to parse a bloc of 15 bytes while your sample is 10 bytes only. On the "official" app SYTPMS, which data do you have ? Does temperature, pressure and battery are displayed ? Does the device has a name or N/A is displayed ?

Since the byte array length's is different and the service uuids uses a different key, I think your sensor works with a new format (or an old format) that I've nerver seen.

[psoukal-nonms]

This is an example of the data I see in the app:

2.6Bar 15.0°C 2.9V

Regards, Peter

On Tue, 5 Sep 2023 at 9:21 PM, Vincent Masselis @.***> wrote:

Theses data are unusual, TPMS Advanced used to parse a bloc of 15 bytes while your sample is 10 bytes only. On the "official" app SYTPMS, which data do you have ? Does temperature, pressure and battery are displayed ?

Since the byte array length's is different and the service uuids uses a different key, I think your sensor works with a new format (or an old format) that I've nerver seen.

— Reply to this email directly, view it on GitHub https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1706254270, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWA6QBNH3WF7GSTCO2MQOB3XY3VJ7ANCNFSM6AAAAAA377WTOY . You are receiving this because you authored the thread.Message ID: @.***>

[aetha]

I'm having the same issue with mine, these ones: https://www.aliexpress.com/item/1005005286360131.html

They work in SYTPMS, (but not TPMSII)

nRF Connect gave me this info

Copied raw data for each:

0x0303A5270308425208FF801E1301BE9720
0x0303A5270308425208FF201C1101992FEB

[VincentMasselis]

Hello @aetha and thanks for you contribution !

Fortunately I bought one of theses sensors 1 month ago (those with a sticker containing 2 hexa chars on the top and the location on the bottom). I'm still reverse engineering them in order to understand which kind of data is sent through theses sensor. The compatibility with theses sensors is my next feature :)

[VincentMasselis]

Good news, I'm working to manage the sensors both of you are currently using. Theses sensors manufacturer by Pecham are not working like Sysgration does, tyre location is not returned but the sensor itself, it's up to the user to tell where the sensor is located. This said, I'm currently working on a new screen to pair the Pecham sensor in an easy and natural way.

I've a quick question for you @aetha and @psoukal-nonms, to make my sensors visible I must plug it to a pressured wheel AND the wheel must be spinning, do your sensors are only visible in theses conditions like me ? How did you pair yours when using the """official""" app ?

[psoukal-nonms]

That’s good news. When do you expect the app to be in the play store?

The sytmps app has you pair an individual sensor at a time.

By screwing in the sensor into a tyre stem it allows it to be pair. If it’s already on the tyre I unscrew and rescrew it so it becomes pressurised. The wheel does not need to be spinning to pair.

Does this make sense?

Regards, Peter

On Wed, 13 Dec 2023 at 4:54 AM, Vincent Masselis @.***> wrote:

Good news, I'm working to manage the sensors both of you are currently using. Theses sensors manufacturer by Pecham are not working like Sysgration does, tyre location is not returned but the sensor itself, it's up to the user to tell where the sensor is located. This said, I'm currently working an a new screen to pair the Pecham sensor is a easy and natural way.

I've a quick question for you @aetha https://github.com/aetha and @psoukal-nonms https://github.com/psoukal-nonms, to make my sensors visible when attached to a pressured way AND the wheel must be spinning, do your sensors are only visible in this conditions like me ? How did you pair yours when using the """official""" app ?

— Reply to this email directly, view it on GitHub https://github.com/VincentMasselis/TPMS-advanced/issues/21#issuecomment-1852317133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWA6QBOUPS5JJJNVOBVG5DDYJB43BAVCNFSM6AAAAAA377WTO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGMYTOMJTGM . You are receiving this because you were mentioned.Message ID: @.***>

[aetha]

My experience has been the same as @psoukal-nonms, unscrewing & then re-tightening them to cause a pressure fluctuation, forces them to wake up. No need to move the wheels to pair.

[VincentMasselis]

Thanks both of you, I'm working on an user experience which match this technical behavior in order to make it as best as possible.

[VincentMasselis]

Hey ! I just pushed a release which include a support for the Pecham sensors into the beta channel of the Play Store. If you want to try this new version, follow this link to become a beta tester.