Other Parts Discussed in Thread: Z-STACK
1, Memory(heap) will overflow when send many packet of zdo-simple-desc-req and receive their zdo-simple-desc-rsp. (in zStackTask.c)
2, If an attribute is accessed from "zclReadWriteCB" callback, when zclReadWriteCB returns a un-success value, the responded "ZCL-Read-Rsp" packet and sent "ZCL-Report" packet can't be analysis by receiver.
3, If attributes are not listed in ascending order, ZCL-Disc-Attr-Rsp could not contain attribute whose attr-ID is lower than the one ahead it.
4, ZCL manufacturer code is not supported by z-stack, both manufacturer-code cluster and manufacturer-code attribute are not supported by z-stack.
5, BDB_Reporting can't support client-direction attributes.
1, APP can set a callback to detect the data-send-confirm event of ZDP-Request.
2, APP can set a callback to detect the data-send-confirm event of ZCL sending.
3, APP can set a callback to detect BDB_Reporing sending ZCL-Report command, and decide if it needs be delayed to sent out.
4，APP can set a callback to detect ZDP-Device-Announce sent Failed.