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

Development
41

Got it !!! i think. Now testing.

media_player.turn_off <- to turn off

after that its working again :slight_smile:

42

Its working.

@RyanEwen thanks for the help.

To let it work:

  1. logout from https://cast.home-assistant.io
  2. Stop the mediaplayer with the media_player.turn_off service
  3. Then start de cast with the service
1 Like
43

Iā€™m having the same issue so thanks for working on this, everyone.

Question: I have never signed into https://cast.home-assistant.io but was able to get a few of my views to show up on my Google Hub via cast. Is signing in a necessary step?

44

My picture cards is also not showing up, even if they are at the default_view view. Works on the computer but if i cast it to my nest, the other cards show up, but the picture Glance-card and the Picture Cards is totally goneā€¦

45

Camera, picture and some custom cards are known not to work from memory.

46

There has to be something else thatā€™s preventing this from working for me. I signed out of the Google Chrome web interface, restarted HA, called a media_player.turn_off service and when I call the cast.show_lovelace_view it still hangs on the ā€œConnectedā€ screen. There are no errors in the log, it just fails to pick the view. I give up until the devs provide a fix. It is just too finicky at this point.

4 Likes
47

This works just fine for me.

  alias: castbabies
  sequence:
  - data:
      entity_id: media_player.vizeo
      view_path: default_view
    service: cast.show_lovelace_view

I use duckdns; port 8123 and 443 are forwarded. Idk if that helps anyone. I also logged in with the online tool first, closed the tab (didnā€™t log out), then in chrome I stopped the device from casting and setup a toggle button for the script which works from lovelace.

I had been having difficulty just like you guys. I stupidly uninstalled adguard and had to restore an image and delete ā€œhome-assistant_v2.dbā€.

Knowing I might permanently (not really) break something by doing things incorrectly, I followed the steps above exactly as I described.

Hope this helps someone.

48

Welcome to the forum, @zensunset!

Thanks for the input, however, I think everyone is able to cast the default_view. The issue is that the service doesnā€™t work for user-created views.

49

Itā€™s not super clear but the problem is just unclear documentation.

I tried to do this with the cast.show_lovelace_view service and it did not work. I then went and authorized access through https://cast.home-assistant.io/ and was able to cast the views without issues. I then started poking around to better understand the view_path attribute. It turns out I had not updated my view idā€™s to view paths. This was probably something I missed in the migration to lovelace. So I just changed id to path in my config and now the cast command works as expected.

image

image
image1062Ɨ2236 241 KB

I tried to edit the docs but Iā€™m a github noob. Help if you can: https://github.com/home-assistant/home-assistant.io/pull/11181

1 Like
50

It seems that the lovelace GUI editor is using path under the hood but itā€™s still not working as expected for me:

image

ACTUALLY

I hadnā€™t tried this since updating HA to 101ā€¦ it seems to be working at the moment

51

I still have the same symptons a few of us isolated at the start of the thread:

Does anyone know if there is actually an active/dedicated issue raised for this on Github or if this is actually on the devs radar? How can we confirm?

3 Likes
52

Iā€™ve seen this issue that is open:

53

Yes, Iā€™ve commented on that one. https://github.com/home-assistant/home-assistant/issues/26758#issuecomment-533834408

But I think itā€™s a different issue?

So Iā€™m still not sure there is a open issue for this?

54

Iā€™ve raised an issue. Could few of you jump on and confirm you have the same issue?
Cheers.

5 Likes
55

Done and same issue here on 0.103.4.
Still no fix :sleepy:

2 Likes
56

Can people confirm that the Lovelace path are still not working???

Itā€™s annoying however, in that case Iā€™m just going to edit the ā€œstatesā€ views rather than the ā€œlovelaceā€ views and that will give me what I need.

If it helps anybody, the ā€œcast.show_lovelace_viewā€ seems to be able to recognise the names of all my ā€œgroupā€ (non-lovelace) view names as shown below (from the configuration.yaml file).

The service should be called ā€œcast.show_states_viewā€!!!

image

57

Never got it to work properly. I try it every release hoping devs actually fixed it butā€¦nope

58

I notice that immediately after rebooting Home Assistant it casts Lovelace ā€œ0ā€ number views, but after a few minutes it revert to the States ā€œ0ā€ number views. Itā€™s very unreliable however, it works one minute then not longer recognises the state path, then later it works again!!! Too frustating!!!

Definitely a bug somewhere in the Cast Lovelace code. I hope someone fixes it, cause Lovelace is so much nicer than States views.

59

Itā€™s annoying that lovelace views canā€™t be displayed reliably, for now use the deprecated STATES views as an interim solution.

Details on how to configure STATES views here: https://www.home-assistant.io/integrations/group/

60

Itā€™s not longer unreliable for me, it refuses to work 100% of the time now. A few versions ago, 1 time out of 5 Iā€™d get an error, now it just doesnā€™t work at all.

Itā€™s a shame as I was really excited about this feature, but this issue doesnā€™t seem to be getting any developer focus at all.

1 Like