Other Parts Discussed in Thread: Z-STACK
Hi team,
Here're few questions from the customer may need your help:
1)The customer wants the parent node to force a device that has dropped (no messages, child, low-power terminal) out of the network and only clear the information about the individual child nodes that the parent node records and then enables the subnodes to be networked after calling bdb_resetLocalAction(), what should they do? For example, delete the corresponding device after a heartbeat packet has not been received for a long time.
Cause of problem: When the parent uses this function NLME_LeaveReq() to take the child out of the network, the child is powered down and cannot request data from the parent node. Messages sent to the end device require the terminal to request data from the parent node, so the parent node cannot issue a Leave instruction.
2) The parent node stores the data sent to the child node and waits for the child node to request the data and issue it. Where are these data stored? How to tell the application that data has been successfully released after a child node poll?
Cause of problem: While data is sent, it is returned successfully, but the data is actually stored in the parent node and is waiting for the child node to poll.
Could you help check this case? Thanks.
Best Regards,
Cherry
