The requested Key Negotiation Method was not accepted.
The device does not have binding table space to support the operation.
The requested device did not exist on a device following a child descriptor request to a parent.
The response was too large to fit in a single unfragmented message.
The device does not have storage space to support the requested operation.
The supplied request type was invalid.
The supplied endpoint was equal to 0x00 or 0xff.
The index in the received command is out of bounds.
A child descriptor was not available following a discovery request to a parent.
The unbind request was unsuccessful due to the coordinator or source device not having an entry in its binding table to unbind.
failure to match any suitable clusters.
The requested endpoint is not described by a simple descriptor.
The device has rejected the command due to security restrictions.
The device is not in the proper state to support the requested operation.
The requested optional feature is not supported on the target device.
A device with the address supplied to the NLME-ADDNEIGHBOR. request is already present in the neighbor table of the device on which the NLME-ADD-NEIGHBOR.request was issued.
Security processing has been attempted on an outgoing frame, and has failed because the security engine produced erroneous output.
An attempt to send a broadcast frame has failed because there is no room in the BTT.
An NLDE-DATA.request has failed due to insufficient buffering available.
The next higher layer has issued a request that is invalid or cannot be executed given the current state of the NWK layer.
An attempt was made to use a MAC Interface with a state that is currently set to FALSE (disabled) or that is unknown to the stack..
An invalid or out-of-range parameter has been passed to a primitive from the next higher layer.
A TLV was malformed or missing relevant information.
Security processing has been attempted on an outgoing frame, and has failed because the frame counter has reached its maximum value.
A required TLV for processing the request was not present.
An NLME-JOIN-DIRECTLY.request has failed because there is no more room in the neighbor table.
Security processing has been attempted on an outgoing frame, and has failed because no key was available with which to process it.
An NLME-JOIN.request has been issued in an environment where no networks are detectable.
An NLME-JOIN.request has been disallowed.
Reserved for future use.
An attempt to discover a route has failed due to a reason other than a lack of routing capacity.
An NLDE-DATA.request has failed due to a routing failure on the sending device or an NLME-ROUTE-DISCOVERY.request has failed due to the cause cited in the accompanying NetworkStatusCode.
An NLME-NETWORK-FORMATION.request has failed to start a network.
Used to indicate that an NLME-SYNC.request has failed at the MAC layer.
An NLME-LEAVE.request has failed because the device addressed in the parameter list is not in the neighbor table of the issuing device.
An NLME-GET.request or NLME-SET.request has been issued with an unknown attribute identifier.
The requested operation or transmission was completed successfully.
The device does not have table space to support the operation.
The request encountered a temporary failure but a retry at a later time should be attempted and may succeed.
A timeout has occurred with the requested operation.
ZDO response status.
Most responses to ZDO commands contain a status byte. The meaning of this byte is defined by the ZigBee Device Profile.
Zigbee Document – 05-3474-23 - Table 2-129. ZDP Enumerations Description
uint8_t