• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 583 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.

CC2652P: Some information about Zigbee Standard (such as manufacturer code, attributes, commands) got from silicon labs

Aries Lord
Genius 5450 points

Part Number: CC2652P
Other Parts Discussed in Thread: Z-STACK

I don't know Silicon-Labs be right or wrong. These information get from its SDK

1, One zigbee-device can own more than one manufacturer code.

2, Same clusterID and a same attitudeID, but manufacturer code is different. The are two different attributes, but they can appear in same device.

3, Same clusterID and same attribute-ID, but one is Server-direction and the other is Client-direction, they are allowed to be with different data-type.

4, Find-and-Bind support one Endpoint binding its target in the same device.

5, Many attributes in a same cluster are set BDB-Reporting, they can be reported at different time. If only one of them value changed, only this one was reported.

  • 0
    TI__Guru**** 223887 points

    Hi Aries,

    I recommend that you review the Zigbee PRO R22/2017 and Zigbee Cluster Library (ZCL) v7 Specifications to check/verify this information.  As manufacturer-specific functionality is not supported by default in Z-Stack, it would be the developer's responsibility to implement these changes to the ZCL layer themselves.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Genius 5450 points

    It is better that z-stack would offers some callback or API to help developer adding manufacturer-specific functionality in their project.