I was cloning a scene I'd recently created (since 2.2.9, I'm pretty sure).
After I went through the steps to clone it and clicked Done, when it displayed the Apps list, the cloned scene wasn't there. Looking in thee logs, there was an error about that time:
Note that during the cloning process, I typed in a new name (something like "Scene: Set LED Lightstrip for Movie Mode"). That time, I did the clone from the parent scene app.
It turns out, it made copies of the scene with the SAME name as before it (ignored the name I gave it).
More interesting, the RM 4 App rule that activated that scene had empty "activate" statements (and the drop down didn't show all the scenes, only the one I'd gone back into and saved with a new name).
Going into the Scenes and re-saving them made them appear again (including in the apps where they were originally)
Now, trying to clone using the "default" name, I don't even see the button to do so:
I don't get your error cloning a Scene, but there is a conflict between how a Scene starts up and giving a clone a new name. Scene overwrites the new name. That can probably be addressed in next release, although I haven't explored in detail why that does what it does.
As for Scene disappearing from a Rule, not seeing that either, and it was probably not related to cloning.
There are some issues with cloning a Scene. For example, it does not offer device replacements when cloning. Scene uses a non-standard method for selecting devices, and Export/Import/Clone doesn't know about that. Work for the future...
Don't know about any such posts. I just cloned 3 different Scenes: no errors, had same name, showed up in Scene list in Rule-4.1 (didn't check Rule 5.1). Didn't hit Done in any of them.
I have found an issue where if I clone a scene and change the name of the cloned scene, It does not take the name change during the cloning process, is simply creates the clone without the new name, just the origin name plus clone. This is a repeatable error for me. I can change the name AFTER the cloning process just fine. But this adds an extra step that is unexpected as you are given the option of changing the name in the cloning process.
This is a known / reported bug. Without boring you with too much history, it used to be that the Groups and Scenes parent app had the ability to clone a Scene. As a consequence of that there is some goofiness about how the name of the Scene is initialized, and you're bumping into that vestige. We will get this sorted in due course. Thanks for your patience.
