My Virtual Color Temperature Light device doesn't always change to the "on" state when I send it a "set level" command. I've successfully worked around it by setting up an automation to send the virtual device a "on" command when notified of a level change.
Presumably this driver mimics the behavior of several "real" smart-bulbs that support pre-staging. But I agree with you, ideally the driver should have a separate command to pre-stage a level (eg. preSetLevel()), whereas setLevel() should also set the state to be "on".
The problem here is that most of the time it does change to "on" when it gets a "set level". Every week or so, it does not.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
