Closed schniepp closed 5 months ago
Hi @schniepp. I'm sorry to hear you're having this issue.
I can see from your attached debug log messages that you are using a previously cached file. This means I cannot see what happened when Chime TTS originally created that file. Could you please run the exact same service call but set cache
to false
, so that I can see the entire process?
I'm confused by what you mean by the "default" chime. There is no default chime in Chime TTS. Could it be that your speaker has its own chime that plays independently of Chime TTS? To test this, I suggest you call chime_tts.say
without no chime_path
and end_chime_path
values. If you still hear the "default" chime it must not be related to Chime TTS.
You can also confirm this another way, by playing the MP3 file generated from the chime_tts.say_url
service.
@nimroddolev — thank you so much for looking into this so quickly!
Re 2. "Default Chime" — you were spot on!
I feel very, very silly now that I could not figure this out by myself :(
I tried TTS via the tts.speak
service, and no matter what I did, I always heard a chime at the beginning — so I figured that this was a fixed feature of the built-in tts.speak
service (and I read a comment somewhere in the forum that I interpreted this way, but I may not have paid enough attention.
It turned out that the two mediaplayers I tested this on were both provided by music assistant, and I believe they had a chime turned on by default. I now deactivated it there, and my problem is done.
Short story is: this was not a chime_tts issue, my problem is solved, and this issue can be closed. Sorry for the inconvenience! Cheers, HS
OK, I guess I can close this — missed this feature in the bottom.
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 | 1389 Downloaded Repositories | 99AccuWeather
can_reach_server | ok -- | -- remaining_requests | 18Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okDashboards
dashboards | 4 -- | -- resources | 68 views | 38 mode | storageRecorder
oldest_recorder_run | June 2, 2024 at 16:58 -- | -- current_recorder_run | June 9, 2024 at 19:23 estimated_db_size | 934.19 MiB database_engine | sqlite database_version | 3.45.1Sonoff
version | 3.7.3 (e240aaf) -- | -- cloud_online | 4 / 5 local_online | 4 / 4Checklist
Describe the issue
My understanding is that chime_tts provides the option of having custom chimes before and after TTS, or also no chime (as opposed to the built-in, TTS service, which always plays the "default" chime in the beginning). In my case, I could never get rid of the original chime. Weirdly, it even plays when I successfully selected custom chimes. In the YAML file below, it will first play the "default" chime, then the custom chime, then comes the TTS, then the custom end chime.
Reproduction steps
Debug logs
Diagnostics dump
No response