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

Development
61

I’ve been programming this for the past day in YAML. It’s working 80% of the time for me, and it shows the lovelace view!!! The script I’m using to get this working is as below (note the use of single quotation marks around the view number. Did this as I couldn’t get URL path name working).

Give my YAML code a try and it’ll hopefully work for you too. I’m on Hassio v0.104.4

script:
  cast_home_assistant_kitchen:
    alias: Home Assistant Cast to Kitchen Display
    sequence:
      - service: media_player.turn_off
        data:
          entity_id: media_player.nest_hub_max
      - delay:
          seconds: 1
      - service: cast.show_lovelace_view
        data:
          entity_id: media_player.nest_hub_max
          view_path: '8'
1 Like
62

I use a similar script to the one @sebdoan uses, for me it works around 60%. When it doesn’t work, I also get an error “unable to find a view…”.

Hope this will be fixed soon.

63

Having the same issue however found that if I start up https://cast.home-assistant.io/, select the target (media player) but not the ‘Source’ (the lovelace view/path), I can cast whatever I want either manually or through automations.

The https://cast.home-assistant.io/ interface also mirrors what ‘Source’ is being viewed/cast. It’s not perfect but should work ok.

64

I just installed 0.105.2 and I can say the latest instance is a lot less stable for this casting feature vs 0.104.3

It now only works 10% of the time.

1 Like
65

Glad to hear I can stop beating my head against that wall and wait for a better release. I just started trying to use it for the first time.

66

I’m still on 0.105.2 but after several days the casting feature seems to get more solid with time. It’s about 50-70% reliable atm.

1 Like
67

My problem is still that we need to authorize through cast.home-assistant.io, which is a manual process. I really hope that it can be automated somehow, so we just have to call the ‘cast.show_lovelace_view’ and the path needed.

68

I’ve never needed to do that

69

Then I need your expertise :+1:… I Simply can’t get it working without.

So without doing anything you can just go to the develop tool, services and select the ‘cast.show_lovelace_view’ and then call the entity of your nest hub using the View either by name or number?

70

This one here works with iOS or anything from Lovelace:

              - type: custom:button-card
                icon: mdi:home-assistant
                name: System
                tap_action:
                  action: call-service
                  service: script.casthomeassistant
              - type: custom:button-card
                icon: mdi:weather-cloudy
                name: Weather
                tap_action:
                  action: call-service
                  service: script.castweather

Script looks like this:


casthomeassistant:
  alias: Cast Home Assistant
  sequence:
  - data:
      entity_id: media_player.lounge_room_tv
      view_path: home_assistant
    service: cast.show_lovelace_view
castweather:
  alias: Cast Weather
  sequence:
  - data:
      entity_id: media_player.lounge_room_tv
      view_path: weather
    service: cast.show_lovelace_view

Other way is (only works on a cast device like chrome) You have to select the device and then you can cast to it:

          - type: entities
            title: Chromecast Control
            show_header_toggle: false
            entities:
              - type: cast
                name: System
                view: "home_assistant"
                hide_if_unavailable: false
              - type: cast
                name: Weather
                view: "weather"
                hide_if_unavailable: false
71

So I was excited to get home and try your approach and… voila, it worked on the very first try.
Unfortunately I kept it running over night, and this morning when I wanted to try again - same script, it “failed”. It shows the Home Assistant luvs Nabu Casa and then it says ‘Connected’. While that might be true, it still doesn’t show the lovelace view I want to cast.
So once again I have to open a Browser, head to cast.home-assistant.io and authorize and cast a lovelace view. When that is done, then I can fire your script and it will work. Also with different views - probably until the authorization is “expired” :frowning:

72

I was having the same problems. I gave up using the cast.show_lovelace_view service. Instead I use CATT : Using CATT and it has been working just great.

1 Like
73

It can take 30 seconds after it shows connected to cast the card… Just leave it there and wait a bit.

74

I have now waited for more than one hour and it still shows the luv screen and ‘Connected’.
So there must be something else wrong.

Do I need to set up some auth_trust to leave out the authorization process with cast.home-assistant.io, could that be it or don’t you have that in your conf?

75

I don’t have anything in my config.

76

Damn :frowning:

Then I’m lost…

77

Try using a path number rather than a a name like mentioned in this post above Google Cast error - Unable to find a view with path xxxx

78

It stopped altogether for me, I simply see “Connected” and nothing else.

anyone else having this issue?

I rebooted both the hub and the server.

79

@Maxi1134 I can confirm this has also happened to my system. I am using the Nabu-Casa generated URL.

I would also like to add that i am now using version 0.106.2. Same issue.

80

Same results for me, while using Nabu Casa, but having your own reverse proxy doesn’t make any difference either. Casted through front-end and through https://cast.home-assistant.io/ gives the same result.

I am only able to fire up “HOME” which doesn’t reflect the HOME i built earlier. Any other page (even with numbers in path/url) ends up with “Error: Unable to find a view with path X”.

1 Like