-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Say URL failing randomly #239
Comments
Hi @MattJeanes, sorry to hear you're been having issues. I noticed that the folder path you have specified for the Please try changing it to: |
Indeed yeah that seems to work - but it gives me the public facing URL and not the It seems to be fine generating the audio from the look of the logs and the fact it works via the normal say command and Here's some of the debug logs with it set to use that path:
|
I'm seeing the same issue. If I want to retrieve the media_content_id by setting the chime_tts.say_url folder path to be somewhere in the Media folder:
the mp3 gets generated just fine, but the action fails "because it's not public" - here's the log for the action call:
|
System Health details
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Checklist
Describe the issue
When I am trying to use the
chime_tts.say_url
to generate a media_content_id to play via a Voice Satellite most of the time it ends up failing withsuccess: false
in the logs but not really any information on why, and sometimes it does work.It seems to do this both with cached audio and fresh audio. I have the path for say URL generated files to
/media/sounds/temp/chime_tts/
in the integration which as per Chime TTS documentation as I understand it this should generate a media_content_id instead of a public URL which is what I want.Note that the normal
say
command works fine, this is only an issue on thesay_url
one.Reproduction steps
Assume Piper is installed and configured for TTS generation
Chime TTS setup:
Response:
Debug logs
Diagnostics dump
config_entry-hacs-35f21d9727dd6bb916e21e58d59e233e.json
The text was updated successfully, but these errors were encountered: