Closed JCummings49 closed 7 months ago
Hi @JCummings49.
You mentioned that you receive these warnings "fairly random and often". From the debug logs you provided it looks like they occurred during startup. Do you also receive these warnings throughout the day?
You didn't mention whether you're having any issues with Chime TTS beyond receiving these warnings. Any additional information might prove useful to understanding the issue.
Regarding the 3 warnings themselves:
2024-04-10 14:40:16.481 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration chime_tts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
This warning is standard for any integration that is not part of the core HA OS, and can be ignored.
2024-04-10 14:40:37.210 WARNING (MainThread) [py.warnings] /usr/local/lib/python3.12/asyncio/base_events.py:1989: RuntimeWarning: coroutine 'ChimeTTSQueueManager.queue_processor' was never awaited handle = None # Needed to break cycles when an exception occurs.
This warning is not related to Chime TTS, but perhaps the asycio
python library. I haven't seen this warning during development & testing which makes it hard for me to dig deeper, and I also can't say if its widespread. Do you receive similar warnings from other integrations?
2024-04-10 14:40:49.663 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from SonosZP.attlocal.net (192.168.1.198). Requested URL: '/media/local/sounds/temp/chime_tts/ayqpvcsz.mp3?authSig=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiIwOGUwOTlkNTAyYmI0NzYzODNmZTdlNzlhMGE3OGVhYSIsInBhdGgiOiIvbWVkaWEvbG9jYWwvc291bmRzL3RlbXAvY2hpbWVfdHRzL2F5cXB2Y3N6Lm1wMyIsInBhcmFtcyI6W10sImlhdCI6MTcxMjU5MzMxNiwiZXhwIjoxNzEyNjc5NzE2fQ.JkLxAseJdnzG6ymLRQbnWSnAlgQSvuBavHlI3LYCWXU'. (Linux UPnP/1.0 Sonos/78.1-52020 (ZPS27))
This warning also doesn't seem related to Chime TTS, but perhaps to the Sonos integration or a networking or permissions issue (as you already wrote). I am afraid I don't think I can be of assistance here. My suggestion would be to test if you continue to receive the warning if you only use Chime TTS on non-Sonos media players. That would tell you whether it's a Sonos-related issue or not.
Hi @JCummings49,
I just released a new beta which includes a potential fix for the RuntimeWarning: coroutine 'ChimeTTSQueueManager.queue_processor' was never awaited
warning.
To install the new beta:
⋮
button in the top right↻ Redownload
optionShow beta versions
option (it may take a moment to update the list)v1.1.0-beta2
from the updated version drop-down listOkay, I've installed the beta. I'll assume this change will eventually get pushed as a dot release at some point.
After the reboot, the only warning I'm seeing is as follows:
Logger: py.warnings Source: runner.py:189 First occurred: 9:27:54 AM (1 occurrences) Last logged: 9:27:54 AM
/usr/local/lib/python3.12/asyncio/base_events.py:1989: RuntimeWarning: coroutine 'ChimeTTSQueueManager.queue_processor' was never awaited handle = None # Needed to break cycles when an exception occurs.
I'll run a few cycles using the Chime TTS integration and see how it goes. I suppose we can consider this original issue closed. Thanks for your help.
I am closing this issue. Please reopen it if it is still relevant.
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1399 Downloaded Repositories | 20 HACS Data | okAccuWeather
can_reach_server | ok -- | -- remaining_requests | 19Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | March 5, 2025 at 6:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | false remote_server | us-east-1-8.ui.nabu.casa certificate_status | ready instance_id | aa0b917ef61c4654a670573e45e1e118 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.04.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 234.7 GB disk_used | 9.5 GB healthy | true supported | true board | odroid-m1 supervisor_api | ok version_api | ok installed_addons | Terminal & SSH (9.10.0), File editor (5.8.0), Matter Server (5.5.1), ESPHome (2024.3.2), Studio Code Server (5.15.0), MariaDB (2.6.1), Samba share (12.3.1), Mosquitto broker (6.4.0)Dashboards
dashboards | 7 -- | -- resources | 14 views | 12 mode | storageRecorder
oldest_recorder_run | April 5, 2024 at 7:58 PM -- | -- current_recorder_run | April 9, 2024 at 7:42 PM estimated_db_size | 264.77 MiB database_engine | mysql database_version | 10.6.12Checklist
Describe the issue
I have started getting the following log warning message. It seems to be fairly random and often. I don't have any automations using Chime TTS that coincide with these warnings. I initially thought it was a permissions problem with the indicated path in the URL, but opening up the permissions doesn't seem to resolve the warning messages,
Logger: homeassistant.components.http.ban Source: components/http/ban.py:138 integration: HTTP (documentation, issues) First occurred: 2:11:41 PM (1 occurrences) Last logged: 2:11:41 PM
Login attempt or request with invalid authentication from SonosZP.attlocal.net (192.168.1.198). Requested URL: '/media/local/sounds/temp/chime_tts/ayqpvcsz.mp3?authSig=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiIwOGUwOTlkNTAyYmI0NzYzODNmZTdlNzlhMGE3OGVhYSIsInBhdGgiOiIvbWVkaWEvbG9jYWwvc291bmRzL3RlbXAvY2hpbWVfdHRzL2F5cXB2Y3N6Lm1wMyIsInBhcmFtcyI6W10sImlhdCI6MTcxMjU5MzMxNiwiZXhwIjoxNzEyNjc5NzE2fQ.JkLxAseJdnzG6ymLRQbnWSnAlgQSvuBavHlI3LYCWXU'. (Linux UPnP/1.0 Sonos/78.1-52020 (ZPS27))
Reproduction steps
1. 2. 3. ...
Debug logs
Diagnostics dump
NA