• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 812 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.

[CC2562P] Strange Cluster

Luca Vetri
Intellectual 560 points

Other Parts Discussed in Thread: Z-STACK

Hi,

I've bought a NodeOn Roller Shutter Node and everything works fine. (Link To It)

My only question is: when I plug the relay I receive a 0x4481 Message with ClusterID 0x1000. Looking at ZigBee Cluster PDF I cant seem to understand 

Also: Do you think there is any way to get an input from the relay node regarding the percentage of roller shutter and so on. I've binded with 0x102 but nothing.

fe 27 44 81 0 0 0 10 a 4d 1 1 0 cc 0 37 4 46 0 0 13 9 1 40 7 b2 a4 fe ff ea 35 90 a 4d 1 4 1 2 2 1 a 4d 1d 10

Edit: Looking at the clusters in input: 

<RX>11:52:31.72 COM4 ZDO_SIMPLE_DESC_RSP (0x4584)
    SrcAddr: 0x581D
    Status: ZDP_SUCCESS (0x0)
    NwkAddr: 0x581D
    Len: 0x18
    Endpoint: 0x01
    ProfileID: 0x0104
    DeviceID: 0x0202
    DeviceVersion: 1 (0x1)
    NumInClusters: 0x07
    InClusterList: 0x0000, 0x0003, 0x0004, 0x0005, 0x0102, 0x1000, 0xFC57
    NumOutClusters: 0x01
    OutClusterList: 0x0019

What kind of device ID is 0x0066? Can I find a complete list online?

<TX>11:56:36.72 COM4 ZDO_SIMPLE_DESC_REQ (0x2504)
    DstAddr: 0x581D
    NWKAddrOfInterest: 0x581D
    Endpoint: 0xF2

<RX>11:56:36.73 COM4 ZDO_SIMPLE_DESC_REQ_SRSP (0x6504)
    Status: afStatus_SUCCESS (0x0)

<RX>11:56:36.74 COM4 ZDO_SIMPLE_DESC_RSP (0x4584)
    SrcAddr: 0x581D
    Status: ZDP_SUCCESS (0x0)
    NwkAddr: 0x581D
    Len: 0x0C
    Endpoint: 0xF2
    ProfileID: 0xA1E0
    DeviceID: 0x0066
    DeviceVersion: 1 (0x1)
    NumInClusters: 0x01
    InClusterList: 0x0021
    NumOutClusters: 0x01
    OutClusterList: 0x0021

Best Regards,

Luca Vetri

  • 0
    Guru 735695 points

    0x1000 is ZLL commissioning cluster.

  • 0 in reply to YiKai Chen
    Intellectual 560 points

    What is it about? 

    Is it useful to me for any attribute reporting?

  • 0
    Intellectual 560 points

    How Do I Control A Relay Switch via Z-Tool? I imagine I need to use AF_DATA_REQUEST but I don't really know what to insert and how to control it.

    Active EndPoints: 0x01 and 0xF2

    On the 0x01 EndPoint as InputCluster we have 0x0102 and OutPut Cluster: 0x0019

  • 0 in reply to Luca Vetri
    Guru 735695 points

    You can refer to ZCL specification to compose ZCLwindow covering command with AF_DATA_REQUEST to control it.

  • 0 in reply to YiKai Chen
    Intellectual 560 points

    Can you help me with formatting the command?

    Does the 2nd bit of frame control have to be activated?

    An example of command i tried is: 0x08 00 05 21 10   where 0x21 is uint8 and 10 is the percentage. (0x05 is Go-To-Lift Percentage)

  • 0 in reply to Luca Vetri
    TI__Guru**** 220447 points

    You do not need the ZCL_CLUSTER_ID_TOUCHLINK without Touchlink commissioning and is is not useful for attribute reporting.  Endpoint 0xF2 is reserved for Green Power.  Device ID is ZCL_DEVICEID_WINDOW_COVERING and Cluster 0x0102 is ZCL_CLUSTER_ID_CLOSURES_WINDOW_COVERING, the attribute and commands for controlling and adjusting automatic window coverings such as drapery motors, automatic shades, and blinds.  Z-Stack provides a zcl_closures module so from this it may be possible to further understand how packets should be structured and what values to send.  Please refer to zclClosures_Send[UpOpen/DownClose/SendStop] -> zclClosures_WindowCoveringSimpleReq, zclClosures_SendGoTo[Lift/Tilt]Value -> zclClosures_WindowCoveringSendGoToValueReq, and zclClosures_SendGoTo[Lift/Tilt]Percentage -> zclClosures_WindowCoveringSendGoToPercentageReq.  From these it should be possible to find a command and format which works for this device.  Please make sure to have a sniffer running to help debug, furthermore it would be useful to sniff the interactions of a known working system to better understand the intended packet structure and interactions.  0x21 is ZCL_DATATYPE_UINT16, not ZCL_DATATYPE_UINT8 (that would be 0x20), and perhaps it would be better to start with a simple up/down and work up to a percentage.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 560 points

    Thank you so much.

    I tried this via Z-Tool. 

    <TX>03:34:39.41 COM4 AF_DATA_REQUEST (0x2401)
    DstAddr: 0xA6AD
    DestEndpoint: 0x01
    SrcEndpoint: 0x01
    ClusterID: 0x0102
    TransID: 0x01
    Options: 0x00
    Radius: 0x1E
    Len: 0x03
    Data: ... (0x01, 0x01, 0x00)

<RX>03:34:39.42 COM4 AF_DATA_REQUEST_SRSP (0x6401)
    Status: afStatus_SUCCESS (0x0)

<RX>03:34:39.43 COM4 AF_DATA_CONFIRM (0x4480)
    Status: afStatus_SUCCESS (0x0)
    Endpoint: 0x01
    TransID: 0x01

    But doesn't seem to answer. I started with 0x00.

  • 0 in reply to Luca Vetri
    TI__Guru**** 220447 points

    That data packet is correct for the ZCL header (frame control, sequence number, command), and no value should be necessary.  This should be structured just like a COMMAND_ON_OFF_TOGGLE command for the ZCL_CLUSTER_ID_GENERAL_ON_OFF cluster.  I have no further advice since the command is sent but a response is not returned, especially without a sniffer log.  As mentioned previously, you should evaluate a known working setup or contact the device manufacturer for more details.

    Regards,
    Ryan