nimroddolev
commented
1 month ago Hi @jesse-kaufman, thank you for opening this issue and for providing the debug log & additional details.
I would like to ask you to please try the following 2 troubleshooting steps to help me get a better idea of what might be causing the issue:
1. MP3 Cover Art
Have you enabled the MP3 cover art option in the Chime TTS configuration page? If so, can you please try disabling it and playing to both Alexa and Google Cast media players and let me know if you have playback on both media players?
2. Test Playback via media_player.play_media Action
If you still experience the issue, I think the other possible cause may be related to how the MP3 is encoded when being prepared for both Alexa and Google Cast media players. The following will help determine if this is the case:
-
Prepare an MP3 via chime_tts.say for both Alexa and Google Cast media players, with
cacheenabled, i.e:action: chime_tts.say target: entity_id: - media_player.dining_room_speaker - media_player.kitchen_echo data: chime_path: /config/www/mp3/reminder.mp3 message: Testing testing 1 2 3 tts_speed: 80.0 cache: true -
Open the debug logs for the call to
chime_tts.sayand retrieve the public URL to the newly generated MP3 file. You should find it in the debug log section that begins with "Calling notify.alexa_media with data:". eg:Calling notify.alexa_media with data: - message: <audio src="https://ha.lloydnet.org/local/chime_tts/tktlko6n.mp3"/> - data: {'type': 'tts'} - target: ['media_player.kitchen_echo'] -
Test if the file is publicly accessible by opening it with your browser. If not, this is likely the issue.
-
If it is accessible, try to play the file to your Alexa media player/s directly, via the
notify.alexa_mediaaction, eg:action: notify.alexa_media data: message: <audio src="https://ha.lloydnet.org/local/chime_tts/tktlko6n.mp3"/> data: {'type': 'tts'} target: - media_player.kitchen_echo
If you don't hear the file then the issue is with the MP3's encoding. If you do hear it, the issue must be somewhere in the code for Chime TTS.
jesse-kaufman
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4993 Installed Version | 2.0.1 Stage | running Available Repositories | 1425 Downloaded Repositories | 45Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | April 13, 2025 at 7:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | us-east-1-1.ui.nabu.casa certificate_status | ready instance_id | 70049538375a4c47910056f2728e678a can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okDashboards
dashboards | 7 -- | -- resources | 28 views | 44 mode | storageRecorder
oldest_recorder_run | May 31, 2024 at 12:05 PM -- | -- current_recorder_run | September 25, 2024 at 9:11 PM estimated_db_size | 11812.54 MiB database_engine | sqlite database_version | 3.45.3Checklist
Describe the issue
When playing to multiple devices that include both an Alexa device and Google Home Mini, the sound plays fine on the Google device, but I get the dreaded "Simon Says" error on the Alexa devices.
I've double-checked the public URLs being sent to Alexa and they all work as expected (plus, it works if only using Alexa devices). I'm not seeing any major errors that jump out at me in the debug logs, either, so I'm stumped on this one ... Everything was working on 1.1.4b4, then stopped when I installed beta 6 as well as the stable 1.1.4 release (what I'm currently running).
Related Home Assistant config:
HA Version: 2024.9.3
Reproduction steps
Debug logs
Diagnostics dump
No response