| Previous | Next |
| E_BLUETOOTH_ATT_INVALID_ATTRIBUTE_VALUE_LENGTH | E_BLUETOOTH_ATT_INSUFFICIENT_ENCRYPTION |
E_BLUETOOTH_ATT_UNLIKELY
Unlikely Error is a server-side catch-all, not a radio diagnosis
E_BLUETOOTH_ATT_UNLIKELY represents ATT error 0x0E. The server accepted the request format and reached the target attribute but could not complete the operation for a reason that does not map cleanly to another ATT error. Peripheral applications often use it when a backend sensor, storage operation, or state transition fails unexpectedly.
Because the code intentionally lacks detail, the useful evidence is usually on the server. A client can determine the failing opcode and handle, but repeated attempts may hide the first failure or trigger side effects if the operation was only partially completed.
How to make the generic result actionable
- Correlate the ATT timestamp with peripheral firmware and application logs.
- Record the exact request value, handle, connection state, and preceding control-point operations.
- Test whether the failure depends on device mode, resource state, or a backend subsystem.
- Avoid mapping every unknown local exception to this code when a standard ATT error is available.
References
- Bluetooth Core: Unlikely Error
- Zephyr: returning ATT errors from server callbacks
- Apple Core Bluetooth: unlikelyError
Looking for a different code? Search another status or error code.