https://devzone.nordicsemi.com/f/nordic-q-a/125159/nrf-connect-shows-unknown-gatt-status-instead-of-value-not-allowedas 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&#39;s att.h , 0x0d should be &#39;invalid length&#39; and 0x13 should be &#39;value not allowed&#39;: #defineen-USTelligent Community 13Thu, 23 Oct 2025 16:52:38 GMThttps://devzone.nordicsemi.com/thread/552294?ContentTypeID=1Thu, 23 Oct 2025 16:52:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2ef78aae-4e42-4b22-a3ae-eec14dd8cc74Susheel Nuguru<p>Keith,</p> <p>0X13 and 0x113 are errors at different layers.&nbsp;nRF Connect (phoone app) displays platform “GATT status” codes.&nbsp;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).</p> <p>You can treat this as &quot;Value Not Allowed&quot; 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.</p><div style="clear:both;"></div>