Slow transitions no longer working with LimitlessLED

[Talismanian]

Home Assistant release with the issue: 0.68.1

Last working Home Assistant release (if known): 0.68.0

Operating environment (Hass.io/Docker/Windows/etc.): Hass.io

Component/platform: LimitlessLED

Description of problem: The report I'm making concerns the behaviour of LimitlessLED in automations. The automation in question fades the lights to to warm white over half an hour around sunset. Usually the bulbs are at their maximum brightness and cool white.

Now when the automation is triggered, the bulbs default to low brightness and half-warmth. Although the bulbs do reach the same endpoint, the starting point is not taken from the bulbs' state when the automation is triggered.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant): Light setup:

light:
  - platform: limitlessled
    bridges:
      - host: 192.168.1.4
        groups:
          - number: 1
            name: Bedroom Lamp
            type: bridge-led
          - number: 1
            name: Bedroom Ceiling
            type: rgbww

Automation setup:

- id: '1507793279733'
  alias: Sunset — warm ceiling lights in Bedroom
  trigger:
  - event: sunset
    offset: -00:20:00
    platform: sun
  condition:
  - condition: state
    entity_id: light.bedroom_ceiling
    state: 'on'
  action:
  - data:
      brightness: 250
      color_temp: 500
      entity_id: light.bedroom_ceiling
      transition: 1800
    service: light.turn_on

Traceback (if applicable):

Additional information:

[amelchio]

I cannot reproduce this and it seems unlikely that it could have appeared in 0.68.1 so I expect it to be some local issue.

Home Assistant cannot see the current state of your bulbs and thus assumes that whatever it last set it to is still current. Do you control the lights outside of Home Assistant? That would make this assumption wrong and the fade could start from an obsolete assumed state.

[amelchio]

I don't think this is a bug so I will close this now. Feel free to open a new issue but if you do, please make an automation that also sets the initial state so I can reproduce the problem.