diff --git a/source/_components/media_player.cast.markdown b/source/_components/media_player.cast.markdown
index 52d0e1d39c0..63271c16760 100644
--- a/source/_components/media_player.cast.markdown
+++ b/source/_components/media_player.cast.markdown
@@ -17,7 +17,7 @@ ha_iot_class: "Local Polling"
 
 Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
 
-Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
+The Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -28,4 +28,15 @@ media_player:
 Configuration variables:
 
 - **host** (*Optional*): Use only if you don't want to scan for devices.
-- **ignore_cec** (*Optional*) A list of chromecasts that should ignore CEC data for determining the active input. [See the upstream documentation for more information.](https://github.com/balloob/pychromecast#ignoring-cec-data)
+- **ignore_cec** (*Optional*) A list of Chromecasts that should ignore CEC data for determining the active input. [See the upstream documentation for more information.](https://github.com/balloob/pychromecast#ignoring-cec-data)
+
+## {% linkable_title Example %}
+
+By setting `host:` you can specify the Chromecast to use.
+
+```yaml
+# Example configuration.yaml entry
+media_player:
+  - platform: cast
+    host: 192.168.1.10
+```