-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Piper TTS fails on long messages #3360
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
When trying to using Piper to generate a long tts message (on Sonos speakers, in my case), the audio never plays on the speaker. This seems to happen at around 35 seconds, for me. Anything shorter than that works fine.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Piper
What is the version of the add-on?
1.4.0
Steps to reproduce the issue
media_player.play_media
service call with a long piper tts message, e.g.The same thing happens if I send
announce: true
, but with it set to false, I can see a message in the Sonos app that says "Unable to play '' - the connection to was lost"Shorter messages, which is pretty much anything under 35 seconds, always works, and anything longer seems to always fail.
I have tried restarting various things (Home Assistant, the addon, etc.), clearing the TTS cache, and none of that has worked.
System Health information
System Information
Home Assistant Community Store
Home Assistant Supervisor
Dashboards
Recorder
Spotify
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Traceback (most recent call last): File "/usr/local/lib/python3.11/dist-packages/wyoming/server.py", line 35, in run if not (await self.handle_event(event)): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/wyoming_piper/handler.py", line 104, in handle_event await self.write_event( File "/usr/local/lib/python3.11/dist-packages/wyoming/server.py", line 26, in write_event await async_write_event(event, self.writer) File "/usr/local/lib/python3.11/dist-packages/wyoming/event.py", line 114, in async_write_event await writer.drain() File "/usr/lib/python3.11/asyncio/streams.py", line 378, in drain await self._protocol._drain_helper() File "/usr/lib/python3.11/asyncio/streams.py", line 167, in _drain_helper raise ConnectionResetError('Connection lost') ConnectionResetError: Connection lost ERROR:asyncio:Task exception was never retrieved future: <Task finished name='Task-8439' coro=<AsyncEventHandler.run() done, defined at /usr/local/lib/python3.11/dist-packages/wyoming/server.py:28> exception=ConnectionResetError('Connection lost')>
Additional information
I see this in the Home Assistant Core log:
The text was updated successfully, but these errors were encountered: