Using scripts to save, apply and delete temporary scenes

[rapid valley]

I am trying to have one script that can be reused to temporarily save scenes and another script to apply and then delete the scenes.

I use input fields in order to have variable scene names.

In my scripts I want to check if the scene with that name exists before saving it or applying it, in order to avoid overwriting scenes or applying scenes that don't exist.

The problem seems to be writing a condition that checks if a scene exists. It doesn't seem to work for me when the scene is "freshly created". Then all my attempts at conditions return "false - the scene doesn't exist" but I can see the scene under the scenes tab in the web GUI.

Why does this happen? Can I flush the new scene to the system so my conditions work immediately, or is there some other magic I have to understand in order to get this to work?

Thanks for any help 🙏

[barren copper]

Maybe add a little time delay?

[tall cloud]

Hi, you can use random names with timestamp prefix or similar. It won't repeat.

[rapid valley]

The script saving the scene and the one applying it are different scripts triggered from different automations. A delay isn't applicable here.

Also; the time it takes to pick up that there really is a scene there seems more to do with whether or not I touch the saved scene in the GUI or not.

But thank you for helping 🙂 🙏

[rapid valley]

Then how will the script that should apply the scene know the name of the scene? The whole function I am trying to achieve is to save and recall a scene from 2 different automations/scripts.

[tall cloud]

Is there any helper where you can save a string? I don't really know 🙂

But maybe if you start telling the problem you want to solve, not the solution you want to implement, it's easier to help you 😉

[barren copper]

Looks like a good time to start sharing the yaml 🙂

[rapid valley]

The problem I want to solve is the following:

1. Something triggers an automation
2. Call script "save scene" with args:

• scene_name - the name of the scene to save
• entities - the entities to snapshot

3. Modify the entities - maybe increase brightness of a light or whatever
4. Wait some time
5. Call script "recall scene" with arg:

• scene_name - the name of the scene to recall and then delete

This way automations can, in a simple way, reuse scripts in step 2 and 5 to make temporary changes to the state of my home, and then revert to the original state later.

[barren copper]

Yeah, if it's simply single scene I see no real use for a script (as it's already a single action). But if you want to make sure you save all attributes even when the light is off you need two scenes, that could be usefull with scripts.

But then, where are you stuck? What did you make? What does it do and what did you expect?

[halcyon anchor]

https://community.home-assistant.io/t/creating-unique-names-for-scene-create-persistant-notification-or-anything-else/742873

[rapid valley]

Creating unique names is not the problem

Home assistant not picking up new scenes in its state is the problem

[barren copper]

Okay, so please share some yaml of what you have 🙂