No triggers listed for devices in creating new automations

[freshcoast]

If this is a pre-existing automation, you will need to delete the trigger and re-create it so the new replacement device is selected, or else edit the trigger in YAML and update the device_id. Your scenario is effectively a device replacement, which is not supported. If that’s the case the device currently selected corresponds to the disabled integration. This is one of the problems with using device triggers/conditions/automations.

IMO, better to use state triggers so you can just update entity names in case of device replacement.

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 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 you h…

Add a method of replacing devices

Automations associated with a device are marked as unavailable if you replace that device if it is faulty/stolen etc… For state automations you just name the new entity_id the same as the old and… you’re done. For device automations you have to search out all the occurrences of the old device_id and replace them with the new one. You cant just edit the new device id to be the same as the old one. For people only using the UI this is daunting task and they would probably end up re-writing all …