home-assistant
2024.10.0 breaks text to speech
The problem
After upgrading all automations with tts stop speaking
What version of Home Assistant Core has the issue?
2024.10.0
What was the last working version of Home Assistant Core?
2024.9.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I'm sure I'm not the only one experiencing this issue.
Are you running Google Cast? You probably need to provide more information. There is a thread here with people experiencing similar issues: https://community.home-assistant.io/t/google-cast-error/778156
I see similar issue with the following in the logs:
Error while executing automation automation.aa_prov_2: CastMediaPlayerEntity._quick_play Failed: Failed to execute quick play http://192.168.0.128:8123/api/tts_proxy/0e26165...0d69_sv-se_6e8b81ac47_cloud.mp3.
Not every time, works 50% of the times, compared to 100% before
me and a bunch of others are using tts.google_cloud_say and it is broken since 2024.10.0, allso microsoft_tts seems to be broken. There are several comments about this issue in this thread -> https://community.home-assistant.io/t/2024-10-heading-in-the-right-direction/777864
Logger: homeassistant.components.tts Source: components/tts/init.py:1080 integration: Text-to-speech (TTS) (documentation, issues) First occurred: 07:59:19 (1 occurrences) Last logged: 07:59:19
Error on load tts: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_en-us_xxxdedxxxe_google_cloud not in cache!
Can confirm for both Google Cloud TTS and Microsoft TTS. Error messages are not very descriptive, let me know if I can provide any additional data.
Error on load tts: 04b3d12595b23216e9056c4dbd6edb0e73edb2bb_en-us_ba229ed5ca_microsoft not in cache! Error on load tts: bb4387ee9ec0351512462bdf8438a2a27ee11d56_en-us_b346d6efd1_google_cloud not in cache!
TTS does work when using Piper though.
a Tiny solution: placing a100 milli second delay in your automation before the ttsaction wil solve your problemfor now. Not happy about it but it works a bit.
a Tiny solution: placing a100 milli second delay in your automation before the ttsaction wil solve your problemfor now. Not happy about it but it works a bit.
Interesting, thanks for this. My use case is the Voice Assistant from phone though, I don't think it is possible to set a delay there.
Oke good luck
Verzonden vanaf Outlook voor Androidhttps://aka.ms/AAb9ysg
From: Henrik Blåfield @.> Sent: Friday, October 4, 2024 8:58:21 AM To: home-assistant/core @.> Cc: Vabis1010 @.>; Comment @.> Subject: Re: [home-assistant/core] 2024.10.0 breaks text to speech (Issue #127518)
a Tiny solution: placing a100 milli second delay in your automation before the ttsaction wil solve your problemfor now. Not happy about it but it works a bit.
Interesting, thanks for this. My use case is the Voice Assistant from phone though, I don't think it is possible to set a delay there.
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/127518#issuecomment-2392962156, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUUBXGQDQ73DX4DFZ3VU4WLZZY4A3AVCNFSM6AAAAABPK7ADKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSHE3DEMJVGY. You are receiving this because you commented.Message ID: @.***>
Same issue here, I have downgrade the HA and wait for a solution. Follow the issue.
Hi. I’m getting this too. When I go to edit the automation and try to edit the media to play I get this error
Visual editor is not supported for this configuration
Key ‘service’ is not expected or not supported by the visual editor. You can still edit your config using YAML.
There was also something about not having action and service at the same time, but I can't replicate it now.
This since I updated to 2024.10.0 yesterday morning,
Hi. I’m getting this too. When I go to edit the automation and try to edit the media to play I get this error
Visual editor is not supported for this configuration Key ‘service’ is not expected or not supported by the visual editor. You can still edit your config using YAML.
There was also something about not having action and service at the same time, but I can't replicate it now.
This since I updated to 2024.10.0 yesterday morning,
Got it but Swedish so don't know how helpful this is
This will probably be fixed by reverting the upgrade of pychromecast here: https://github.com/home-assistant/core/pull/127555 Looking at this, is will end up in 2024.10.1.
Although I don't get that the upgrade has been merged last minute and ended up in the final release without being in the beta.
That fix will only fix the issues with cast, I am not convinced that the issues mentioned here are caused by cast.
This will probably be fixed by reverting the upgrade of pychromecast here: https://github.com/home-assistant/core/pull/127555
Looking at this, is will end up in 2024.10.1.
Although I don't get that the upgrade has been merged last minute and ended up in the final release without being in the beta.
Not sure what Chromecast casting would have anything to do with this, unless there's some weird dependecy hidden behind.
Can confirm this is still present in 2024.10.1, so not related to the Chromecast change which was indeed reverted in .1.
Not sure what Chromecast casting would have anything to do with this, unless there's some weird dependecy hidden behind.
Well. looking at the error message mentioned above here (I've had the same) it has everything to do with casting to chromecast devices. Error while executing automation automation.aa_prov_2: CastMediaPlayerEntity._quick_play Failed: Failed to execute quick play http://192.168.0.128:8123/api/tts_proxy/0e26165...0d69_sv-se_6e8b81ac47_cloud.mp3..
There are 2 TTS issues going on after 2024.10 :)
What would be the other issue? Would be good to provide some error message/log entry for it. And btw, 2024.10.1 fixes it for me as well.
There are 2 TTS issues going on after 2024.10 :)
What would be the other issue? Would be good to provide some error message/log entry for it.
And btw, 2024.10.1 fixes it for me as well.
The other issue is, Google Cloud TTS and Microsoft TTS stopped working after 2024.10.0.
I don't even have a Chromecast right now active. The error is repeated for example when using Voice Assist through browser, mobile app etc.
These are the log entries, as listed above as well.
Error on load tts: 04b3d12595b23216e9056c4dbd6edb0e73edb2bb_en-us_ba229ed5ca_microsoft not in cache! Error on load tts: bb4387ee9ec0351512462bdf8438a2a27ee11d56_en-us_b346d6efd1_google_cloud not in cache!
The .1 update did not fix automations where tts messages is sent. Still the unexpected "service" complaint
Indeed, I get the same error.
I tried to delete the service line in YAML and tested just the tts part of the automation and it works. But when you exit and go back to it, the service line is back. The same if I delete the action line.
I think the Visual editor is maybe adding the lines back but then can't deal with it. Can't see how it would get put back after editing the YAML.
There are 2 TTS issues going on after 2024.10 :)
What would be the other issue? Would be good to provide some error message/log entry for it. And btw, 2024.10.1 fixes it for me as well.
The other issue is, Google Cloud TTS and Microsoft TTS stopped working after 2024.10.0.
I don't even have a Chromecast right now active. The error is repeated for example when using Voice Assist through browser, mobile app etc.
These are the log entries, as listed above as well.
Error on load tts: 04b3d12595b23216e9056c4dbd6edb0e73edb2bb_en-us_ba229ed5ca_microsoft not in cache! Error on load tts: bb4387ee9ec0351512462bdf8438a2a27ee11d56_en-us_b346d6efd1_google_cloud not in cache!
Yeah, I don't have a Chromecast either, only a dumb speaker connected to an old Raspberry Pi running 'PiCorePlayer' and 'Logitech Media Server', and because I've had so many issues historically with Google Cloud TTS, it's now always the first thing I check on an update. I didn't have 2024.10.0 on my system long enough (less than than 10 minutes) to do any real troubleshooting, I didn't even try and get log entries, sorry, but other peoples errors regarding the required speech data 'not being in cache' seem to tally with my system only being able to say something that had previously been cached. Unless https://github.com/home-assistant/core/pull/127555 fixes the non-chromecast related issue too, which from some comments above, it doesn't, I'll be staying on 2024.9.3, and probably going back to waiting till closer to the end of the month for more .0 and .1 bugs to be squished.
@ekalle-swe, you can't define both action and service. Please use the forums or discord for this question
@ekalle-swe, you can't define both action and service. Please use the forums or discord for this question
Exactly, but it's doing it itself. If I remove one of them, it get's put back.
@ekalle-swe, you can't define both action and service. Please use the forums or discord for this question
Exactly, but it's doing it itself. If I remove one of them, it get's put back.
Not me, has been added by gui. Has been created through gui and has been working up to the day of upgrade.
Don't have discord
@ekalle-swe, you can't define both action and service. Please use the forums or discord for this question
Tested to make a new automation Media Player/ play media and as soon as I select the speaker group "all speakers", this appears. They are a group of Google home speakers, if that is related. Don't have any other to test. And for "you can't have both..." Yes, we know! That's kind of the reason behind it all!
If it was not obvious, my point was more being, don't move the discussion of this issue away from the original topic. Please create a separate one because this only causes noise for the original issue