It seems to me that the scene editor was designed such that someone could adjust physical dimmers in the real world, then edit the scene file, and the scene file would automatically assume that what you wanted to edit was to modify the script to match the state of nature at that moment. Is there a way to never modify a script unless you modify it on the console? What is happening now is that, I set up a script, save it, then later when I edit it, if something is one the fritz, it immediately edits the script to match whatever messed-up state my lights are in (if someone manually turns on a light, then I edit the scene, it changes the scene for that light from off to on even though I am editing the “Room X light off” scene. This might not be a big issue if it really was a single bulb scene, but when I have whole-house scenes and need to edit one aspect of it, the entire scene is ruining itself every time I edit it, since it seems to default to updating to current real-world state when I edit it, when all I wanted to do is change the behavior of one bulb. Am I missing something? Is there a setting to tell the scene editor to never load current states as part of the editing process?
I don’t know if there is a setting for that but you could considering managing your scenes in YAML, it’ll prevent the UI editor from importing current device states in your scene.