From e688e955b8afaf21828d0b1d8d82d3ad12e361a3 Mon Sep 17 00:00:00 2001 From: Thomas Augustinus Date: Mon, 18 May 2020 10:57:42 +0200 Subject: [PATCH] description of the dashboard path (#13370) the description was missing - and it made it quite a guesswork to make it work. --- source/_integrations/cast.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index 725fdfee5ce..ef67f9489bd 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -16,14 +16,14 @@ 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. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call): +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). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url` Typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call): ```yaml 'cast_downstairs_on_kitchen': alias: Show Downstairs on kitchen sequence: - data: - dashboard_path: lovelace-cast- + dashboard_path: lovelace entity_id: media_player.kitchen view_path: downstairs service: cast.show_lovelace_view