Skip to content
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

Fails to play on a cast device #153

Open
3 of 4 tasks
Wazbat opened this issue Sep 5, 2024 · 3 comments
Open
3 of 4 tasks

Fails to play on a cast device #153

Wazbat opened this issue Sep 5, 2024 · 3 comments

Comments

@Wazbat
Copy link

Wazbat commented Sep 5, 2024

System Health details

System Information

version core-2024.9.0
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.4
os_name Linux
os_version 6.6.46-haos
arch x86_64
timezone Europe/London
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 4988
Installed Version 2.0.1
Stage running
Available Repositories 1395
Downloaded Repositories 3
Home Assistant Cloud
logged_in true
subscription_expiration 29 September 2024 at 02:00
relayer_connected true
relayer_region eu-central-1
remote_enabled true
remote_connected true
alexa_enabled false
google_enabled true
remote_server eu-central-1-18.ui.nabu.casa
certificate_status ready
instance_id 91aad9cfb4294836b05a2f41ad01467e
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 13.1
update_channel stable
supervisor_version supervisor-2024.08.0
agent_version 1.6.0
docker_version 26.1.4
disk_total 234.0 GB
disk_used 9.4 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons Studio Code Server (5.15.0), Whisper (2.1.2), Terminal & SSH (9.14.0), Mosquitto broker (6.4.1), openWakeWord (1.10.0)
Dashboards
dashboards 4
resources 3
views 7
mode storage
Recorder
oldest_recorder_run 26 August 2024 at 11:06
current_recorder_run 5 September 2024 at 00:25
estimated_db_size 182.61 MiB
database_engine sqlite
database_version 3.45.3
Spotify
api_endpoint_reachable ok

Checklist

  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of currently previous issues..

Describe the issue

When trying to play audio using TTS, the cast device fails to play the sound with the following error:

Failed to cast media http://192.168.1.235:8123/api/tts_proxy/513b617bc5de6f894ff2d8cb9fbca7234d5de01b_en_707b9c91cf_tts.elevenlabs_tts.mp3 from internal_url (http://192.168.1.235:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address

I've pasted the url in browser and it plays just fine. It also played it just fine in the past.

I'm wondering if this could perhaps be due to something like a race condition? Maybe HA is telling the cast device to play the file before it's ready?

Reproduction steps

  1. Select a chromecast device
  2. Select media to play
  3. Select ElevenLabs TTS as the source
  4. Type text
  5. Click send
  6. Nothing plays

Debug logs

No response

Diagnostics dump

No response

@Technically-Possible
Copy link

Same issue
image
image

@Technically-Possible
Copy link

Technically-Possible commented Sep 12, 2024

Also to add to this i can see in 11 labs that the file isn't in the history so it's not actually generating any audio, which is. probably why we can't cast it, but I don't know why it's. not generating audio through the TTS system because if I do it through the assistant system within home assistant, it works fine. It just seems to be the TTS system interacting with 11 labs.

@Wazbat
Copy link
Author

Wazbat commented Sep 12, 2024

I think that's an unrelated issue. On my end it's generating the audio file (accessible via the url), so it's in the history

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants