#TTS issues

1 messages · Page 1 of 1 (latest)

obtuse widget
#

Having the same issue. I didn’t have the internal & external URLs defined, but I’ve added them and no difference

lusty veldt
#

@obtuse widget what did you set them as?

#

You want to set https:// for external and http:// for internal if you're using Nabu Casa

lusty veldt
#

You can usually confirm that's the issue by sending a test tts and checking the HA logs

obtuse widget
#

thanks. they look like this (except my internal is a the name rather than IP address). Having said, it looks like the situation has actually got worse for me now. Possibly because I tried unlinking and then linking Home Assistant in Google Home, I see my google devices now show as "unavailable" in HA. So, a call to TTS is now failing for that reason (no such errors in log earlier). Looks like I need to work out how to get my devices to show up again!

lusty veldt
#

@obtuse widget you don't need the Nabu casa skill for tts, so that isn't directly related

#

Try using the IP address:8123 instead of hostnames. You might have an issue with mdns and it's just another layer to go wrong

#

Use http://ha_ip_address:8123

obtuse widget
#

That did it, thank you very much! Strange that it had been working without those fields filled…

lusty veldt
#

Were you sitting on an old version of HA core?

#

Also you might be able to sync your entities now to google Assistant, since this is working

obtuse widget
#

I was on 2021.7.4. when it was still previously working. It actually stopped around the time I updated the OS (HA OS 6.2 from 6.1) but I assume that was a coincidence...

austere halo
#

I cleaned up the internal URL, which used to look like: //192.168.1.22:8123/api/webhook and got rid of the api and webhook part and then it started working. I thought this worked at one point in time, but seems reliable with just the ip address and the port 8123 part.

lusty veldt
#

@austere halo yeah that's all it should have ever been. The /api/webhook/ would have always been wrong 😬