Operation aborted.
Generic allocation error.
Item already exists.
Module has already been initialized.
Bad scan duration.
Encryption/decryption operation failed.
Mismatched or insufficient security level
When this is returned in a BGAPI response, the application tried to read or write the value of a user attribute from the GATT database.
No attribute found within the given attribute handle range.
The attribute cannot be read or written using the Read Blob Request
The Client Characteristic Configuration descriptor is not configured according to the requirements of the profile or service.
The attribute requires authentication before it can be read or written.
The attribute requires authorization before it can be read or written.
The Encryption Key Size used for encrypting this link is insufficient.
The attribute requires encryption before it can be read or written.
Insufficient Resources to complete the request
The attribute value length is invalid for the operation
The attribute handle given was not valid on this server
Offset specified was past the end of the attribute
The attribute PDU was invalid
The attribute value is out of range as defined by a profile or service specification.
The server requests the client to rediscover the database.
Too many prepare writes have been queued
The profile or service request cannot be serviced because an operation that has been previously triggered is still in progress.
The attribute cannot be read
Attribute Server does not support the request received from the client.
The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested.
The attribute type is not a supported grouping attribute as defined by a higher layer specification.
The attribute parameter value was not allowed.
The attribute cannot be written
The requested write operation cannot be fulfilled for reasons other than permissions.
Error using crypto functions
The ACL Connection Already Exists error code indicates that an attempt to create a new ACL Connection to a device when there is already a connection to this device.
Advertising for a fixed duration completed or, for directed advertising, that advertising completed without a connection being created.
Pairing or authentication failed due to incorrect results in the pairing or authentication procedure. This could be due to an incorrect PIN or Link Key
The Controller cannot perform channel assessment because it is not supported.
The master, at this time, is unable to make a coarse adjustment to the piconet clock, using the supplied parameters. Instead the master will attempt to move the clock using clock dragging.
Command requested cannot be executed because the Controller is in a state where it cannot process this command at this time.
The Connection Accept Timeout has been exceeded for this connection attempt.
LL initiated a connection but the connection has failed to be established. Controller did not receive any packets from remote end.
Controller is at limit of connections it can support.
The Connection Rejected Due To Limited Resources error code indicates that an incoming connection was rejected due to limited resources.
The Controller could not calculate an appropriate value for the Channel selection operation.
The Connection Rejected Due To Security Reasons error code indicates that a connection was rejected due to security requirements not being fulfilled, like authentication or pairing.
The Connection was rejected because this device does not accept the BD_ADDR. This may be because the device will only accept connections from specific BD_ADDRs.
Local device terminated the connection.
Connection was terminated because the Message Integrity Check (MIC) failed on a received packet.
Link supervision timeout has expired.
Operation was rejected because the controller is busy and unable to process the request.
LMP transaction was started that collides with an ongoing transaction.
The requested encryption mode is not acceptable at this time.
The Host is busy with another pairing operation and unable to support the requested pairing. The receiving device should retry pairing again later.
LMP PDU or LL PDU that includes an instant cannot be performed because the instant when this would have occurred has passed.
The HCI command or LMP PDU sent is only possible on an encrypted link.
Command contained invalid parameters.
Number of operations requested has been reached and has indicated the completion of the activity (e.g., advertising or scanning).
Link key cannot be changed because a fixed unit key is being used.
LL procedure has collided with the same transaction or procedure that is already in progress.
Connection terminated due to link-layer procedure timeout.
The MAC of the 802.11 AMP was requested to connect to a peer, but the connection failed.
Controller is out of memory.
A request to the Controller issued by the Host and still pending was successfully canceled.
An attempt was made to send or receive a packet that exceeds the maximum allowed packet l
The device does not allow pairing. This can be for example, when a device only allows pairing during a certain time window after some user input allows pairing
It was not possible to pair as a unit key was requested and it is not supported.
A parameter value requested is outside the mandatory range of parameters for the given HCI command or LMP PDU.
Pairing failed because of missing PIN, or authentication failed because of missing Key
The remote device terminated the connection because of low resources
Remote Device Terminated Connection due to Power Off
User on the remote device terminated the connection.
The Controller is disallowing an authentication or pairing procedure because too little time has elapsed since the last authentication or pairing attempt failed.
The IO capabilities request or response was rejected because the sending Host does not support Secure Simple Pairing even though the receiving Link Manager does.
The Synchronous Connection Limit to a Device Exceeded error code indicates that the Controller has reached the limit to the number of synchronous connections that can be achieved to a device.
Remote device terminated the connection because of an unacceptable connection interval.
A command was sent from the Host that should identify an Advertising or Sync handle, but the Advertising or Sync handle does not exist.
Connection does not exist, or connection open request was cancelled.
No other error code specified is appropriate to use.
A feature or parameter value in the HCI command is not supported.
The remote device does not support the feature associated with the issued command.
Data was corrupted.
Hardware failure
Bluetooth cannot be used on this hardware
Invalid periodic advertising sync handle
Returned when local host did not find a connection-oriented channel with given destination CID.
Returned when connection-oriented channel has not received connection response message within maximum timeout.
Returned when connection-oriented channel disconnected due to remote end send flow control credits exceed 65535.
Returned when connection-oriented channel disconnected due to remote end send data even without credit.
Returned when local host received a connection-oriented channel connection response with an invalid destination CID.
Returned when connection-oriented channel disconnected due to LE connection is dropped.
Returned when local host disconnect the connection-oriented channel by sending disconnection request.
Returned when connection-oriented channel has run out of flow control credit and local application still trying to send data.
Returned when remote disconnects the connection-oriented channel by sending disconnection request.
Returned when local host application tries to send a command which is not suitable for L2CAP channel's current state.
Returned when trying to assign an address that is used by one of the devices in the Device Database, or by the Provisioner itself.
Returned when trying to reuse an address of a previously deleted device before an IV Index Update has been executed.
Returned when trying to add a key or some other unique resource with an ID which already exists
An attempt was made to initialize a subsystem that was already initialized.
Application key is not bound to a model
Returned when trying to manipulate a key or some other resource with an ID which does not exist
Returned when the requested bind operation cannot be performed due to general constraints
Returned when the requested delete operation cannot be performed due to general constraints
Returned when the requested state cannot be set
Returned when the requested update operation cannot be performed due to general constraints
Returned when The node cannot serve the request due to insufficient resources
Returned when address in request was not valid
Returned when the key identified by AppKeyIndex is not stored in the node
Returned when the NetKeyIndex and AppKeyIndex combination is not valid for a Config AppKey Update
Returned when model identified is not found for a given element
Returned when the key identified by NetKeyIndex is not stored in the node
Returned when the model does not support the publish mechanism
Returned when the key identified is already stored in the node and the new NetKey value is different
Returned when the model does not support the subscribe mechanism
Returned when requested setting is not supported
Returned when storing of the requested parameters failed
Returned when The node cannot start advertising with Node Identity or Proxy since the maximum number of parallel advertising is reached
Returned when an unspecified error took place
Returned when trying to use a reserved address or add a "pre-provisioned" device using an address already used by some other device
Returned when an operation cannot be executed because a pre-configured limit for keys, key bindings, elements, models, virtual addresses, provisioned devices, or provisioning sessions is reached
In a BGAPI response, the user supplied malformed data; in a BGAPI event, the remote end responded with malformed or unrecognized data
Returned when trying to establish a friendship as a Low Power Node, but no acceptable friend offer message was received.
An attempt was made to use a subsystem that wasn't initialized yet. Call the subsystem's init function first.
Device could not assign unicast addresses to all of its elements.
The computed confirmation value did not match the expected value.
The provisioning data block could not be decrypted.
An unrecognized provisioning PDU was received.
A provisioning PDU with wrong length or containing field values that are out of bounds was received.
Provisioning link was unexpectedly closed before provisioning was complete.
Provisioning could not be continued due to insufficient resources.
An unexpected error happened during provisioning.
An unexpected (out of sequence) provisioning PDU was received.
Application key or publish address are not set
The bonding does not exist.
Bonding procedure can't be started because device has no space left for bond.
PS key not found
Flash reserved for PS store is full
Error received from radio
The pairing procedure cannot be performed as authentication requirements cannot be met due to IO capabilities of one or both devices
Indicates that the pairing over the LE transport failed due to a Pairing Request sent over the BR/EDR transport in process.
The SMP command received is not supported on this device
The confirm value does not match the calculated compare value
Indicates that the BR/EDR Link Key generated on the BR/EDR transport cannot be used to derive and distribute keys for the LE transport.
Indicates to the remote device that the DHKey Check value received doesn't match the one calculated by the local device.
The resultant encryption key size is insufficient for the security requirements of this device
The Invalid Parameters error code indicates: the command length is invalid or a parameter is outside of the specified range.
Indicates that the device chose not to accept a distributed key.
Indicates that the confirm values in the numeric comparison protocol do not match.
Out of Band data is not available for authentication
Pairing is not supported by the device
The user input of passkey failed, for example, the user cancelled the operation
Pairing or authentication procedure is disallowed because too little time has elapsed since last pairing request or security request
Pairing failed due to an unspecified reason
Unspecified error
Bus error, e.g. invalid DMA address
Module is busy and cannot carry out requested operation.
CCA failure.
Error in open NVM
Data received does not form a complete command
Command was not recognized
Command or parameter maximum length exceeded
ALU operation output NaN
ALU numeric overflow
ALU numeric underflow
Critical fault
Infinity encountered during array store conversion
NaN encountered during array store conversion
Overflow during array store
Underflow during array store conversion
MATH Infinity encountered
MATH NaN encountered
MATH numeric overflow
MATH numeric underflow
Object/construct has been deleted.
EEPROM MFG version mismatch.
EEPROM Stack version mismatch.
Item/list/queue is empty.
Generic error.
Flash erase failed.
Flash programming failed.
Flash verification failed.
Flash write is inhibited.
Item/list/queue is full.
Item/list/queue has been overflowed.
Operation/module is Idle, cannot carry requested operation.
Operation is in progress and not yet complete (pass or fail).
Initialization failed.
Invalid channel mask.
Invalid configuration provided.
Invalid count.
Invalid credentials.
Invalid handle.
Invalid index.
Invalid key.
Invalid mode.
Generic invalid argument or consequence of invalid argument.
Invalid range.
Invalid signature / verification failed.
Generic invalid state error.
Invalid type for operation.
Generic I/O failure.
I/O failure due to timeout.
Already/still owning resource.
Operation cannot be done while construct is waiting.
Illegal call from ISR.
MAC ACK unknown header type.
MAC command transmit failure.
MAC incorrect scan type.
MAC indirect timeout.
MAC no ACK received.
MAC no data.
MAC scanning.
The MAC transmit queue is full
MAC unknown header type.
Message is too long.
Illegal call because network is down.
Illegal call because network is up.
Invalid operation as there are no beacons.
No more resource available to perform the operation.
No task/construct waiting/pending for that action/event.
Feature not available due to software configuration.
Item could not be found.
Module has not been initialized.
Failure due to not being joined in a network.
Module is not ready for requested operation.
Feature not supported.
Invalid null pointer received as argument.
The initialization was aborted as the NVM3 instance is not aligned properly in memory
The initialization was aborted as the NVM3 instance was already opened with other parameters
The initialization was aborted as the NVM3 page size is not supported
The initialization was aborted as the size of the NVM3 instance is too small
The application that there was an error initializing some of the tokens
Failed to read on/via given object.
Failed to write on/via given object.
No error.
Generic ownership error.
Operation not allowed per permissions.
Generic reception error.
Decryption failed
Image checksum is not valid.
Operation cannot be done while construct is suspended.
Operation timed out.
Generic transmission error.
The expected ACK was received after the last transmission
The transmit attempt was blocked from going over the air. Typically this is due to the Radio Hold Off (RHO) or Coexistence plugins as they can prevent transmits based on external signals.
Transmit is busy.
Transmit is incomplete.
An unsupported channel setting was specified
An unsupported power setting was specified
The transmit attempt failed because the radio scheduler could not find a slot to transmit this packet in or a higher priority event interrupted it
Transmit underflowed.
The request failed due to regulatory limitations
The connection request was aborted by host
The connection request failed because the WPA handshake did not complete successfully
The connection request failed because the AP rejected the device
The connection request failed because of a timeout
The firmware download took too long
Invalid firmware keyset
The connection request failed because no suitable AP was found
No Packets waiting to be received
The request failed because the retry limit was exceeded
SecureLink key (re)negotiation failed
The SecureLink MAC key installation failed
The SecureLink MAC key is already installed in OTP
The SecureLink MAC key was not found
The SecureLink MAC key cannot be installed in RAM
The sleep mode is granted
The WFx does not go back to sleep
The request failed because the MSDU life time was exceeded
Unknown request ID or wrong interface ID used
The request is successful but some parameters have been ignored
The device is in an inappropriate state to perform the request
Non-blocking operation would block.
Item would overflow.
The application is trying to overwrite an address table entry that is in use
An error occurred when trying to encrypt at the APS Level
The application tried to use a binding that has been remotely modified and the change has not yet been reported to the application
The application is trying to delete or overwrite a binding that is in use
The channel has changed.
The APS layer attempted to send or deliver a message and failed
A Zigbee EZSP error has occured. Track the origin and corresponding EzspStatus for more info.
An error occurred when trying to encrypt at the APS Level
An attempt to generate random bytes failed because of insufficient random data from the radio
The chosen security level is not supported by the stack
The message could not be sent because the link key corresponding to the destination is not authorized for use in APS data messages
A Zigbee route error command frame was received indicating that a message sent to this node along a many-to-one route failed en route
The maximum number of in-flight messages ::EMBER_APS_UNICAST_MESSAGE_COUNT has been reached
After moving, a mobile node's attempt to re-establish contact with the network failed
The network has been closed for joining.
The network has been opened for joining.
After a device joined a Secured Network, a Link Key was requested (::EMBER_GET_LINK_KEY_WHEN_JOINING) but no response was ever received.
An attempt was made to join a Secured Network, but the device did not receive a Network Key.
The local node ID has changed. The application can get the new node ID by calling ::sl_zigbee_get_node_id()
Packet is dropped by packet-handoff callbacks
The local PAN ID has changed. The application can get the new PAN ID by calling ::emberGetPanId()
An attempt was made to join a Secured Network without a pre-configured key, but the Trust Center sent encrypted data using a pre-configured key.
An attempt was made to join a Secured Network using a pre-configured key, but the Trust Center sent back a Network Key in-the-clear when an encrypted Network Key was required. (::EMBER_REQUIRE_ENCRYPTED_KEY)
There was an attempt to form or join a network with security without calling ::sl_zigbee_set_initial_security_state() first
The received signature corresponding to the message that was passed to the CBKE Library failed verification and is not valid
A Zigbee route error command frame was received indicating that a source routed message from this node failed en route
A critical and fatal error indicating that the version of the stack trying to run does not match with the chip it's running on
There was an attempt to broadcast a key switch too quickly after broadcasting the next network key. The Trust Center must wait at least a period equal to the broadcast timeout so that all routers have a chance to receive the broadcast of the new network key
The EUI of the Trust center has changed due to a successful rejoin after TC Swapout
A Trust Center Swapout Rejoin has occurred without the EUI of the TC changing
Status Codes contains error and status code definitions used by Simplicity SDK software components and stacks.