Adding another +1 voice here, hoping for a toggle button that defaults to Off, or something similar, so that devices aren’t triggered to change state while editing a scene.
In my case, I have an air purifier in a few different scenes that, unfortunately, doesn’t save power state. So if it is switched off during editing a scene, I have to go to it an manually turn it back on once the scene is saved/exited and power is restored.
Consider me an upvote as well. Although I understand some logic of allowing a scene to capture the state of current entities in their entirety, that needs to be an option, or at least an option to turn it off while editing.
I have been getting yelled at by my wife every time I try to modify a scene and it turn off lights in front of her (or doing even disruptive things).
I am looking at comments on this subject going on for years. I can’t believe that the powers at be managing this for home assistant aren’t listening to the outpouring request to stop this madness - for years now.
HA is a great platform. I would like to be able to continue to use scenes because it makes life easier when I integrate with Alexa and HomeKit. Of course I could edit everything in yaml, but that defeats the purpose of a gui. I can also use scripts or automations instead, but again, a scene has a specific purpose and usefulness that I would like to use the way other platforms would work.
Make it a configurable choice at least
Having things like lights change as you build the scene makes sense so that you can see the light setup during testing (you could just as easily fire the scene to test it). When you set the temperature on multiple thermostats and it fires as you edit, this is really bad. Thermostats should only be adjusted when you are explicitly pushing a test button.
Edit: After thinking on this, I think scenes function fine. Scripts have a pretty similar GUI, and for things other than lights, scripts do seem to be better. I didn’t notice how easy scripts are to write (even through the scripts GUI), and they only set the properties that I intend them to set. The scene I was working with was setting all kinds of properties on the portable A/C rather than just setting the temperature. Seems like scenes should only be used with really simple changes (lights and really nothing else?).
I vote in favor of this improvement ASAP
Thank
This remains an embarrassingly infuriating behavior. I am certain the attitude of existing “it would be a lot of work to fix it in the one way we proposed already” is not helpful. Scenes should open in in “read-only” for the states if needed, with a “enable live preview state to modify or display yaml” at least. I can’t see how that would require using the state engines snapshot when substituting a view only control describing the currently defined scene elements and/or letting a user get to the yaml editor without applying a state (especially ones that might include things like turning off computers that said individual might be using, or otherwise toggling unexpected entities when troubleshooting etc.).
Definitely this needs attention its impossible to create a scene in an automated house without states constantly changing due to activity in the house.
+1 for this feature change req
Back here again, after plunging the house into darkness again, this time with a bit more knowledge and time.
aaaaaand… I entirely disagree with the stated answer that “this is a core issue, not a front-end one, so it’s really hard to fix”
Disclaimer: I’m not proficient in Polymer, and this is the first time I’ve really taken a look under the hood of the home-assistant interface, but I am a full-time senior front-end developer. I’m willing to be told the reason why what I’m reading here is not in fact the case.
I can see why the live state has been put forward as a reason, and I can see that the front-end is currently making use of the live state, and I can even see that there are good reasons for doing it that way, but if you take a look at the scene editor code it first loads the scene config (line 583) then applies the scene (line 606).
The current version then uses and modifies the live state in the view, but I can’t see any particular reason why it couldn’t be just referring to the data pulled in from the YAML file without having applied it.
I’d love to spend a weekend getting a dev environment set up and test my theory, but realistically that’s not likely to happen any time soon.
+1. I can’t stress how frustrating it is when trying to edit a scene, especially scene’s involving lights that are constantly being triggered around the house. “excuse me honey, do you mind if we sit in complete darkness and not move at all while I make changes to my scene”. I hope to see this is top of the list for 2024.
Use scripts instead of scenes and it’ll do exactly what you want right now. Yes I know this will not solve the scene problem, but it’s something you can do right this moment to achieve the exact same result. With a UI and all.
+1 I freaked out my wife while modifying scenes the other day by turning off all the lights while she was showering. 
+1, makes the scene functionality incredibly unattractive to use.
Can you make actions (for Apple Watch or now CarPlay) from scripts the same way or similar to how it works for scenes? Or do you need to create an automation linking the id to the script you want to run?
+1 verry annoying, locked myself out when modifying sleep scene ( plug for core switch was off)
A lot of talk here about not being able to edit scenes without activating them—which would be much more sensible design than the current, although fortunately I don’t care what my neighbors think, so I personally get nothing besides amusement wondering what they make of my outside lights flashing and changing colors at 2AM or in the middle of the day—but the other part of this thread was “improve scene editor”. I’m here to upvote being able to say “Add all my current lights” when creating a new scene, rather than having to add them (dozens of them) one by one.
I do actually have a custom card on my dashboard that gives the state of all lights to be copied and pasted directly into scenes.yaml, but I’d sure just like to be able to hit a button to do this within HA and not have to fire up my FTP client everytime I want to save the current lights as a scene. It is still much faster than creating a scene through the current UI in HA, though.
definitely got surprised when my security camera started shouting at me, did not expect attempting to edit a scene would instantly apply it, it is NOT intuitive nor desirable, quite baffled this is being discussed since 5 years
Yeah, I have to find the rare times that I am home alone to do wide spanning scenes. Please, PLEASE make this an opt-in feature!
While everyone waits for this FR, you can get the behavior you desire in the UI using a script instead of a scene. It’s the same thing. You can even make it faster by having the things be called in parallel instead of series by using the parallel action.
Hi all
New to HA and agree this feature caused me confusion. Realised I’d not added a light to a turn off scene and tried to edit and everything came on. Thought I’d done something wrong.
In the posts above I see many comments suggesting voting for this change - sorry to be a dumbo but how do you do that ?
Regards
Andy
Scroll to the top of the topic and click the vote button.
Thanks. Done…461 votes now……