You still start the process and authorise it via https://cast.home-assistant.io/, the card is for casting specific views to the device, as far as I know.
I can only get the cast working, if I open my lovelace view through the nabu casa link.
If I open up my lovelace through 192.168.X.X:8123/lovelace, then I won’t be able to - because it states that it required https.
The same goes for the Ariela app, that connects to my public IP address. Cast requires HTTPS.
So to achieve this I will have to always open xxxxxxxxxxxxxxxxxxxxx.nabu.casa link.
Great thing, this HA Cast. Bought a Google Nest Hub after reading the blog post. Installed it. Got discovered by HA right away. Casting via the https://cast.home-assistant.io/ per view works fine. Also the start-casting works via the type: cast entities in Lovelace. But I only got that running by view < number >, not by view < path >. Maybe it’s related to the fact I’m using
views:
- !include ui-lovelace/home.yaml
...etc...
I get path errors (shown on the Nest Hub) if i use view: home or view: ui-lovelace/home or even view: ui-lovelace/home.yaml. But with view numbers, it’s fine.
Can’t wait to see more features, especially trigger casting a specific card from an automation. (E.g. show some specific light buttons when a movement sensor is triggered at a certain period of the day.)
Did you put the view name in quotes? I found I even had to put the view number in quotes. If you haven’t set a path for a view that may also be why. I think the path name is different to the title.
Ah, path is not referring to the path where my yaml’s for the views are stored. My files are in <config-folder>/ui-lovelace/<view-file>.yaml and my view definition is in <config-folder>/ui-lovelace.yaml. I don’t use paths in my views then.
But whatever I try (view: "home", view: "Home", view: home, view: Home), only view: 1 works. But I can live with that.
see here https://www.home-assistant.io/lovelace/views/#paths
You have to explicitly define a path for the view - it’s not the title or name used here. If you don’t define a path it uses 0, 1, 2 etc as the path. I agree it’s a bit confusing too.
Just for shits & giggles I added path to my views:
I’ve just found out that I needed to add a NAT rule to do a hairpin NAT, as I figured out the reason why my views wouldn’t cast when logged in via cast.home-assistant.io.
Since you provide a HTTPS link for this to work, it assumes that everything is configured to be set up using your external WAN address. So when it comes time to connect, our computer receives a message from HASS via cast.homeassistant.io, and then replies to that with it’s internal address. Since the HASS webserver is expecting a response from the external address, it will ignore that response and time out.
My HA is published over https with an own certificate. I can access the frontend from outside of my network.
When I start the cast- I constantly get an Image with the HA logo, a heart and the Nabu Casa logo. Under this there is a message written: Not connected
I have my own certificate authority so have my own cert in HA. Normally I block outside access but even with outside access open I get the same Image of HA logo, heart and Nabu Casa logo with message Not Connected.
I’m guessing cast.home-assistant.io might be getting a certificate invalid error because my root cert is not publicly available.
I’m also using Nginx as a reverse proxy and there was a mention about that above, but they are able to connect, just not display cards, so I’m guessing that is a separate issue.
Have a look after you select cast and pick a device to cast to, go back to the device you are casting from and make sure you select a view to cast (its an option that comes up after). After I make that selection HA casts properly.