Response error 500

In my case the problem was an existing automation which I wrote in automations.yaml, without a unique ID.

I could see but not edit this rule in the UI. Creating new rules in the UI caused the famous 500. I could, however, clear automations.yaml, then create new rules via UI, and even ‘migrate’ my previously handwritten rule from the UI to file. Perfect. Just not intuitive.