-
Notifications
You must be signed in to change notification settings - Fork 30
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
TTS is failing when used with VoiceAssistant #29
Comments
Same issue |
I was having this issue as well and gave up. I instead switched to Microsoft's TTS which has the same voices plus more, is much more responsive, and is free. Took a little to setup the azure account but got it up and running and am using this integration: https://github.com/hugobloem/wyoming-microsoft-tts |
A major update is published with a lot of changes and fixes. Please check if your issues are fixed! |
Hello, I don't think it change anything in that matter. At least for longer messages it still brakes
it did manage to process shorter answer although. What's strange it looks like it's giving up immediately, not waiting for some timeout. Anyway, when try to tts the same longer text in Media sources - it's fine |
That's really strange. I've tested with really long responses and never had an issue. For example, I just asked assist to read a poem and it was reasonably fast (as the TTS still has no streaming capabilities). How LONG text you trying to tts? Looking also the log, it looks like your home assistant is cancelling this request Certainly! Here's an expanded version of the poem:
The sun sets low on the horizon's line,
Bathing the world in hues so fine.
Orange and pink, with gentle grace,
Colors dance across the sky's vast space.
In the heart of dusk, beauty displays,
The end of a bustling, vibrant day.
Nature whispers in a soothing tone,
Guiding the weary traveler home.
The breeze carries tales from distant lands,
Through rustling leaves and whispering sands.
The melody of night begins to play,
As daylight slowly fades away.
Stars emerge in the velvet sky,
Twinkling like dreams eager to fly.
Embraced by shadow, wrapped in night,
The world prepares for moonlit flight.
Rest now, gentle soul, |
I've tried now in English - since so far it was all in Polish, but I have the same result: If you can point how to debug it better - I can do it, but just enabling debug for integration does nothing (logs are the same). This is "raw" output from conversation debug:
|
@Saur0o0n The only time when I was able to reproduce a similar error was after restarting Home Assistant and calling the TTS while the chromecast integration was not ready. Trying again after 5-10 seconds, the TTS worked fine. A new release has been published with some enhancements in fine-tuning sync/async calls, error catching, and debug logging, which may help. Im not familiar with SyncWorker so i dont know how to help debugging this error further.
|
Having said that, I've started getting errors with an unusually high number of frames on the WAV response from OpenAI (frames=2147483647). Maybe switching back to mp3 is a good solution, but i need to work on the chime. Im investigating this.
|
Hi, and thank you for all the updates.
So sadly nothing helpfull. |
Unfortunately, it seems like there's an issue with the core TTS component. There is a stale issue there, but so far no fixes or response on this. I'll try switching to MP3 and probably provide the option in the config flow to select the output format. |
For reference, have the same problem, opened an issue in January. home-assistant/core#135713 |
Hi,
I thought that is was somehow related to response time, but now I'm not sure. When used with "Try voice" button (in Voice Assistants configuration) it can be slow, but it does work. Also when tested from Media menu - it's ok.
But when used with Voice Assistant it brakes the tts subroutine somehow - in logs I can only find this:
The text was updated successfully, but these errors were encountered: