Closed KLForsythe closed 2 years ago
tts documentation tts source (message by IssueLinks)
Hey there @pvizeli, mind taking a look at this issue as it has been labeled with an integration (tts
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
Hello, This issue is related to somehow an issue something near a year ago. The media_library is not handled by vlc source code. It tries to open the media-source url and the entity cannot discover the path.
As per error in the reported issue VLC is unable to open the MRL 'media-source://tts/picotts?message=Door+open&language=en-US'
And here mine not available in home assistant log [00007efd848594c0] main input error: Your input can't be opened [00007efd848594c0] main input error: VLC is unable to open the MRL 'media-source://tts/google_translate?message=hello&cache=true&language=fr'. Check the log for details.
I was able to use VLC to play some media library file by calling the entity with the full path. I am not able to search the VLC and TTS integration. I will fallback on espeak for now
I tried switching from vlc to gstreamer, to see if it made a difference. With gstreamer, just as with vlc, tts works in 2022.4.7 but not in version 2022.5.4. However, the logs provided some additional information.
On making the following service call:
service: tts.picotts_say
data:
entity_id: media_player.gstreamer
message: hello
In version 2022.4.7 (which works), I see the following in the logs:
17.05.22 14:02:59 (-0400) homeassistant 2022-05-17 18:02:59 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [4011783168] Sending {"id":2,"type":"event","event":{"c":{"media_player.gstreamer":{"+":{"lu":1652810579.62104,"c":"1c9edb9d075bd7c41e745e8bcc5af2c9","a":{"volume_level":1.0,"media_content_id":"https://hjbb4d67bd2a65f576t8736.balena-devices.com/api/tts_proxy/a94a8fe5ccb19ba61c4c0873d391e987982fbbd3_en-us_-_picotts.wav","media_duration":-1,"media_title":"","media_artist":"","media_album_name":""}}}}}}
While making the same service call in version 2022.5.4 (which does not work), I see the following:
:32
17.05.22 14:27:54 (-0400) homeassistant 2022-05-17 18:27:54 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [4015399048] Sending {"id":2,"type":"event","event":{"c":{"media_player.gstreamer":{"+":{"lu":1652812074.154196,"c":{"user_id":"aa5c86f2f6744bfa97fc0947ec32d3ca","id":"0180d346c8724988a8c08c5c26c44aaa"},"a":{"media_content_id":"media-source://tts/picotts?message=hello"}}}}}}
As you can see, there is a substantial difference between the media_content_id in the working version vs the non-working version.
Why is the media_content_id being configured differently? And what changes need to be made so tts can work in version 2022.5?
@balloob @frenck Could this PR https://github.com/home-assistant/core/pull/70835 have caused the problem noted above?
Do you have any insight into what changes I need to make so that tts.picotts_say will work in HomeAssistant Container? I've followed all the instructions in the documentation and those listed in the breaking changes ( I am not using the deprecated base_url in the tts settings for example, and instead have internal_url and external_url set - this worked in 2022.4.7).
I would really appreciate it if you could help me figure out what has changed between 2022.4.7 and 2022.5 that is now preventing tts say services from getting the url they were setting previously.
Yeah, looks like VLC and GStreamer both don't resolve media sources. I will open a PR to fix that.
The problem
With release 2022.5, the tts integration is no longer working with my configuration. It was working up to 2022.4.7.
Instead of hearing a local announcement through the speaker connected to my rPi, I see the following in my container logs:
I am not using the deprecated option BASE_URL, which was noted as a breaking change in the docs - the INTERNAL_URL and EXTERNAL_URL options are set in the configuration.yaml, and work fine in versions 2022.4.7 and earlier, and haven't been able to find any other breaking changes that could contribute to this problem. But something must have changed other than the listed breaking changes - tts worked well with my configuration up until 2022.5.
I'd appreciate any assistance.
What version of Home Assistant Core has the issue?
2022.5
What was the last working version of Home Assistant Core?
2022.4
What type of installation are you running?
Home Assistant Container
Integration causing the issue
tts, vlc, picotts
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tts/
Diagnostics information
No response
Example YAML snippet