Scene change ignores transition time

[Phadeguy]

The problem

Activating a scene with call-service action and scene.turn_on appears to ignore the transition time. It worked fine in the past and then broke a few revisions ago. I've seen this kind of thing break and then fix itself later, but this one has been persistent. Thanks for being awesome!!

What version of Home Assistant Core has the issue?

2022.4.7

What was the last working version of Home Assistant Core?

2022.4.7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Hue

Link to integration documentation on our website

https://www.home-assistant.io/integrations/scene/

Diagnostics information

No response

Example YAML snippet

type: button
tap_action:
  action: call-service
  service: scene.turn_on
  service_data:
    transition: 60
  target:
    entity_id: scene.david_blue_lights
show_icon: false
name: Wake
hold_action:
  action: none

Anything in the logs that might be useful for us?

No response

Additional information

I used the visual editor to create the YAML snippet supplied in this ticket.

[probot-home-assistant[bot]]

scene documentation scene source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (scene) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[lizsugar]

I was experiencing this on 2022.4.5 and am still experiencing it on 2022.5.0

[Ekinox87]

Hi there, I'm currently experiencing same behaviour ; transition times do not apply anymore. Currently running core-2022.5.5. However I noticed that new service hue.activate_scene works fine. Hope this input will help ! Cheers :)

[Gronda74]

I've noticed similar behaviour recently. Currently on 2022.5.5.

Oddly, the transition works fine on Hue and Home Assistant scenes on a straight bulb, but Home Assistant scenes do not repsect the transition time on my Hue Go's. As @Ekinox87 notes, using a scene set in the Hue app works fine.

[jaypi95]

I'm experiencing the same thing as well but additionally I can't use transition times over 900 seconds anymore in scripts or automations. The only other mention of this I've found is #2843 in core which has been fixed years ago.

Not sure if they're caused by the same bug or if I should open a separate issue for that.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jaypi95]

Just tested it, the issue is still not solved.

[Phadeguy]

Yes, this issue still exists.

[KHWW]

For me its also not working, the philips hue scenes are fine, but the one created in HASS are not.

[mkarnebeek]

Do we have any workarounds?

[Gronda74]

Only to set the scene in the Hue app and call that in HASS with a transition.

[MaggiR]

I observe this issue (partly): Brightness transition during scene change works for my Hue devices and for my Tradfri E27 bulb, but not for my Tradfri GU10 bulbs. The latter, however, transition successfully when changing light color instead of brightness.

[wile-e1]

I just wanted to follow up on this since the issue has been opened for some time and there still doesn't seem to be a resolution.

Being able to create scenes is a fantastic ability, but not being able to use transitions really makes the use of them quite jarring and frustrating. Being blasted with lights at 100% first thing in the morning instead of a nice smooth fade to 100% over a few minutes is a completely different wake-up experience.

Most of my house has Hue bulbs, but unfortunately, falling back to Hue scenes is not an option since all my bulbs have been migrated to Zigbee2MQTT.

I really hope someone can make some headway on this.

My setup: HomeAssistant 2023.3.6 Supervisor 2023.03.3 Operating System 9.5 Frontend 20230309.1 - latest

Running on a VM on unRaid.

[bramkragten]

Is this a frontend issue? Does it only not work correctly when in a Lovelace config? Or does it never work, also when called from an automation, or the service dev tools?

[foreverimagining]

Because I too encountered this problem and would like to see it fixed someday for my convenience in the future, I went through and checked the status in my Home Assistant. I tried the "scene.turn_on" service in the dev tools and made a button that calls it with a transition on my dashboard and both worked just as expected, fading into the correct brightness and color. Automations are where it gets funky.

When I test run the action within the automation interface, it does just fine. However, an automation that triggers on its own is where things go wrong. I made a test automation that would trigger when I turned on an outlet, and it worked. When I then added the service call action to the automation that turns on my lights before sunset, it failed (still), and the lights came on instantly.

It seems that the trend is that when I myself conduct an action to activate the scene, the transition works, but when Home Assistant triggers it, or at least when it is triggered by the Sun integration, and based on previous troubles, time, the transition doesn't work. Others will have to comment if they experience the same.

Personally, I found a work-around by using the service "scene.apply" and inputting the state, color mode, brightness, and color value. It runs correctly with the transition in my light automations, but I have to copy and paste the data for the particular scene I want each time I write a new automation. Kind of defeats the purpose of having the scenes.

Hardware/Software I am using: Home Assistant 2023.3.5 Supervisor 2023.03.3 Operating System 9.5 Frontend 20230309.1 - latest Running in a VM on Proxmox Hue Color Ambience bulbs connected via the Hue Bridge, but I do have a zigbee stick if I need to change over.

[heathfx]

works perfectly on my 2021.6.2 server, broken on my 2023.4.4 server.

Hue Bridge and bulbs on latest FW as of this comment.

[husjon]

Same issue tested with ZHA (migrated from Zigbee2MQTT). Single lights can be transitioned no problem, but scenes seem to use default time of the bulb (which I set to 1 second previously using Z2M).

My lights are all Ikea bulbs (FLOALT panel WS 30x90, TRADFRI bulb GU10 CWS 345lm, TRADFRI bulb E27 CWS 806lm)

My Setup: Home Assistant 2023.4.5 (docker)

[chrismanivong]

This is still open since more than a year now. I started into scene transitions some days ago. No I found why I do not succeed. I'm working with Z2M and bulbs, light stripes and panels from different vendors. Steering light works perfectly unless this scene based thing.

I also have some Tuya Wifi devices connected by Tuya integration. I will test them now.

[Sirgrant618]

Also still having this issue on latest docker image install (2023.10.3) creating a scene within HA for hue bulbs attached to hue bridge.

[DavyStack]

Same issue here. All latest HA updates and Hue firmware. Automations completely ignore transition.

[Sirgrant618]

Even just calling the service in the developer panel it won’t respect the transition times. Transitions work with scenes that live on the hue bridge, at least.

On Mon, Nov 6, 2023 at 4:15 AM DavyStack @.***> wrote:

Same issue here. All latest HA updates and Hue firmware. Automations completely ignore transition.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/frontend/issues/12540#issuecomment-1794491387, or unsubscribe https://github.com/notifications/unsubscribe-auth/APX5YQYRG3BYKAXUQK22RPLYDC2FRAVCNFSM5U3SMCX2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZZGQ2DSMJTHA3Q . You are receiving this because you commented.Message ID: @.***>

[Twanislas]

Hi folks, I did some digging and it looks like it might be related to ZigBee groups feature support and/or when using mixed bulb models.

My test setup : ZigBee (ZigBee2MQTT) group with 3 bulbs, 1x Hue, 2x Ikea. I created 2 scenes, one targetting the light group with the 3 bulbs (scene.office_bright_group) and a second one targetting each bulb (3) instead of the group (scene.office_bright_individual).

Now I turn the group off and then when recalling scene.office_bright_group with a transition time of 60, all 3 lights turn on instantly, ignoring the transition. When recalling scene.office_bright_individual with a transition time of 60, the 2 Ikea bulbs turn on instantly but the Hue bulb correctly applies the transition time.

In my specific case, it looks like the Ikea bulbs do not support the transition when turned on from a scene since the transition works when using light.turn_on. Interestingly, when using light.turn_on to turn on the ZigBee group directly, the transition time works on the 3 bulbs.

So my belief is that there's an issue when applying the transition time only when using scene.turn_on.

Hope these findings will help...

[Twanislas]

Digging deeper, I found that transition fails to apply only when setting a color temperature (using any of the color parameters like color_name or color_temp_kelvin). This makes sense since applying a scene will restore all the saved states from a light (including color).

Using light.turn_on on my 3 bulbs group, the transision works flawlessy as soon as I remove any color parameters.

[mattdmoore]

Adding more info to @Twanislas's answer: my Ikea bulbs connected via Zigbee2MQTT behave exactly the same, but transitions break only when both brightness and temperature are being adjusted simultaneously. Tested from Node-RED calling the light.turn_on service.

If I adjust either parameter individually they transition just fine, but when changing both together I get the same instant brightness activation, followed by a gradual temperature transition.

Not sure where to look for the problem, but hopefully this might help someone figure it out.

[Sirgrant618]

Some more clues:

If I create a scene using a hue ROOM (not individual bulbs, with brightness and color/white temp specified), then transition time is respected. If I create the same scene using individual bulbs (with brightness and color/white temp specified) then transition time is NOT respected. Same thing if I make a scene with just 1 hue bulb with brightness and color specified.

All my hue bulbs are connected via hue bridges. The room is auto-created by the hue bridge (and I think technically it's a zigbee group living on the hue bridge).

[1358]

I tried to find reproduciblal things now for several weeks as this buggs me out. Transitions work if:

• RGB value is adjusted (from RGB to RGB)
• Brightness is adjusted (from ... to ... :) )
• PARTLY: 3rd party vendor target speaking Zigbee Light Link (e.g. some of these dimmers) work in that overall-working-szenario fine, too.

Transitions do not work:

• If color temperature and/or brightness is adjusted.
• 3rd party devicess are the only ones showing a roughly discretizated transition in that case (might be 10 hard steps or so during the transition period)

I saved several scenes created by the hue app. If the color scheme defaults to "color" in the hue app everything seems to work fine, if it defaults to "color temperature" the transition in HA fails as soon as even one "color temperature" device is included in that scene.

[Gronda74]

This appears to be fixed in 2024.3.0. 😃

[Phadeguy]

Can confirm: works for me now. Thank you, team!!

[husjon]

On my end it seem to work on all my lights except for my IKEA FLOALT panel WS 30x90. When a scene has transition time, I am able to only control color temperature but not brightness (as in brightness over time). Both possible in isolation using light.turn_on, but not at the same time.

[mattdmoore]

Updated to 2024.3.0 but still not fixed for me, both Home Assistant scenes and Node-RED triggers are still ignoring transition times when temperature and brightness are adjusted simultaneously

[RemyyB]

I have the same issue with Zigbee2MQTT devices. The weird thing is, if I set color sync to true. And when I change the value directly via Zigbee2MQTT, and then change the scene with a transition in Home Assistant, the scene transition does work. Still trying to figure this issue

[jvalrog]

Facing the same issue, my scene sets both brightness and temperature, and transitions are totally ignored

[brooksben11]

For whatever reason, this only recently became an issue for me. I've had the same scene working fine for years and a few versions ago it stopped doing a nice transition when activated (just using the default transition time on my hue bulbs). Oddly enough, when backing out of the scene editor it goes through the correct transitions during the shutdown of the bulbs.

While trying to get it working again, I noticed that with only one bulb in the scene it works fine, and each additional bulb appears to shorten the transition time. After adding a few bulbs, it essentially becomes an instantaneous transition.