jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Merge remote-tracking branch 'origin/current' into rc

Browse source
This commit is contained in:
Paulus Schoutsen 2018-03-28 15:32:13 -07:00
commit 5526af141b
5 changed files with 19 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

10
source/_components/http.markdown
View file

@ -75,8 +75,6 @@ To use those kind of [sensors](/components/sensor.http/) or [binary sensors](com
All [requests](/developers/rest_api/#post-apistatesltentity_id) need to be sent to the endpoint of the device and must be **POST**.
If you want to use Home Assistant to host or serve static files then create a directory called `www` under the `.homeassistant` configuration path. The static files in `.homeassistant/www/` can be accessed by the following URL `http://your.domain:8123/local/`.
If you want to apply additional IP filtering, and automatically ban brute force attempts, set `ip_ban_enabled` to `True` and the maximum number of attempts. After the first ban, an `ip_bans.yaml` file will be created in the root configuration folder. It will have the banned IP address and time in UTC when it was added:
```yaml
@ -89,3 +87,11 @@ After a ban is added a Persistent Notification is populated to the Home Assistan
<p class='note warning'>
Please note, that sources from `trusted_networks` won't be banned automatically.
</p>
## {% linkable_title Hosting files %}
If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config` on Hass.io, `.homeassistant` elswhere). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`.
<p class='note'>
If you've had to create the `www/` folder for the first time, you'll need to restart Home Assistant.
</p>

7
source/_components/media_player.mediaroom.markdown
View file

@ -47,7 +47,7 @@ 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 *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.
In most cases (single STB) you just need to setup the *platform* and discovery will do the rest.
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.
@ -55,8 +55,9 @@ If the STB is on the same network segment as Home Assistant, it can determine wh
### {% linkable_title Example `press_button` script %}
The `play_media` function can be used in scripts to change channels.
The `play_media` function can be used in scripts to change channels and emulate button pressing from a remote control.
{% raw %}
```yaml
# Example play_media script
#
@ -67,6 +68,8 @@ press_button:
entity_id: media_player.mediaroom_stb
media_content_id: "{{ value }}"
media_content_type: "channel"
```
{% endraw %}
### {% linkable_title Example configuration with 2 STB %}