Hue Effects not saving in Scenes

[jnsn]

The problem

To me this is a similar issue as https://github.com/home-assistant/core/issues/84671.

When trying to save an effect for a Hue light in a scene, the effect is not saved when closing and re-opening the scene editor.

When you set an effect and simply re-open the pop-up the effect is still selected, but upon saving this seems lost.

What version of Home Assistant Core has the issue?

2023.1.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Philips Hue

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @balloob, @marcelveldt, mind taking a look at this issue as it has been labeled with an integration (hue) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of hue can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign hue Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[marcelveldt]

1. Please try to use native Hue scenes as much as possible because they are optimized for the Hue ecosystem (and have special features like effects, dynamics etc.)

2. Do you have any other lights on your setup to test if this is a Hue specific issue or maybe broader ? Creating scenes in HA is like creating a snapshot of the state.

[jweisner]

I have ten Hue lights in my setup, and the HA scene editor stopped working for all of them after the 2022-12 release.

I can change the effect in HA's scene editor, the lights will switch to that effect, but there is no option to save the changes in the scene editor. It acts like no changes were made, so this feels like an editor UI bug.

[jweisner]

I manually added

effect: "breathe"

to the entities in the scene in scenes.yaml, and I can flash my kids' lights to call them for dinner again ;)

[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!

Code owner commands

Code owners of scene can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign scene Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[marcelveldt]

Changed integration to scene because this is not a Hue specific bug but more likely with HA scenes not saving effects ?

[lundyfpv]

Any movement on this? I just started messing with scenes and I notice my Effects aren't saving as others have mentioned.

[tedivm]

I can confirm that this is happening on the latest release, although editing the yaml file directly works so it's not a show stopper.

[zebpalmer]

I have a scene with a mix of hue, zigbee, and WLED devices where I'm applying effects to wled and hue bulbs. I thought I was doing something wrong as the hue effects weren't getting applied when the scene activated and I was sure I'd saved the effect in the scene editor. I tried re-saving them several times before searching for and finding this bug.

[jdaandersj]

I am also having this issue

[PV-Web]

Same problem here when adding hue bulb with effects to any scene. They wont trigger and I get this error once the scene is triggered: HA scene failed to call service scene/turn_on. string value is None for dictionary value @ data['effect'] Does anyone know a workaround for this? until it it fixed

[EPinci]

Actually, with 2023.11.2, the scenes.yaml file does contain the "effect_list" and "effect" entry. Looks like the problem is in reading/applying it, not in saving it...

[tedivm]

When I've manually entered the items into the yaml file everything worked fine, so if it suddenly stopped that's a new bug.

[issue-triage-workflows[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.

[tedivm]

This is still a real issue.

[PV-Web]

Indeed, Still an issue. But no clue how to fix this

[mark3apps]

Same thing here. Having this issue with my hue bulbs.

[BlackHawk1912]

Same thing with WiZ lamps. I had two WiZ bulbs with working scenes and effects. I repositioned the lamps and added a third and now effects aren't saved anymore on scene editor.

Home Assistant Container; Core v2024.3.3; Frontend v20240307.0

[dcarpio01]

Same issue with my wiz bulbs. I have 19 of them that I recently tried to put into various scenes. They all don't save their color temp or effect presets.

[BlackHawk1912]

@dcarpio01 I found a workaround by editing older WiZ scenes in the scences.yaml. Maybe you want to give it a shot.

[therihawk]

This issue is still not solved. I cannot save effects on any of my WiZ bulbs. If anyone can comment explaining exactly what needs to be done to work around this issue via YAML, maybe including a snippet, that would be super helpful.