From 178175fbf47c6fa03d7d2e3fe7901230cd2504eb Mon Sep 17 00:00:00 2001 From: Diogo Gomes Date: Mon, 12 Feb 2018 21:50:16 +0000 Subject: [PATCH] Added Example for 2 STB (#4649) --- .../_components/media_player.mediaroom.markdown | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/source/_components/media_player.mediaroom.markdown b/source/_components/media_player.mediaroom.markdown index 17724f0d763..828656b7e9f 100644 --- a/source/_components/media_player.mediaroom.markdown +++ b/source/_components/media_player.mediaroom.markdown @@ -47,6 +47,19 @@ Notice that all parameters are optional, and discovery should configure everythi The component has been developed for Portuguese TV operators currently using the Mediaroom platform, but should also work in other deployments in which the STB can be controlled remotely through a socket on port 8082. -In most cases (single STB) you just need to setup the *name* and discovery will do the rest. In case you have more than one STB you are required to set the *host* in each one of the entries. +In most cases (single STB) you just need to setup the *platform* and discovery will do the rest. In case you have more than one STB you are required to set the *host* in each one of the entries. If the STB is on the same network segment as Home Assistant, it can determine whether the device is turned on or off. Without this, the component will fail to determine the Set-top box status, and you are required to add the *optimistic* configuration variable. + +### {% linkable_title Example configuration with 2 STB %} + +```yaml +# Example configuration.yaml entry for 2 STB +media_player: + - platform: mediaroom + host: 192.168.1.64 + name: Living Room STB + - platform: mediaroom + host: 192.168.1.65 + name: Bedroom STB +```