RE: Zigbee Cluster Library (Zcl) issues

Marjeris Romero — Mon, 09 Mar 2020 17:28:38 GMT

Hi,

Question1. Color control cluster has cluster ID 0x0300 and command ID 0x07 Move to Color is describe in section 5.2.2.3.10 of the ZCL spec.

Since the payload consists for 3 x 16 bits then you should write a total of 12 characters in the payload. The last four characters will be the transition time.

There is also some information about the CurrentX and CurrentY color values in the specification, and both values have a range of 0000-feff

CurrentX Attribute
The CurrentX attribute contains the current value of the normalized chromaticity value x, as defined in the CIE xyY Color Space. It is updated as fast as practical during commands that change the color.
The value of x SHALL be related to the CurrentX attribute by the relationship
x = CurrentX / 65536 (CurrentX in the range 0 to 65279 inclusive)

CurrentY Attribute
The CurrentY attribute contains the current value of the normalized chromaticity value y, as defined in the CIE xyY Color Space. It is updated as fast as practical during commands that change the color.
The value of y SHALL be related to the CurrentY attribute by the relationship
y = CurrentY / 65536 (CurrentY in the range 0 to 65279 inclusive)

Question2. If you are using the CLI agent example you should now that this example erased the zigbee network data after reset by default, since it's mean to be used as a developing tool. You will need to commission the lights again after reseting the example. If you want to store the network data in NVRAM you need to set ERASE_PERSISTENT_CONFIG to ZB_FALSE in the source code. For a product that is going to be release to the market you will usually want to make a custom coordinator, so the thought is that you can use the CLI example as a developing tool to see which commands you need to implement in your coordinator and then add them to the Light control coordinator for example.

Best regards,

Marjeris