diff --git a/source/_components/cast.markdown b/source/_components/cast.markdown
index 59ac474f86e..a7f8c7b0f89 100644
--- a/source/_components/cast.markdown
+++ b/source/_components/cast.markdown
@@ -15,6 +15,17 @@ discovered if you enable [the discovery integration](/components/discovery/). If
 you don't have the discovery integration enabled, you can enable the Cast
 integration by going to the Integrations page inside the config panel.
 
+## Home Assistant Cast
+
+The Cast integration allows you to start Home Assistant Cast on any Chromecast device, using 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.
+
+```json
+{
+  "entity_id": "media_player.office_display_4",
+  "view_path": "lights"
+}
+```
+
 ## Advanced use
 
 The Cast integration has some extra configuration options available for advanced
diff --git a/source/_posts/2019-08-06-home-assistant-cast.markdown b/source/_posts/2019-08-06-home-assistant-cast.markdown
index 64c38bb15b6..e73a70353a3 100644
--- a/source/_posts/2019-08-06-home-assistant-cast.markdown
+++ b/source/_posts/2019-08-06-home-assistant-cast.markdown
@@ -59,5 +59,5 @@ entities:
 
 This is the first release of Home Assistant Cast, and so we focused on the minimum that was worthy of a release. We still have some more things planned:
 
-- Allow starting Home Assistant Cast from Home Assistant itself (not a browser), as part of an automation or script.
+- Allow starting Home Assistant Cast from Home Assistant itself (not a browser), as part of an automation or script. [This is live now since Home Assistant 0.99.](/components/cast/#home-assistant-cast)
 - Use Home Assistant Cast as a text-to-speech target (inspired by [lovelace-browser-commander by @thomasloven](https://github.com/thomasloven/lovelace-browser-commander)).