• Replies 14 replies
  • Subscribers 19 subscribers
  • Views 764 views
  • Users 0 members are here
Options
Related

Unique

DaveBrillhart

I need a way for any data field running on a device to be able to generate the same "unique" ID for that device. I know there is a "uniqueIdentifier" method, but that is only unique for a particular app. So 2 different data fields running on that same device will generate two different values.

One way would be to get the serial number for an attached power meter. In my use case, for the fields we create there will always be a power meter. So that would work. The ANT ID isn't visible to CIQ, but this suggests the serial number should be. I get this error. Any ideas? Or if this isn't available to data fields, is there another way? I need to support devices from API 2.4 and up.

  • I found a way to get a unique value - the Device ID sent in the onMessage payload. This should work for our needs. This isn't the ANT ID, but we don't need that, just a unique number.

    Garmin Rally Dual (ROAD BIKE)
    8:52:02 POWER DEVICE NUMBER: 809893

    Garmin Rally Single (MOUNTAIN BIKE)
    8:53:42 POWER DEVICE NUMBER: 115972

    4iiii (GRAVEL BIKE)
    8:57:23 POWER DEVICE NUMBER: 28510

    Wahoo KICKR Core 2 (INDOOR TRAINER)
    9:02:55 POWER DEVICE NUMBER: 49005

  • in reply to the-ninth

    uniqueIdentifier is different for every app. my client has a bunch of data fields, and we're prefer to limit the number of "keys" used to authenticate a user to one or a small set, rather than every app have its own. since power meters are used by all these apps, the Device ID for the user's power meter(s) would allow for this.

  • in reply to DaveBrillhart
    DaveBrillhart said:
    uniqueIdentifier is different for every app. my client has a bunch of data fields, and we're prefer to limit the number of "keys" used to authenticate a user to one or a small set, rather than every app have its own. since power meters are used by all these apps, the Device ID for the user's power meter(s) would allow for this.

    I understand, but I was referring to what you called the unique random registration string that you store locally. If you already have found your ID in the power meter, then the point is moot anyway.

  • in reply to the-ninth

    Oh yeah got it! I actually didn't know about "uniqueIdentifier" when I generated my own random string in the current implementation.