WTH duplicate an automation is not so easy?

[wanico]

It would be great if when I duplicate an automation it would only ask me the entities/devices… to replace
e.g. Motion sensor was => motion sensor becomes?
Light was => Light becomes?

At least, it could stay as it is today but I would expect the action not to change when I select a new entity/device.
e.g. I had an action to set my cover to set my cover position to 40% in my original automation. When I duplicate it and replace my cover by another one, the action is reset to the first in the list.
So finally I just duplicate the template of the original automation not much more.

[atlflyer]

What you’re describing sounds a lot like blueprints.

[Didgeridrew]

This sound like an issue that may be caused by using Device-based parameters.

Why and how to avoid device_ids in automations and scripts

Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. [image] It works… but it is certainly not a “great way to start” because it is storing up problems for the future. Far better to use an entity, with state or numeric_state. Device_id problems The yaml will be longer and harder to follow, which may make maintenance difficult, especially a few months down the line when y…