Closed hertzg closed 2 months ago
Same Issue for me. Used "say" within an automation in mode restart. So when the automation is triggered twice the first run is canceled while say is running. Then it is broken till homeassistant restart.
My hot fix in my case is that I changed automation mode to single.
Release 1.1.3
Thank you @hertzg for opening the issue. I believe I have found a solution and will include it in the upcoming release.
I released a new beta which includes the fix for this issue. I would like to ask you to please upgrade to the new beta version, v1.1.4-beta5, and let me know if the issue is now resolved.
The issue seems to be resolved in v1.1.4-beta5, I'll let you know if the dreaded #161 reoccurs, so far so good.
System Health details
System Information
Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | pendingDashboards
dashboards | 2 -- | -- resources | 0 views | 1 mode | storageRecorder
oldest_recorder_run | August 23, 2024 at 5:41 AM -- | -- current_recorder_run | August 23, 2024 at 6:14 PM estimated_db_size | 1.29 MiB database_engine | sqlite database_version | 3.40.1Checklist
Describe the issue
When calling the
.say
service from a script, if somehow the script execution is canceled, the sound plays one last time and any consecutive calls will just fill up the queue.The only workaround is to restart homeassistant.
Here's a video demonstrating the issue:
https://github.com/user-attachments/assets/fdae8ab8-16ee-49f4-8151-d99b5aa87d9e
Reproduction steps
Debug logs
Diagnostics dump
No response
Might be related to #161