I have a tablet panel with some buttons for predefined scenes. But the scenes are hard coded. It would be nice if we were able to set up lights, and store this on f.x. long press on the scene button.
So a new scene.create command that store the scene on the hard drive.
You’re describing how the scene editor works. Go to scenes, click “add scene”, set your lights and such in the state you want to capture, list the lights and devices you changed in the scene and click save. The scene will be saved “to the hard drive” and running it will put your lights and such back into the same state they were in when you saved it.
The purpose of the scene.create service is to capture the state of lights and such as part of an automation or script before changing them and then restoring them to that state after some amount of time has passed or an event has occurred. If you want to just manually make a new scene to use wherever, use the scene editor after adjusting all your stuff to the state you want.
Thanks for your answer, can this be done from the lovelace frontend as I don’t think I get my wife to go into development to just set up the scene?
I see. You basically want scene editing to become a user task rather then an admin one. Not really any way to do that right now. Even if you used a button tied to scene.create you (the admin) would have to hard-code in the list of devices to capture state for rather then letting the user pick.
This makes more sense. Just a suggestion you might want to re-phrase a bit to mention easy scene creation and editing by users (not admins). I don’t think you actually care about how scene.create service works right? That just happens to be how you’ve tried to work around this limitation right now. With a manually made dashboard that includes a button that calls that service.
Agree! This seems like some so basic, I’m really astonished that it doesn’t get more attention.