Why my Custom Characteristic always show hex value instead of Int or Text?

RE: Why my Custom Characteristic always show hex value instead of Int or Text?

Amal-Niraltek — Fri, 13 Oct 2023 07:42:23 GMT

Thanks. I did the same and also modified the code as below and it works fine as text. INT format is not available as of now i guess in definitions. I have another query and i think its better to open in another ticket. Thanks for the information.

attr_char_value.max_len = 10;
attr_char_value.init_len = 10;
char * value = "xxxxxxxxxx";
attr_char_value.p_value = value;

RE: Why my Custom Characteristic always show hex value instead of Int or Text?

tesc — Thu, 12 Oct 2023 14:21:21 GMT

Hi,

For known characteristics (such as the ones from Bluetooth SIG) the nRF Connect app knows how to format the characteristic value. For instance as a number, as text, or as binary (on/off) values.

For custom characteristics, the nRF Connect app does not know how to format the characteristic value, and defaults to showing the hex value and the corresponding ascii character. This is what you see; when using the decimal value 123, it corresponds to the hexadecimal value 0x7B, or the ascii character '{'.

If you long press on the line, in the nRF Connect app, you should get a menu where you can select "edit" for selecting how the characteristic should be formatted.

In the left hamburger menu in the nRF Connect app for Android, you will have "Definitions", which lists known services and characteristics. There you can also export or import definition files that are compatible with nRF Connect for Desktop.

Regards,
Terje

RE: Why my Custom Characteristic always show hex value instead of Int or Text?

Amal-Niraltek — Thu, 12 Oct 2023 07:25:46 GMT

And i am checking it in nrf connect android app.