Glad to hear it fixed the problem.
Please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic has been resolved. This helps users find answers to similar questions.
For more information about the Solution tag, refer to guideline 21 in the FAQ.
As for your question, when choosing an action in the Automation Editor it defaults to highlighting a Device Action. This type of action was created to solve a problem with a service call action. If you rename an entity’s entity_id existing service calls in your automations continue to refer to the entity by its old entity_id. Naturally this causes existing service calls to fail.
A Device Action is supposed to avoid this problem by assigning an unchangeable device_id to a physical device. You can freely change its entity_id but it won’t break existing Device Actions because they continue to use the unchangeable device_id.
That’s the theory but in practice something went wrong on your system and your Device Actions failed by referencing a non-existent entity.