Thankyou @Nimrod_Dolev, I also really like this integration. I was listening to a podcast the other day on alarm design, and this is exactly what they said. Use a chime to get people’s attention, then something to indicate the specific alert - in this case it’s TTS but it could also be a particular sound effect that has meaning. Bad alarm design uses all sorts of horrible beeps and alarms with no meaning that we we have to learn or investigate what they’re for.
However, I’m having a couple of issues with version 1.0.0.
Cache doesn’t work for me, it throws an Unknown Error. I’m using a rPi4 with HASSOS.
Announce at 100% volume when music is currently playing. The Announce feature increases the volume first, plays the chime and TTS, then returns to the volume back normal. e.g. if the music is at 15% and the announce is at 100%, then the result is music is playing at 15%, submit the chime_tts → music plays at 100% for 1 second, chime_tts announcement at 100%, music continues playing 100% for another 1 second, then music volume returns to 15%.
Hi, new here. Using 1.1.0 Beta 4. On Sonos paired setup
Since using the Beta 4, the recording is playing twice and only out of 1 speaker
Removing this audio_conversion: “-filter:a volume=1.5” stops the repeating but still only out of 1 speaker. Apologies if a known issue, let me know if logs would be useful.
Current automation.
data:
chime_path: bells
message: The alarm is now set.
tts_platform: tts.piper
announce: true
audio_conversion: "-filter:a volume=1.5"
target:
entity_id:
- media_player.kitchen_sonos```
Can’t seem to get any audio output either testing via the call service below with v1.0.0.
service: chime_tts.say
data:
chime_path: custom_components/chime_tts/mp3s/bells.mp3
end_chime_path: custom_components/chime_tts/mp3s/tada.mp3
message: This is a test message using Chime TTS.
tts_platform: cloud
volume_level: 0.75
announce: true
target:
entity_id: media_player.living_room
@Coolie1101 and @stormshaker I would suggest updating to the latest BETA version (v1.1.0-beta4) as you will have better success with it as there have been quite a few updates made.
@Coolie1101 Your YAML works for me as designed! I would double check your folder setup for allowlist_external_dirs
service: chime_tts.say
data:
chime_path: custom_components/chime_tts/mp3s/bells.mp3
end_chime_path: custom_components/chime_tts/mp3s/tada.mp3
message: This is a test message using Chime TTS.
tts_platform: cloud
volume_level: 0.6
announce: true
target:
entity_id: media_player.couch_echo_left_amz
Tried without the chime as well, but got the same result.
service: chime_tts.say
data:
message: This is a test message using Chime TTS.
tts_platform: cloud
volume_level: 0.6
target:
entity_id: media_player.living_room
This error originated from a custom integration.
Logger: custom_components.chime_tts
Source: custom_components/chime_tts/__init__.py:1150
integration: Chime TTS (documentation, issues)
First occurred: 10:21:53 AM (3 occurrences)
Last logged: 1:34:55 PM
Error calling `media_player.play_media` service: No media content id found
Does the media player work after calling the service?
service: tts.speak
target:
entity_id: tts.home_assistant_cloud
data:
cache: false
media_player_entity_id: media_player.living_room
message: test test test
I believe the two folders need to be separate You can’t combine them into one. One should be a temporary folder and then the other one should be your output folder
Using the chime_tts.say_url service with notify.alexa_media should work, but since v1.0.0 you can simply use chime_tts.say and specify your Alexa media_player, which should simplify your script.
It’s not clear which service is throwing the Message malformed: extra keys not allowed @ data['sequence'] error. It would be helpful to see the debug logs to determine where this error occurs.
To debug the problem I suggest you call chime_tts.say via the Services tab in the Developer tools page, that way you will be able to tell if the issue is related to Chime TTS. If not, it’s likely an issue with your scipt.
Either way: the debug logs are the best way for me to understand what the issue might be.
Hi Steffen, sorry to hear you’re experiencing this issue.
Thank you for the debug logs. Unfortunately they don’t reveal any clues, as they indicate that the correct steps were taken by Chime TTS.
My best guess as to what is causing the issue, is that after fading out and pausing the playing music, the Chime TTS audio announcement replaces the paused music, so there isn’t anything to resume.
Could you try setting the announce parameter to true? I am curious if that might fix the issue. Eg:
service: chime_tts.say
data:
chime_path: ding_dong
offset: 450
final_delay: 100
message: Hallo dies ist ein Test
tts_platform: edge_tts
volume_level: 0.6
fade_audio: true
announce: true
target:
entity_id: media_player.sonos_buero
Hi @Desert_AIP, I think the issue you’re having of the blank audio from Amazon Polly is due to an incorrect/missing configuration for the Amazon Polly platform in your Home Assistant instance, as these errors indicate that Chime TTS wasn’t able to find it in the list of installed TTS platforms.
Have you been able to successfully use the Amazon Polly TTS platform outside of Chime TTS, i,e with the tts.amazon_polly_say service?
If you still expereince the issue on the beta then please provide me with your debug log messages so that I might be able to see what the issue is.
…music continues playing 100% for another 1 second, then music volume returns to 15%.
For this issue I would again ask you to send me your debug log messages as it’s difficult to tell what could be causing the issue without any additionhal information.
