Custom trigger IDs are not displayed in the new 2026.10 trigger selector

### Checklist - [x] I have updated to the latest available Home Assistant version. - [x] I have cleared the cache of my browser. - [x] I have tried a different browser to see if it is related to my browser. - [x] I have tried reproducing the issue in [safe mode](https://www.home-assistant.io/blog/2023/11/01/release-202311/#restarting-into-safe-mode) to rule out problems with unsupported custom resources. ### Describe the issue you are experiencing With the [new trigger ID system in 2026.10](https://www.home-assistant.io/blog/2026/10/07/release-202610/#the-best-automation-feature-you-never-used), the UI trigger selector now ignores any custom trigger IDs and only shows the automatically generated ones, which are very confusing if your automation uses multiple similar triggers. ### Describe the behavior you expected The checkbox selector should discover manual IDs and use those names instead of the auto-generated ones when available. In addition, the UI ID editor should be added back so that advanced users can keep using custom, more descriptive IDs. Ideally, the setup would be similar to the way it was before, but with the extra benefit of the new IDs. That way, new users can start right away, while advanced users still benefit from the better checkbox UI! There are also arguments to be made about just enabling the manual ID field by default, but I feel like that's a separate discussion. ### Steps to reproduce the issue 1. Have many automations in <2026.10 which have

Posted by inventor7777 on Oct 8, 2026, 1:32 PM

Tags

• ux (Other)

Related issues

• To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
• > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
• I hate that too, but I think it’s more the ux than the concept of a default.
• > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
• "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
• The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.