core: 2023.7 killed cloudsay

The problem

After upgrading all my tts automations stopped working. I noticed an error message about the yaml saying base_url was preventing google_translate / google_say from starting when in fact that was the line that allowed it to work in the first place because it let the google speakers know what url to use to get the media through nabucasa. This also seems to be counter to the whole 6 months deprecation thing. This seems to be a recurring thing that has been happening throughout the history of releases. This is a breaking change and there seems to be no fix for it. Searching for a solution that won’t be killed by a release as the year of the voice needs to, you know, speak. Screenshot from 2023-07-07 16-25-50

What version of Home Assistant Core has the issue?

core-2023.7.1

What was the last working version of Home Assistant Core?

core-2023.6.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

google_translate

Link to integration documentation on our website

https://www.home-assistant.io/integrations/google_translate

Diagnostics information

No response

Example YAML snippet

# Text to speech
tts:
  - platform: google_translate
    service_name: google_say
    cache: true
    cache_dir: /tts
    time_memory: 300
    base_url: https://mynabucasaweird-id.ui.nabu.casa

Anything in the logs that might be useful for us?

Invalid config for [tts.google_translate]: [base_url] is an invalid option for [tts.google_translate]. Check: tts.google_translate->base_url.

Additional information

From Mariusthvdb who commented on May 26, 2020:

just to be sure: is your now added base_url under tts the external_url?
Ive only been able to get tts google to talk, using my external_url under internal_url.....

neither the IP address https://192.168.1.72:8123, or the https://hassio.local:8123 make tts speak. (I do hear the bleep)

Ive checked the core.config, and that shows 0.0.0.0 for internal_url... which seems incorrect?

and, even when I use:

homeassistant:
  name: Ha Rpi4
  internal_url: !secret base_url

(which is silly of course, setting the internal_url to the external_url....) and my system starts speaking again, the setting isnt reflected in core.config where internal_url then still is showing 0.0.0.0

all in all I feel this issue should still be open, as it now is solved using a hack...

what is wrong here? thanks for checking if you would

About this issue

Original URL
State: closed
Created a year ago
Reactions: 4
Comments: 37 (1 by maintainers)

Most upvoted comments

@emontnemery Eric can you please take a look at this thread and consider adding , prefer_external=True to the statement base = get_url(self.tts.hass, prefer_external=True) in HomeAssistant/components/tts/init.py line 876 thereby maintaining the elimination of baseurl and adding back the functionality that is required to have tts talk to google devices?

vhillaire on Jul 9, 2023

Ahh what an idiot, of course. Thank you. Unfortunately, it didn’t fix the issue for me anyway. Although my issue has changed slightly now. Originally the google device would be stuck in buffering and this is no longer the case.

error:

` Logger: aiohttp.server Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:403 First occurred: 19:17:21 (2 occurrences) Last logged: 19:17:21

Error handling request Traceback (most recent call last): File “/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py”, line 332, in data_received messages, upgraded, tail = self._request_parser.feed_data(data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “aiohttp/_http_parser.pyx”, line 551, in aiohttp._http_parser.HttpParser.feed_data aiohttp.http_exceptions.BadStatusLine: 400, message=“Bad status line ‘Invalid method encountered’” `

and

` Logger: homeassistant.components.cast.media_player Source: components/cast/media_player.py:378 Integration: Google Cast (documentation, issues) First occurred: 19:17:21 (1 occurrences) Last logged: 19:17:21

Failed to cast media https://192.168.1.105:8123/api/tts_proxy/ac9e1662ad3c736bf0aa5ac97316a4a2fa3859e2_en-ie_b51835fb6e_cloud.audiooutput.mp3 from internal_url (<internal_URL>). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address `

Switch my internal URL back to automatic and everything is working now.

Jaykurb on Jul 19, 2023

Nice work @Korpip , can you commit the code changes on behalf of @emontnemery , as I think he is on leave.

ZoltrixGFC on Jul 31, 2023

Seems like adding ,prefer_external=True to the statement base = get_url(self.tts.hass,prefer_external=True) in HomeAssistant/components/tts/init.py line 876 might do the trick someone more familiar with the code might know.

To reach that from ssh 22222 I have to “docker exec -t -i homeassistant /bin/bash” correct?

Our home loves the TTS and waiting for this is getting harder. Hopefully the devs can get some free time to fix this but until then I will try to do what I can from my end.

Edit. It worked. I was able to copy the file to /config/ and edit it and then copy it back after using the file editor add-on to make the changes.

Local url has to not have HTTPS. Did a full power down and power on.

Korpip on Jul 26, 2023

What did the trick for me was (apart from removing the tts section from config.yaml) to change, on /config/network, the Home Assistant URL > Internet url from http://blablabla.duckdns.org:8123 to https://blablabla.duckdns.org:8123 (note the httpS)

Then in my automation :
service: tts.speak
data:
  message: Attention. You've got mail
  media_player_entity_id: media_player.salon
  language: en-us
target:
  entity_id: tts.google_en_com
tts.google_en_com being the entity of the Google Translate text-to-speech integration.

THANK YOU!!! it works for me too!

hmakmur on Jul 18, 2023

Historically, because there are lots of changes, we see bugs when new version comes up first Wed of the month . You should never install it until 3rd week of the month if you are not willing to deal with the bugs. I am thankful for all HA teams and volunteers for their hard work to improve this product. I think they do exceptional work. I dont know if there are any project is this active with new features and 3-4 changes every months to correct bugs.

hmakmur on Jul 14, 2023

questa rotta adesso non mi piace. Se non ci sarà un cambio, io tolgo il disturbo e non andrò avanti. Mi sembra assurdo che per avere google occorre abbonarsi a nabu casa. Chiedo se questo è vero e se resterà così. Grazie tante

mikimast on Jul 14, 2023

Seems like adding ,prefer_external=True to the statement base = get_url(self.tts.hass,prefer_external=True) in HomeAssistant/components/tts/init.py line 876 might do the trick someone more familiar with the code might know. Screenshot from 2023-07-08 09-10-31

vhillaire on Jul 8, 2023

Here aswell… 😦

AussiSG on Jul 8, 2023