[Feature Request] Operate color temp and brightness separately about adaptive-lighting HOT 17 CLOSED

Is this true for all MQTT lights?

from adaptive-lighting.

@psbankar could you try the latest commit, I've added a separate_turn_on_commands option.

from adaptive-lighting.

This is a duplicate of #16.

from adaptive-lighting.

I think psbankar means for his light, when adaptive-lighting sends the command to the lights [60% brightness, 1000k], it only picks up the 60% brightness and the 1000k does not get set. It may fix the issue to have send the [60% brightness] setting and THEN [1000k] setting which will allow the lights to react to each new setting seperatly

from adaptive-lighting.

@nickg90, a right, I misremembered what you were asking.

from adaptive-lighting.

Yes, @nickg90 got it right. In the latest commit, the light on command is triggering before the usual color temp and brightness command so it didn't work for me.

from adaptive-lighting.

Could you tell me the exact sequence of commands that you need?

from adaptive-lighting.

now it does

- service: light.turn_on
  data:
    color_temp: ...
    entity_id: light.yolo
- service: light.turn_on
  data:
    brightness: ...
    entity_id: light.yolo

from adaptive-lighting.

As @nickg90 said, I need the brightness and color_temp/RGB commands split up. i.e you could use a separate command for setting the brightness and separate for color_temp/RGB.

from adaptive-lighting.

Yes, that is exactly what I implemented.

Could you try it?

from adaptive-lighting.

Ok, I figured out what was going wrong for me. Because of transition, color_temp, and brightness attributes, three separate commands were being sent. And because of the transition command, the light was turning on at full brightness again. I have fixed the issue for me by adding a condition to ignore the transition command.

from adaptive-lighting.

That shouldn't be needed, I can fix it.

Are you able to do?

- service: light.turn_on
  data:
    color_temp: ...
    entity_id: light.yolo]
    transition: ...
- service: light.turn_on
  data:
    brightness: ...
    entity_id: light.yolo
    transition: ...

from adaptive-lighting.

Yes those commands work

from adaptive-lighting.

OK then I should change the implementation.

The only thing you need to do separately is the color and brightness?

from adaptive-lighting.

Yes, that's right. You can combine transition with color and brightness so only two commands are sent.

from adaptive-lighting.

I've made the changes accordingly, now it sends one light.turn_on for

• brightness (and optionally white_value) + transition
• color + transition

from adaptive-lighting.

I consider this solved. Please ping me here if this is not the case.

from adaptive-lighting.