zigbee-herdsman
Version:
An open source ZigBee gateway solution with node.js.
952 lines • 104 kB
TypeScript
/** Status Defines */
export declare enum SLStatus {
/** No error. */
OK = 0,
/** Generic error. */
FAIL = 1,
/** Generic invalid state error. */
INVALID_STATE = 2,
/** Module is not ready for requested operation. */
NOT_READY = 3,
/** Module is busy and cannot carry out requested operation. */
BUSY = 4,
/** Operation is in progress and not yet complete (pass or fail). */
IN_PROGRESS = 5,
/** Operation aborted. */
ABORT = 6,
/** Operation timed out. */
TIMEOUT = 7,
/** Operation not allowed per permissions. */
PERMISSION = 8,
/** Non-blocking operation would block. */
WOULD_BLOCK = 9,
/** Operation/module is Idle, cannot carry requested operation. */
IDLE = 10,
/** Operation cannot be done while construct is waiting. */
IS_WAITING = 11,
/** No task/construct waiting/pending for that action/event. */
NONE_WAITING = 12,
/** Operation cannot be done while construct is suspended. */
SUSPENDED = 13,
/** Feature not available due to software configuration. */
NOT_AVAILABLE = 14,
/** Feature not supported. */
NOT_SUPPORTED = 15,
/** Initialization failed. */
INITIALIZATION = 16,
/** Module has not been initialized. */
NOT_INITIALIZED = 17,
/** Module has already been initialized. */
ALREADY_INITIALIZED = 18,
/** Object/construct has been deleted. */
DELETED = 19,
/** Illegal call from ISR. */
ISR = 20,
/** Illegal call because network is up. */
NETWORK_UP = 21,
/** Illegal call because network is down. */
NETWORK_DOWN = 22,
/** Failure due to not being joined in a network. */
NOT_JOINED = 23,
/** Invalid operation as there are no beacons. */
NO_BEACONS = 24,
/** Generic allocation error. */
ALLOCATION_FAILED = 25,
/** No more resource available to perform the operation. */
NO_MORE_RESOURCE = 26,
/** Item/list/queue is empty. */
EMPTY = 27,
/** Item/list/queue is full. */
FULL = 28,
/** Item would overflow. */
WOULD_OVERFLOW = 29,
/** Item/list/queue has been overflowed. */
HAS_OVERFLOWED = 30,
/** Generic ownership error. */
OWNERSHIP = 31,
/** Already/still owning resource. */
IS_OWNER = 32,
/** Generic invalid argument or consequence of invalid argument. */
INVALID_PARAMETER = 33,
/** Invalid null pointer received as argument. */
NULL_POINTER = 34,
/** Invalid configuration provided. */
INVALID_CONFIGURATION = 35,
/** Invalid mode. */
INVALID_MODE = 36,
/** Invalid handle. */
INVALID_HANDLE = 37,
/** Invalid type for operation. */
INVALID_TYPE = 38,
/** Invalid index. */
INVALID_INDEX = 39,
/** Invalid range. */
INVALID_RANGE = 40,
/** Invalid key. */
INVALID_KEY = 41,
/** Invalid credentials. */
INVALID_CREDENTIALS = 42,
/** Invalid count. */
INVALID_COUNT = 43,
/** Invalid signature / verification failed. */
INVALID_SIGNATURE = 44,
/** Item could not be found. */
NOT_FOUND = 45,
/** Item already exists. */
ALREADY_EXISTS = 46,
/** Generic I/O failure. */
IO = 47,
/** I/O failure due to timeout. */
IO_TIMEOUT = 48,
/** Generic transmission error. */
TRANSMIT = 49,
/** Transmit underflowed. */
TRANSMIT_UNDERFLOW = 50,
/** Transmit is incomplete. */
TRANSMIT_INCOMPLETE = 51,
/** Transmit is busy. */
TRANSMIT_BUSY = 52,
/** Generic reception error. */
RECEIVE = 53,
/** Failed to read on/via given object. */
OBJECT_READ = 54,
/** Failed to write on/via given object. */
OBJECT_WRITE = 55,
/** Message is too long. */
MESSAGE_TOO_LONG = 56,
/** EEPROM MFG version mismatch. */
EEPROM_MFG_VERSION_MISMATCH = 57,
/** EEPROM Stack version mismatch. */
EEPROM_STACK_VERSION_MISMATCH = 58,
/** Flash write is inhibited. */
FLASH_WRITE_INHIBITED = 59,
/** Flash verification failed. */
FLASH_VERIFY_FAILED = 60,
/** Flash programming failed. */
FLASH_PROGRAM_FAILED = 61,
/** Flash erase failed. */
FLASH_ERASE_FAILED = 62,
/** MAC no data. */
MAC_NO_DATA = 63,
/** MAC no ACK received. */
MAC_NO_ACK_RECEIVED = 64,
/** MAC indirect timeout. */
MAC_INDIRECT_TIMEOUT = 65,
/** MAC unknown header type. */
MAC_UNKNOWN_HEADER_TYPE = 66,
/** MAC ACK unknown header type. */
MAC_ACK_HEADER_TYPE = 67,
/** MAC command transmit failure. */
MAC_COMMAND_TRANSMIT_FAILURE = 68,
/** Error in open NVM */
CLI_STORAGE_NVM_OPEN_ERROR = 69,
/** Image checksum is not valid. */
SECURITY_IMAGE_CHECKSUM_ERROR = 70,
/** Decryption failed */
SECURITY_DECRYPT_ERROR = 71,
/** Command was not recognized */
COMMAND_IS_INVALID = 72,
/** Command or parameter maximum length exceeded */
COMMAND_TOO_LONG = 73,
/** Data received does not form a complete command */
COMMAND_INCOMPLETE = 74,
/** Bus error, e.g. invalid DMA address */
BUS_ERROR = 75,
/** CCA failure. */
CCA_FAILURE = 76,
/** MAC scanning. */
MAC_SCANNING = 77,
/** MAC incorrect scan type. */
MAC_INCORRECT_SCAN_TYPE = 78,
/** Invalid channel mask. */
INVALID_CHANNEL_MASK = 79,
/** Bad scan duration. */
BAD_SCAN_DURATION = 80,
/** Bonding procedure can't be started because device has no space left for bond. */
BT_OUT_OF_BONDS = 1026,
/** Unspecified error */
BT_UNSPECIFIED = 1027,
/** Hardware failure */
BT_HARDWARE = 1028,
/** The bonding does not exist. */
BT_NO_BONDING = 1030,
/** Error using crypto functions */
BT_CRYPTO = 1031,
/** Data was corrupted. */
BT_DATA_CORRUPTED = 1032,
/** Invalid periodic advertising sync handle */
BT_INVALID_SYNC_HANDLE = 1034,
/** Bluetooth cannot be used on this hardware */
BT_INVALID_MODULE_ACTION = 1035,
/** Error received from radio */
BT_RADIO = 1036,
/** Returned when remote disconnects the connection-oriented channel by sending disconnection request. */
BT_L2CAP_REMOTE_DISCONNECTED = 1037,
/** Returned when local host disconnect the connection-oriented channel by sending disconnection request. */
BT_L2CAP_LOCAL_DISCONNECTED = 1038,
/** Returned when local host did not find a connection-oriented channel with given destination CID. */
BT_L2CAP_CID_NOT_EXIST = 1039,
/** Returned when connection-oriented channel disconnected due to LE connection is dropped. */
BT_L2CAP_LE_DISCONNECTED = 1040,
/** Returned when connection-oriented channel disconnected due to remote end send data even without credit. */
BT_L2CAP_FLOW_CONTROL_VIOLATED = 1042,
/** Returned when connection-oriented channel disconnected due to remote end send flow control credits exceed 65535. */
BT_L2CAP_FLOW_CONTROL_CREDIT_OVERFLOWED = 1043,
/** Returned when connection-oriented channel has run out of flow control credit and local application still trying to send data. */
BT_L2CAP_NO_FLOW_CONTROL_CREDIT = 1044,
/** Returned when connection-oriented channel has not received connection response message within maximum timeout. */
BT_L2CAP_CONNECTION_REQUEST_TIMEOUT = 1045,
/** Returned when local host received a connection-oriented channel connection response with an invalid destination CID. */
BT_L2CAP_INVALID_CID = 1046,
/** Returned when local host application tries to send a command which is not suitable for L2CAP channel's current state. */
BT_L2CAP_WRONG_STATE = 1047,
/** Flash reserved for PS store is full */
BT_PS_STORE_FULL = 1051,
/** PS key not found */
BT_PS_KEY_NOT_FOUND = 1052,
/** Mismatched or insufficient security level */
BT_APPLICATION_MISMATCHED_OR_INSUFFICIENT_SECURITY = 1053,
/** Encryption/decryption operation failed. */
BT_APPLICATION_ENCRYPTION_DECRYPTION_ERROR = 1054,
/** Connection does not exist, or connection open request was cancelled. */
BT_CTRL_UNKNOWN_CONNECTION_IDENTIFIER = 4098,
/**
* 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
*/
BT_CTRL_AUTHENTICATION_FAILURE = 4101,
/** Pairing failed because of missing PIN, or authentication failed because of missing Key */
BT_CTRL_PIN_OR_KEY_MISSING = 4102,
/** Controller is out of memory. */
BT_CTRL_MEMORY_CAPACITY_EXCEEDED = 4103,
/** Link supervision timeout has expired. */
BT_CTRL_CONNECTION_TIMEOUT = 4104,
/** Controller is at limit of connections it can support. */
BT_CTRL_CONNECTION_LIMIT_EXCEEDED = 4105,
/**
* 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.
*/
BT_CTRL_SYNCHRONOUS_CONNECTION_LIMIT_EXCEEDED = 4106,
/**
* 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.
*/
BT_CTRL_ACL_CONNECTION_ALREADY_EXISTS = 4107,
/** Command requested cannot be executed because the Controller is in a state where it cannot process this command at this time. */
BT_CTRL_COMMAND_DISALLOWED = 4108,
/** The Connection Rejected Due To Limited Resources error code indicates that an incoming connection was rejected due to limited resources. */
BT_CTRL_CONNECTION_REJECTED_DUE_TO_LIMITED_RESOURCES = 4109,
/**
* 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.
*/
BT_CTRL_CONNECTION_REJECTED_DUE_TO_SECURITY_REASONS = 4110,
/**
* 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.
*/
BT_CTRL_CONNECTION_REJECTED_DUE_TO_UNACCEPTABLE_BD_ADDR = 4111,
/** The Connection Accept Timeout has been exceeded for this connection attempt. */
BT_CTRL_CONNECTION_ACCEPT_TIMEOUT_EXCEEDED = 4112,
/** A feature or parameter value in the HCI command is not supported. */
BT_CTRL_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE = 4113,
/** Command contained invalid parameters. */
BT_CTRL_INVALID_COMMAND_PARAMETERS = 4114,
/** User on the remote device terminated the connection. */
BT_CTRL_REMOTE_USER_TERMINATED = 4115,
/** The remote device terminated the connection because of low resources */
BT_CTRL_REMOTE_DEVICE_TERMINATED_CONNECTION_DUE_TO_LOW_RESOURCES = 4116,
/** Remote Device Terminated Connection due to Power Off */
BT_CTRL_REMOTE_POWERING_OFF = 4117,
/** Local device terminated the connection. */
BT_CTRL_CONNECTION_TERMINATED_BY_LOCAL_HOST = 4118,
/**
* The Controller is disallowing an authentication or pairing procedure because too little time has elapsed
* since the last authentication or pairing attempt failed.
*/
BT_CTRL_REPEATED_ATTEMPTS = 4119,
/**
* 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
*/
BT_CTRL_PAIRING_NOT_ALLOWED = 4120,
/** The remote device does not support the feature associated with the issued command. */
BT_CTRL_UNSUPPORTED_REMOTE_FEATURE = 4122,
/** No other error code specified is appropriate to use. */
BT_CTRL_UNSPECIFIED_ERROR = 4127,
/** Connection terminated due to link-layer procedure timeout. */
BT_CTRL_LL_RESPONSE_TIMEOUT = 4130,
/** LL procedure has collided with the same transaction or procedure that is already in progress. */
BT_CTRL_LL_PROCEDURE_COLLISION = 4131,
/** The requested encryption mode is not acceptable at this time. */
BT_CTRL_ENCRYPTION_MODE_NOT_ACCEPTABLE = 4133,
/** Link key cannot be changed because a fixed unit key is being used. */
BT_CTRL_LINK_KEY_CANNOT_BE_CHANGED = 4134,
/** LMP PDU or LL PDU that includes an instant cannot be performed because the instant when this would have occurred has passed. */
BT_CTRL_INSTANT_PASSED = 4136,
/** It was not possible to pair as a unit key was requested and it is not supported. */
BT_CTRL_PAIRING_WITH_UNIT_KEY_NOT_SUPPORTED = 4137,
/** LMP transaction was started that collides with an ongoing transaction. */
BT_CTRL_DIFFERENT_TRANSACTION_COLLISION = 4138,
/** The Controller cannot perform channel assessment because it is not supported. */
BT_CTRL_CHANNEL_ASSESSMENT_NOT_SUPPORTED = 4142,
/** The HCI command or LMP PDU sent is only possible on an encrypted link. */
BT_CTRL_INSUFFICIENT_SECURITY = 4143,
/** A parameter value requested is outside the mandatory range of parameters for the given HCI command or LMP PDU. */
BT_CTRL_PARAMETER_OUT_OF_MANDATORY_RANGE = 4144,
/**
* 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.
*/
BT_CTRL_SIMPLE_PAIRING_NOT_SUPPORTED_BY_HOST = 4151,
/**
* The Host is busy with another pairing operation and unable to support the requested pairing.
* The receiving device should retry pairing again later.
*/
BT_CTRL_HOST_BUSY_PAIRING = 4152,
/** The Controller could not calculate an appropriate value for the Channel selection operation. */
BT_CTRL_CONNECTION_REJECTED_DUE_TO_NO_SUITABLE_CHANNEL_FOUND = 4153,
/** Operation was rejected because the controller is busy and unable to process the request. */
BT_CTRL_CONTROLLER_BUSY = 4154,
/** Remote device terminated the connection because of an unacceptable connection interval. */
BT_CTRL_UNACCEPTABLE_CONNECTION_INTERVAL = 4155,
/** Advertising for a fixed duration completed or, for directed advertising, that advertising completed without a connection being created. */
BT_CTRL_ADVERTISING_TIMEOUT = 4156,
/** Connection was terminated because the Message Integrity Check (MIC) failed on a received packet. */
BT_CTRL_CONNECTION_TERMINATED_DUE_TO_MIC_FAILURE = 4157,
/** LL initiated a connection but the connection has failed to be established. Controller did not receive any packets from remote end. */
BT_CTRL_CONNECTION_FAILED_TO_BE_ESTABLISHED = 4158,
/** The MAC of the 802.11 AMP was requested to connect to a peer, but the connection failed. */
BT_CTRL_MAC_CONNECTION_FAILED = 4159,
/**
* 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.
*/
BT_CTRL_COARSE_CLOCK_ADJUSTMENT_REJECTED_BUT_WILL_TRY_TO_ADJUST_USING_CLOCK_DRAGGING = 4160,
/** A command was sent from the Host that should identify an Advertising or Sync handle, but the Advertising or Sync handle does not exist. */
BT_CTRL_UNKNOWN_ADVERTISING_IDENTIFIER = 4162,
/** Number of operations requested has been reached and has indicated the completion of the activity (e.g., advertising or scanning). */
BT_CTRL_LIMIT_REACHED = 4163,
/** A request to the Controller issued by the Host and still pending was successfully canceled. */
BT_CTRL_OPERATION_CANCELLED_BY_HOST = 4164,
/** An attempt was made to send or receive a packet that exceeds the maximum allowed packet l */
BT_CTRL_PACKET_TOO_LONG = 4165,
/** The attribute handle given was not valid on this server */
BT_ATT_INVALID_HANDLE = 4353,
/** The attribute cannot be read */
BT_ATT_READ_NOT_PERMITTED = 4354,
/** The attribute cannot be written */
BT_ATT_WRITE_NOT_PERMITTED = 4355,
/** The attribute PDU was invalid */
BT_ATT_INVALID_PDU = 4356,
/** The attribute requires authentication before it can be read or written. */
BT_ATT_INSUFFICIENT_AUTHENTICATION = 4357,
/** Attribute Server does not support the request received from the client. */
BT_ATT_REQUEST_NOT_SUPPORTED = 4358,
/** Offset specified was past the end of the attribute */
BT_ATT_INVALID_OFFSET = 4359,
/** The attribute requires authorization before it can be read or written. */
BT_ATT_INSUFFICIENT_AUTHORIZATION = 4360,
/** Too many prepare writes have been queued */
BT_ATT_PREPARE_QUEUE_FULL = 4361,
/** No attribute found within the given attribute handle range. */
BT_ATT_ATT_NOT_FOUND = 4362,
/** The attribute cannot be read or written using the Read Blob Request */
BT_ATT_ATT_NOT_LONG = 4363,
/** The Encryption Key Size used for encrypting this link is insufficient. */
BT_ATT_INSUFFICIENT_ENC_KEY_SIZE = 4364,
/** The attribute value length is invalid for the operation */
BT_ATT_INVALID_ATT_LENGTH = 4365,
/** The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. */
BT_ATT_UNLIKELY_ERROR = 4366,
/** The attribute requires encryption before it can be read or written. */
BT_ATT_INSUFFICIENT_ENCRYPTION = 4367,
/** The attribute type is not a supported grouping attribute as defined by a higher layer specification. */
BT_ATT_UNSUPPORTED_GROUP_TYPE = 4368,
/** Insufficient Resources to complete the request */
BT_ATT_INSUFFICIENT_RESOURCES = 4369,
/** The server requests the client to rediscover the database. */
BT_ATT_OUT_OF_SYNC = 4370,
/** The attribute parameter value was not allowed. */
BT_ATT_VALUE_NOT_ALLOWED = 4371,
/** 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. */
BT_ATT_APPLICATION = 4480,
/** The requested write operation cannot be fulfilled for reasons other than permissions. */
BT_ATT_WRITE_REQUEST_REJECTED = 4604,
/** The Client Characteristic Configuration descriptor is not configured according to the requirements of the profile or service. */
BT_ATT_CLIENT_CHARACTERISTIC_CONFIGURATION_DESCRIPTOR_IMPROPERLY_CONFIGURED = 4605,
/** The profile or service request cannot be serviced because an operation that has been previously triggered is still in progress. */
BT_ATT_PROCEDURE_ALREADY_IN_PROGRESS = 4606,
/** The attribute value is out of range as defined by a profile or service specification. */
BT_ATT_OUT_OF_RANGE = 4607,
/** The user input of passkey failed, for example, the user cancelled the operation */
BT_SMP_PASSKEY_ENTRY_FAILED = 4609,
/** Out of Band data is not available for authentication */
BT_SMP_OOB_NOT_AVAILABLE = 4610,
/** The pairing procedure cannot be performed as authentication requirements cannot be met due to IO capabilities of one or both devices */
BT_SMP_AUTHENTICATION_REQUIREMENTS = 4611,
/** The confirm value does not match the calculated compare value */
BT_SMP_CONFIRM_VALUE_FAILED = 4612,
/** Pairing is not supported by the device */
BT_SMP_PAIRING_NOT_SUPPORTED = 4613,
/** The resultant encryption key size is insufficient for the security requirements of this device */
BT_SMP_ENCRYPTION_KEY_SIZE = 4614,
/** The SMP command received is not supported on this device */
BT_SMP_COMMAND_NOT_SUPPORTED = 4615,
/** Pairing failed due to an unspecified reason */
BT_SMP_UNSPECIFIED_REASON = 4616,
/** Pairing or authentication procedure is disallowed because too little time has elapsed since last pairing request or security request */
BT_SMP_REPEATED_ATTEMPTS = 4617,
/** The Invalid Parameters error code indicates: the command length is invalid or a parameter is outside of the specified range. */
BT_SMP_INVALID_PARAMETERS = 4618,
/** Indicates to the remote device that the DHKey Check value received doesn't match the one calculated by the local device. */
BT_SMP_DHKEY_CHECK_FAILED = 4619,
/** Indicates that the confirm values in the numeric comparison protocol do not match. */
BT_SMP_NUMERIC_COMPARISON_FAILED = 4620,
/** Indicates that the pairing over the LE transport failed due to a Pairing Request sent over the BR/EDR transport in process. */
BT_SMP_BREDR_PAIRING_IN_PROGRESS = 4621,
/** 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. */
BT_SMP_CROSS_TRANSPORT_KEY_DERIVATION_GENERATION_NOT_ALLOWED = 4622,
/** Indicates that the device chose not to accept a distributed key. */
BT_SMP_KEY_REJECTED = 4623,
/** Returned when trying to add a key or some other unique resource with an ID which already exists */
BT_MESH_ALREADY_EXISTS = 1281,
/** Returned when trying to manipulate a key or some other resource with an ID which does not exist */
BT_MESH_DOES_NOT_EXIST = 1282,
/**
* 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
*/
BT_MESH_LIMIT_REACHED = 1283,
/** Returned when trying to use a reserved address or add a "pre-provisioned" device using an address already used by some other device */
BT_MESH_INVALID_ADDRESS = 1284,
/** In a BGAPI response, the user supplied malformed data; in a BGAPI event, the remote end responded with malformed or unrecognized data */
BT_MESH_MALFORMED_DATA = 1285,
/** An attempt was made to initialize a subsystem that was already initialized. */
BT_MESH_ALREADY_INITIALIZED = 1286,
/** An attempt was made to use a subsystem that wasn't initialized yet. Call the subsystem's init function first. */
BT_MESH_NOT_INITIALIZED = 1287,
/** Returned when trying to establish a friendship as a Low Power Node, but no acceptable friend offer message was received. */
BT_MESH_NO_FRIEND_OFFER = 1288,
/** Provisioning link was unexpectedly closed before provisioning was complete. */
BT_MESH_PROV_LINK_CLOSED = 1289,
/**An unrecognized provisioning PDU was received. */
BT_MESH_PROV_INVALID_PDU = 1290,
/**A provisioning PDU with wrong length or containing field values that are out of bounds was received. */
BT_MESH_PROV_INVALID_PDU_FORMAT = 1291,
/**An unexpected (out of sequence) provisioning PDU was received. */
BT_MESH_PROV_UNEXPECTED_PDU = 1292,
/**The computed confirmation value did not match the expected value. */
BT_MESH_PROV_CONFIRMATION_FAILED = 1293,
/**Provisioning could not be continued due to insufficient resources. */
BT_MESH_PROV_OUT_OF_RESOURCES = 1294,
/**The provisioning data block could not be decrypted. */
BT_MESH_PROV_DECRYPTION_FAILED = 1295,
/**An unexpected error happened during provisioning. */
BT_MESH_PROV_UNEXPECTED_ERROR = 1296,
/**Device could not assign unicast addresses to all of its elements. */
BT_MESH_PROV_CANNOT_ASSIGN_ADDR = 1297,
/**Returned when trying to reuse an address of a previously deleted device before an IV Index Update has been executed. */
BT_MESH_ADDRESS_TEMPORARILY_UNAVAILABLE = 1298,
/**Returned when trying to assign an address that is used by one of the devices in the Device Database, or by the Provisioner itself. */
BT_MESH_ADDRESS_ALREADY_USED = 1299,
/**Application key or publish address are not set */
BT_MESH_PUBLISH_NOT_CONFIGURED = 1300,
/**Application key is not bound to a model */
BT_MESH_APP_KEY_NOT_BOUND = 1301,
/** Returned when address in request was not valid */
BT_MESH_FOUNDATION_INVALID_ADDRESS = 4865,
/** Returned when model identified is not found for a given element */
BT_MESH_FOUNDATION_INVALID_MODEL = 4866,
/** Returned when the key identified by AppKeyIndex is not stored in the node */
BT_MESH_FOUNDATION_INVALID_APP_KEY = 4867,
/** Returned when the key identified by NetKeyIndex is not stored in the node */
BT_MESH_FOUNDATION_INVALID_NET_KEY = 4868,
/** Returned when The node cannot serve the request due to insufficient resources */
BT_MESH_FOUNDATION_INSUFFICIENT_RESOURCES = 4869,
/** Returned when the key identified is already stored in the node and the new NetKey value is different */
BT_MESH_FOUNDATION_KEY_INDEX_EXISTS = 4870,
/** Returned when the model does not support the publish mechanism */
BT_MESH_FOUNDATION_INVALID_PUBLISH_PARAMS = 4871,
/** Returned when the model does not support the subscribe mechanism */
BT_MESH_FOUNDATION_NOT_SUBSCRIBE_MODEL = 4872,
/** Returned when storing of the requested parameters failed */
BT_MESH_FOUNDATION_STORAGE_FAILURE = 4873,
/**Returned when requested setting is not supported */
BT_MESH_FOUNDATION_NOT_SUPPORTED = 4874,
/**Returned when the requested update operation cannot be performed due to general constraints */
BT_MESH_FOUNDATION_CANNOT_UPDATE = 4875,
/**Returned when the requested delete operation cannot be performed due to general constraints */
BT_MESH_FOUNDATION_CANNOT_REMOVE = 4876,
/**Returned when the requested bind operation cannot be performed due to general constraints */
BT_MESH_FOUNDATION_CANNOT_BIND = 4877,
/**Returned when The node cannot start advertising with Node Identity or Proxy since the maximum number of parallel advertising is reached */
BT_MESH_FOUNDATION_TEMPORARILY_UNABLE = 4878,
/**Returned when the requested state cannot be set */
BT_MESH_FOUNDATION_CANNOT_SET = 4879,
/**Returned when an unspecified error took place */
BT_MESH_FOUNDATION_UNSPECIFIED = 4880,
/**Returned when the NetKeyIndex and AppKeyIndex combination is not valid for a Config AppKey Update */
BT_MESH_FOUNDATION_INVALID_BINDING = 4881,
/** Invalid firmware keyset */
WIFI_INVALID_KEY = 2817,
/** The firmware download took too long */
WIFI_FIRMWARE_DOWNLOAD_TIMEOUT = 2818,
/** Unknown request ID or wrong interface ID used */
WIFI_UNSUPPORTED_MESSAGE_ID = 2819,
/** The request is successful but some parameters have been ignored */
WIFI_WARNING = 2820,
/** No Packets waiting to be received */
WIFI_NO_PACKET_TO_RECEIVE = 2821,
/** The sleep mode is granted */
WIFI_SLEEP_GRANTED = 2824,
/** The WFx does not go back to sleep */
WIFI_SLEEP_NOT_GRANTED = 2825,
/** The SecureLink MAC key was not found */
WIFI_SECURE_LINK_MAC_KEY_ERROR = 2832,
/** The SecureLink MAC key is already installed in OTP */
WIFI_SECURE_LINK_MAC_KEY_ALREADY_BURNED = 2833,
/** The SecureLink MAC key cannot be installed in RAM */
WIFI_SECURE_LINK_RAM_MODE_NOT_ALLOWED = 2834,
/** The SecureLink MAC key installation failed */
WIFI_SECURE_LINK_FAILED_UNKNOWN_MODE = 2835,
/** SecureLink key (re)negotiation failed */
WIFI_SECURE_LINK_EXCHANGE_FAILED = 2836,
/** The device is in an inappropriate state to perform the request */
WIFI_WRONG_STATE = 2840,
/** The request failed due to regulatory limitations */
WIFI_CHANNEL_NOT_ALLOWED = 2841,
/** The connection request failed because no suitable AP was found */
WIFI_NO_MATCHING_AP = 2842,
/** The connection request was aborted by host */
WIFI_CONNECTION_ABORTED = 2843,
/** The connection request failed because of a timeout */
WIFI_CONNECTION_TIMEOUT = 2844,
/** The connection request failed because the AP rejected the device */
WIFI_CONNECTION_REJECTED_BY_AP = 2845,
/** The connection request failed because the WPA handshake did not complete successfully */
WIFI_CONNECTION_AUTH_FAILURE = 2846,
/** The request failed because the retry limit was exceeded */
WIFI_RETRY_EXCEEDED = 2847,
/** The request failed because the MSDU life time was exceeded */
WIFI_TX_LIFETIME_EXCEEDED = 2848,
/** Critical fault */
COMPUTE_DRIVER_FAULT = 5377,
/** ALU operation output NaN */
COMPUTE_DRIVER_ALU_NAN = 5378,
/** ALU numeric overflow */
COMPUTE_DRIVER_ALU_OVERFLOW = 5379,
/** ALU numeric underflow */
COMPUTE_DRIVER_ALU_UNDERFLOW = 5380,
/** Overflow during array store */
COMPUTE_DRIVER_STORE_CONVERSION_OVERFLOW = 5381,
/** Underflow during array store conversion */
COMPUTE_DRIVER_STORE_CONVERSION_UNDERFLOW = 5382,
/** Infinity encountered during array store conversion */
COMPUTE_DRIVER_STORE_CONVERSION_INFINITY = 5383,
/** NaN encountered during array store conversion */
COMPUTE_DRIVER_STORE_CONVERSION_NAN = 5384,
/** MATH NaN encountered */
COMPUTE_MATH_NAN = 5394,
/** MATH Infinity encountered */
COMPUTE_MATH_INFINITY = 5395,
/** MATH numeric overflow */
COMPUTE_MATH_OVERFLOW = 5396,
/** MATH numeric underflow */
COMPUTE_MATH_UNDERFLOW = 5397
}
/**
* Many EmberZNet API functions return an ::EmberStatus value to indicate the success or failure of the call.
* Return codes are one byte long.
*/
export declare enum EmberStatus {
/** The generic "no error" message. */
SUCCESS = 0,
/** The generic "fatal error" message. */
ERR_FATAL = 1,
/** An invalid value was passed as an argument to a function. */
BAD_ARGUMENT = 2,
/** The requested information was not found. */
NOT_FOUND = 3,
/** The manufacturing and stack token format in non-volatile memory is different than what the stack expects (returned at initialization). */
EEPROM_MFG_STACK_VERSION_MISMATCH = 4,
/** The manufacturing token format in non-volatile memory is different than what the stack expects (returned at initialization). */
EEPROM_MFG_VERSION_MISMATCH = 6,
/** The stack token format in non-volatile memory is different than what the stack expects (returned at initialization). */
EEPROM_STACK_VERSION_MISMATCH = 7,
/** There are no more buffers. */
NO_BUFFERS = 24,
/** Packet is dropped by packet-handoff callbacks. */
PACKET_HANDOFF_DROP_PACKET = 25,
/** Specifies an invalid baud rate. */
SERIAL_INVALID_BAUD_RATE = 32,
/** Specifies an invalid serial port. */
SERIAL_INVALID_PORT = 33,
/** Tried to send too much data. */
SERIAL_TX_OVERFLOW = 34,
/** There wasn't enough space to store a received character and the character was dropped. */
SERIAL_RX_OVERFLOW = 35,
/** Detected a UART framing error. */
SERIAL_RX_FRAME_ERROR = 36,
/** Detected a UART parity error. */
SERIAL_RX_PARITY_ERROR = 37,
/** There is no received data to process. */
SERIAL_RX_EMPTY = 38,
/** The receive interrupt was not handled in time and a character was dropped. */
SERIAL_RX_OVERRUN_ERROR = 39,
/** The MAC transmit queue is full. */
MAC_TRANSMIT_QUEUE_FULL = 57,
/** MAC header FCF error on receive. */
MAC_UNKNOWN_HEADER_TYPE = 58,
/** MAC ACK header received. */
MAC_ACK_HEADER_TYPE = 59,
/** The MAC can't complete this task because it is scanning. */
MAC_SCANNING = 61,
/** No pending data exists for a data poll. */
MAC_NO_DATA = 49,
/** Attempts to scan when joined to a network. */
MAC_JOINED_NETWORK = 50,
/** Scan duration must be 0 to 14 inclusive. Tried to scan with an incorrect duration value. */
MAC_BAD_SCAN_DURATION = 51,
/** emberStartScan was called with an incorrect scan type. */
MAC_INCORRECT_SCAN_TYPE = 52,
/** emberStartScan was called with an invalid channel mask. */
MAC_INVALID_CHANNEL_MASK = 53,
/** Failed to scan the current channel because the relevant MAC command could not be transmitted. */
MAC_COMMAND_TRANSMIT_FAILURE = 54,
/** An ACK was expected following the transmission but the MAC level ACK was never received. */
MAC_NO_ACK_RECEIVED = 64,
/** MAC failed to transmit a message because it could not successfully perform a radio network switch. */
MAC_RADIO_NETWORK_SWITCH_FAILED = 65,
/** An indirect data message timed out before a poll requested it. */
MAC_INDIRECT_TIMEOUT = 66,
/**
* The Simulated EEPROM is telling the application that at least one flash page to be erased.
* The GREEN status means the current page has not filled above the ::ERASE_CRITICAL_THRESHOLD.
*
* The application should call the function ::halSimEepromErasePage() when it can to erase a page.
*/
SIM_EEPROM_ERASE_PAGE_GREEN = 67,
/**
* The Simulated EEPROM is telling the application that at least one flash page must be erased.
* The RED status means the current page has filled above the ::ERASE_CRITICAL_THRESHOLD.
*
* Due to the shrinking availability of write space, data could be lost.
* The application must call the function ::halSimEepromErasePage() as soon as possible to erase a page.
*/
SIM_EEPROM_ERASE_PAGE_RED = 68,
/**
* The Simulated EEPROM has run out of room to write new data and the data trying to be set has been lost.
* This error code is the result of ignoring the ::SIM_EEPROM_ERASE_PAGE_RED error code.
*
* The application must call the function ::halSimEepromErasePage() to make room for any further calls to set a token.
*/
SIM_EEPROM_FULL = 69,
/**
* Attempt 1 to initialize the Simulated EEPROM has failed.
*
* This failure means the information already stored in the Flash (or a lack thereof),
* is fatally incompatible with the token information compiled into the code image being run.
*/
SIM_EEPROM_INIT_1_FAILED = 72,
/**
* Attempt 2 to initialize the Simulated EEPROM has failed.
*
* This failure means Attempt 1 failed, and the token system failed to properly reload default tokens and reset the Simulated EEPROM.
*/
SIM_EEPROM_INIT_2_FAILED = 73,
/**
* Attempt 3 to initialize the Simulated EEPROM has failed.
*
* This failure means one or both of the tokens ::TOKEN_MFG_NVDATA_VERSION or ::TOKEN_STACK_NVDATA_VERSION
* were incorrect and the token system failed to properly reload default tokens and reset the Simulated EEPROM.
*/
SIM_EEPROM_INIT_3_FAILED = 74,
/**
* The Simulated EEPROM is repairing itself.
*
* While there's nothing for an app to do when the SimEE is going to
* repair itself (SimEE has to be fully functional for the rest of the
* system to work), alert the application to the fact that repair
* is occurring. There are debugging scenarios where an app might want
* to know that repair is happening, such as monitoring frequency.
* @note Common situations will trigger an expected repair, such as
* using an erased chip or changing token definitions.
*/
SIM_EEPROM_REPAIRING = 77,
/**
* A fatal error has occurred while trying to write data to the Flash.
* The target memory attempting to be programmed is already programmed.
* The flash write routines were asked to flip a bit from a 0 to 1,
* which is physically impossible and the write was therefore inhibited.
* The data in the Flash cannot be trusted after this error.
*/
ERR_FLASH_WRITE_INHIBITED = 70,
/**
* A fatal error has occurred while trying to write data to the Flash and the write verification has failed.
* Data in the Flash cannot be trusted after this error and it is possible this error is the result of exceeding the life cycles of the Flash.
*/
ERR_FLASH_VERIFY_FAILED = 71,
/**
* A fatal error has occurred while trying to write data to the Flash possibly due to write protection or an invalid address.
* Data in the Flash cannot be trusted after this error and it is possible this error is the result of exceeding the life cycles of the Flash.
*/
ERR_FLASH_PROG_FAIL = 75,
/**
* A fatal error has occurred while trying to erase the Flash possibly due to write protection.
* Data in the Flash cannot be trusted after this error and it is possible this error is the result of exceeding the life cycles of the Flash.
*/
ERR_FLASH_ERASE_FAIL = 76,
/** The bootloader received an invalid message (failed attempt to go into bootloader). */
ERR_BOOTLOADER_TRAP_TABLE_BAD = 88,
/** The bootloader received an invalid message (failed attempt to go into the bootloader). */
ERR_BOOTLOADER_TRAP_UNKNOWN = 89,
/** The bootloader cannot complete the bootload operation because either an image was not found or the image exceeded memory bounds. */
ERR_BOOTLOADER_NO_IMAGE = 90,
/** The APS layer attempted to send or deliver a message and failed. */
DELIVERY_FAILED = 102,
/** This binding index is out of range for the current binding table. */
BINDING_INDEX_OUT_OF_RANGE = 105,
/** This address table index is out of range for the current address table. */
ADDRESS_TABLE_INDEX_OUT_OF_RANGE = 106,
/** An invalid binding table index was given to a function. */
INVALID_BINDING_INDEX = 108,
/** The API call is not allowed given the current state of the stack. */
INVALID_CALL = 112,
/** The link cost to a node is not known. */
COST_NOT_KNOWN = 113,
/** The maximum number of in-flight messages = i.e., ::EMBER_APS_UNICAST_MESSAGE_COUNT, has been reached. */
MAX_MESSAGE_LIMIT_REACHED = 114,
/** The message to be transmitted is too big to fit into a single over-the-air packet. */
MESSAGE_TOO_LONG = 116,
/** The application is trying to delete or overwrite a binding that is in use. */
BINDING_IS_ACTIVE = 117,
/** The application is trying to overwrite an address table entry that is in use. */
ADDRESS_TABLE_ENTRY_IS_ACTIVE = 118,
/** An attempt was made to transmit during the suspend period. */
TRANSMISSION_SUSPENDED = 119,
/** Security match. */
MATCH = 120,
/** Drop frame. */
DROP_FRAME = 121,
/** */
PASS_UNPROCESSED = 122,
/** */
TX_THEN_DROP = 123,
/** */
NO_SECURITY = 124,
/** */
COUNTER_FAILURE = 125,
/** */
AUTH_FAILURE = 126,
/** */
UNPROCESSED = 127,
/** The conversion is complete. */
ADC_CONVERSION_DONE = 128,
/** The conversion cannot be done because a request is being processed. */
ADC_CONVERSION_BUSY = 129,
/** The conversion is deferred until the current request has been processed. */
ADC_CONVERSION_DEFERRED = 130,
/** No results are pending. */
ADC_NO_CONVERSION_PENDING = 132,
/** Sleeping (for a duration) has been abnormally interrupted and exited prematurely. */
SLEEP_INTERRUPTED = 133,
/**
* 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.
*/
PHY_TX_SCHED_FAIL = 135,
/** The transmit hardware buffer underflowed. */
PHY_TX_UNDERFLOW = 136,
/** The transmit hardware did not finish transmitting a packet. */
PHY_TX_INCOMPLETE = 137,
/** An unsupported channel setting was specified. */
PHY_INVALID_CHANNEL = 138,
/** An unsupported power setting was specified. */
PHY_INVALID_POWER = 139,
/** The requested operation cannot be completed because the radio is currently busy, either transmitting a packet or performing calibration. */
PHY_TX_BUSY = 140,
/** The transmit attempt failed because all CCA attempts indicated that the channel was busy. */
PHY_TX_CCA_FAIL = 141,
/**
* 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.
*/
PHY_TX_BLOCKED = 142,
/** The expected ACK was received after the last transmission. */
PHY_ACK_RECEIVED = 143,
/** The stack software has completed initialization and is ready to send and receive packets over the air. */
NETWORK_UP = 144,
/** The network is not operating. */
NETWORK_DOWN = 145,
/** An attempt to join a network failed. */
JOIN_FAILED = 148,
/** After moving, a mobile node's attempt to re-establish contact with the network failed. */
MOVE_FAILED = 150,
/**
* An attempt to join as a router failed due to a Zigbee versus Zigbee Pro incompatibility.
* Zigbee devices joining Zigbee Pro networks (or vice versa) must join as End Devices, not Routers.
*/
CANNOT_JOIN_AS_ROUTER = 152,
/** The local node ID has changed. The application can get the new node ID by calling ::emberGetNodeId(). */
NODE_ID_CHANGED = 153,
/** The local PAN ID has changed. The application can get the new PAN ID by calling ::emberGetPanId(). */
PAN_ID_CHANGED = 154,
/** The channel has changed. */
CHANNEL_CHANGED = 155,
/** The network has been opened for joining. */
NETWORK_OPENED = 156,
/** The network has been closed for joining. */
NETWORK_CLOSED = 157,
/** An attempt to join or rejoin the network failed because no router beacons could be heard by the joining node. */
NO_BEACONS = 171,
/**
* 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).
*/
RECEIVED_KEY_IN_THE_CLEAR = 172,
/** An attempt was made to join a Secured Network, but the device did not receive a Network Key. */
NO_NETWORK_KEY_RECEIVED = 173,
/** After a device joined a Secured Network, a Link Key was requested (::EMBER_GET_LINK_KEY_WHEN_JOINING) but no response was ever received. */
NO_LINK_KEY_RECEIVED = 174,
/**
* 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.
*/
PRECONFIGURED_KEY_REQUIRED = 175,
/** The passed key data is not valid. A key of all zeros or all F's are reserved values and cannot be used. */
KEY_INVALID = 178,
/** The chosen security level (the value of ::EMBER_SECURITY_LEVEL) is not supported by the stack. */
INVALID_SECURITY_LEVEL = 149,
/**
* An error occurred when trying to encrypt at the APS Level.
*
* To APS encrypt an outgoing packet, the sender
* needs to know the EUI64 of the destination. This error occurs because
* the EUI64 of the destination can't be determined from
* the short address (no entry in the neighbor, child, binding
* or address tables).
*
* Every time this error code is seen, note that the stack initiates an
* IEEE address discovery request behind the scenes. Responses
* to the request are stored in the trust center cache portion of the
* address table. Note that you need at least 1 entry allocated for
* TC cache in the address table plugin. Depending on the available rows in
* the table, newly discovered addresses may replace old ones. The address
* table plugin is enabled by default on the host. If you are using an SoC
* platform, please be sure to add the address table plugin.
*
* When customers choose to send APS messages by using short addresses,
* they should incorporate a retry mechanism and try again, no sooner than
* 2 seconds later, to resend the APS message. If the app always
* receives 0xBE (IEEE_ADDRESS_DISCOVERY_IN_PROGRESS) after
* multiple retries, that might indicate that:
* a) destination node is not on the network
* b) there are problems with the health of the network
* c) there may not be any space set aside in the address table for
* the newly discovered address - this can be rectified by reserving
* more entries for the trust center cache in the address table plugin
*/
IEEE_ADDRESS_DISCOVERY_IN_PROGRESS = 190,
/**
* An error occurred when trying to encrypt at the APS Level.
*
* This error occurs either because the long address of the recipient can't be
* determined from the short address (no entry in the binding table)
* or there is no link key entry in the table associated with the destination,
* or there was a failure to load the correct key into the encryption core.
*/
APS_ENCRYPTION_ERROR = 166,
/** There was an attempt to form or join a network with security without calling ::emberSetInitialSecurityState() first. */
SECURITY_STATE_NOT_SET = 168,
/**
* There was an attempt to set an entry in the key table using an invalid long address. Invalid addresses include:
* - The local device's IEEE address
* - Trust Center's IEEE address
* - An existing table entry's IEEE address
* - An address consisting of all zeros or all F's
*/
KEY_TABLE_INVALID_ADDRESS = 179,
/** There was an attempt to set a security configuration that is not valid given the other security settings. */
SECURITY_CONFIGURATION_INVALID = 183,
/**
* 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.
*/
TOO_SOON_FOR_SWITCH_KEY = 184,
/** The received signature corresponding to the message that was passed to the CBKE Library failed verification and is not valid. */
SIGNATURE_VERIFY_FAILURE = 185,
/**
* The message could not be sent because the link key corresponding to the destination is not authorized for use in APS data messages.
* APS Commands (sent by the stack) are allowed.
* To use it for encryption of APS data messages it must be authorized using a key agreement protocol (such as CBKE).
*/
KEY_NOT_AUTHORIZED = 187,
/** The security data provided was not valid, or an integrity check failed. */
SECURITY_DATA_INVALID = 189,
/** The node has not joined a network. */
NOT_JOINED = 147,
/** A message cannot be sent because the network is currently overloaded. */
NETWORK_BUSY = 161,
/** The application tried to send a message using an endpoint that it has not defined. */
INVALID_ENDPOINT = 163,
/** The application tried to use a binding that has been remotely modified and the change has not yet been reported to the application. */
BINDING_HAS_CHANGED = 164,
/** An attempt to generate random bytes failed because of insufficient random data from the radio. */
INSUFFICIENT_RANDOM_DATA = 165,
/** A Zigbee route error command frame was received indicating that a source routed message from this node failed en route. */
SOURCE_ROUTE_FAILURE = 169,
/**
* 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 route error frame was delivered by an ad-hoc search for a functioning route.
*/
MANY_TO_ONE_ROUTE_FAILURE = 170,
/**
* 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. The
* software (stack) on the chip must be replaced with software
* compatible with the chip.
*/
STACK_AND_HARDWARE_MISMATCH = 176,
/** An index was passed into the function that was larger than the valid range. */
INDEX_OUT_OF_RANGE = 177,
/** There are no empty entries left in the table. */
TABLE_FULL = 180,
/** The requested table entry has been erased and contains no valid data. */
TABLE_ENTRY_ERASED = 182,
/** The requested function cannot be executed because the library that contains the necessary functionality is not present. */
LIBRARY_NOT_PRESENT = 181,
/** The stack accepted the command and is currently processing the request. The results will be returned via an appropriate handler. */
OPERATION_IN_PROGRESS = 186,
/**
* The EUI of the Trust center has changed due to a successful rejoin.
* The device may need to perform other authentication to verify the new TC is authorized to take over.
*/
TRUST_CENTER_EUI_HAS_CHANGED = 188,
/** Trust center swapped out. The EUI has changed. */
TRUST_CENTER_SWAPPED_OUT_EUI_HAS_CHANGED = 188,
/** Trust center swapped out. The EUI has not changed. */
TRUST_CENTER_SWAPPED_OUT_EUI_HAS_NOT_CHANGED = 191,
/** NVM3 is telling the application that the initialization was aborted as no valid NVM3 page was found. */
NVM3_TOKEN_NO_VALID_PAGES = 192,
/** NVM3 is telling the application that the initialization was aborted as the NVM3 instance was already opened with other parameters. */
NVM3_ERR_OPENED_WITH_OTHER_PARAMETERS = 193,
/** NVM3 is telling the application that the initialization was aborted as the NVM3 instance is not aligned properly in memory. */
NVM3_ERR_ALIGNMENT_INVALID = 194,
/** NVM3 is telling the application that the initialization was aborted as the size of the NVM3 instance is too small. */
NVM3_ERR_SIZE_TOO_SMALL = 195,
/** NVM3 is telling the application that the initialization was aborted as the NVM3 page size is not supported. */
NVM3_ERR_PAGE_SIZE_NOT_SUPPORTED = 196,
/** NVM3 is telling the application that there was an error initializing some of the tokens. */
NVM3_ERR_TOKEN_INIT = 197,
/** NVM3 is telling the application there has been an error when attempting to upgrade SimEE tokens. */
NVM3_ERR_UPGRADE = 198,
/** NVM3 is telling the application that there has been an unknown error. */
NVM3_ERR_UNKNOWN = 199,
/**
* This error is reserved for customer application use.
* This will never be returned from any portion of the network stack or HAL.
*/
AP