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
Currently, when any light attribute is changed (brightness, color, temperature), an active colorloop effect is turned off.
(Do we even want to keep that behavior?)
However, when changing the light color, we first send the color command to the light and only turn off the effect afterwards. This will cause the light to miss the color command and cause mismatched state in HA.
The color command needs to be sent a second time at the moment.
We likely should turn off the effect first in the turn_on method, then send the color commands.
Currently, when any light attribute is changed (brightness, color, temperature), an active colorloop effect is turned off.
(Do we even want to keep that behavior?)
However, when changing the light color, we first send the color command to the light and only turn off the effect afterwards. This will cause the light to miss the color command and cause mismatched state in HA.
The color command needs to be sent a second time at the moment.
We likely should turn off the effect first in the turn_on method, then send the color commands.
(noticed whilst testing #99)
The text was updated successfully, but these errors were encountered: