Bug with automation aliases

Configuration
1

Hi there.

Since version 0.92.1, the trigger in my automation does not work.

I’ve been struggling to find the reason. Using the automation editor, I could have it running sometimes, and sometimes not.

After days of tests, I finally discovered the issue was the alias.

Any previously existing automation alias prevent the trigger to work.

If I rename the alias, it works fine.

Everything else work. Meaning related actions can be triggered manually.

What can cause this ? Is there anyway I can “clean up” the old aliases which might create this bug ?

2

I ended up renaming all my aliases and it fixed my problem.

Still this is a weird bug and might deserve a lookup.

3

Are they in quotes (particularly if you have spaces in the alias)?

- id: mains_power_fail_alert
  alias: 'Mains Power Fail Alert'
  initial_state: true
  trigger:

Some example show this, others don’t. I’ve always wrapped my aliases in quotes and haven’t had a problem.

4

I used to wrap my aliases in quotes, but now I only do that when linter/config checker complains :wink: