zigbee-herdsman

/** Status Codes contains error and status code definitions used by Simplicity SDK software components and stacks. */ 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, /** The MAC transmit queue is full */ MAC_TRANSMIT_QUEUE_FULL = 83, /** * 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_SCHEDULER_FAIL = 84, /** An unsupported channel setting was specified */ TRANSMIT_INVALID_CHANNEL = 85, /** An unsupported power setting was specified */ TRANSMIT_INVALID_POWER = 86, /** The expected ACK was received after the last transmission */ TRANSMIT_ACK_RECEIVED = 87, /** * 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_BLOCKED = 88, /** The initialization was aborted as the NVM3 instance is not aligned properly in memory */ NVM3_ALIGNMENT_INVALID = 89, /** The initialization was aborted as the size of the NVM3 instance is too small */ NVM3_SIZE_TOO_SMALL = 90, /** The initialization was aborted as the NVM3 page size is not supported */ NVM3_PAGE_SIZE_NOT_SUPPORTED = 91, /** The application that there was an error initializing some of the tokens */ NVM3_TOKEN_INIT_FAILED = 92, /** The initialization was aborted as the NVM3 instance was already opened with other parameters */ NVM3_OPENED_WITH_OTHER_PARAMETERS = 93, /** 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, /** Packet is dropped by packet-handoff callbacks */ ZIGBEE_PACKET_HANDOFF_DROPPED = 3073, /** The APS layer attempted to send or deliver a message and failed */ ZIGBEE_DELIVERY_FAILED = 3074, /** The maximum number of in-flight messages ::EMBER_APS_UNICAST_MESSAGE_COUNT has been reached */ ZIGBEE_MAX_MESSAGE_LIMIT_REACHED = 3075, /** The application is trying to delete or overwrite a binding that is in use */ ZIGBEE_BINDING_IS_ACTIVE = 3076, /** The application is trying to overwrite an address table entry that is in use */ ZIGBEE_ADDRESS_TABLE_ENTRY_IS_ACTIVE = 3077, /** After moving, a mobile node's attempt to re-establish contact with the network failed */ ZIGBEE_MOVE_FAILED = 3078, /** The local node ID has changed. The application can get the new node ID by calling ::sl_zigbee_get_node_id() */ ZIGBEE_NODE_ID_CHANGED = 3079, /** The chosen security level is not supported by the stack */ ZIGBEE_INVALID_SECURITY_LEVEL = 3080, /** An error occurred when trying to encrypt at the APS Level */ ZIGBEE_IEEE_ADDRESS_DISCOVERY_IN_PROGRESS = 3081, /** An error occurred when trying to encrypt at the APS Level */ ZIGBEE_APS_ENCRYPTION_ERROR = 3082, /** There was an attempt to form or join a network with security without calling ::sl_zigbee_set_initial_security_state() first */ ZIGBEE_SECURITY_STATE_NOT_SET = 3083, /** * 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 */ ZIGBEE_TOO_SOON_FOR_SWITCH_KEY = 3084, /** The received signature corresponding to the message that was passed to the CBKE Library failed verification and is not valid */ ZIGBEE_SIGNATURE_VERIFY_FAILURE = 3085, /** The message could not be sent because the link key corresponding to the destination is not authorized for use in APS data messages */ ZIGBEE_KEY_NOT_AUTHORIZED = 3086, /** The application tried to use a binding that has been remotely modified and the change has not yet been reported to the application */ ZIGBEE_BINDING_HAS_CHANGED = 3087, /** The EUI of the Trust center has changed due to a successful rejoin after TC Swapout */ ZIGBEE_TRUST_CENTER_SWAP_EUI_HAS_CHANGED = 3088, /** A Trust Center Swapout Rejoin has occurred without the EUI of the TC changing */ ZIGBEE_TRUST_CENTER_SWAP_EUI_HAS_NOT_CHANGED = 3089, /** An attempt to generate random bytes failed because of insufficient random data from the radio */ ZIGBEE_INSUFFICIENT_RANDOM_DATA = 3090, /** A Zigbee route error command frame was received indicating that a source routed message from this node failed en route */ ZIGBEE_SOURCE_ROUTE_FAILURE = 3091, /** 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 */ ZIGBEE_MANY_TO_ONE_ROUTE_FAILURE = 3092, /** 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 */ ZIGBEE_STACK_AND_HARDWARE_MISMATCH = 3093, /** The local PAN ID has changed. The application can get the new PAN ID by calling ::emberGetPanId() */ ZIGBEE_PAN_ID_CHANGED = 3094, /** The channel has changed. */ ZIGBEE_CHANNEL_CHANGED = 3095, /** The network has been opened for joining. */ ZIGBEE_NETWORK_OPENED = 3096, /** The network has been closed for joining. */ ZIGBEE_NETWORK_CLOSED = 3097, /** * 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) */ ZIGBEE_RECEIVED_KEY_IN_THE_CLEAR = 3098, /** An attempt was made to join a Secured Network, but the device did not receive a Network Key. */ ZIGBEE_NO_NETWORK_KEY_RECEIVED = 3099, /** After a device joined a Secured Network, a Link Key was requested (::EMBER_GET_LINK_KEY_WHEN_JOINING) but no response was ever received. */ ZIGBEE_NO_LINK_KEY_RECEIVED = 3100, /** * 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. */ ZIGBEE_PRECONFIGURED_KEY_REQUIRED = 3101, /** A Zigbee EZSP error has occured. Track the origin and corresponding EzspStatus for more info. */ ZIGBEE_EZSP_ERROR = 3102 } /** Status values used by EZSP. */ export declare enum EzspStatus { /** Success. */ SUCCESS = 0, /** Fatal error. */ SPI_ERR_FATAL = 16, /** The Response frame of the current transaction indicates the NCP has reset. */ SPI_ERR_NCP_RESET = 17, /** The NCP is reporting that the Command frame of the current transaction is oversized (the length byte is too large). */ SPI_ERR_OVERSIZED_EZSP_FRAME = 18, /** The Response frame of the current transaction indicates the previous transaction was aborted (nSSEL deasserted too soon). */ SPI_ERR_ABORTED_TRANSACTION = 19, /** The Response frame of the current transaction indicates the frame terminator is missing from the Command frame. */ SPI_ERR_MISSING_FRAME_TERMINATOR = 20, /** The NCP has not provided a Response within the time limit defined by WAIT_SECTION_TIMEOUT. */ SPI_ERR_WAIT_SECTION_TIMEOUT = 21, /** The Response frame from the NCP is missing the frame terminator. */ SPI_ERR_NO_FRAME_TERMINATOR = 22, /** The Host attempted to send an oversized Command (the length byte is too large) and the AVR's spi-protocol.c blocked the transmission. */ SPI_ERR_EZSP_COMMAND_OVERSIZED = 23, /** The NCP attempted to send an oversized Response (the length byte is too large) and the AVR's spi-protocol.c blocked the reception. */ SPI_ERR_EZSP_RESPONSE_OVERSIZED = 24, /** The Host has sent the Command and is still waiting for the NCP to send a Response. */ SPI_WAITING_FOR_RESPONSE = 25, /** The NCP has not asserted nHOST_INT within the time limit defined by WAKE_HANDSHAKE_TIMEOUT. */ SPI_ERR_HANDSHAKE_TIMEOUT = 26, /** The NCP has not asserted nHOST_INT after an NCP reset within the time limit defined by STARTUP_TIMEOUT. */ SPI_ERR_STARTUP_TIMEOUT = 27, /** The Host attempted to verify the SPI Protocol activity and version number, and the verification failed. */ SPI_ERR_STARTUP_FAIL = 28, /** The Host has sent a command with a SPI Byte that is unsupported by the current mode the NCP is operating in. */ SPI_ERR_UNSUPPORTED_SPI_COMMAND = 29, /** Operation not yet complete. */ ASH_IN_PROGRESS = 32, /** Fatal error detected by host. */ HOST_FATAL_ERROR = 33, /** Fatal error detected by NCP. */ ASH_NCP_FATAL_ERROR = 34, /** Tried to send DATA frame too long. */ DATA_FRAME_TOO_LONG = 35, /** Tried to send DATA frame too short. */ DATA_FRAME_TOO_SHORT = 36, /** No space for tx'ed DATA frame. */ NO_TX_SPACE = 37, /** No space for rec'd DATA frame. */ NO_RX_SPACE = 38, /** No receive data available. */ NO_RX_DATA = 39, /** Not in Connected state. */ NOT_CONNECTED = 40, /** The NCP received a command before the EZSP version had been set. */ ERROR_VERSION_NOT_SET = 48, /** The NCP received a command containing an unsupported frame ID. */ ERROR_INVALID_FRAME_ID = 49, /** The direction flag in the frame control field was incorrect. */ ERROR_WRONG_DIRECTION = 50, /** * The truncated flag in the frame control field was set, indicating there was not enough memory available to * complete the response or that the response would have exceeded the maximum EZSP frame length. */ ERROR_TRUNCATED = 51, /** * The overflow flag in the frame control field was set, indicating one or more callbacks occurred since the previous * response and there was not enough memory available to report them to the Host. */ ERROR_OVERFLOW = 52, /** Insufficient memory was available. */ ERROR_OUT_OF_MEMORY = 53, /** The value was out of bounds. */ ERROR_INVALID_VALUE = 54, /** The configuration id was not recognized. */ ERROR_INVALID_ID = 55, /** Configuration values can no longer be modified. */ ERROR_INVALID_CALL = 56, /** The NCP failed to respond to a command. */ ERROR_NO_RESPONSE = 57, /** The length of the command exceeded the maximum EZSP frame length. */ ERROR_COMMAND_TOO_LONG = 64, /** The UART receive queue was full causing a callback response to be dropped. */ ERROR_QUEUE_FULL = 65, /** The command has been filtered out by NCP. */ ERROR_COMMAND_FILTERED = 66, /** EZSP Security Key is already set */ ERROR_SECURITY_KEY_ALREADY_SET = 67, /** EZSP Security Type is invalid */ ERROR_SECURITY_TYPE_INVALID = 68, /** EZSP Security Parameters are invalid */ ERROR_SECURITY_PARAMETERS_INVALID = 69, /** EZSP Security Parameters are already set */ ERROR_SECURITY_PARAMETERS_ALREADY_SET = 70, /** EZSP Security Key is not set */ ERROR_SECURITY_KEY_NOT_SET = 71, /** EZSP Security Parameters are not set */ ERROR_SECURITY_PARAMETERS_NOT_SET = 72, /** Received frame with unsupported control byte */ ERROR_UNSUPPORTED_CONTROL = 73, /** Received frame is unsecure, when security is established */ ERROR_UNSECURE_FRAME = 74, /** Incompatible ASH version */ ASH_ERROR_VERSION = 80, /** Exceeded max ACK timeouts */ ASH_ERROR_TIMEOUTS = 81, /** Timed out waiting for RSTACK */ ASH_ERROR_RESET_FAIL = 82, /** Unexpected ncp reset */ ASH_ERROR_NCP_RESET = 83, /** Serial port initialization failed */ ERROR_SERIAL_INIT = 84, /** Invalid ncp processor type */ ASH_ERROR_NCP_TYPE = 85, /** Invalid ncp reset method */ ASH_ERROR_RESET_METHOD = 86, /** XON/XOFF not supported by host driver */ ASH_ERROR_XON_XOFF = 87, /** ASH protocol started */ ASH_STARTED = 112, /** ASH protocol connected */ ASH_CONNECTED = 113, /** ASH protocol disconnected */ ASH_DISCONNECTED = 114, /** Timer expired waiting for ack */ ASH_ACK_TIMEOUT = 115, /** Frame in progress cancelled */ ASH_CANCELLED = 116, /** Received frame out of sequence */ ASH_OUT_OF_SEQUENCE = 117, /** Received frame with CRC error */ ASH_BAD_CRC = 118, /** Received frame with comm error */ ASH_COMM_ERROR = 119, /** Received frame with bad ackNum */ ASH_BAD_ACKNUM = 120, /** Received frame shorter than minimum */ ASH_TOO_SHORT = 121, /** Received frame longer than maximum */ ASH_TOO_LONG = 122, /** Received frame with illegal control byte */ ASH_BAD_CONTROL = 123, /** Received frame with illegal length for its type */ ASH_BAD_LENGTH = 124, /** Received ASH Ack */ ASH_ACK_RECEIVED = 125, /** Sent ASH Ack */ ASH_ACK_SENT = 126, /** Received ASH Nak */ ASH_NAK_RECEIVED = 127, /** Sent ASH Nak */ ASH_NAK_SENT = 128, /** Received ASH RST */ ASH_RST_RECEIVED = 129, /** Sent ASH RST */ ASH_RST_SENT = 130, /** ASH Status */ ASH_STATUS = 131, /** ASH TX */ ASH_TX = 132, /** ASH RX */ ASH_RX = 133, /** Failed to connect to CPC daemon or failed to open CPC endpoint */ CPC_ERROR_INIT = 134, /** No reset or error */ NO_ERROR = 255 } export declare enum EmberStackError { ROUTE_ERROR_NO_ROUTE_AVAILABLE = 0, ROUTE_ERROR_TREE_LINK_FAILURE = 1, ROUTE_ERROR_NON_TREE_LINK_FAILURE = 2, ROUTE_ERROR_LOW_BATTERY_LEVEL = 3, ROUTE_ERROR_NO_ROUTING_CAPACITY = 4, ROUTE_ERROR_NO_INDIRECT_CAPACITY = 5, ROUTE_ERROR_INDIRECT_TRANSACTION_EXPIRY = 6, ROUTE_ERROR_TARGET_DEVICE_UNAVAILABLE = 7, ROUTE_ERROR_TARGET_ADDRESS_UNALLOCATED = 8, ROUTE_ERROR_PARENT_LINK_FAILURE = 9, ROUTE_ERROR_VALIDATE_ROUTE = 10, ROUTE_ERROR_SOURCE_ROUTE_FAILURE = 11, ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE = 12, ROUTE_ERROR_ADDRESS_CONFLICT = 13, ROUTE_ERROR_VERIFY_ADDRESSES = 14, ROUTE_ERROR_PAN_IDENTIFIER_UPDATE = 15, NETWORK_STATUS_NETWORK_ADDRESS_UPDATE = 16, NETWORK_STATUS_BAD_FRAME_COUNTER = 17, NETWORK_STATUS_BAD_KEY_SEQUENCE_NUMBER = 18, NETWORK_STATUS_UNKNOWN_COMMAND = 19 } export declare enum EmberGPStatus { /** Success Status */ OK = 0, /** Match Frame */ MATCH = 1, /** Drop Frame */ DROP_FRAME = 2, /** Frame Unprocessed */ UNPROCESSED = 3, /** Frame Pass Unprocessed */ PASS_UNPROCESSED = 4, /** Frame TX Then Drop */ TX_THEN_DROP = 5, /** No Security */ NO_SECURITY = 6, /** Security Failure */ AUTH_FAILURE = 7 } /** Type of Ember software version */ export declare enum EmberVersionType { PRE_RELEASE = 0, ALPHA_1 = 17, ALPHA_2 = 18, ALPHA_3 = 19, BETA_1 = 33, BETA_2 = 34, BETA_3 = 35, GA = 170 } /** * For emberSetTxPowerMode and mfglibSetPower. * uint16_t */ export declare enum EmberTXPowerMode { /** * The application should call ::emberSetTxPowerMode() with the * txPowerMode parameter set to this value to disable all power mode options, * resulting in normal power mode and bi-directional RF transmitter output. */ DEFAULT = 0, /** * The application should call ::emberSetTxPowerMode() with the * txPowerMode parameter set to this value to enable boost power mode. */ BOOST = 1, /** * The application should call ::emberSetTxPowerMode() with the * txPowerMode parameter set to this value to enable the alternate transmitter * output. */ ALTERNATE = 2, /** * The application should call ::emberSetTxPowerMode() with the * txPowerMode parameter set to this value to enable both boost mode and the * alternate transmitter output. */ BOOST_AND_ALTERNATE = 3,// (BOOST | ALTERNATE) USE_TOKEN = 32768 } /** uint8_t */ export declare enum EmberKeepAliveMode { KEEP_ALIVE_SUPPORT_UNKNOWN = 0, MAC_DATA_POLL_KEEP_ALIVE = 1, END_DEVICE_TIMEOUT_KEEP_ALIVE = 2, KEEP_ALIVE_SUPPORT_ALL = 3 } /** This is the Extended Security Bitmask that controls the use of various extended security features. */ export declare enum EmberExtendedSecurityBitmask { /** * If this bit is set, the 'key token data' field is set in the Initial Security Bitmask to 0 (No Preconfig Key token). * Otherwise, the field is left as is. */ PRECONFIG_KEY_NOT_VALID = 1, /** * This denotes that the network key update can only happen if the network key update request is unicast and encrypted * i.e. broadcast network key update requests will not be processed if bit 1 is set */ SECURE_NETWORK_KEY_ROTATION = 2, /** This denotes whether a joiner node (router or end-device) uses a Global Link Key or a Unique Link Key. */ JOINER_GLOBAL_LINK_KEY = 16, /** * This denotes whether the device's outgoing frame counter is allowed to be reset during forming or joining. * If the flag is set, the outgoing frame counter is not allowed to be reset. * If the flag is not set, the frame counter is allowed to be reset. */ EXT_NO_FRAME_COUNTER_RESET = 32, /** This denotes whether a device should discard or accept network leave without rejoin commands. */ NWK_LEAVE_WITHOUT_REJOIN_NOT_ALLOWED = 64, /** This denotes whether a router node should discard or accept network Leave Commands. */ NWK_LEAVE_REQUEST_NOT_ALLOWED = 256, /** * This denotes whether a node is running the latest stack specification or is emulating R18 specs behavior. * If this flag is enabled, a router node should only send encrypted Update Device messages while the TC * should only accept encrypted Updated Device messages. */ R18_STACK_BEHAVIOR = 512, ZDO_LEAVE_FROM_NON_PARENT_NOT_ALLOWED = 4096 } /** This is the Initial Security Bitmask that controls the use of various security features. */ export declare enum EmberInitialSecurityBitmask { /** Enables Distributed Trust Center Mode for the device forming the network. (Previously known as ::EMBER_NO_TRUST_CENTER_MODE) */ DISTRIBUTED_TRUST_CENTER_MODE = 2, /** Enables a Global Link Key for the Trust Center. All nodes will share the same Trust Center Link Key. */ TRUST_CENTER_GLOBAL_LINK_KEY = 4, /** Enables devices that perform MAC Association with a pre-configured Network Key to join the network. It is only set on the Trust Center. */ PRECONFIGURED_NETWORK_KEY_MODE = 8, HAVE_TRUST_CENTER_UNKNOWN_KEY_TOKEN = 16, HAVE_TRUST_CENTER_LINK_KEY_TOKEN = 32, /** * This denotes that the ::EmberInitialSecurityState::preconfiguredTrustCenterEui64 has a value in it containing the trust center EUI64. * The device will only join a network and accept commands from a trust center with that EUI64. * Normally this bit is NOT set and the EUI64 of the trust center is learned during the join process. * When commissioning a device to join onto an existing network that is using a trust center and without sending any messages, * this bit must be set and the field ::EmberInitialSecurityState::preconfiguredTrustCenterEui64 must be populated with the appropriate EUI64. */ HAVE_TRUST_CENTER_EUI64 = 64, /** * This denotes that the ::EmberInitialSecurityState::preconfiguredKey is not the actual Link Key but a Root Key known only to the Trust Center. * It is hashed with the IEEE Address of the destination device to create the actual Link Key used in encryption. * This is bit is only used by the Trust Center. The joining device need not set this. */ TRUST_CENTER_USES_HASHED_LINK_KEY = 132, /** * This denotes that the ::EmberInitialSecurityState::preconfiguredKey element has valid data that should be used to configure * the initial security state. */ HAVE_PRECONFIGURED_KEY = 256, /** * This denotes that the ::EmberInitialSecurityState::networkKey element has valid data that should be used to configure * the initial security state. */ HAVE_NETWORK_KEY = 512, /** * This denotes to a joining node that it should attempt to acquire a Trust Center Link Key during joining. * This is necessary if the device does not have a pre-configured key, or wants to obtain a new one * (since it may be using a well-known key during joining). */ GET_LINK_KEY_WHEN_JOINING = 1024, /** * This denotes that a joining device should only accept an encrypted network key from the Trust Center (using its pre-configured key). * A key sent in-the-clear by the Trust Center will be rejected and the join will fail. * This option is only valid when using a pre-configured key. */ REQUIRE_ENCRYPTED_KEY = 2048, /** * This denotes whether the device should NOT reset its outgoing frame counters (both NWK and APS) when * ::emberSetInitialSecurityState() is called. * Normally it is advised to reset the frame counter before joining a new network. * However, when a device is joining to the