nrf Connect shows 'unknown Gatt status' instead of 'Value not allowed'

[kruenheck]

as shown in this document:

https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-54/out/en/host/attribute-protocol--att-.html and Zephyr's att.h, 0x0d should be 'invalid length' and 0x13 should be 'value not allowed':

#define BT_ATT_ERR_INVALID_ATTRIBUTE_LEN    0x0d

#define BT_ATT_ERR_UNLIKELY         0x0e

#define BT_ATT_ERR_INSUFFICIENT_ENCRYPTION  0x0f

#define BT_ATT_ERR_UNSUPPORTED_GROUP_TYPE   0x10

#define BT_ATT_ERR_INSUFFICIENT_RESOURCES   0x11

#define BT_ATT_ERR_DB_OUT_OF_SYNC       0x12

#define BT_ATT_ERR_VALUE_NOT_ALLOWED        0x13

while nrfConnect correctly identifies 0x0d, it shows 'unknown GATT service' for 0x13 (see image)

 

Thank you

[Susheel Nuguru]

Keith,

0X13 and 0x113 are errors at different layers. nRF Connect (phoone app) displays platform “GATT status” codes. OS normally reports many ATT errors as 0x0100 | att_code. So 0x0113 appears. It looks like the app did not label the 0x113 to any specific mapping yet, so it prints the default “Unknown GATT status (0x0113).

You can treat this as "Value Not Allowed" and if you use want to be sure, you can sniff the air packets to see if we are doing and assuming the right things.