#TTS / Sonos issue in 2023.5.0b1
1 messages ยท Page 1 of 1 (latest)
there's a new method for playing TTS/announcements, but those should work just fine
Is the new method documented anywhere? I would be happy to try it
it's automatic, you're using it ๐
anything that uses announce in the play_media service call triggers it, which TTS does
are you using a script or automation? or have you tried just the service call by itself?
Ah, interesting. I did try some manual service calls (tts.cloud_say and tts.google_translate_say with the Sonos media_players as entity_ids) and they threw the same error.
I wonder if something changed in the Sonos firmware. They pushed out a 15.3 update to S2 devices on 4/18. If it was rolled out gradually, I might have just received it today.
shouldn't be related
can you clarify if you're getting an actual error in the UI when you make the service calls? the logging error is actually semi-expected
No error in the UI. Call Service button turns to green checkmark
oh weird, hold on a minute
i think i know what's going on, you're not crazy nor doing anything wrong ๐
Haha... Oh good
the error you see is a red herring, but should still be improved
if you have a local audio file (some short alert sound), try to play that with media_player.play_media and with announce: true
the problem is that TTS audio file URLs aren't resolving properly
sorry about that, this should fix it: https://github.com/home-assistant/core/pull/92154
thanks for testing and reporting the issue ๐
ok it should be in the next beta. do me a favor and test out TTS while music is playing and let me know how it works ๐
(once next beta is out)
Will do! Thanks for hanging out here and looking into the issue so quickly
new beta just cut, please test when it's out
and I just put in another fix for the unnecessary error messages you were seeing, but that won't be until the next beta
Just installed, TTS working as before. Thanks again.
The only other weirdness I've seen with the May beta is that the logfile keeps telling me to remove the deprecated history: element from config.yaml, but when I remove it and restart, history actually (correctly?) becomes inaccessible for all entities. Graphs don't render, etc. Adding history: back to the config returns everything to normal with data intact. Should I ping bdraco?
i'd just create an issue for that
glad it was an easy fix
and again: try the TTS while music is playing. no need to snapshot/restore anymore ๐
Nice... I hadn't bothered doing that in my scripts, good to know it's baked in now