Blueprint Trigger Selector some Motion Sensors "no triggers available" .... Bug Reported

I did. My point was not about ‘we need a feature for XYZ’ but about ‘the way it works right now is not right’. It should not be filtering / excluding Entities based on “Show As” … at all. “Show As” value is irrelevant to functionality of the entity. Its purely cosmetic -yet still- the Selector excludes any “Show As” value it doesnt yet ‘know about’… just not right.

The new triggers use device_class. That’s it. Drew already mentioned and found a trigger that’s being added that doesn’t use device_class.

Again, this is a work in progress and all features may not exist, but they are coming.

There’s nothing more to argue here. There’s no bug. There’s just future confirmed features.

Closing because this is just going in circles and all questions have been answered.