The log error: Error calling tts.media_source.generate_media_source_id: Invalid TTS provider selected
suggests that the Amazon Polly TTS service is not configured correctly on your Home Assistant instance. Please call the chime_tts.say_url service with Amazon Polly as the TTS platform to see if the issue is with Amazon Polly or with the Echo speaker.
I just came across this and I’d like to use chime_tts for my Alerts. But for Alerts you have to set up a Notifier and I’m struggling to see how to set this up or if indeed that is even possible. Has anyone done this ? Is it possible?
Hi @jazzmonger, I am not sure if I understood your last message. Have you configured Amazon Polly and tested it with the chime_tts.say_url service (not the chime_tts.say service)?
Ok, well I don’t think it’s possible directly in its current form.
I will take a closer look at it when I can and perhaps add support in a future release.
Just playing around last night with the latest (
v0.10.0) version of this integration. I have this action called from an automation:
- service: chime_tts.say
data:
message: Just testing the doorbell!
tts_platform: cloud # also tried google_translate
volume_level: 0.7
target:
entity_id:
- media_player.office_speaker
- media_player.hallway_speaker
This resulted in the following error:
2023-12-03 20:04:05.167 ERROR (Thread-10) [homeassistant.components.cast.media_player] Failed to cast media https://<public_url>:8123/mediasoundstempchime_tts/yxmy87d7.mp3?authSig= from internal_url (https://<public_url>:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
When tested, the url returned a 404, which wasn’t surprising given the rather odd mediasoundstempchime_tts path. I’ve checked the integration config, and it’s correctly reporting the temporary MP3 folder path as /media/sounds/temp/chime_tts/
Much better! Thanks for the quick response I’ll go back to experimenting and playing.
One further question: is there any built-in way within this integration to get rid of the default Google Home “chime” when first sending a TTS announce down to it?
My first issue is it is not using the port of the home assistant URL of https://agilehumor.com:8123 and instead is omitting the port #
Log snippet:
2023-12-04 10:07:04.677 DEBUG (MainThread) [custom_components.chime_tts] Final URL = Coming Soon
My second issue is that it does not seem to be generating the full public URL (www path?) and using the local. As this is first time installed, unsure of expected results.
Hi @AgileHumor. I am not sure why the file paths for the generated MP3s aren’t working for your setup. I haven’t heard from any other users who ran into this issue.
Could you please describe your Home Assistant instance in a little more detail? Are you running HAOS or a Docker container, etc?
Which version of Chime TTS do you have installed?
It would be helpful to see the debug logs for Chime TTS to better understand what the issue might be. To see debug logs for the integration please follow these steps:
