Lovelace Cast issues

Configuration
,
#1

Hi all,

I am trying to get the Lovelace cast integration set up. Just to set the stage, here are a few assumptions:

  1. My instance is publicly available (with https)
  2. My Google Assistant integration is working as expected
  3. My iOS app is working as expected (over LTE, not local wifi)
  4. I have the LinuxServer letsencrypt nginx proxy sitting in front of HA using their default configs.

I am unable to get the Lovelace cast integration to work properly:

  • Locally using the cast.show_lovelace_view service: Nothing happens on the display (other Media services work, like TTS)
  • Externally using https://cast.home-assistant.io: I get a “unable to connect to the home assistant websocket api” error

Unsure if these 2 issues are related, however one thing I have noticed, when initiating from the https://cast.home-assistant.io URL, I see no activity on my proxy. Whereas from my app or web interface, nginx logs are very busy.

Any ideas?

#2

Anyone have some ideas? I am seeing others have success but I’m stuck :0

#3

For what it’s worth, I have the same issue right now. Did you ever fix this?

I think it might be related to the fact that if you query my external HASS domain, my DNS server returns the internal IP of my HASS box. This is so that I can use the same URL regardless of if i’m home or not. So when my Google Display tries to query the external URL it gets served an internal one which it can’t serve.

#4

Nope. I haven’t bothered since. I’ve seen other folks use CATT instead.

#5

Maybe one suggestion: I just tried accessing https://cast.home-assistant.io/ from my phone without local wifi connection. I also figured, that the external_url/internal_url might have sth to do with it, since they’re using different ports.

1 Like
#6

I have never been able to cast my dashboards and have always got the “Not Connected, unable to connect to the home assistant websocket api” message on my cast device. I thought that the new media option to cast lovelace would solve my problem but sadly it doesn’t . however i have always been able to cast using https://cast.home-assistant.io/ no problem. anyone have any ideas?

#7

i saw this elsewhere and just tried it and it worked for me - try adding the below to configuration.yaml. if you don’t use ddns i think just your nabucasa link would work, but really i have no idea what i’m talking about so maybe not. in any event - this worked for me using my no-ip ddns and port forwarding to my rpi.

homeassistant:
  internal_url: http://<INTERNAL_IP:8123
  external_url: https://<MY-SUB>.duckdns.org
2 Likes
#8

I just found the problem, i had a mistake in my external url in config/settings/general. i can cast lovelace now. OMG

1 Like
#9

Your solution just works great for me.
I was loosing my mind trying to make it work and now it is working perfectly.

in case it helps others , I’m using nabu casa cloud and I have included in the configuration.yaml the internal url and in the external url the nabu casa url.

no more problems so far.

thanks a lot !