Remove individual user-defined scripts from "By type" action picker

[marcinbauer-ohf]

Summary

When selecting Script in the By type tab of the Add action dialog, every user-defined script is listed as a separate action entry alongside built-in script domain services (Reload, Toggle, Turn on, Turn off).

Problem

1. Indistinguishable duplicates — scripts with identical or default names (e.g. "New script") appear as multiple identical entries with no way to tell them apart (see screenshot)
2. Wrong paradigm — user-defined script instances are not action types. The "By type" tab should list action types, not specific callable instances. This creates a confusing mix of type-level services and instance-level entries in the same list

Expected behavior

Individual user-defined scripts should be removed from the "By type" list. Only the built-in script domain services (Turn on, Turn off, Toggle, Reload) should remain. Users who want to call a specific script should use the By target tab or the search field.

Screenshots

Environment

• Home Assistant Frontend

[karwosts]

If you go by target, doesn't that only allow you to pick an entity which then gives the option to use script.turn_on?

There still needs to also be a way to call script.my_script action, not just script.turn_on (entity: script.my_script) Or is that only going to be possible via search?

[marcinbauer-ohf]

By target yes:

But by type shouldn't list all of the available targets:

The current resulting YAML is also not aligned with how we format triggers/conditions/actions:

[karwosts]

The current resulting YAML is also not aligned with how we format triggers/conditions/actions:

How would you format that red highlighted box yaml otherwise?

[marcinbauer-ohf]

Its still possible to use this YAML (to create breaking changes), it's just we shouldn't use this format when using UI. We should use script.toggle, and entitiy_id.

[karwosts]

Only script.<script_id> supports the user-defined UI fields though. I actually find that much more UI and user friendly than script.toggle 😕

Also calling the script directly has different behavior than using turn_on or toggle, one is blocking and the other is not blocking.