This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Can a Endpoint in a zigbee device search identifying endpoint in the same zigbee device by using “find-and-bind”?

Other Parts Discussed in Thread: Z-STACK

In zigbee network, a client endpoint of a zigbee device can search and bind the sever endpoint in any zigbee device in the same Network by using “find-and-bind”. but when there is one zigbee device in Network,and it has two or more endpoint, one is client(on-off switch) and the other is sever(on-off light),can the client endpoint bind with the sever endpoint by “find-and-bind”.

  • Technically a bind could be created through finding & binding if the node is both an initiator and target at the same time but I don't know if this would be automatically accomplished through Z-Stack.  ZDP_BindReq could be used to manually and definitively create the bind.

    Binding provides a mechanism for attaching an endpoint on one node to one or more endpoints on another node across the network, and the finding and binding process is part of commissioning. It does not really correlate to inter-node communication. You can use event callbacks to perform the desired endpoint actions within the node without the use of binding.

    Regards,
    Ryan

  • So I can understand that in zigbee 3.0 protocol, "find-and-bind" is controlled by "BDB commission", and it beeing an initiator or a target is determined by the set(active) Endpoint's Cluster list. But if I want 2 Endpoint communicate with each other by double-work, I muster fill the out-cluster-list and in-cluster-list of these Endpoin with same cluster-ID, and I make them binding each other by "find-and-bind", what will happen? Both "2 Endpoin in a same Node" and "2 Endpoin in different Node".
  • As stated previously, I am not sure if the bind will be created automatically through the find-and-bind process since this is not its intended purpose and such application is not commonly considered. Please try it out and see what happens, if it doesn't work then you should still be able to accomplish a manual bind (ZDP_BindReq).

    Regards,
    Ryan