Bind Status Code: Not Supported.

Are you sure you use correct endpoint?

Discovered it works in one direction only. Bind Successful but shutter doesn't move with remote command.

Does remote send ZCL command?

Yes, sends Open, Close commands, I do receive them

Pacchetto: Incoming MSG
	A)ClusterID: 102
	B)Source Address: 3b67
	C)Link Quality Indicator: 171
	C.1)RSSI: -33
	D)Payload Length: 3
	D.1)Trans Sequence Number: 0
	D.2)Manufacturer Specific: false
	X)SrcEP: 1
	X)dstEP: 1
	E)Zigbee Command: 0
	E.2)OPEN SHUTTER

Where do you receive this? Shouldn’t the command be sent to window covering device?

I've bind with the coordinator as well

Why does it work on one direction only?

In your sniffer log, does your remote also send ZCL command to window covering device?

Let me check

I don't see any command.

Then, you should check if your binding command is success for window covering device.

In the sniffer I see a binding RSP = Success. Is it enough?

If you do binding to coordinator and window covering device on your remote device, you should send binding requests twice to your remote device. Do you see success on both binding requests?

Yes

Binding between Remote and Window Covering Device depends on the direction if success or not.

Ifi put DstAddr, srcAddr and srcEP the remote values It doesn't work, the other way around it works.

If you only do binding to window covering device, can you see ZCL command sent from your remote device?

Could you elaborate what do you mean by this?

I'm also trying to bind a philips light bulb to his dimmer switch. Still status 0x84.

Hello Ayman,

Have you removed BDB Finding & Binding during commissioning?  Otherwise some clusters could be binding automatically during the identify time.  Section 6.2 in SWRA615 has a small description about cluster types for binding.  There is a list of enabled bdb_ZclType[1/2]Clusters inside of the bdb_finding_and_binding.c file.  You can also review the Zigbee Fundamental Project Development and ZCL SLAs, which include some binding examples.  Here is the critical part of ZDO_ProcessBindUnbindReq:

  if ( !osal_ExtAddrEqual( SourceAddr.addr.extAddr, NLME_GetExtAddr()) ||
        (pReq->dstAddress.addrMode != Addr64Bit &&
         pReq->dstAddress.addrMode != AddrGroup) )
  {
    bindStat = ZDP_NOT_SUPPORTED;
  }

Where ZDP_NOT_SUPPORTED is 0x84.

Regards,
Ryan

How do I remove the BDB Finding & Binding during Commissioning? I'm using ZSTACK Monitor And Test API

It's not enabled in the ZNP by default, in applications for which MT has been added you can reference zclSample*_BdbCommissioningModes inside the zcl_sample*.c file.  I'm not certain this is the cause for ZDP_NOT_SUPPORTED.

Regards,
Ryan

Child threads were accidentally deleted.  Ayman had written:

Is binding only cluster 0x0102 enough?

On one direction I get status 0x84, what does it mean?

ZDP not supported is quite ambiguous, it could mean that it does not support bindings, or the cluster/endpoint is incorrect for the bind requested.  Since you are having such issue, it would be a good idea to capture sniffer logs of a working setup between the two devices, and further investigate their datasheets to further determine what the disparity could be.

Regards,
Ryan