zigbee-herdsman 0.50.1 → 0.52.0

package/dist/adapter/ember/enums.d.ts

@@ -1,4 +1,4 @@
-/** Status Defines */
+/** Status Codes contains error and status code definitions used by Simplicity SDK software components and stacks. */
 export declare enum SLStatus {
     /** No error. */
     OK = 0,
@@ -162,6 +162,34 @@ export declare enum SLStatus {
     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 */
@@ -554,417 +582,77 @@ export declare enum SLStatus {
     /** 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,
+    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,
     /**
-     * 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,
+     * 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. */
-    CHANNEL_CHANGED = 155,
+    ZIGBEE_CHANNEL_CHANGED = 3095,
     /** The network has been opened for joining. */
-    NETWORK_OPENED = 156,
+    ZIGBEE_NETWORK_OPENED = 3096,
     /** 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,
+    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).
+     * Network Key in-the-clear when an encrypted Network Key was required. (::EMBER_REQUIRE_ENCRYPTED_KEY)
      */
-    RECEIVED_KEY_IN_THE_CLEAR = 172,
+    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. */
-    NO_NETWORK_KEY_RECEIVED = 173,
+    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. */
-    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,
+    ZIGBEE_NO_LINK_KEY_RECEIVED = 3100,
     /**
-     * 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
+     * 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.
      */
-    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.
-     */
-    APPLICATION_ERROR_0 = 240,
-    APPLICATION_ERROR_1 = 241,
-    APPLICATION_ERROR_2 = 242,
-    APPLICATION_ERROR_3 = 243,
-    APPLICATION_ERROR_4 = 244,
-    APPLICATION_ERROR_5 = 245,
-    APPLICATION_ERROR_6 = 246,
-    APPLICATION_ERROR_7 = 247,
-    APPLICATION_ERROR_8 = 248,
-    APPLICATION_ERROR_9 = 249,
-    APPLICATION_ERROR_10 = 250,
-    APPLICATION_ERROR_11 = 251,
-    APPLICATION_ERROR_12 = 252,
-    APPLICATION_ERROR_13 = 253,
-    APPLICATION_ERROR_14 = 254,
-    APPLICATION_ERROR_15 = 255
+    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 {
@@ -1151,6 +839,24 @@ export declare enum EmberStackError {
     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,
@@ -1162,12 +868,6 @@ export declare enum EmberVersionType {
     BETA_3 = 35,
     GA = 170
 }
-export declare enum EmberLeaveRequestFlags {
-    /** Leave and rejoin. */
-    AND_REJOIN = 128,
-    /** Leave. */
-    WITHOUT_REJOIN = 0
-}
 /**
  * For emberSetTxPowerMode and mfglibSetPower.
  * uint16_t
@@ -1253,13 +953,13 @@ export declare enum EmberInitialSecurityBitmask {
      * 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
@@ -2169,4 +1869,25 @@ export declare enum EmberGpSinkTableEntryStatus {
     /** The proxy table entry is not in use. */
     UNUSED = 255
 }
+export declare enum EmberLeaveNetworkOption {
+    /** Leave with no option. */
+    WITH_NO_OPTION = 0,
+    /** Leave with option rejoin. */
+    WITH_OPTION_REJOIN = 32,
+    /** Leave is requested. */
+    IS_REQUESTED = 64
+}
+/**
+ * Packet transmit priorities in terms of getting into the MAC queue.
+ *
+ * SL_802154_TRANSMIT_PRIORITY_HIGH High priority headers go on the front of the queue.
+ * SL_802154_TRANSMIT_PRIORITY_NORMAL  Normal priority headers go on the back of the queue.
+ * SL_802154_TRANSMIT_PRIORITY_SCAN_OKAY Normally, only beacon requests and orphan notifications can be sent during a scan.
+ * They are submitted with SCAN_OKAY and go on the front of the queue. Other packets could be submitted with this priority, but it is not recommended.
+ */
+export declare enum EmberTransmitPriority {
+    HIGH = 0,
+    NORMAL = 1,
+    SCAN_OKAY = 2
+}
 //# sourceMappingURL=enums.d.ts.map