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 <frenck@frenck.nl>
This commit is contained in:
DK 2019-11-17 11:42:49 -08:00 committed by Franck Nijhof
parent 3572980d21
commit 8f62732379

View File

@ -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
{