I’m playing around with HAss installed on a cubieboard (os cubian) and my google home.
the google home is found and shown in the state panel and recognise with this entityid:
media_player.livingroom
when trying the tts service from the “services” developper tool it doesn’t play the message on google home.
If I go in state page and turn off the home device, I can hear it turn on when calling the service (I can hear a kind of “blip” sound) so the google home is recognized. Its state switched to “on” after the call.
The message sound file is generated and saved in the cache folder so the tts is working.
I probably miss something to make the sound being played on the home device.
Do you have any clue for me?
What he means is that you have to add the base_url option in the http component if you use https.
The reason is, that TTS is actually telling the device it should connect to your HASS installation and play a published audio file. Without SSL this works with any address HASS is listening on. With SSL however the certificate verification fails when not using the correct hostname.
Edit: Well, I don’t know if it’s actually the certificate verification that is the problem. In my case it’s the reverse proxy that requires additional credentials, and therefore returns forbidden errors. Anyways, the main point is that your Google Home needs a working URL it can connect to.
I Had the same problem after enable secure connection,
for me ,router port forwarding solve the problem and everything work fine again:
port 443 to port 8123