Hi Nim,
tried your solution.
Really good idea, has the option to set the speed, thats fine.
The installation isn’t without problems.
The path settings for custom sounds were not well documented, can’t find a working setup.
Feature request: When using a template in the message definition box, we loose the visual editor. This is hard, cause all the dropdown boxes with the predefined values also get lost. Maybe there is a chance to do some better input box. Sometimes I found a box for entering ,yaml code especial on the definition pages of front end elements of lovelace.
With best regards
Gerhard
Will spent you coffee for the work (and even more if the problems were solved)
Thank you so much for your support, it is very appreciated!
Regarding the custom sounds, have you reviewed the documentation for using a local folder of your own chime audio files?
In terms of your feature request for retaining the dropdown lists when switching to YAML editing mode: unfortunately this is not currently possible due to how Home Assistant has implemented the actions UI.
You are correct that some custom lovelace cards support both at the same time, however this is not the case actions (like those added by Chime TTS). Home Assistant’s actions UI is not customizable, and therefore I cannot change any UI behaviour. I would also like to see this supported, as it would definitely improve the user experience…but unfortunately my hands are tied.
Hi @Gerhard56. Following up on your request for using templates in the message textfield while in the visual editor: I just released a new beta version, v1.2.2-beta1, which implements this.