Random Position for Cover

[armedad]

service: cover.set_cover_position
data:
  position: >
    {{ range(1,20) | random | int }}
target:
  entity_id: cover.your_cover_entity_name

i’m using entity id’s instead of device id because of this:

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 yo…

but if you really want to stay with device_id, you can still use the position template