Voice Nabu Casa

It would be really helpful if Home Assistant introduced a new blueprint selector for Text-to-Speech service providers that, when an entity is selected (e.g., a TTS engine like Nabu Casa, Google or Piper) would dynamically update another selector to show only the supported voices for that provider.

Right now, we’re limited to a plain text input for the voice name, which isn’t user-friendly… especially when each provider has different and sometimes undocumented voice options. A dynamic dropdown would reduce errors, make blueprint UIs cleaner, and give users a much better experience when using TTS in automations or blueprints.

Blacky :grinning: