for my cameras to get them to work I had to add them as “pictures” in lovelace.
Would you mind share the code in lovelace ?
Did anyone work out why some of us are getting, “There were no suitable Chromecast devices to cast to found” ?
It could be your anti-virus blocking it - that was my problem with Eset Internet Security.
Sorry for taking so long, I broke my hass.io but i fixed it now. Anyway this will depend on the camera you have, for DoorBird I do
hold_action:
action: none
image: >-
http://192.168.0.89/bha-api/video.cgi?http-user=USERNAME&http-password=PASSWORD
tap_action:
action: none
type: picture
As far as I know, you can’t just put RTSP in there. You need a camera that lets you view the image in a browser. Hope this was helpful.
Edit: I got that URL from https://www.ispyconnect.com
2 Likes
What to do if you don’t use duckdns and is on static public with no https?
It needs https idk why I think it’s a requirement by Google cast or something.
But shouldn’t it be possible to do it through the Nabu Casa hub then. That is with https?
Yes it is possible with nabu casa, because if you have remote access enabled it uses https
But how do I tell Home Assistant to use that?
I have it enabled and I did test it directly with the cast.homeassistant page which works great.
When I add it to my lovelace using the config above it just shows me:
"Caste Home Assistant" Cast Requires HTTPS
I just copied and pasted my nabu casa url into the HA cast page.
After lots of trial an error I can now cast views from a card by using its number in quotation marks.
e.g. view: “4”
I did, and it asks me if I want to stay logged in which I clicked yes to. On that page I can then do a cast, but that doesn’t change anything on the Lovelace card?
So I did as suggested as written above and finally after approving, I clicked on the nabu casa link and went to the Lovelace page. Now I can do the casting.
So if I open up Lovelace on my local lan this won’t work neither if I use the Public IP Address on the Android Ariela App.
I have no idea what this means.
That’s not where you enter the URL.
Look at the example in the top post again,
# The path of the view (or number)
view: lights
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.
Fiddled around with the lines/syntax in the “raw editor” a lot before it finally seemed OK.
Weird since it looks very similar to whats stated above…
Now I just gotta pick up the Google Hub in the store…
Card looks like this when there is no Google Hub to cast to 
I ended up using: https://github.com/skorokithakis/catt
My custom cards did not work with Home Assistant Cast.
Does anyone know if there is any ongoing project to port Catt to Hass.io?
4 Likes
I’ve seen this happen intermittently on my network. However, it seems to go away once I open the cast extension in Chrome and it finds my devices.
The steps I use to fix it:
- Visit https://cast.home-assistant.io in Google Chrome (this is really important)
- Open the Chrome menu by clicking on the three dots in the top right corner, and select the option to cast.
- Wait for the spinner to disappear and the list to show your cast devices.
- Close the menu by clicking outside or pressing escape.
- You should now see the cast button on the page.
Hope this is helpful
2 Likes