core: when I play TTS to mpd integration, 4 errors are logged trying to fetch art files
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
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 2
- Comments: 18 (2 by maintainers)
It’s not stale. It has received no attention from the maintainer. The problem still needs to be fixed.