| Previous | Next |
| E_BLUETOOTH_ATT_INSUFFICIENT_AUTHENTICATION | E_BLUETOOTH_ATT_INVALID_OFFSET |
E_BLUETOOTH_ATT_REQUEST_NOT_SUPPORTED
The requested ATT procedure is outside the server capability
E_BLUETOOTH_ATT_REQUEST_NOT_SUPPORTED carries ATT error 0x06. It is returned for a recognized request that the server does not support, rather than for an unknown attribute or malformed PDU. An older stack may omit an optional procedure, or a constrained peripheral may implement only the subset required by its profile.
Fallback must preserve semantics. Replacing Read Multiple Variable with separate reads can be valid, while replacing a reliable queued write with independent writes can break atomicity. The client should select an alternative only when the profile and data consistency requirements allow it.
Useful compatibility checks
- Identify the exact ATT opcode rejected by the server.
- Check whether the procedure is mandatory for the claimed Bluetooth and profile version.
- Use a simpler standardized procedure only when it produces equivalent results.
- Avoid treating the error as transient; firmware support normally does not appear after retrying.
References
- Bluetooth Core: request and response procedure support
- Zephyr: ATT request support and error codes
- Microsoft: Bluetooth COM error codes
Looking for a different code? Search another status or error code.