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

Development
142

I managed to make Google Cast work.
Create new dashboard here: Configuration → Dashboards
one field is URL which will be prefilled by title, for me it was lovelace-doorbell (title was doorbell)
then url of this dashboard will be http://homeassistant.local:8123/lovelace-doorbell/0

automation should look like this:

service: cast.show_lovelace_view
data:
  entity_id: media_player.living_room_display
  dashboard_path: lovelace-doorbell
  view_path: '0'
3 Likes
143

Work perfect , thanks @radar !!!

no need http, https and complet path…just media_player.x off, then on, then call first lovelace, then view_path “0”

work perfect!

144

I had the same problem - I had to use both view_path: and dashboard_path:

my dashboard is called castdash and the URL to it is https://…:8123/lovelace/castdash

service: cast.show_lovelace_view
data:
dashboard_path: lovelace
entity_id: media_player.nesthub2392
view_path: castdash

145

This is all entirely unnecessary though.

The simple answer is that my dashboard path wasn’t being generated properly. Once I added value for, “path” into the Lovelace view (I added, path: HUD to the existing dashboard named, Landscape Dashboard), then refreshed the dashboard, and changed the configuration of the step of the show_lovelace_view to be:

service: cast.show_lovelace_view
data:
  entity_id: media_player.living_room_display
  dashboard_path: landscape-dashboard
  view_path: "0"

… then it worked.

Initially, the dashboard’s path was messed up, still showing something like, “/landscape-dashboard/0” – I’m not sure how or why things weren’t working that way, but I did generate that dashboard from the initial, out-of-the-box Lovelace view that came with Home Assistant. I’m guessing that’s what generated this problem in the first place since I tried a million variations otherwise.

146

I agree, things seem to work much better with the newest versions of Home Assistant vs before. This is the YAML code I currently use. I find that turning the device off first works better for edge cases when the device is already in-use.

script:
  test_example:
    sequence:
      - service: media_player.turn_off
        data:
          entity_id: media_player.master_bedroom_display
      - delay: "00:00:01"
      - service: cast.show_lovelace_view
        data:
          entity_id: media_player.master_bedroom_display
          view_path: 'cast'
147

Now that this CAST feature is somewhat stable, I’ve been playing around with it a bit more. I’ve noticed that the CAST feature does not support “camera_view: live” for Picture cards.

Does anyone know of any alternative cards that will allow for a live view of my cameras when using the CAST feature?

148

It does allow it from what I recall. Mine isn’t currently working, but I haven’t bothered to debug it and my camera RTSP stream conversion server needs to be rebuilt. Remember the rules for this type of casting though:

  • Stream source has to be accessible EXTERNALLY (e.g. outside of your network), so open up and forward the port on your router; AND
  • Stream source has to be a proper HTTPS stream with a valid (non-self-signed, signed using a public Certificate Authority) SSL certificate; AND
  • SSL cipher and TLS version has to be appropriate. (e.g. NOT SSL v2 or v3, so essentially TLS >= 1.0).

Here’s what I have right now (which doesn’t work, but should, since I believe it has worked before):

  - camera_view: live
    type: picture-glance
    title: Front Door
    entities: []
    tap_action:
      action: more-info
    image: >-
      https://your.android.tinycam.url.here.com:8083/axis-cgi/mjpg/video.cgi?camera=1&fps=5&compression=40&resolution=1280x720
    camera_image: camera.front_door_camera

If I remember to do so, I will follow up on this thread once I rebuild my RTSP stream conversion server for my Wyze Cam Outdoor v2

1 Like