| Previous | Next |
| STATUS_BTH_ATT_INSUFFICIENT_AUTHENTICATION | STATUS_BTH_ATT_INVALID_OFFSET |
STATUS_BTH_ATT_REQUEST_NOT_SUPPORTED
The failure concerns the requested ATT procedure itself
STATUS_BTH_ATT_REQUEST_NOT_SUPPORTED is ATT error 0x06. It is returned when the ATT server does not support the request procedure received from the client, rather than when a specific attribute is absent or denied.
The useful question is therefore which opcode was sent and why. A client can be connected to a valid GATT server while attempting a procedure that the peer does not implement, does not expose in its current feature set, or cannot use in the current interaction path.
What to check
- Record the ATT request opcode, connection role, peer firmware version, ATT MTU, and the service or profile feature that caused the client to choose the procedure.
- Select a profile-compatible procedure after checking the peripheral's documented capabilities; do not replace the request with an unrelated attribute access as a workaround.
- Keep Request Not Supported distinct from Invalid PDU: the former identifies a syntactically recognized request that the server does not support.
References
- Bluetooth SIG: Attribute Protocol (ATT)
- Bluetooth SIG: Generic Attribute Profile (GATT)
- Microsoft: Bluetooth GATT client
Looking for a different code? Search another status or error code.