You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When issuing commands to the example lighting app that hit the ColorControl cluster and the OnOff cluster, the commands are applied in the opposite order that they are received.
Steps (using the example lighting app):
Ensure that OnOff is set to Off in the lighting app.
Issue a MoveToColorTemperature command to the lighting app with TransitionTime set to zero and the options mask and override set so command will execute while off.
When the ack for that command is received immediately issue an On command to the lighting app.
Expected behaviour:
The light turns on with the new colour temperature.
Actual behaviour:
The light turns on with the old colour temperature.
The colour temperature changes.
I believe the cause is that the colour control server treats a TransitionTime of 0 as 1 instead and schedules a timer to actually change the colour temperature 100 ms later. The command's ack is sent and received before then, so the On command gets sent and processed (and the light turns on) before the colour temperature has been updated.
The text was updated successfully, but these errors were encountered:
When issuing commands to the example lighting app that hit the ColorControl cluster and the OnOff cluster, the commands are applied in the opposite order that they are received.
Steps (using the example lighting app):
Expected behaviour:
Actual behaviour:
I believe the cause is that the colour control server treats a TransitionTime of 0 as 1 instead and schedules a timer to actually change the colour temperature 100 ms later. The command's ack is sent and received before then, so the On command gets sent and processed (and the light turns on) before the colour temperature has been updated.
The text was updated successfully, but these errors were encountered: