Lovelace Cast issues

Tags: #<Tag:0x00007f7396ee0140> #<Tag:0x00007f7396ee0078>

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?

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

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.

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