I’ve already encountered the problem. But for me, it’s not specifically related to scene duplication.
If you change the trigger device in the hub without having removed it, it’s impossible to save the scene.
For example, I replaced the temperature sensor with another one and for that I had to delete the hub and add another one back, even though it had the same values, etc.
Hello,
I confirm this has already happened to me: after modifying or duplicating a scene I couldn’t save it. I had to delete it and recreate it. I thought I wasn’t waiting long enough for the elements to update. In any case, I’ve already had this problem
I just tested: if you change the selected device in a trigger « Device state change », you must then re-enter a value that will trigger the scene
If you don’t enter a value, the scene is not valid and therefore cannot be saved.
However, it’s true that we could add an error on the action or the trigger that is causing the problem to indicate to the user where a value is missing
What I’m trying to understand is just whether it’s a bug or not. Because, if the scene isn’t filled in correctly, it’s intentional that it prevents you from saving
If you can make a video recording of the bug, that would be great!
