From 8f62732379d7c6d2721c332f548ff3767aea5679 Mon Sep 17 00:00:00 2001 From: DK <16869713+poldim@users.noreply.github.com> Date: Sun, 17 Nov 2019 11:42:49 -0800 Subject: [PATCH] Update to clarify path declaration in lovelace config (#11181) * Update to clarify path declaration in lovelace config This was not very clear as many people were having this issue: https://community.home-assistant.io/t/google-cast-error-unable-to-find-a-view-with-path-xxxx/138180/48 * Update source/_integrations/cast.markdown Looks good Co-Authored-By: Franck Nijhof --- source/_integrations/cast.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index eff0317b1ac..29190ff4128 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -13,7 +13,7 @@ You can enable the Cast integration by going to the Integrations page inside the ## Home Assistant Cast -Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. +Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). ```json {