Closed dbullendsl closed 2 months ago
Hi @dbullendsl,
I believe this issue was fixed in v1.0.0 Can you please let me know if it still happens for you in the new version?
Thank you.
@dbullendsl, do you have an update?
working ok for me now - close
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4800 Installed Version | 1.34.0 Stage | running Available Repositories | 1398 Downloaded Repositories | 35AccuWeather
can_reach_server | ok -- | -- remaining_requests | 17Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.02.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 457.7 GB disk_used | 17.1 GB healthy | true supported | true board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | Duck DNS (1.15.0), File editor (5.8.0), Studio Code Server (5.15.0), Advanced SSH & Web Terminal (17.1.1), Samba Backup (5.2.0), Z-Wave JS (0.4.4), Mosquitto broker (6.4.0), ESPHome (2024.2.0), Zigbee2MQTT (1.35.3-1), Piper (1.4.0), Whisper (1.0.2)keymaster
zwave_integration | zwave_js -- | -- network_status | onDashboards
dashboards | 4 -- | -- resources | 22 views | 45 mode | storageRecorder
oldest_recorder_run | February 19, 2024 at 11:41 PM -- | -- current_recorder_run | February 24, 2024 at 8:57 AM estimated_db_size | 753.38 MiB database_engine | sqlite database_version | 3.44.2Sonoff
version | 3.6.0 (8dd8af9) -- | -- cloud_online | 0 / 1 local_online | 1 / 1 debug | failed to load:Spotify
api_endpoint_reachable | ok -- | --Checklist
Describe the issue
Alexa devices do not return to prior playback levels after playing output chime_tts:say if the devices were already playing from another source, ie Spotify.
It appears from the log that the call waits for the Alexa to return from Playing to not playing, but if the devices have been playing prior to the announcement they remain in playing mode and never signal the end of the announcement.
What I did in the past using the chime_tts:say_url call which returned the URL and the duration of the announcement. I'd wait a period equal to the duration+2 seconds and then issue a set volume command.
Reproduction steps
Debug logs