Using CATT here and I also experience this 10 minutes timeout, probably a google thing.
Confirming I am also having the timeout issue with cast firmware 1.46.203796 on my two devices that upgraded. My third device that is still on 1.44 is fine.
That is both with CATT and HA Cast
Yup, same here on a nest hub. Was working fine. Now on 1.46.203796 times out after 10 minutes.
I think if we keep something playing in the background on the receiver side. It should prevent the timeout. Some blank music perhaps??
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.
Ok it looks like a google firmware issue. Go ask google.
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.
Ok it looks like a google firmware issue. Go ask google.
Same issue here. Times out after 10 minutes… Does anybody know how to solve this?
Is it possible to rotate the screen? I have a screen in portrait mode?
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 
1 Like
ssl_certificate: /ssl/certificate.pem
ssl_key: /ssl/privkey.pem
base_url: https://192.168.17.161
cors_allowed_origins:
- https://www.home-assistant.io
- https://cast.home-assistant.io
- https://192.168.17.193
I also get this error, did you manage to solve this?
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?
1 Like
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.
1 Like
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
anyone having the same problem?
I have the same problem and would love to find a resolution. Have you found anything?
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.
1 Like