Transition time ignored when running scene from automation

Configuration
1

I currently have the following automation running:

alias: Wakey-Scene
description: ""
trigger:
  - platform: template
    value_template: >-
      {{ as_timestamp(states('sensor.lg_d802_next_alarm')) - 60 <
      as_timestamp(now()) }}
condition:
  - condition: device
    type: is_off
    device_id: 2f76b60ccc04ea809bd8a1e7cae9e3db
    entity_id: light.ceiling_local
    domain: light
action:
  - service: light.turn_on
    data:
      transition: 0
      brightness_pct: 1
    target:
      device_id: 2f76b60ccc04ea809bd8a1e7cae9e3db
  - delay:
      hours: 0
      minutes: 0
      seconds: 3
      milliseconds: 0
  - service: scene.turn_on
    data:
      entity_id: scene.sunrise_start
      transition: 0
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: scene.turn_on
    data:
      transition: 300
    target:
      entity_id: scene.sunrise_end
mode: single

However, when the alarm triggers and sunrise_end runs, it goes through the transition to the right color and brightness within something like 8-10 seconds.

The ceiling light is a Lidl zigbee lamp that supports transitions.
Any ideas what’s going on?

Edit: I just found this. seems to be an issue for several years already.
I worked around it now by instead of setting a scene, I am using the Light Turn On service to directly set the values to transition to.

2

Sorry to resurrect this old thread, but did you ever solve this problem or did you stick with the workaround? Seems pointless having light scenes if we can’t use them as intended.
Looking at the link you provided, I see that the last report was in October. This bug has been annoying me for at least a year. My morning automation is not nearly as nice as it could be without the slow ramping up of my bedroom lights.

3

Nope, still the same issue.