• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 1456 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

unicast in a network with one Zigbee coordinator and multiple Zigbee routers

Edge Goldberg
Intellectual 955 points


I am a beginner here. I am working on an application ( like STAR network ) using Sample Switch application as a Zigbee Coordinator and Sample Light application on more than one Zigbee Routers. I want to control the light ( on/off ) on a single router amongst the many routers in the network. But after the invocation of EZ-mode the ( on/off state ) light on all the routers are changing their states after sending the command from the coordinator. How to resolve this issue?
 
Is address based packet filtering already enabled in this stack? If so how can I use unicast?

  • 0
    Guru 735695 points
    When you enable EZ-mode, device will do binding automatically and I think that is why your ZC (Sample Switch) sending command to all ZR (Sample Light). You can try to disable EZ-mode on your Sample Switch and Sample Light. In this way, SW2 will become end device binding and you can do binding between Sample Switch and the only Light that you want to control.
  • 0 in reply to YiKai Chen
    Intellectual 955 points
    Thank you Mr. Yikai. I have a couple of questions.
    1. Is it possible for two devices to communicate without binding , at the application level ( specific end point ) ?
    2. I want to control the specific ROUTER out of many ROUTERs. Is it possible to control the specific Router using its address by Coordinator?
  • 0 in reply to Edge Goldberg
    Guru 735695 points
    Yes. You have to know the destination short address and endpoint in this case. When a device joins Zigbee network, it will broadcast end node announcement with short address. You can receive end node announcement on coordinator and use API ZDP_ActiveEPIFReqs() to request its endpoint. After you have the destination address and endpoint information, you can send data to it with API AF_DataRequest().
  • 0 in reply to YiKai Chen
    Intellectual 955 points
    Sir, I am unable to find any API where the device is announcing its short address, can you help me on this?
  • 0 in reply to Edge Goldberg
    Guru 735695 points
    You can register Device_annce by using "ZDO_RegisterForZDOMsg(task_id, Device_annce);" in your init function and process "case Device_annce:" in XXX_ProcessZDOMsgs().
  • 0 in reply to YiKai Chen
    Intellectual 955 points
    Thank you Mr. YiKai.
  • 0 in reply to YiKai Chen
    Intellectual 955 points

    While working with the SampleSwitch (as ZC) and SampleLight (as ZR) applications, I have already defined, known endpoint as 8 for both. I used your suggested method to get the destination short address. As I already know the endpoint, I filled the endpoint descriptor fields and only Endpoint field in the simple descriptor. I kept the other simple descriptor fields to the garbage value. Also in the AF_DataRequest(), I passed destination address and source endpoint only with length of data equal to 10 bytes, option field with AF_SKIP_ROUTING.
    Why am I not able to get the data on the SampleLight (as ZR) with case AF_INCOMING_MSG_CMD used for accessing the SYS_EVENT_MSG?
    Also whenever I generate the command zclGeneral_SendOnOff_Cmd_Toggle () in sample switch at the inner level this function actually uses AF_DataRequest(). In this case why it cannot go to the case AF_INCOMING_MSG_CMD in the SampleLight?

    It first goes to the zclSampleLight_OnOffCB(), after finishing this it is generating the SYS_EVENT_MSG with hdr to the default case statement.