Google Cast error - Unable to find a view with path xxxx

Development
81

I have the same issue since upgrading. Google home hub says Connected, but never progresses past this. Cast can no longer access my views (cast.nabucasa page or Dev/Services) other than a ‘home’ one that looks like an ‘all entities’ page that’s not an actual view I have configured myself. Using Nabu Casa URL for access.

82

The (only) view being casted looks very much like the deprecated “states” view - found in your.ha.io.url/states: https://github.com/home-assistant/home-assistant-polymer/issues/4459

That would explain why the so-called home being casted is totally different than the home you have built.

83

i use Duckdsn, i just have old home. I have wiped with old snapshot and i have always the problem. It’s https://cast.home-assistant.io problem.

84

Just bumping the thread for posterity.

I have the exact same issue.

Can only cast default_view from the service.

Only see HOME using https://cast.home-assistant.io/

All other views give the “Error: unable to finve view …” When called by service.

currently running version 0.104.3

85

Suggest you all post here https://github.com/home-assistant/home-assistant-polymer/issues/4614

This has also stopped working for me… not sure when.

1 Like
86

So i actually got a bit further. A friend of mine just got his first Google Nest Hub, so I was thinking that I would give the cast function another shot, on a fairly new installation of Home Assistant. The installation is pretty similiar to mine. Same hardware and same version.

I opened up the Services and made a service call and boom, same issue. Says Connected and nothing happens. Hmm, I then tried using the media_player.turn_off so that the stream stopped and tried the cast.lovelace again. Bing, there we go, it connected straight away. Without using the cast.home-assistant.io. What the heck? I’ve been trying that for weeks now. What is the difference here?

Finally it came to my mind, that we didn’t set up the Nabu Casa subscription yet, but we went with the DuckDns.org option. So when accessing Home Assistant on the local lan, we had to access the site with https://192.xxx.xxx.xxx.

I didn’t set up that part in my home, since I didn’t want to open any ports in my Firewall in the first place. I’ve used the Nabu Casa subscription from almost the beginning. Unfortunately, that doesn’t help me with the lan when I access my Home Assistant instance. It will still be http://192.xxx.xxx.xxx.
So whenever I try to fire the cast.lovelace from http, then it won’t work, unless I authorize via the cast.home-assistant.io page. But if I head directly to the Nabu Casa Remote page, then I can do it without. Unfortunately that doesn’t help me me much when I try to automate this.

Question is, can I somehow get the certificate stored locally that is also being used via Nabu Casa, or will I have to use DuckDns or create a self-signed certificate to get this https working on my lan as well?

87

So this began working late last week After 2 or 3 days being down but as of the weekend has gone down again. Haven’t made any config changes in a fortnight or so. I assume there’s changes or something happening server side which is making the service unreliable?

Keeping an eye on the following for now
https://github.com/home-assistant/core/issues/32370

1 Like
88

it works for the default_view ‘0’ 100% of the time. for the custom dashboards it’s different.
sometimes it works and sometimes it doesn’t. when i trigger it from services it doesn’t work then i trigger it again from services without the dashboard_path and then again with the dashboard_path it works. i will post a video of the working cast.

89

I’ve yet to be able to get Cast to work via Automation/DevTools service. Only the special card OR via cast.home-assistant.io.

How are you getting cast to work via Automation?

I’ve tried through DuckDNS, NabuCasa, I’m using standard ports.

90

this works 50% of the time

- id: '1591682005536'
  alias: Test Nest Hub
  description: ''
  trigger:
  - event: start
    platform: homeassistant
  - entity_id: media_player.hub_huiskamer
    platform: state
    to: 'off'
  action:
  - data:
      dashboard_path: nest-hub
      entity_id: media_player.hub_huiskamer
      view_path: begane-grond
    service: cast.show_lovelace_view
91

Home assistant cast

92

i managed to make it work 100% of the time from automations:

- id: '1591682005536'
  alias: Test Nest Hub
  description: ''
  trigger:
  - event: start
    platform: homeassistant
  - entity_id: media_player.hub_huiskamer
    platform: state
    to: 'off'
  action:
  - data:
      entity_id: media_player.hub_huiskamer
      view_path: begane-grond
    service: cast.show_lovelace_view
  - delay: '00:00:05'
  - data:
      dashboard_path: nest-hub
      entity_id: media_player.hub_huiskamer
      view_path: begane-grond
    service: cast.show_lovelace_view

in this automation i first send the command without dashboard and then with a delat of 5 second with dashboard and that works. if i put the delay on 2 seconds it says connected but not show the page, with 5 seconds it works everytime. it should be fixed though but this is a work around for the time being.

4 Likes
93

Can confirm this works for me too. As expected, a “cannot find path xxx” is displayed following the first command, but five seconds later, I see the expected view.

94

This is not working for me, I get ‘Unable to view path xxx’ and it just stays on that page most of the time, I had 2 or 3 successes in the ~30 times I tested.

I believe the issue is the hosted app that the Nest loads is not always able to get the paths from my HA instance, even thought I change nothing it works sometimes, but most of the time not.
I might be wrong, but my theory is that there is a very short timeout on the app on the call to the HA instance app to retrieve the available paths, and due to my geographic region (South Africa), is causing the issues.

1 Like
95

Lucky you! Keep us posted on reliability. Not working for me!

96

@NeilDuToit92
u can try to up the delay with a second a time, this is how i came to a reliable solution for my enviroment.

97

In my case, I need to turn off then on the hub, with a delay between them, to have it working. After 1 hour of testing, 100% of success.
Here is my code:

- entity_id: input_boolean.test
    platform: state
    to: 'on'
  action:
  - data:
      entity_id: media_player.nest_hub
    service: media_player.turn_off
  - delay: "00:00:01"
  - data:
      entity_id: media_player.nest_hub
    service: media_player.turn_on
  - data:
      entity_id: media_player.nest_hub
      view_path: test
    service: cast.show_lovelace_view
  - delay: '00:00:05'
  - data:
      dashboard_path: lovelace
      entity_id: media_player.nest_hub
      view_path: test
    service: cast.show_lovelace_view
7 Likes
98

@radar, you might just have found the solution there… I have been calling ‘stop’ before trying to cast. Turning it off and on again seems to be working in the ~10 tests I just performed. I’ll continue testing over the next few days.

99

Got one path error right now after one day of testing.

100

It seems I was a little too optimistic about the first workaround as it has stopped working for me. I’ve since changed to @radar’s approach and so far (after an hour) it’s been 100% successful, however custom cards are not showing.

@radar / @NeilDuToit92 are you able to see custom cards with this solution?