I donât believe you need âto:â since the docs show an example without. Iâve always used/seen âplatformâ being listed before the âentity_idâ but I suppose that should not really make any difference if the HA parsers worked independently of that order.
edit: i know its enabled by default but just wondering if it ever got disabled at some point and the recovery state of the automation is then out of whack.
Yeah you have âtriggerâ inside your template and Iâm almost sure that it is this that he complains about. Canât test right now as Iâm not home. Your example canât work, did you try exactly the code I suggested?
Your template is wrong and you need to change data to data_template and payload_template to payload (as far as I know payload_template is not valid for automations.
When you execute an automation manually the trigger and condition part are skipped and it goes straight to the action part. And your action part canât work when you trigger it manually, because you donât have a trigger then and your template will fail. To ensure that the trigger part is correct, change the action part to something easy like turn on a switch, then change the input select and see if the switched turned on.
Edit: I just saw that your error message shows that it is the trigger in the template for the service call that is causing the issues and not the trigger part.
Error rendering template for call_service at pos 1: UndefinedError: 'trigger' is undefined
Edit 2: Just tested this in my test environment and can confirm it works as intended: