Are you sure the state is “locked” and “unlocked” and not “on” and “off”? Does ot disarm the alarm when you teigger the automation manually? ( this will skip the trigger and condition part and go directly to the action part)
That’s not correct, I tried a bunch of automations with data where I didn’t put the entity_id into the data section in the past. HA doesn’t care, it should do it automatically. If I had more time I would provide you some working examples, but you can easily try it yourself. Maybe I’ll find some time tonight to check the alarm panel one.
A workaround for having automations with secrets and preventing that they are edited in the GUI is with automation secret. Automations in that file will not be editable in the GUI and thus be safe to use.
# Configuration.yaml example
# for the frontend
automation: !include automations.yaml
# for your automations with secrets
automation secret: !include secret_automations.yaml