Replies: 2 comments
-
I just tried to downgrade chime_tts to V1.1.6-beta5 and after a restart, I still have the issue :-( I am now wondering if the issue could be related to the fact that 2 days ago, I also upgraded HomeAssistant to the latest version... |
Beta Was this translation helpful? Give feedback.
-
Just looked at Home Assistant Core log and here is what I found: And here are the details of the Detected blocking call to listdir entry: Logger: homeassistant.util.loop Detected blocking call to listdir with args ('http://192.168.0.200:8123/local/chime_tts',) inside the event loop by custom integration 'chime_tts' at custom_components/chime_tts/helpers/filesystem.py, line 52: dir_contents = os.listdir(parent_directory) (offender: /config/custom_components/chime_tts/helpers/filesystem.py, line 52: dir_contents = os.listdir(parent_directory)), please create a bug report at https://github.com/nimroddolev/chime_tts/issues For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#listdir Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 227, in sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 213, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.13/asyncio/base_events.py", line 708, in run_until_complete self.run_forever() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 679, in run_forever self._run_once() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2027, in _run_once handle._run() File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) File "/config/custom_components/chime_tts/queue_manager.py", line 92, in async_queue_processor await self.async_process_queue() File "/config/custom_components/chime_tts/queue_manager.py", line 50, in async_process_queue await self._process_service_call(service_call) File "/config/custom_components/chime_tts/queue_manager.py", line 57, in _process_service_call result = await asyncio.wait_for( File "/usr/local/lib/python3.13/asyncio/tasks.py", line 507, in wait_for return await fut File "/config/custom_components/chime_tts/init.py", line 189, in async_say_execute return await async_prepare_media(hass, params, options, media_players_array, is_say_url, start_time) File "/config/custom_components/chime_tts/init.py", line 299, in async_prepare_media audio_dict = await async_get_playback_audio_path(params, options) File "/config/custom_components/chime_tts/init.py", line 845, in async_get_playback_audio_path if not validate_audio_dict(hass, is_local, is_public, audio_dict): File "/config/custom_components/chime_tts/init.py", line 898, in validate_audio_dict if not (external_local_path.startswith("http://localhost") or filesystem_helper.path_exists(external_local_path)): File "/config/custom_components/chime_tts/helpers/filesystem.py", line 52, in path_exists dir_contents = os.listdir(parent_directory) |
Beta Was this translation helpful? Give feedback.
-
Hi,
A couple days ago I upgraded chime_tts, as well as Home Assistant OS & Core, to their latest version, and since then I am getting an error every time I try to generate an mp3 with the say_url service.
The file is succesfully generated in my /config/www/chime_tts/ folder (I can play it), but while generating the response the say_url service seems to throw an error trying to look for the generated mp3 in the wrong (/local/chime_tts/) folder.
Here is the action I used and the response I get:

I have enabled debug mode, and here is a snapshot of the log:

And here are my Folder Path configs (which I left to their default values):

Has anybody else experienced this issue? A few days back it used to work really fine...
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions