• State
  • Locked Locked
  • Replies 12 replies
  • Subscribers 56 subscribers
  • Views 920 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.

ZigBee network deployment: Could not bind Endpoints

Prasoon Sharma
Prodigy 75 points

Other Parts Discussed in Thread: Z-STACK

Hello everyone,

I've been working on a zigbee network consisting of one coordinator(TI coordinator module) and two router devices, a dimmer and a touch a keypad to control that dimmer, both from same manufacturer(not TI). I'm using Z-Tool v2.0.6 and Z-Stack version is 2.7.1

I'm stuck, so I've some question that I've asked below.

I've also attached the logs.

N/W & IEEE address(Dimmer): 0xDC1D, 0x000D6F000C6B7662

N/W & IEEE address(Keypad): 0x7357, 0x000D6F000207B1D6

 

Start Time: 2/1/2022 7:38:55 PM

 

<TX>07:39:28.48 COM7 SYS_OSAL_NV_WRITE (0x2109)

    Id: 0x0003

    Offset: 0x00

    Len: 0x01

    Value: . (0x03)

 

<RX>07:39:28.51 COM7 SYS_OSAL_NV_WRITE_SRSP (0x6109)

    Status: SUCCESS (0x0)

 

<TX>07:39:30.11 COM7 SYS_RESET (0x4100)

    Type: 0x01 (SOFT RESET) (0x1)

 

<RX>07:39:36.7 COM7 SYS_RESET_RESPONSE (0x4180)

    Reason: 0x02

    TransportRev: 0x02

    Product: 0x00

    MajorRel: 0x02

    MinorRel: 0x06

    HwRev: 0x03

 

<TX>07:41:34 COM7 SYS_OSAL_NV_WRITE (0x2109)

    Id: 0x008F

    Offset: 0x00

    Len: 0x01

    Value: . (0x01)

 

<RX>07:41:34.01 COM7 SYS_OSAL_NV_WRITE_SRSP (0x6109)

    Status: SUCCESS (0x0)

 

<TX>07:41:45.09 COM7 ZB_START_REQUEST (0x2600)

 

<RX>07:41:45.85 COM7 ZB_START_REQUEST_RSP (0x6600)

 

<RX>07:41:45.85 COM7 ZDO_STATE_CHANGE_IND (0x45C0)

    State: 8 (0x8)

 

<RX>07:41:46.35 COM7 ZDO_STATE_CHANGE_IND (0x45C0)

    State: 8 (0x8)

 

<RX>07:41:46.86 COM7 ZDO_STATE_CHANGE_IND (0x45C0)

    State: 8 (0x8)

 

<RX>07:41:47.38 COM7 ZDO_STATE_CHANGE_IND (0x45C0)

    State: 8 (0x8)

 

<RX>07:41:48.4 COM7 ZDO_STATE_CHANGE_IND (0x45C0)

    State: 9 (0x9)

 

>>>>>>>>>> I gave the JOIN(as stated on the remote key) command to both the routers from the remote provided by the manufacturer and both the device(router) joins the network. Below are the logs that shows the indication.

(Also, the coordinator receives some messages, when I now press the keys on keypad, but could not show it since I've not registered the AF on coordinator)

Q 1: Are these devices got binded to the coordinator or they just joined the zigbee network?

 

*** WARNING ***

    Unsupported or unformatted message received.  Raw data:

    0C 45 CA 57 73 D6 B1 07 02 00 6F 0D 00 00 00

 

<RX>07:42:14.66 COM7 ZDO_END_DEVICE_ANNCE_IND (0x45C1)

    SrcAddr: 0x7357

    NwkAddr: 0x7357

    IEEEAddr: 0x000D6F000207B1D6

    Capabilities: 0x8E

 

*** WARNING ***

    Unsupported or unformatted message received.  Raw data:

    0C 45 CA 1D DC 62 76 6B 0C 00 6F 0D 00 00 00

 

<RX>07:42:17.76 COM7 ZDO_END_DEVICE_ANNCE_IND (0x45C1)

    SrcAddr: 0xDC1D

    NwkAddr: 0xDC1D

    IEEEAddr: 0x000D6F000C6B7662

    Capabilities: 0x8E

 >>>>>>>>>>> Below are the logs to show the forum the active EPs and Simple Descriptor of all those EPs of both the router devices.

<TX>07:42:48.51 COM7 ZDO_ACTIVE_EP_REQ (0x2505)

    DstAddr: 0x7357

    NWKAddrOfInterest: 0x7357

 

<RX>07:42:48.53 COM7 ZDO_ACTIVE_EP_REQ_SRSP (0x6505)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:42:48.54 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0x7357

    Relay Count: 0x00

    Relay List

 

<RX>07:42:48.6 COM7 ZDO_ACTIVE_EP_RSP (0x4585)

    SrcAddr: 0x7357

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0x7357

    ActiveEPCount: 0x03

    ActiveEPList: ... (0x01, 0x02, 0xC4)

 

<TX>07:43:10.37 COM7 ZDO_ACTIVE_EP_REQ (0x2505)

    DstAddr: 0xDC1D

    NWKAddrOfInterest: 0xDC1D

 

<RX>07:43:10.39 COM7 ZDO_ACTIVE_EP_REQ_SRSP (0x6505)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:43:10.41 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0xDC1D

    Relay Count: 0x00

    Relay List

 

<RX>07:43:10.45 COM7 ZDO_ACTIVE_EP_RSP (0x4585)

    SrcAddr: 0xDC1D

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0xDC1D

    ActiveEPCount: 0x03

    ActiveEPList: ... (0x01, 0x02, 0xC4)

 

<TX>07:43:46.44 COM7 ZDO_SIMPLE_DESC_REQ (0x2504)

    DstAddr: 0x7357

    NWKAddrOfInterest: 0x7357

    Endpoint: 0x01

 

<RX>07:43:46.46 COM7 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:43:46.47 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0x7357

    Relay Count: 0x00

    Relay List

 

<RX>07:43:46.52 COM7 ZDO_SIMPLE_DESC_RSP (0x4584)

    SrcAddr: 0x7357

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0x7357

    Len: 0x0A

    Endpoint: 0x01

    ProfileID: 0x0104

    DeviceID: 0x0101

    DeviceVersion: VER_100 (0x0)

    NumInClusters: 0x00

    InClusterList

    NumOutClusters: 0x01

    OutClusterList: 0x0019

 

<TX>07:43:53.05 COM7 ZDO_SIMPLE_DESC_REQ (0x2504)

    DstAddr: 0x7357

    NWKAddrOfInterest: 0x7357

    Endpoint: 0x02

 

<RX>07:43:53.06 COM7 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:43:53.08 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0x7357

    Relay Count: 0x00

    Relay List

 

<RX>07:43:53.13 COM7 ZDO_SIMPLE_DESC_RSP (0x4584)

    SrcAddr: 0x7357

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0x7357

    Len: 0x0A

    Endpoint: 0x02

    ProfileID: 0xC25D

    DeviceID: 0x0001

    DeviceVersion: VER_100 (0x0)

    NumInClusters: 0x01

    InClusterList: 0x0001

    NumOutClusters: 0x00

    OutClusterList

 

<TX>07:43:58.68 COM7 ZDO_SIMPLE_DESC_REQ (0x2504)

    DstAddr: 0x7357

    NWKAddrOfInterest: 0x7357

    Endpoint: 0xC4

 

<RX>07:43:58.7 COM7 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:43:58.71 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0x7357

    Relay Count: 0x00

    Relay List

 

<RX>07:43:58.76 COM7 ZDO_SIMPLE_DESC_RSP (0x4584)

    SrcAddr: 0x7357

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0x7357

    Len: 0x0A

    Endpoint: 0xC4

    ProfileID: 0xC25D

    DeviceID: 0x0001

    DeviceVersion: VER_100 (0x0)

    NumInClusters: 0x01

    InClusterList: 0x0001

    NumOutClusters: 0x00

    OutClusterList

 

<TX>07:44:19.14 COM7 ZDO_SIMPLE_DESC_REQ (0x2504)

    DstAddr: 0xDC1D

    NWKAddrOfInterest: 0xDC1D

    Endpoint: 0x01

 

<RX>07:44:19.15 COM7 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:44:19.17 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0xDC1D

    Relay Count: 0x00

    Relay List

 

<RX>07:44:19.22 COM7 ZDO_SIMPLE_DESC_RSP (0x4584)

    SrcAddr: 0xDC1D

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0xDC1D

    Len: 0x0A

    Endpoint: 0x01

    ProfileID: 0x0104

    DeviceID: 0x0101

    DeviceVersion: VER_100 (0x0)

    NumInClusters: 0x00

    InClusterList

    NumOutClusters: 0x01

    OutClusterList: 0x0019

 

<TX>07:44:25.7 COM7 ZDO_SIMPLE_DESC_REQ (0x2504)

    DstAddr: 0xDC1D

    NWKAddrOfInterest: 0xDC1D

    Endpoint: 0x02

 

<RX>07:44:25.71 COM7 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:44:25.73 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0xDC1D

    Relay Count: 0x00

    Relay List

 

<RX>07:44:25.77 COM7 ZDO_SIMPLE_DESC_RSP (0x4584)

    SrcAddr: 0xDC1D

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0xDC1D

    Len: 0x0A

    Endpoint: 0x02

    ProfileID: 0xC25D

    DeviceID: 0x0001

    DeviceVersion: VER_100 (0x0)

    NumInClusters: 0x01

    InClusterList: 0x0001

    NumOutClusters: 0x00

    OutClusterList

 

<TX>07:44:40.92 COM7 ZDO_SIMPLE_DESC_REQ (0x2504)

    DstAddr: 0xDC1D

    NWKAddrOfInterest: 0xDC1D

    Endpoint: 0xC4

 

<RX>07:44:40.93 COM7 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:44:40.95 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0xDC1D

    Relay Count: 0x00

    Relay List

 

<RX>07:44:41 COM7 ZDO_SIMPLE_DESC_RSP (0x4584)

    SrcAddr: 0xDC1D

    Status: ZDP_SUCCESS (0x0)

    NwkAddr: 0xDC1D

    Len: 0x0A

    Endpoint: 0xC4

    ProfileID: 0xC25D

    DeviceID: 0x0001

    DeviceVersion: VER_100 (0x0)

    NumInClusters: 0x01

    InClusterList: 0x0001

    NumOutClusters: 0x00

    OutClusterList

 >>>>>> Sending AF-REGISTER to coordinator to see the received messages on the Z-Tool screen whenever I press the keypad.

Also FYI, whenever I want to control the dimmer(control bulb's brightness) or keypad(key press through commands) through coordinator, I need to send messages to EP 2 on both the devices but , when i receive messages from keypad or dimmer the messages shows the the source and dest EP as 1(shown in logs below).

Q2: WHY SO??

Also, when I send control commands from coordinator, the cluster ID that I pass is 0x009A(because only that cluster id could control the dimmer and keypad and the AF_INCOMING_MSG also shows the ClusterID =0x009A).

<TX>07:45:04.07 COM7 AF_REGISTER (0x2400)

    EndPoint: 0x01

    AppProfID: 0x0104

    AppDeviceId: 0x0000

    AppDevVer: 0x00

    LatencyReq: NO_LATENCY_REQS (0x0)

    AppNumInClusters: 0x09

    AppInClusterList: 0x0000, 0x0001, 0x0003, 0x0006, 0x0008, 0x009A, 0x0004, 0x0005, 0x0007

    AppNumOutClusters: 0x09

    AppOutClusterList: 0x0000, 0x0001, 0x0003, 0x0006, 0x0008, 0x009A, 0x0004, 0x0005, 0x0007

 

<RX>07:45:04.08 COM7 AF_REGISTER_SRSP (0x6400)

    Status: afStatus_SUCCESS (0x0)

 

<TX>07:45:08.74 COM7 AF_REGISTER (0x2400)

    EndPoint: 0x02

    AppProfID: 0x0104

    AppDeviceId: 0x0000

    AppDevVer: 0x00

    LatencyReq: NO_LATENCY_REQS (0x0)

    AppNumInClusters: 0x09

    AppInClusterList: 0x0000, 0x0001, 0x0003, 0x0006, 0x0008, 0x009A, 0x0004, 0x0005, 0x0007

    AppNumOutClusters: 0x09

    AppOutClusterList: 0x0000, 0x0001, 0x0003, 0x0006, 0x0008, 0x009A, 0x0004, 0x0005, 0x0007

 

<RX>07:45:08.76 COM7 AF_REGISTER_SRSP (0x6400)

    Status: afStatus_SUCCESS (0x0)

 >>>>>> Now I want to control the dimmer through keypad, so in my opinion I should bind the EP2 on keypad to EP2 on dimmer(since the communication occurs on EP2 on both devices when i send the control commands from coordinator). But, when I try to bind the EP on both the devices, only EP1 on keypad gets binded to EP2 on dimmer(Binding EP2 on both does not shows ZDP_SUCCESS), and still I cannot control the dimmer from the keypad.

Q3: Can anybody please guide me on where I'm wrong. I'm stuck, please help.

<TX>07:46:04.19 COM7 ZDO_BIND_REQ (0x2521)

    DstAddr: 0x7357

    SrcAddress: 0x000D6F000207B1D6

    SrcEndpoint: 0x01

    ClusterID: 0x0001

    BindAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)

    BindAddr: bvk..o.. (0x62, 0x76, 0x6B, 0x0C, 0x00, 0x6F, 0x0D, 0x00)

    BindEndpoint: 0x02

 

<RX>07:46:04.21 COM7 ZDO_BIND_REQ_SRSP (0x6521)

    Status: afStatus_SUCCESS (0x0)

 

<RX>07:46:04.22 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0x7357

    Relay Count: 0x00

    Relay List

 

<RX>07:46:04.28 COM7 ZDO_BIND_RSP (0x45A1)

    SrcAddr: 0x7357

    Status: ZDP_SUCCESS (0x0)

 

<RX>07:46:08.57 COM7 ZDO_SRC_RTG_IND (0x45C4)

    DstAddr: 0x7357

    Relay Count: 0x00

    Relay List

 

<RX>07:46:23.78 COM7 AF_INCOMING_MSG (0x4481)

    GroupID: 0x0000

    ClusterID: 0x009A

    SrcAddr: 0x7357

    SrcEndpoint: 0x01

    DstEndpoint: 0x01

    WasBroadcast: 0x00

    LinkQuality: 0x9C

    SecurityUse: 0x00

    Timestamp: 0x00137620

    TransSeqNumber: 0x00

    Len: 0x05

    Data: .x... (0x11, 0x78, 0xCF, 0x06, 0x00)

I just want to know if I'm wrong anywhere or there is something wrong with the dimmer and keypad.

I would be thankful to anybody who could be of any help.

 

  • 0
    Guru 735695 points

    Cluster ID 0x0001 should be power configuration cluster. I suppose you should do binding to endpoint with level control , cluster ID 0x0008, for dimmer control.

  • 0 in reply to YiKai Chen
    Prodigy 75 points

    But none of the EPs on both the devices has 0x0008 cluster id in InClusterList or OutClusterList. You can see that in the responses of ZDO_SIMPLE_DESC_RSP

  • 0 in reply to Prasoon Sharma
    Guru 735695 points

    If the device doesn’t support level control cluster, I don’t think you can use it to send level control commands.

  • 0 in reply to YiKai Chen
    Prodigy 75 points

    I'm able to control the level when I send level-set data from coordinator to the dimmer's EP2 using clusterID 0x009A. But when I want to control the dimmer using the keypad, the ZDO_BIND_REQ does not respond ZDP_SUCCESS when I give 0x009A in  ClusterID param, also I'm cannot see any cluster like 0x009A in InclusterList or OutClusterList on any EP of both the device. So, I just want to know if there is something wrong with the devices?

    I found about this 0x009A cluster also through the AF_INCOMING_MSG because in that the ClusterID param is 0x009A(you can check the logs above).

  • 0 in reply to Prasoon Sharma
    Guru 735695 points

    Then, I suppose you should binding to cluster ID 0x009a.

  • 0 in reply to YiKai Chen
    Prodigy 75 points

    When I use clusterID 0x009A while binding, the 'status' attribute in ZDO_BIND_RSP shows 0x8c and not ZDP_SUCCESS

  • 0 in reply to Prasoon Sharma
    Prodigy 75 points

    Also, could you please check the logs if I'm am sending any wrong commands anywhere.

  • 0 in reply to Prasoon Sharma
    Guru 735695 points

    It’s not easy to read console log. Can you setup sniffer and provide sniffer log?

  • 0
    TI__Guru**** 220427 points

    Hello Prasoon,

    Both devices have identical Simple Descriptor Responses, the main endpoint of importance being 0x01 which has a Profile ID of 0x0104/ZCL_HA_PROFILE_ID, Device ID of 0x0101/ZCL_DEVICEID_DIMMABLE_LIGHT, and Cluster ID of 0x0019 (possibly OTA Upgrade).  I don't know where the Cluster ID 0x009A originates since it does not show up on the Simple Descriptor Response for this endpoint, and your Bind Requests show Cluster ID 0x0001.  If the endpoints/clusters of both devices are identical then I would not expect they should be bound together as they are both clients.  Also, 0x8C indicates a ZCL_STATUS_UNREPORTABLE_ATTRIBUTE (not shown in the console log).

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 75 points

    I'm confused. I got your point but when I want to control both the devices by sending commands(AF_DATA_REQUEST) from my ZC(I register the AF on my ZC for that), both the devices(dimmer & keypad) could only communicate on EP2 with profile 0x0104 and cluster 0x009A(but when we see simple desc of EP2 on both the devices, it has profile 0xC25D & cluster 0x0001). And when data comes from the keypad(AF_INCOMING_MSG), it comes from EP1.

    I don't understand what is happening.

    Also, regarding the binding, only EP1 on keypad binding to EP2 on dimmer using ClusterID 0x0001 comes up with ZDP_SUCCESS, all other combinations gives 0x8C(ZCL_STATUS_UNREPORTABLE_ATTRIBUTE, as stated by you), and I could not understand how that is happening.

    Is it something wrong with the device?

  • 0 in reply to Prasoon Sharma
    Guru 735695 points

    According to your console log, only endpoint 1 of both devices uses HA profile (0x0104) and another two endpoints, 0x02, 0xC4 use 0xC25D as profile ID which I suppose is custom profile from manufacturer. Maybe you should contact manufacturer for device details.

  • 0 in reply to Prasoon Sharma
    TI__Guru**** 220427 points

    I agree with YK, it is hard to know more without further understanding the manufacturer's intended use of these devices.  If they are already operational in a system/network outside of the Z-Stack ZNP firmware & Z-Tool interface, perhaps you can set up a new sniffer log within a working environment to further understand what over-the-air communication should be taking place.

    Regards,
    Ryan