No thanks, that’s fine. I want this to be here to bring the devs attention. I’ll open a new Feature with a clear description in a new thread and will crosslink this one.
EDIT. Feature Request opened: Improve Scene editor, allow scene edits without setting devices' states
Quote from my post at: 0.102: Official Android App, Almond, Scene editor - #122 by i00
Completely agree… I don’t want my skylight opening and letting the rain in to my house just because I am editing a sunny scene when it is raining!!
I also think this should be changed. 
I second this request!
In my case, I have a node red flow trigger on a light status change, so it becomes really frustrating when I start editing a scene but then node red takes control and changes my lights. Should have an offline edit mode as suggested.
Please fix this. I shouldn’t have to use the text editor because it’s 11pm at night and I don’t want to wake up my family with lights going on and off.
I also vote to have this issue addressed. I was really surprised that when creating a scene, I would be disturbing the current state of devices. For me, it wasn’t even editing the scene, because I was creating a new one, but rather, assuming that setting values for the included devices was just that - prepping the scene / values… nope, devices went off (on) and people were not happy.
The other consideration here is - do we want home assistant to be a toy/novelty or do we want to be confident that it can handle (semi) mission critical / production use cases?
On this production side note, I’m still surprised HA has not prioritized persistent timers - again - if a device needs to run for an hour and HA has a blip and needs to be restarted - it doesn’t know if entities should stopped or started again for however many minutes.
The current behavior of the scenes editor is not viable and dangerous!!! I have my PC screens on a smart device. When I created my “Turn off my studio” scene, my PC screens turned off while I was setting up the scene, and I had to end the setup because I was basically blind. How dumb is that?
I am trying to image what happens when someone is trying to configure his fire water sprinklers in the scene editor. You need to have an umbrella every time you enter the setup - Hahaha. Or Garden springlers. What a waste of water. Man, this thing really wasn’t thought through.
Or just image someone with a heart condition is setting up his alarms in the scenes and the sirene goes of - the guy gets a freak’n heart attack…
This scene setup up is super dangerous.
Needs fix’n ASAP.
Cheers!
fully agree. This is a very anonying feature, I just want to edit the scene, in the end it just run it doesn’t make sense at all.
I’m guessing they don’t think this is very important or dangerous because it was not fixed in the new releases that just came out. Very fun sitting up scenes with people in the house turning on lights you want off and setting off the alarm and siren. I guess I’m lucky that I don’t have the water shutoff valve and dump valve yet for a water leak 
I guess the simplest explanation is: they do not use the GUI scenes editor Otherwise it’d already be fixed. Assuming we’ll get this fixed some day - it may take a long while until they fix it as they emphasized that the current solution is already very complex and making it work as we want it - may be even more complex. And complex things take time, usually a lot of time.
+1 - Scenes should be editable via the GUI without having to enable the scene.
+1 for editing the scene without first running it. Or at least have a pop-up warn the users that the scene will be run. There are safety concerns here like accidentally turning on a heater when someone is touching it.
+1 it’s super annoying that editing scenes runs the actions by itself.
+1 came here to bump this - still the WORST idea. Cant edit a scene in the GUI without the whole house going nuts!
Everyone on here realizes that the way the scene editor works is it captures the current state of selected devices right? It’s not like the script editor, you aren’t configuring a sequence of actions.
When you make a scene you select devices. Then you “edit” the scene by changing the state of those devices in the real world. When you save the scene it captures the state of those devices as the scene and running the scene returns all your devices to the state they were in.
So when you edit a scene the first thing it has to do is run the scene. This recreates the state you saved. Then you change those devices in the real world and save to update the scene.
Honestly this is pretty normal. Look into some other home automation platforms and I think you’ll find scening features are often offered in the same way. I wouldn’t say no to a warning though, I do forget sometimes.
But it seems like what you all want is a script. A script can do everything a scene can do and more after all. The big difference is that you don’t capture the current state of devices, instead you define what you want to happen step by step. And then there’s no reason to execute a script to edit it, the current state of stuff doesn’t matter.
Some may know how it works, some not. It’s not the point. I know a few Smart Home Automation systems and none of them implements scenes the way HA does it. And there’s surely a reason for this.
The way it works is irrelevant for the end users. What matters is that it’s doing things none wants it to do. It’s not a bug, it’s the way they implemented it. And it’s wrong. It makes people mad, so basically it isn’t helpful. People are hesitant to use it because the way it works. This means it should be changed. It’s a perfect candidate for this year’s streamlining experience Initiative in HA.
There’s 15 participants in this thread. The first issue you linked at the top of this thread has 5 replies and 3 participants besides the developer telling people its working as intended. The second has no replies other then a developer closing it as working as intended.
There are currently 150k deployments of Home Assistant according to analytics (which means there’s a lot more then that since plenty of people don’t turn on analytics). If you’re going to say “no one wants this” you’re going to need to present more evidence then a very small sample size of unhappy users.
EDIT: I see the feature request, sorry was in the middle. 164 is a good amount, fair enough. I’m not 100% disagreeing but I do feel like if you take away the “capture current device state” part of scenes then scenes are frankly kind of pointless. They’re just bad scripts basically. Anyway the FR makes the point more regardless.
EDIT 2: LOL I see I replied to the FR a year ago. At the time it appears I was supremely frustrated by this as well but since then have kind of come around a bit. Or at least am able to acknowledge that I get more about why this change was made. Funny how things change.
You probably didn’t pay attention and did not notice that both were closed within 2 days. Not because of inactivity - because the devs said it’s not a bug. A closed issue cannot be commented anymore. That explains how little community feedback is captured in github.
But as you see - the discussion in the Feature Request section of this community forum is quite extensive. 164 voters are already a lot if you compare it to other features voted in the forum. Some have 300-400 votes, but 164 is also quite a number.
Noone wants to get rid of it. It makes scene creation very easy. That’s the whole point of scenes in other systems. Scenes need GUI support by definition. This support here is only good when you create a scene, but not when you want to tweak it. That’s all.
I find this feature very annoying. I don’t want to activate a Scene when I click on it. I just want to EDIT it. At least offer a way to edit without running it.
I also am very annoyed at this feature.