Status
When the configuration frame is accepted, the status field is set to 0x00.
However, command responses may return error codes within the status field of the ZCL response frame. The main error codes are:
| Error code | Error type | Comment |
|---|---|---|
| 0x80 | Malformed command | Most of the time, the command has got wrong number of fields. |
| 0x81 | Unsupported cluster command | The "cluster specific command" is not supported by the cluster. |
| 0x82 | Unsupported general command | The “General command” is not supported by the cluster |
| 0x86 | Unsupported attribute | The attribute is not supported or the command does not apply to the attribute. |
| 0x87 | Invalid field | One of the parameter fields is invalid. Frequent cause: Max < Min in configure reporting. |
| 0x88 | Invalid value | The request is incorrectly formatted. Frequent causes: Unexpected frame size, or Bad attribute type; or on batch case if a specific batch is not available. |
| 0x89 | Insufficient space | The parameter or the expected response is too big. Typical cause: attempting to read a very large attribute which is designed to be read through filters and scope specifiers, typically the TIC cluster. The client should limit the number of requested result fields. |
| 0x8c | Unreportable attribute | The “configure reporting” or “read reporting configuration” is not supported by the selected attribute. Either the attribute does not exist in the cluster or it is not reportable. |
| 0x8d | bad port | Invalid port specified When the option bit “NoHeaderPort” is used a port num can be specified it can’t be 0, 6 or 125 and > 223. |
| 0x8e | Frame too short | The request seems too short. Maybe some missing arguments or malformed request |
| 0x8f | Frame too long | The request seems too long. Maybe some extra arguments or malformed request.. |
| 0x90 | Unsupported type | The specified data type does not support the new multi criteria report configuration |
| 0x91 | Bad mode | The specified mode of criteria is not allowed. Only the reserved one 3 (0b11) should not be used. |
| 0x92 | Unsupported slot | The slot specified to define the criteria is out of range. |
| 0x93 | Bad event | Required Trigger event (Fall/Exceed) is incompatible with required mode (Delta, Treshold). |
| 0x94 | No available Actions | No possibility to launch actions. Waiting for availability. |
| 0x95 | Unsupported occurence | Occurrence High = Occurrence Low = 0 is forbidden |
| 0x96 | Read only data | The data/attribute is "read only". It can't be written. |
| 0x97 | Selected index of Action is invalid | The action index is invalid. Number of available action depends on the sensor type. At least 5 (Action 0 to 4). |
| 0x98 | Action list size is to long | The actions list of a criteria slot is too long. Size of action list per criteria slot depends on sensor type. At list 5 bytes. Sometimes upt o 19 bytes |
| 0x99 | Unsupported specific write | Trying to write an attribute that is not "writable" or does not exist |
| 0xc2 | Batch report: No free slot | The required batch configuration could not be added. The number of batch reportable slots is currently limited to 8. |
| 0xc3 | Batch report: Invalid Tag size. | At least one other batch report configuration uses a different Tag size. Use the same tag size for all batches configured on a device. |
| 0xc4 | Batch report: Duplicate tag label | A requested Tag label is already used by another batch report configuration. Choose another tag label. |
| 0xc5 | Batch report: Label out of range | Tag label is bigger than it should be according to Tag size. Tag label must be a number between : 0 and ([2^(Tag size ] – 1) |
| 0xc6 | Batch report: No change required | Required Batch configuration does not change curent one. (not really an error) |
