Stream / Casting to Chromecast devices no longer works after updating .110 (internal/extrernal_url)

Configuration
1

Hi all,

Have anyone else experienced after the .110 update, when streaming from a Camera to Chromecast devices eg. a Nesthub, that the stream looks like it loads but then just shows a text “Smart Home Camera” and then nothing happens?

I also noticed that the Cast function (Lovelace cast), no longer seems to work for me after the base_url was removed. Now I just get the “Error: Unable to connect to the Home Assistant websocket API.”
Not sure if this is related, but I wanted to provide what seemed to happen at the same time.

Current config:

homeassistant:

  #Connection URLS
  internal_url: https://xxx.xxx.xxx:8123
  external_url: https://xxxx.duckdns.org

I did try the internal without https --> http - but no luck
Also, I tried changing it to the duckdns.org:8123 - no luck either

So far I don’t see any erros in the logs :thinking:

1 Like
2

There is a bug in zeroconf (mdns) that was fixed in 0.110.4.

The internal and external urls are not related.

3

Hey Nick,

Oh okay, but I do still face the issue now that I just upgraded to 0.110.4.
I kept the internal_url and external_url as above - still no errors in the log but same message.

But if I look in the “Supervisor Log” I see this?
20-05-30 22:51:36 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].

4

What was your base_url set to before the upgrade?

5

I used the https://xxxx.duckdns.org:8123

6

You can’t use HTTPS internally as it will be self-signed, and the Google Homes/Chromecast will not work with self-signed certs. Either use HTTP for internal, or remove it and just use external HTTPS.

You can try setting both internal and external to the external address if the http internal doesnt work.

7

I actually did try that. First removed the internal_url completely and rebooted. No luck.
Then I tried with the http://mylocalip:8123 and rebooted - same outcome:

BTW: When removing the internal_url: I’m still only able to access the local IP by using the https in front.

“Smart Home Camera” and no stream.
… Or the websocket API error when trying to Cast a lovelace view.

8

I don’t understand it. This was working before with the base_url pointing towards duckdns and I was only able to access my Home Assistant with https locally as well.

I tried removing the internal_url again and did a full reboot of my NUC. Still no joy.
My TTS is also broken so I added the base_url with only http://localip:8123 as it states in the documentation - not even that world anymore :sleepy:.

What have I messed up :hot_face:

9

Hi all,

So I don’t know why and if I somehow missed trying this, even though I was pretty sure I did or if it was a matter of xx amount of reboots.

But what seemed to fix my Camera Stream to Google Cast Units and the TTS on my Google Home Minis was setting my external_url and internal_url as shown below:

  #Connection URLS
  external_url: https://xxxx.duckdns.org
  internal_url: https://xxxx.duckdns.org:8123

Thanks for your support guys!

2 Likes
10

thank you so much , have same problem with chromecast on my Bravia TV after set this internal and external url like you show, finally stream on my chromecast is back working again ! It was a very good solution, thanks!

11

Thank you very much! you saved my day!

12

I also have problems casting a mjpg stream to chromecast.
The stream works fine from VLC.

What internal or external URL should I add? I do not use duckdns (yes).