Attachments (2) Download All
Nordic Case Info
  • Case ID: 323559
Options

How to add custom UUIDs definitions in nRF Connect for Mobile?

zpm1066

Hello,

In nRF Connect for Mobile, custom UUIDs show up as unknown, making it difficult to identify them easily.

Is there a way to add custom UUIDs, as can be done for example, on a Mac by adding the custom UUIDs to the "uuid_definitions.json" (located in folder /Users/username/Library/Application\ Support/nrfconnect)?

If not, How do I request an enhancement to nRF Connect for Mobile?

Thank you.

Parents
  • 0

    Hi,

    Are you using Android? If so, I just had a talk with the engineer responsible for that app. What you do is to long tap and select, and then press the edit icon.

    Regards,

    Elfving

  • 0 in reply to Elfving

    Hi Elfving,

    Thank you for your response. Sounds good. I'm on an iPhone.

    Please let me know the appropriate action is to load the custom UUIds on an iPhone.


    Regards,

    Ravi

  • 0 in reply to zpm1066

    Hi Elfving,

    I took another look at the nRF Connect for Mobile iPhone version. I can set the data parser for a Characteristic (e.g. Hex to Unsigned int) but don't see a way to import custom UUIDs. There is a file import for DFU.

    Hopefully there is a method of importing custom UUIDs, as can be done on a Mac/PC.


    Regards,
    Ravi

  • 0 in reply to zpm1066

    Unfortunately nRF Connect for Mobile for iOS does not support adding custom UUIDs as of now. 

    Though the app has no database of its own, instead it downloads the UUIDs from here. Meaning that there is one workaround. You can make a pull request with your own UUIDs, and the app will update itself with them.

    Regards,

    Elfving

Reply
  • 0 in reply to zpm1066

    Unfortunately nRF Connect for Mobile for iOS does not support adding custom UUIDs as of now. 

    Though the app has no database of its own, instead it downloads the UUIDs from here. Meaning that there is one workaround. You can make a pull request with your own UUIDs, and the app will update itself with them.

    Regards,

    Elfving

Children
  • 0 in reply to Elfving

    Hi Elfving,

    Thank you.

    How do I submit an enhancement request to the nRF Connect for Mobile team for adding custom UUIDs from a UUID definitions file? 

    Regards,
    Ravi

  • 0 in reply to zpm1066

    Letting us know here is fine Slight smile 

    I can forward the requests to the right department. When it comes to this enhancement request though, they are allready aware of it.

    Regards,

    Elfving

  • 0 in reply to Elfving

    Hi Elfving,

    Thanks. I’ll see if I can find someone who has an Android phone and try out the long tap suggestion later this morning.

    Does this allow a custom UUID definition file to be imported into Android? Appreciate if you can elaborate on the steps. 

    Regards,
    Ravi

  • 0 in reply to zpm1066

    There is unfortunately no way to export/import UUID names yet.

    Though if you know of a standard or a popular UUID, you can create a PR here. 

    Regards,

    Elfving

  • 0 in reply to Elfving

    Hi Elfving,

    Thank you for the link to the bluetooth-number-database. Perhaps there is a little disconnect from my side for the request.

    For the Thingy53, in the nRF Connect for Mobile iOS app, I'm able to view the Sensor Hub Service UUID and all the BME688 & BMI1749 standard UUIDs. These are correct and match what I see in the Mac/PC uuid_definitions.json. Sensor values are being updated correctly.

    However, what's missing in the nRF Connect for Mobile iOS are the corresponding names for the UUIDs, as available in the uuid_definitions.json.

    I managed to check the nRF Connect Mobile app on an Android phone. It has the same issue as the iOS, the UUIDs are showing up as "Unknown Characteristic".

    I'd like to have the "unknown" names in the nRF Connect for Mobile replaced by actual UUID names. The ability to import a uuid_definitions.json file, as on the Mac/PC, and have the nRF Connect app set the names.

    As discussed before, an enhancement to nRF Connect for Mobile should resolve the issue. Hopefully the nRF Connect for Mobile dev team can provide a resolution. Thank you.


    Regards,
    Ravi

Terms of service