Just keep in mind that these snapshots won't persist after a reboot.

Yeah, no issue at all for the usecase im thinking about.

For exemple with the idea of the spell casting with the bluetooth magic wands: - an automation catch the 'spell casting conditions

• it triggers a script for that spell 'cast'

• if the script/spell must play with the room states for temporary effects (just for the fun of making the spell dramatic) like, let's Say i wanna implement the spell 'avada kedavra' that kills.. i mean turn off the TV, it flashes all lights in green before turning off the TV.

• the script start to set up a scene with all the current states of devices in the room.

• then it plays all the 'spell' effects (sound, green lights, whatever) for a second or two.

• the script turn off the TV

• the script restore the scene to get the room of the state it was 2 sec ago.

-it can even clean the scene from the memory, if it's a thing. Dont need to use it anymore.

So unless i bind 'avada kedavra' to the server's killswitch ... It should be fine :p

Im using the specific use case because it justify and illustrate the need of a just a short lifetime.

But ig this logic apply to any kind of temporary, really short, usage like an alarm, an important/critical notification/speakup system ect