Encoding FIT Serial Number from BLE Sensors

Nikeow 12 days ago

I noticed that the FITSDK expects a FITUInt32 for the serial number. However, when connecting to sensors as BLE, the Serial number can be a combination of digits and letters.

is this a known issue? Can I encode the Serial number into the FIT File?

0 muktihari 10 days ago

I don't know the best practice for this case, I'm just thinking how about encode the serial number using developer data as string format?

0 Nikeow 9 days ago in reply to muktihari

yeah that's an option but that would only be useful to either me or any sites that picks that up.

On the other hand, it seems I'm seeing a new can of worms on this. what I meant is this.

eg: I have a Polar H10

the polar documentation says that the SN is on the Pod itself

ourpolar.com/.../where-can-i-find-the-serial-number-of-my-polar-device

but when I check, the SN on the Pod is not the same as the SN returned by BLE and also not the SN returned by ANT+

I connected my Garmin to the Pod under ANT+ and BLE and both of them are different from the SN on the pod. (essentially, I am seeing 3 diff serial numbers)

The polar App on the phone, connected via BLE does show the Same SN as when I query the pod for the SN via BLE

So.....

mind blown..

0 Nikeow 9 days ago in reply to muktihari

Edit: Maybe it's not the SN It's reporting because I see it being reported as ID in the Polar App? But Garmin shows it as SN and it gets reported as SN when querying the DeviceInfo