carleeno
commented
3 months ago Hi, Please make sure you update to the latest version of this integration.
Duplicate of #136
Closed Technically-Possible closed 3 months ago
carleeno
commented
3 months ago Hi, Please make sure you update to the latest version of this integration.
Duplicate of #136
Technically-Possible
commented
3 months ago Has the way to use this changed too I cant get it to send any data or receive it I'm getting Logger: homeassistant.components.cast.media_player Source: components/cast/media_player.py:405 integration: Google Cast (documentation, issues) First occurred: 12:56:43 am (13 occurrences) Last logged: 1:05:00 am
Failed to cast media http://192.168.86.43:8123/api/tts_proxy/a0f58f7e9238b8d577822294c20673c243bd091f_en_-_tts.elevencave.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address Failed to cast media http://192.168.86.43:8123/api/tts_proxy/d7ebbc248898f4cc76779a5aad78a8431a25f143_en_-_tts.elevencave.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address Failed to cast media http://192.168.86.43:8123/api/tts_proxy/7db8219752476d725fcc1fe642dcca252f41d5f8_en_-_tts.elevenisac.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address Failed to cast media http://192.168.86.43:8123/api/tts_proxy/a94a8fe5ccb19ba61c4c0873d391e987982fbbd3_en_-_tts.elevencave.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address Failed to cast media http://192.168.86.43:8123/api/tts_proxy/a94a8fe5ccb19ba61c4c0873d391e987982fbbd3_en_-_tts.elevencort.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Any time I try send a messages to be made into audio I Checked 11labs it never makes it to it
Technically-Possible
commented
3 months ago I have Plenty of the quota left I have generated text from it before and all the voices work it just seems like the data isn't making it from home assistant to 11 labs even though the 11 labs integration says it's working completely fine
carleeno
commented
3 months ago Hmm, that's a different error than what you first posted. That isn't related to the update, it's generating the audio just fine, but you're having a network problem preventing your cast device from accessing the generated MP3.
Try testing the integration directly in your browser instead of using a cast device. Go to Settings -> Voice Assistant -> edit your assistant -> Try Voice, and see if it works there.
Technically-Possible
commented
3 months ago I apologize if my previous message was unclear. The system is not generating audio at all, and I am unable to connect it to Eleven Labs in any capacity. I have attempted various methods to trigger it within Home Assistant, including manual attempts, but to no avail. It does not seem to communicate with the Eleven Labs website. While I can generate audio directly on the Eleven Labs platform, the integration is failing to connect. Initially, the API recognized the voices, but when attempting to generate audio, it encounters issues.
carleeno
commented
3 months ago I'm sorry, I can't help you without the relevant error messages from your logs.
The logs you shared last do not show any errors with this integration, only cast errors.
The previous logs you shared indicate it was the old version that still had Domi as the default. Those logs also show that you had duplicate entities which were not found (elevenlabs_tts_2 and elevenlabstts)
I'd recommend you completely remove the integration and entities (including any duplicates), and install the latest version. Then try to generate audio directly without cast devices using my instructions in the previous message, and if it still doesn't work, filter the logs for [custom_components.elevenlabs_tts.elevenlabs] to see the relevant errors.
Technically-Possible
commented
3 months ago Logger: homeassistant.components.cast.media_player Source: components/cast/media_player.py:405 integration: Google Cast (documentation, issues) First occurred: 1:10:09 am (7 occurrences) Last logged: 8:50:03 am
Failed to cast media http://192.168.86.43:8123/api/tts_proxy/d7ebbc248898f4cc76779a5aad78a8431a25f143_en_-_tts.elevencave.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address Failed to cast media http://192.168.86.43:8123/api/tts_proxy/d7ebbc248898f4cc76779a5aad78a8431a25f143_en_-_tts.elevenisac.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address Failed to cast media http://192.168.86.43:8123/api/tts_proxy/240e90da06439aa78e2bc54b29ba46186bfbf1bd_en_-_tts.elevencave.mp3 from internal_url (http://192.168.86.43:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
carleeno
commented
3 months ago Those logs are not from this integration. Try searching HA forums for those cast errors.
Technically-Possible
commented
3 months ago I understand this may seem like a casting issue however this is most definitely a Eleven labs issue Due to the fact every other tts voice installed on the system works completely fine with casting it's just 11 labs that doesn't
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1385 Downloaded Repositories | 35Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 8 August 2024 at 1:00 am 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-16.ui.nabu.casa certificate_status | ready instance_id | f11ed2b58ae54e7ea4ae9297ea074e4c can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.4 -- | -- update_channel | beta supervisor_version | supervisor-2024.07.0 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 30.8 GB disk_used | 9.1 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | AirCast (4.2.1), Whisper (2.1.2), AdGuard Home (5.1.1), Terminal & SSH (9.14.0), Google Assistant SDK (2.5.0), File editor (5.8.0), Matter Server (6.3.1), openWakeWord (1.10.0), Music Assistant Server (beta) (2.2.0b2)Dashboards
dashboards | 2 -- | -- resources | 20 views | 4 mode | storageRecorder
oldest_recorder_run | 31 July 2024 at 8:19 am -- | -- current_recorder_run | 1 August 2024 at 4:07 pm estimated_db_size | 171.88 MiB database_engine | sqlite database_version | 3.45.3Checklist
Describe the issue
All of a sudden my 11 labs voices just stopped working when I checked the integration it says that there was an error and to cheque the logs and the logs say that they're not able to find the voice of Domi bear in mind they're not actually pointing at that voice and they're pointing at custom voices i've made I've filled out all the details assumingly correct but for some reason it keeps erroring and saying that I can't find the voice domi
Reproduction steps
Debug logs
Diagnostics dump
No response