when I play TTS to mpd integration, 4 errors are logged trying to fetch art files

ktownsend-personal commented 2 years ago

The problem

I am getting a set of 4 errors in the core log when I play TTS to the MPD integration. Other media_player devices don't generate these errors when they play the same TTS files. The MPD addon appears to have 4 corresponding CURL errors. The MPD addon also has the same 4 CURL errors when it plays non-TTS sound files, but those don't get logged in core at all. It appears the MPD integration is not filtering these CURL errors raised by the MPD addon.

This is the same issue as #47889, but I'm having to start a new issue because that issue was never acknowledged by the integration owner and it got closed as stale. If the issue lies outside of the MPD integration, please confirm true source of the issue.

My system plays a lot of TTS, so this is inflating my logs significantly.

Is it possible to disable art lookup? Not only would that work around my issue, but it would be more efficient to avoid the lookups.

What version of Home Assistant Core has the issue?

2022.9.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

mpd

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

* From core log:
Logger: homeassistant.components.tts
Source: components/tts/__init__.py:707
Integration: Text-to-Speech (TTS) (documentation, issues)
First occurred: 5:55:04 PM (8 occurrences)
Last logged: 5:56:12 PM
Error on load tts: Wrong tts file format!

* From MPD add-on log:
exception: CURL failed: The requested URL returned error: 404
exception: CURL failed: The requested URL returned error: 404
exception: CURL failed: The requested URL returned error: 404
exception: CURL failed: The requested URL returned error: 404
player: played "http://192.168.34.13:8123/api/tts_proxy/9c3de9e8ebd203887310ec65b109597256112c6a_en_-_google_translate.mp3"

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

mpd documentation mpd source _{^{(message by IssueLinks)}}

potzkin commented 2 years ago

same problem with mine:

Home Assistant 2022.9.4 Supervisor 2022.08.6 Operating System 9.0

From MPD add-on log: MPD connected. exception: CURL failed: The requested URL returned error: 404 exception: CURL failed: The requested URL returned error: 404 exception: CURL failed: The requested URL returned error: 404 exception: CURL failed: The requested URL returned error: 404 player: played "http://192.168.1.140:8123/api/tts_proxy/40bd001563085fc35165329ea1ff5c5ecbdbbeef_en_-_google_translate.mp3" exception: CURL failed: The requested URL returned error: 404 exception: CURL failed: The requested URL returned error: 404 exception: CURL failed: The requested URL returned error: 404 exception: CURL failed: The requested URL returned error: 404 player: played "http://192.168.1.140:8123/api/tts_proxy/40bd001563085fc35165329ea1ff5c5ecbdbbeef_en_-_google_translate.mp3"
From ha: ERROR (MainThread) [homeassistant.components.tts] Error on load tts: Wrong tts file format!

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ktownsend-personal commented 1 year ago

as far as I know, this is still an issue

Sireone commented 1 year ago

Seeing the same issue as well. Any workaround?

lupa18 commented 1 year ago

same here

the-px commented 1 year ago

Same

Andsbf commented 1 year ago

same

pmannk commented 1 year ago

Still experiencing the same issue here

neekz0r commented 1 year ago

This is actually kind of a big deal. Because its an auth failure, this can cascade into an ip ban. Which really horks the media player system.

You are then left with one of three options: have a broken media player system. Configure the login_attempts_threshold to be high, which breaks some security stances, or some wierd script that removes the IP that was just banned from the ip_bans list.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ktownsend-personal commented 1 year ago

It's not stale. It has received no attention from the maintainer. The problem still needs to be fixed.

stalakerob commented 11 months ago

Same issue here. Wanted to keep this issue report alive. But its more than a year old now so it seems nobody cares unfotunately.

kjosavik commented 11 months ago

I am experiencing this as well

gregkg commented 10 months ago

Ran into this exact issue yesterday after installing MPD to my Raspberry Pi voice satellite. 4 core log 'invalid authentication errors' while trying to retrieve album cover art when streaming & 4 'on load tts: Wrong tts file format' error when doing TTS. HAOS version is 2023.12.4

dolai1 commented 10 months ago

Same here. MPD instance on another subnet, which I am guessing relates...

jerblack commented 9 months ago

I am experiencing the same issue? Any explanations on why this seems to just seems to be getting ignored? This is breaking Piper TTS to mpd for me right now, since every time I try to use TTS, it is silent and my mpd.log shows this:

Jan 30 12:37 : exception: CURL failed: The requested URL returned error: 404 Not Found
Jan 30 12:37 : exception: CURL failed: The requested URL returned error: 404 Not Found
Jan 30 12:37 : exception: CURL failed: The requested URL returned error: 404 Not Found
Jan 30 12:37 : exception: CURL failed: The requested URL returned error: 404 Not Found
Jan 30 12:37 : player: played "http://homeassistant.home:8123/api/tts_proxy/64047c501706ed3240c5a73503ed036c0f128dc7_en-us_a24df4c9b0_tts.piper.mp3"

Even trying to play an mp3 to that mpd instance through Media in Home Assistant fails.

Jan 30 12:34 : exception: CURL failed: The requested URL returned error: 401 Unauthorized
Jan 30 12:34 : exception: CURL failed: The requested URL returned error: 401 Unauthorized
Jan 30 12:34 : exception: CURL failed: The requested URL returned error: 401 Unauthorized
Jan 30 12:34 : exception: CURL failed: The requested URL returned error: 401 Unauthorized
Jan 30 12:37 : player: played "http://homeassistant.home:8123/media/media/{test}.mp3?authSig={auth_string}"

Sireone commented 8 months ago

Ditto! Anyone have success fixing this?

issue-triage-workflows[bot] commented 5 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

neekz0r commented 5 months ago

bump, No, it is not stale.

ser commented 4 months ago

I am tracing this issue as it drives me mad, I filed a related issue: https://github.com/nimroddolev/chime_tts/issues/159

jared-skinner commented 4 months ago

Just tried setting this up. I'm experiencing this too.

ClubspeedChris commented 1 month ago

Same problem here, but its been years so I have no hope it'll ever be looked at. Any other options you guys are using?

melyux commented 1 month ago

This is what someone said (idk who)

Advised that these messages are due to MPD looking for thumbnail images (in 4 different formats) relating to the music file being played ... so ... fortunately we can ignore these messages more as a warning - and unfortunately this issue can not be fixed in the context of the addon.

ktownsend-personal commented 1 month ago

Frankly, I am disappointed that not a single maintainer of MPD or of Home Assistant has taken the time to even acknowledge this issue, even if just to say it's low priority or unfixable. I wouldn't even mind a suggestion of a different local audio integration alternative with better support. sigh

home-assistant / core