It looks like this, so the same apart from the chime TTS mp3s URL option.
I tried to amend it to include the “/config/”, but when I save, it switches it back!
The editor in HASS is wierd - try prepending the /www/chime_tts parameter with /config THEN press TAB. should take you to the next line without clearing your entry.
Then you should be able to save it.
the media_content_id: should be a ip address or FQN do you have any network connection to your hass server from outside your network? Is media_source a network name?
I know that when I starting using this package, I had some false starts. I’ve completely deleted the whole thing including going to the /custom_components folder an making sure that there weren’t any residual pieces laying about. Then reinstalling from HACS and entering the values in the configuration as they are now.
I’ve been working on a substantial release which includes quite a few new features and bugfixes which include issues with the default folder paths for both chime_tts.say and chime_tts.say_url.
It’s not quite ready, and the documentation isn’t complete yet, but I would be grateful for feedback whether these issues persist for you in the new version or have been addressed so I have released a beta (v0.14.0-beta1).
So far…
When trying to change the default TTS service the config doesn’t seem to take anything and throws an error. I’ve tried Piper, tts.piper tts.elevenlabs_tts, All with the same results.
I’ve updated to latest beta and the config panel does accept a default tts platform. Although even tho it’s configured when I try to create a call to ctts:say the platform still requires a value to be input for the platform - shouldn’t it be pre-filled for the default value?
Also, the issue I raised earlier about the volume not reverting to previous now seems resolved.
Hi @BENZAKOUR86. I don’t own either of those devices so unfortunately I can’t confirm. When enabling the announce parameter in the latest version, chime_tts.say checks whether the feature is supported by the media_player platform, and if not, it fades out & pauses any currently playing music and then after the announcement is completed it resumes the music and fades it back in.
If the feature doesn’t work as expected I would be happy to troubleshoot with you and see if there’s a way I can add support for these platforms.
hi @Nimrod_Dolev,
Thank you for your response. I can confirm that I’ve tested the announce feature on both Google Nest Hub 2 and Nest Mini 2, and unfortunately, it does not work as expected on these devices. Despite enabling the announce parameter in the latest version, the feature does not function properly.
I appreciate your willingness to troubleshoot and potentially add support for these platforms. If there’s any further information I can provide or if you need assistance with testing, please let me know.
Problem w Alexa in v1.0.0 ? --I installed v1.0.0 yesterday, and ever since my Chime TTS announcements have not been working over Alexa – they play the starting chime OK, then announce that they’re having difficulty with the Simon Says skill --which I do not think I’ve ever enabled in my Alexa account
My automations send message to a persistent notif. in HA, then a notif. to my iPhone, then Chime TTS targeting 3 Amazon Echo units w most options not selected --just chime path, volume level, join players & unjoin players, cache, announce, & gender= female. Using Nabu Casa Cloud for TTS option.
Has been working REALLY well (v0.13.0), with only minor occasional hiccups (maybe timing glitches, maybe with cloud services). But after v1.0.0, I don’t think it has played properly even once. (Can’t test right now, due to sleeping folks in house.)
Hi @tim.plas, I’m sorry to hear you’ve been having issues with the new version.
In your comment you mentioned using using the gender parameter, which has been deprecated. There is a new beta version of Chime TTS which replaced gender with voice. Could you please upgrade to the beta and let me know if it fixes your issues?
Enable the Show beta versions option (it may take a moment to update the list)
Select version v1.0.1-beta2 from the updated version drop-down list
Restart Home Assistant
Another possible cause might be that you don’t have an external URL configured in your configuration.yaml file. Can you please add the following YAML to configuration.yaml ?
I upgraded to v1.0.1-beta2 then built & ran a quick new automation for testing.
Unfortunately the issue was still present after the upgrade.
I did not know what to put into the “voice” parameter, so didn’t use that at all.
I then updated configuration.yaml as you suggested to include internal & external URLs.
Unfortunately still had the same difficulty.
The exact voice message I’m getting from Alexa Echo is “Sorry I’m having trouble accessing your Simon Says xxxx skill right now.” --I can’t quite catch the word right after Simon Says; it sounds something like “Simon Says noss skill”.
I tried to enable debug logging, but am unsure where to put the YAML lines you suggested? When I tried putting that into configuration.yaml it failed the “Check Configuration” in Developer Tools.
I can certainly try again for debugging info, if I find out what I’m missing about setting up debug log.
