Light CTL model: State bindings guidance

[Chris_Dev]

After doing some reading, I realized that the light CTL server model does not contain the generic OnPowerUp set message. It is contained within the light CTL setup server.

Here is a deduced state binding diagram for the light CTL model (From sections 6.1.2 and 6.1.3):

Double arrows show reverse bindings, a change in one shall cause a change in the other.

The specification states (Section 6.4.3.2.2):

When a Light CTL Server receives a Light CTL Set message or a Light CTL Set Unacknowledged message, it shall set the Light CTL Lightness state to the CTL Lightness field of the message, the Light CTL Temperature state to the CTL Temperature field of the message, and the Light CTL Delta UV state to the CTL Delta UV field of the message, unless the message has the same values for the SRC, DST, and TID fields as the previous message received within the last 6 seconds.

According to the state bindings, this is what will happen upon receiving a Light CTL set message:

I cannot make sense out of this, there will occur multiple state changes on the actual lightness. So this meaning that you can only change the lightness OR the CTL temperature? The specification says otherwise. 

[Hung Bui]

Hi Chris,

If you have a look at table 6.124 in Mesh Model spec, you can find that the model expand in to 2 elements. One is Main and one is Temperature. The Light Lightness Actual is bound to Generic Level on the Main element, and will not change state when the Light CTL Temperature change. 

[Chris_Dev]

Ah if you have a look at table 6.122, this pretty much clears it up.

The main element:

Light CTL is bound to:

1. Light Lightness

2. Light CTL Temperature

Light CTL Temperature Range is bound to:

1. Light CTL

The temperature element:

Light CTL Temperature bound to:

1. Light CTL

2. Generic Level

Generic level bound to:

1. Light CTL Temperature

[Hung Bui]

Yes, it's pretty clear the CTL temperature bound to Generic Level on the temperature element.