Checking in with the same timeout issue after device updated to 1.46.203796.
Also, seem to be having issues with the service calls. Need to go through the https://cast.home-assistant.io/ website first before it will respond to calls from other browsers.
Same issue here with the Google Nest Hub mini timing out after about 10 minutes or so after a recent firmware upgrade. I’m running cast firmware version 1.46.203796 in Australia.
Is there anyone who can tell me how to choose which theme is being presented through the cast?
When I cast, the default theme is the one presented.
Please help
I got it working with the “https://cast.home-assistant.io/” Website is it Possible yet to start it with a service or someting like that? Without logging on that Webpage, just directly from HA?
I have HTTPS working via letsencrypt and duckdns and ngnix but I get stuck at the Nabu Casa screen…
during the authorization process i had to toggle wifi on and off…
my router does not support NAT pinhole… DNS lookup inside own network…
do i need this? i think i do…
i cannot accesss my home assistant via https webaddress locally, only from outside the network with https web address.
locally in the network I have to use IP addresses. https does not work.
Hey everyone I think google had an update this past few days and suddenly I stopped being able to change views, the link button that I created doesn´t work anymore, and also not being able to change thru HA cast, anyone having the same problem?
Hi. I am new to nest hub. Any ideas, why all anything related with history is stuck on “Loading state history”? Same applies to history-graph, or badges history tab. And it works on PC and phone
I get the same issue. All card using “history” feature make a call on https://FQDN/api/history/period/… When I check the access log of my nginx (in proxy mode) I found 401 error which mean not authorized :<SOURCEIP> - - [30/Nov/2020:22:47:05 +0100] "GET /api/history/period/2020-11-27T21:47:05.800Z?filter_entity_id=sensor.temperature_ext&end_time=2020-11-30T21:47:05.800Z&minimal_response HTTP/1.1" 401 2191 "https://<FQDN>/lovelace/home" "Mozilla/5.0 (Linux; Android) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Safari/537.36 CrKey/1.50.229149"
So all graph-type card, or if I click on legacy temperature card, I get a “loading”.
I guess my nest Hub is not sending header (the token?) in http requests.
I have the same setup, but on a HP N54L Microserver. I tried a cast to my Gen 1 Chromecast and it worked fine with my own https URL. I’m not using NabuCasa yet.
Can I ask how you have things set up? I am using docker images of nginx reverse proxy with duckdns to access home assistant core via https but when I enter my url at the authorization website the authorization redirect simply times out when I’m on my home network. Interestingly the authorization website works on an external network but the login is automatically aborted. I assume that is a security feature of the home assistant cast api.
Basically I have Debian 10 with docker installed. Then installed HA in docker. I haven’t really done much with the cast feature since then the post you are referencing, so I don’t even know if it’s still working for me.
I’ve recently got a google hub max so making something to work on that is on my to do list, just not anytime soon unfortunately.
I think my issue is stemming from the fact that my url is not accessible from inside my LAN. I’m not sure why or how to fix it but that helps explain why when I attempt to authorize using the home assistant cast site it just times out.