Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
fa563cba7e
50 changed files with 284 additions and 152 deletions
|
|
@ -110,7 +110,7 @@ then device authentication is required. Press the icon in the upper left corner
|
|||
|
||||
<img src='/images/screenshots/developer-tools.png' />
|
||||
|
||||
Select `apple_tv` as domain, `apple_tv_authenticate` as service and enter `{'entity_id': 'XXX'}` into "Service Data", but replace XXX with the entity id of your device (e.g. `media_player.apple_tv`). Press the button and hopefully you are presented with an input dialog asking for a pin code:
|
||||
Select `apple_tv` as domain, `apple_tv_authenticate` as service and enter `{"entity_id": "XXX"}` into "Service Data", but replace XXX with the entity id of your device (e.g. `media_player.apple_tv`). Press the button and hopefully you are presented with an input dialog asking for a pin code:
|
||||
|
||||
<img src='/images/components/apple_tv/auth_start.jpg' />
|
||||
|
||||
|
|
|
|||
|
|
@ -32,3 +32,17 @@ Configuration variables:
|
|||
It is recommended to create a dedicated user on Arlo website to be used within Home Assistant and then share your Arlo cameras.
|
||||
|
||||
Finish its configuration by visiting the [Arlo sensor page](/components/sensor.arlo/) or [Arlo camera page](/components/camera.arlo/).
|
||||
|
||||
The Arlo component also provides a service to enable/disable the motion detection sensor. The example below enables the motion detection every time the Home Assistant service starts.
|
||||
|
||||
```yaml
|
||||
#automation.yaml
|
||||
- alias: Enable Arlo upton HA start'
|
||||
initial_state: 'on'
|
||||
trigger:
|
||||
platform: homeassitant
|
||||
event: start
|
||||
action:
|
||||
service: camera.enable_motion_detection
|
||||
entity_id: camera.arlo_frontdoor
|
||||
```
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ comments: false
|
|||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Other
|
||||
ha_category: Utility
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -222,3 +222,12 @@ automation:
|
|||
entity_id: climate.kitchen
|
||||
swing_mode: 1
|
||||
```
|
||||
#### {% linkable_title Customization %}
|
||||
|
||||
The step for the setpoint can be adjusted (default to 0,5 increments) by adding the following line into configuration
|
||||
|
||||
'''yaml
|
||||
customize:
|
||||
- entity_id
|
||||
target_temp_step: 1
|
||||
'''
|
||||
|
|
|
|||
|
|
@ -68,11 +68,11 @@ devicename:
|
|||
|
||||
| Parameter | Default | Description |
|
||||
|----------------|-------------------------------|---------------------------------------------------------------------------------------------------------|
|
||||
| `name` | Host name or "Unnamed Device" | The friendly name of the device |
|
||||
| `mac` | None | The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP |
|
||||
| `name` | Host name or "Unnamed Device" | The friendly name of the device. |
|
||||
| `mac` | None | The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP. |
|
||||
| `picture` | None | A picture that you can use to easily identify the person or device. You can also save the image file in a folder "www" in the same location (can be obtained from developer tools) where you have your configuration.yaml file and just use `picture: /local/favicon-192x192.png`. |
|
||||
| `icon` | mdi:account | An icon for this device (use as an alternative to `picture`). |
|
||||
| `gravatar` | None | An email address for the device's owner. If provided, it will override `picture` |
|
||||
| `track` | [uses platform setting] | If `yes`/`on`/`true` then the device will be tracked. Otherwise its location and state will not update |
|
||||
| `hide_if_away` | False | If `yes`/`on`/`true` then the device will be hidden if it is not at home |
|
||||
| `consider_home` | [uses platform setting] | Allows you to override the global `consider_home` setting from the platform configuration on a per device level |
|
||||
| `gravatar` | None | An email address for the device's owner. If provided, it will override `picture`. |
|
||||
| `track` | [uses platform setting] | If `yes`/`on`/`true` then the device will be tracked. Otherwise its location and state will not update. |
|
||||
| `hide_if_away` | False | If `yes`/`on`/`true` then the device will be hidden if it is not at home. |
|
||||
| `consider_home` | [uses platform setting] | Seconds to wait till marking someone as not home after not being seen. Allows you to override the global `consider_home` setting from the platform configuration on a per device level. |
|
||||
|
|
|
|||
|
|
@ -17,6 +17,10 @@ As an alternative to the router-based device tracking, it is possible to directl
|
|||
|
||||
If you're on Debian or Ubuntu, you might have to install the packages for `arp` and `nmap`. Do so by running `$ sudo apt-get install net-tools nmap`. On a Fedora host run `$ sudo dnf -y install nmap`.
|
||||
|
||||
<p class='note'>
|
||||
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
|
||||
</p>
|
||||
|
||||
Host detection is done via Nmap's "fast scan" (`-F`) of the most frequently used 100 ports, with a host timeout of 5 seconds.
|
||||
|
||||
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
|
|
|||
|
|
@ -11,12 +11,16 @@ logo: ffmpeg.png
|
|||
ha_category: Hub
|
||||
---
|
||||
|
||||
The FFmpeg component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
|
||||
The `ffmpeg` component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
|
||||
|
||||
<p class='note'>
|
||||
You need the `ffmpeg` binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from [debian-backports](https://backports.debian.org/Instructions/). If you want [hardware acceleration](https://trac.ffmpeg.org/wiki/HWAccelIntro) support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the [FFmpeg](http://www.ffmpeg.org/) website.
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
|
||||
</p>
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -18,11 +18,14 @@ This offers the official frontend to control Home Assistant.
|
|||
frontend:
|
||||
```
|
||||
|
||||
#### Themes
|
||||
### {% linkable_title Themes %}
|
||||
|
||||
Starting with version 0.49 you can define themes:
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
frontend:
|
||||
themes:
|
||||
happy:
|
||||
|
|
@ -31,13 +34,15 @@ frontend:
|
|||
primary-color: blue
|
||||
```
|
||||
|
||||
The example above defined two themes named `happy` and `sad`. For each theme you can set values for CSS variables. For a partial list of variables used by the main frontend see [ha-style.html](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/resources/ha-style.html)
|
||||
The example above defined two themes named `happy` and `sad`. For each theme you can set values for CSS variables. For a partial list of variables used by the main frontend see [ha-style.html](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/resources/ha-style.html).
|
||||
|
||||
There are 2 themes-related services:
|
||||
- `frontend.reload_themes` - reloads theme configuration from yaml.
|
||||
- `frontend.set_theme(name)` - sets backend-preferred theme name.
|
||||
|
||||
- `frontend.reload_themes`: reloads theme configuration from your `configuration.yaml` file.
|
||||
- `frontend.set_theme(name)`: sets backend-preferred theme name.
|
||||
|
||||
Example in automation:
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: 'Set theme at startup'
|
||||
|
|
@ -48,5 +53,5 @@ automation:
|
|||
action:
|
||||
service: frontend.set_theme
|
||||
data:
|
||||
name: pink
|
||||
name: happy
|
||||
```
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ ha_release: 0.23
|
|||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The HDMI CEC component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use `cec-client` (part of the `libcec` package) to listen to traffic on the CEC bus and discover the correct numbers.
|
||||
The `hdmi_cec` component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use `cec-client` (part of the `libcec` package) to listen to traffic on the CEC bus and discover the correct numbers.
|
||||
|
||||
## {% linkable_title CEC Setup %}
|
||||
|
||||
|
|
@ -25,6 +25,10 @@ The computer running Home Assistant must support CEC, and of course be connected
|
|||
|
||||
[libcec](https://github.com/Pulse-Eight/libcec) must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. `libcec` installs Python 3 bindings by default as a system Python module. If you are running Home Assistant in a [Python virtual environment](/getting-started/installation-virtualenv/), make sure it can access the system module, by either symlinking it or using the `--system-site-packages` flag.
|
||||
|
||||
<p class='note'>
|
||||
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
|
||||
</p>
|
||||
|
||||
#### {% linkable_title Symlinking into virtual environment %}
|
||||
|
||||
Create a symlink to the `cec` installation. Keep in mind different installation methods will result in different locations of cec.
|
||||
|
|
|
|||
|
|
@ -28,6 +28,7 @@ image_processing:
|
|||
source:
|
||||
- entity_id: camera.garage
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **region** (*Required*): Country or region. List of supported [values](https://github.com/openalpr/openalpr/tree/master/runtime_data/config).
|
||||
|
|
|
|||
|
|
@ -17,8 +17,6 @@ ha_release: 0.47
|
|||
|
||||
Some pre-defined classifiers can be found here: https://github.com/opencv/opencv/tree/master/data
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
|
||||
To setup OpenCV with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -17,6 +17,10 @@ ha_iot_class: "Local Polling"
|
|||
|
||||
The `seven_segments` image processing platform allows you to read physical seven segments displays through Home Assistant. [`ssocr`](https://www.unix-ag.uni-kl.de/~auerswal/ssocr/) is used to extract the value shown on the display which is observed by a [camera](/components/camera/). `ssocr` need to be available on your system. Check the installation instruction for Fedora below or use `$ sudo apt-get install ssocr` on a Debian-based system:
|
||||
|
||||
<p class='note'>
|
||||
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
|
||||
</p>
|
||||
|
||||
```bash
|
||||
$ sudo dnf -y install imlib2-devel
|
||||
$ git clone https://github.com/auerswal/ssocr.git
|
||||
|
|
|
|||
|
|
@ -18,26 +18,44 @@ Philips Hue support is integrated into Home Assistant as a light platform. The p
|
|||
|
||||
Once discovered, if you have a custom default view, locate `configurator.philips_hue` in the entities list ( < > ) and add it to a group in `configuration.yaml`. Restart Home Assistant so that the configurator is visible in the Home Assistant dashboard. Once Home Assistant is restarted, locate and click on `configurator.philips_hue` to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in home assistant. Once complete, the configurator entity isn't needed anymore and can be removed from any visible group in `configuration.yaml`.
|
||||
|
||||
When you configure the Hue bridge from Home Assistant, it writes a token to a file in your Home Assistant [configuration directory](/docs/configuration/). That token authenticates the communication with the Hue bridge. This token uses the IP Address of the Hue Bridge. If the IP address for the Hue Bridge changes, you will need to register the Hue Bridge with Home Assistant again. To avoid this you may set up DHCP registration for your Hue Bridge, so that it always has the same IP address.
|
||||
|
||||
Restarting Home Assistant once more should result in the Hue lights listed as "light" entities. Add these light entities to configuration.yaml and restart home assistant once more to complete the installation.
|
||||
|
||||
If you want to enable the component without relying on the [discovery component](/components/discovery/), add the following lines to your `configuration.yaml`:
|
||||
If you want to enable the component without relying on the [discovery component](/components/discovery/), add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
light:
|
||||
platform: hue
|
||||
host: DEVICE_IP_ADDRESS
|
||||
- platform: hue
|
||||
host: DEVICE_IP_ADDRESS
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Optional*): IP address of the device, eg. 192.168.1.10. Required if not using the `discovery` component to discover Hue bridges.
|
||||
|
||||
- **allow_unreachable** (*Optional*): (true/false) This will allow unreachable bulbs to report their state correctly.
|
||||
- **filename** (*Optional*): Make this unique if specifying multiple Hue hubs.
|
||||
- **allow_in_emulated_hue** (*Optional*): )true/false) Enable this to block all Hue entities from being added to the `emulated_hue` component.
|
||||
- **allow_hue_groups** (*Optional*): (true/false) Enable this to stop Home Assistant from importing the groups defined on the Hue bridge.
|
||||
|
||||
### {% linkable_title Multiple Hue bridges %}
|
||||
|
||||
If you use multiple Hue bridges then it's needed that you provide a configuration file for every bridge. The bridges can't share a single configuration file.
|
||||
|
||||
Add `filename` to your Hue configuration entry in your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
light:
|
||||
- platform: hue
|
||||
host: BRIDGE1_IP_ADDRESS
|
||||
filename: phue.conf
|
||||
- platform: hue
|
||||
host: BRIDGE2_IP_ADDRESS
|
||||
filename: phue2.conf
|
||||
```
|
||||
|
||||
### {% linkable_title Using Hue Groups in Home Assistant %}
|
||||
|
||||
The Hue API allows you to group lights. Home Assistant also supports grouping of entities natively, but sometimes it can be usefull to use Hue Groups to group light bulbs. By doing so, Home Assistant only needs to send one API call to change the state of all the bulbs in those groups instead of one call for every light in the group. This causes all the bulbs to change state simultaniously.
|
||||
|
|
@ -73,10 +91,11 @@ More information can be found on the [Philips Hue API documentation](https://www
|
|||
|
||||
### {% linkable_title Using Hue Scenes in Home Assistant %}
|
||||
|
||||
The Hue platform has it's own concept of Scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you've never used, almost all very poorly named.
|
||||
The Hue platform has it's own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you've never used, almost all very poorly named.
|
||||
|
||||
To avoid user interface overload we don't expose Scenes directly. Instead there is a [light.hue_activate_scene](/components/light/#service-lighthue_activate_scene) service which can be used by `automation` or `script` components.
|
||||
To avoid user interface overload we don't expose scenes directly. Instead there is a [light.hue_activate_scene](/components/light/#service-lighthue_activate_scene) service which can be used by `automation` or `script` components.
|
||||
This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant.
|
||||
|
||||
For instance:
|
||||
|
||||
```yaml
|
||||
|
|
@ -92,7 +111,7 @@ script:
|
|||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `group_name` | no | The group/room name of the lights. Find this in the Hue official app.
|
||||
| `scene_name` | no | The name of the Scene. Find this in the Hue official app.
|
||||
| `scene_name` | no | The name of the scene. Find this in the Hue official app.
|
||||
|
||||
*Note*: `group_name` is not linked to Home Assistant group name.
|
||||
|
||||
|
|
@ -100,15 +119,14 @@ script:
|
|||
|
||||
How do you find these names?
|
||||
|
||||
The easiest way to do this is only use the scenes from the 2nd generation Hue app. That is organized by Room (Group) and Scene
|
||||
Name. Use the values of Room name and Scene name that you see in the app. You can test these work on the `dev-service` console of your Home Assistant instance.
|
||||
The easiest way to do this is only use the scenes from the 2nd generation Hue app. That is organized by room (group) and scene Name. Use the values of room name and scene name that you see in the app. You can test these work on the `dev-service` console of your Home Assistant instance.
|
||||
|
||||
Alternatively, you can dump all rooms and scene names using this [gist](https://gist.github.com/sdague/5479b632e0fce931951c0636c39a9578). This does **not** tell you which groups and scenes work together but it's sufficient to get values that you can test in the `dev-service` console.
|
||||
|
||||
*** Caveats ***
|
||||
|
||||
The Hue API doesn't activate Scenes directly, only on a Hue Group (typically Rooms, especially if using the 2nd gen app). But Hue Scenes don't actually reference their group. So heuristic matching is used.
|
||||
The Hue API doesn't activate scenes directly, only on a Hue Group (typically rooms, especially if using the 2nd gen app). But Hue Scenes don't actually reference their group. So heuristic matching is used.
|
||||
|
||||
Neither Group names or Scene names are guaranteed unique in Hue. If you are getting non deterministic behavior, adjust your Hue scenes via the App to be more identifying.
|
||||
Neither group names or scene names are guaranteed unique in Hue. If you are getting non deterministic behavior, adjust your Hue scenes via the App to be more identifying.
|
||||
|
||||
The Hue hub has limitted spaces for Scenes, and will delete Scenes if new ones get created that would overflow that space. The API docs say this is based on Least Recently Used.
|
||||
The Hue hub has limitted spaces for scenes, and will delete scenes if new ones get created that would overflow that space. The API docs say this is based on "Least Recently Used".
|
||||
|
|
|
|||
|
|
@ -52,14 +52,15 @@ Determine your bulb ip (using router, software, ping ...)
|
|||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
This component is tested to work with the following models:
|
||||
This component is tested to work with the following models. If you have a different model and it is working please let us know.
|
||||
</p>
|
||||
|
||||
- **YLDP01YL**: LED Bulb (White)
|
||||
- **YLDP02YL**: LED Bulb (Color)
|
||||
- **YLDP03YL**: LED Bulb (Color) - E26
|
||||
- **YLDD02YL**: Lightstrip (Color)
|
||||
|
||||
If you have a different model and it is working please let us know.
|
||||
</p>
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ comments: false
|
|||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: "Other"
|
||||
ha_category: "Utility"
|
||||
---
|
||||
|
||||
The logger component lets you define the level of logging activities in Home Assistant.
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ Supported devices:
|
|||
- Other Denon AVR receivers (untested)
|
||||
- Marantz receivers (experimental)
|
||||
|
||||
<pre class='note'>
|
||||
<pre class='note warning'>
|
||||
If you have something else using the IP controller for your Denon AVR 3808CI, such as your URC controller, it will not work! There is either a bug or security issue with some models where only one device could be controlling the IP functionality.
|
||||
</pre>
|
||||
|
||||
|
|
|
|||
|
|
@ -18,23 +18,24 @@ The `vizio` component will allow you to control [SmartCast](https://www.vizio.co
|
|||
|
||||
## Pairing
|
||||
|
||||
Before adding TV to Home Assistant you'll need to pair it manually, to do so follow these steps:
|
||||
Before adding your TV to Home Assistant you'll need to pair it manually. To do so follow these steps:
|
||||
|
||||
Install the command-line tool using pip (you can choose to download it manually):
|
||||
Install the command-line tool using pip (or you can choose to download it manually):
|
||||
|
||||
```bash
|
||||
$ pip3 install git+https://github.com/vkorn/pyvizio.git@master
|
||||
$ pip3 install -I .
|
||||
```
|
||||
|
||||
Make sure that your TV is on, as sometimes it won't show PIN code if it wasn't on during pairing initialization.
|
||||
Make sure that your TV is on before continuing.
|
||||
|
||||
If you don't know IP address of your TV run following command:
|
||||
|
||||
```bash
|
||||
$ pyvizio --ip=0 --auth=0 discover
|
||||
```
|
||||
|
||||
Initiate pairing:
|
||||
Enter the following command to initiate pairing:
|
||||
|
||||
```bash
|
||||
$ pyvizio --ip={ip} pair
|
||||
|
|
@ -44,20 +45,20 @@ Initiation will show you two different values:
|
|||
|
||||
| Value | Description |
|
||||
|:----------------|:---------------------|
|
||||
| Challenge type | Usually it's should be `"1"`, if it's not the case for you, use additional parameter `--ch_type=your_type` in the next step |
|
||||
| Challenge type | Usually it should be `"1"`. If not, use the additional parameter `--ch_type=your_type` in the next step |
|
||||
| Challenge token | Token required to finalize pairing in the next step |
|
||||
|
||||
Finally, at this point PIN code should be displayed at the top of your TV. With all these values, you can now finish pairing:
|
||||
Finally, at this point a PIN code should be displayed at the top of your TV. With all these values, you can now finish pairing:
|
||||
|
||||
```bash
|
||||
$ pyvizio --ip={ip} pair_finish --token={challenge_token} --pin={tv_pin}
|
||||
```
|
||||
|
||||
You will need authentication token returned by this command to configure Home Assistant.
|
||||
You will need the authentication token returned by this command to configure Home Assistant.
|
||||
|
||||
## Configuration
|
||||
|
||||
To add your Vizio TV to your installation, add following to your `configuration.yaml` file:
|
||||
To add your Vizio TV to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -70,13 +71,13 @@ media_player:
|
|||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): IP address of your TV.
|
||||
- **access_token** (*Required*): Authentication token you've received in last step of the pairing process.
|
||||
- **access_token** (*Required*): Authentication token you received in the last step of the pairing process.
|
||||
|
||||
## Notes and limitations
|
||||
|
||||
### Turning TV on
|
||||
|
||||
If you do have `Power Mode` of your TV configured to be `Eco Mode`, turning device ON won't work.
|
||||
If the `Power Mode` of your TV is set to `Eco Mode`, turning the device ON won't work.
|
||||
|
||||
### Changing tracks
|
||||
|
||||
|
|
@ -87,7 +88,8 @@ Changing tracks works like channels switching. If you have source other than reg
|
|||
Source list shows all external devices connected to the TV through HDMI plus list of internal devices (TV mode, Chrome Cast, etc.).
|
||||
|
||||
<p class='note'>
|
||||
Vizio SmartCast service is accessible through HTTPS with self-signed certificate. It means that if you have low LOGLEVEL in your Home Assistant configuration, you'll see a lot of warnings like this `InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised.`
|
||||
Vizio SmartCast service is accessible through HTTPS with self-signed certificate. If you have low LOGLEVEL in your Home Assistant configuration, you'll see a lot of warnings like this:
|
||||
`InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised.`
|
||||
|
||||
As an option, you could proxy all calls for example through NGINX.
|
||||
You can adjust the log level for `media_player` components with the [logger](https://home-assistant.io/components/logger/) component, or if you need to keep a low log level for `media_player` you could proxy calls to your TV through an NGINX reverse proxy.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -63,6 +63,7 @@ Thanks to the [`proc`](https://en.wikipedia.org/wiki/Procfs) file system, variou
|
|||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: command_line
|
||||
name: CPU Temperature
|
||||
command: "cat /sys/class/thermal/thermal_zone0/temp"
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: page
|
||||
title: "FRITZ!Box"
|
||||
title: "FRITZ!Box Call Monitor"
|
||||
description: "Instructions how to integrate a phone call monitor for AVM FRITZ!Box routers into Home Assistant."
|
||||
date: 2016-08-13 15:00
|
||||
sidebar: true
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: page
|
||||
title: "FRITZ!Box"
|
||||
title: "FRITZ!Box Net Monitor"
|
||||
description: "Instructions how to integrate an AVM FRITZ!Box monitor into Home Assistant."
|
||||
date: 2017-01-17 22:00
|
||||
sidebar: true
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: page
|
||||
title: "London Undergound"
|
||||
title: "London Underground"
|
||||
description: "Display the current status of London underground & overground lines within Home Assistant."
|
||||
date: 2017-07-15 18:45
|
||||
sidebar: true
|
||||
|
|
|
|||
|
|
@ -13,6 +13,8 @@ ha_release: 0.39
|
|||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `pocketcasts` sensor platform let one monitor the podcasts at [Pocket Casts](https://play.pocketcasts.com/).
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
|
|
@ -23,7 +25,7 @@ sensor:
|
|||
password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
Configuration options for the PocketCasts Sensor:
|
||||
Configuration variables:
|
||||
|
||||
- **username** (*Required*): The username to access the PocketCasts service.
|
||||
- **password** (*Required*): The password for the given username.
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ sensor:
|
|||
unit_of_measurement: MB
|
||||
```
|
||||
|
||||
### {% linkable_title Value for other Home Assistant instance %}
|
||||
### {% linkable_title Value from another Home Assistant instance %}
|
||||
|
||||
The Home Assistant [API](/developers/rest_api/) exposes the data from your attached sensors. If you are running multiple Home Assistant instances which are not [connected](/developers/architecture/#multiple-connected-instances) you can still get information from them.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
|
|||
---
|
||||
|
||||
|
||||
The `scrape` sensor platform is scraping information from websites. The sensor loads a HTML page and gives you the option to search and split out a value. As this is not a full-blown web scraper like [scrapy](https://scrapy.org/). It will most likely only work with simple webpages and it can be time-consuming to get the right section.
|
||||
The `scrape` sensor platform is scraping information from websites. The sensor loads a HTML page and gives you the option to search and split out a value. As this is not a full-blown web scraper like [scrapy](https://scrapy.org/), it will most likely only work with simple webpages and it can be time-consuming to get the right section.
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
|
|
|
|||
|
|
@ -15,6 +15,20 @@ ha_iot_class: "Local Polling"
|
|||
|
||||
The `supervisord` platform allows you to track the states of [Supervisord](http://supervisord.org/).
|
||||
|
||||
It required that you enable the HTTP feature in the `/etc/supervisord.conf` configuration file.
|
||||
|
||||
```text
|
||||
[inet_http_server]
|
||||
port=127.0.0.1:9001
|
||||
```
|
||||
|
||||
After a restart of `supervisord` you should be able to access the web interface. If needed then this could be added as a [iFrame panel](/components/panel_iframe/).
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/supervisor.png' />
|
||||
</p>
|
||||
|
||||
|
||||
To use this sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -8,9 +8,9 @@ comments: false
|
|||
sharing: true
|
||||
footer: true
|
||||
logo: synology.png
|
||||
ha_category: Sensor
|
||||
ha_category: System Monitor
|
||||
ha_release: 0.32
|
||||
ha_iot_class: depends
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
|
@ -31,14 +31,6 @@ sensor:
|
|||
- network_up
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
After booting Home Assistant it can take up to 15 minutes for the sensors to show up. This is due to the fact that sensors are created after Home Assistant has fully been initialized.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
This sensor will wake up your Synology NAS if it's in hibernation mode.
|
||||
</p>
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The IP address of the Synology NAS to monitor
|
||||
|
|
@ -79,7 +71,15 @@ Configuration variables:
|
|||
- **volume_disk_temp_avg**: Displays the average temperature of all disks in the volume (creates a new entry for each volume).
|
||||
- **volume_disk_temp_max**: Displays the maximum temperature of all disks in the volume (creates a new entry for each volume).
|
||||
|
||||
Separate User Configuration:
|
||||
<p class='note'>
|
||||
After booting Home Assistant it can take up to 15 minutes for the sensors to show up. This is due to the fact that sensors are created after Home Assistant has fully been initialized.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
This sensor will wake up your Synology NAS if it's in hibernation mode.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Separate User Configuration %}
|
||||
|
||||
Due to the nature of the Synology DSM API it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.
|
||||
|
||||
|
|
|
|||
|
|
@ -55,14 +55,14 @@ You will notice that the output from the service is not just a single value (it
|
|||
```yaml
|
||||
sensor:
|
||||
# Example configuration.yaml entry
|
||||
platform: tcp
|
||||
name: Central Heating Pressure
|
||||
host: 10.0.0.127
|
||||
port: 8888
|
||||
timeout: 5
|
||||
payload: "r WaterPressure\n"
|
||||
value_template: "{% raw %}{{ value.split(';')[0] }}{% endraw %}"
|
||||
unit_of_measurement: Bar
|
||||
- platform: tcp
|
||||
name: Central Heating Pressure
|
||||
host: 10.0.0.127
|
||||
port: 8888
|
||||
timeout: 5
|
||||
payload: "r WaterPressure\n"
|
||||
value_template: "{% raw %}{{ value.split(';')[0] }}{% endraw %}"
|
||||
unit_of_measurement: Bar
|
||||
```
|
||||
|
||||
### {% linkable_title hddtemp %}
|
||||
|
|
@ -89,12 +89,12 @@ The entry for the `configuration.yaml` file for a `hddtemp` sensor could look li
|
|||
```yaml
|
||||
sensor:
|
||||
# Example configuration.yaml entry
|
||||
platform: tcp
|
||||
name: HDD temperature
|
||||
host: 127.0.0.1
|
||||
port: 7634
|
||||
timeout: 5
|
||||
payload: "\n"
|
||||
value_template: "{% raw %}{{ value.split('|')[3] }}{% endraw %}"
|
||||
unit_of_measurement: "°C"
|
||||
- platform: tcp
|
||||
name: HDD temperature
|
||||
host: 127.0.0.1
|
||||
port: 7634
|
||||
timeout: 5
|
||||
payload: "\n"
|
||||
value_template: "{% raw %}{{ value.split('|')[3] }}{% endraw %}"
|
||||
unit_of_measurement: "°C"
|
||||
```
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ stop you're interested in
|
|||
3. Tick the 'map data' layer, and wait for clickable objects to load
|
||||
4. Click the bus stop node to reveal its tags on the left
|
||||
|
||||
The `destination` must be a valid location returned by the transportAPI query. Valid destinations can be checked by performing a GET query to `/uk/bus/stop/{atcocode}/live.json` in the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml##bus_information). A bus sensor is added in the following `configuration.yaml` file entry:
|
||||
The `destination` must be a valid location in the "direction" field returned by a GET query to `/uk/bus/stop/{atcocode}/live.json` as described in the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml##bus_information). A bus sensor is added in the following `configuration.yaml` file entry:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for multiple sensors
|
||||
|
|
|
|||
|
|
@ -27,10 +27,7 @@ sensor:
|
|||
key: XXXXXXXXXXXXXXXXXXX
|
||||
secret: YYYYYYYYYYYYYYYYY
|
||||
departures:
|
||||
- name: Mot järntorget
|
||||
from: Musikvägen
|
||||
heading: Järntorget
|
||||
delay: 10
|
||||
- from: Musikvägen
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
|
@ -41,6 +38,21 @@ Configuration variables:
|
|||
- **name** (*Optional*): Name of the route.
|
||||
- **from** (*Required*): The start station.
|
||||
- **heading** (*Optional*): Direction of the travelling.
|
||||
- **delay** (*Optional*): Delay in minutes.
|
||||
- **delay** (*Optional*): Delay in minutes. Defaults to 0.
|
||||
|
||||
The data are coming from [Västtrafik](https://vasttrafik.se/).
|
||||
|
||||
A full configuration example could look like this:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: vasttrafik
|
||||
key: XXXXXXXXXXXXXXXXXXX
|
||||
secret: YYYYYYYYYYYYYYYYY
|
||||
departures:
|
||||
- name: Mot järntorget
|
||||
from: Musikvägen
|
||||
heading: Järntorget
|
||||
delay: 10
|
||||
```
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ in the `_1h_` part of the sensor name with `1` to `36`. E.g. `weather_24h` will
|
|||
```yaml
|
||||
sensor:
|
||||
- platform: wunderground
|
||||
- api_key: your_api_key
|
||||
api_key: your_api_key
|
||||
monitored_conditions:
|
||||
- weather_1d_metric
|
||||
- weather_1n_metric
|
||||
|
|
|
|||
|
|
@ -104,11 +104,12 @@ In Home Assistant, we trigger actions based on intents produced by Snips using t
|
|||
|
||||
```yaml
|
||||
snips:
|
||||
intents:
|
||||
ActivateLightColor:
|
||||
action:
|
||||
- service: light.turn_on
|
||||
data_template:
|
||||
entity_id: light.{% raw %}{{ objectLocation | replace(" ","_") }}{% endraw %}
|
||||
color_name: {% raw %}{{ objectColor }}{% endraw %}
|
||||
|
||||
intent_script:
|
||||
ActivateLightColor:
|
||||
action:
|
||||
- service: light.turn_on
|
||||
data_template:
|
||||
entity_id: light.{% raw %}{{ objectLocation | replace(" ","_") }}{% endraw %}
|
||||
color_name: {% raw %}{{ objectColor }}{% endraw %}
|
||||
```
|
||||
|
|
|
|||
|
|
@ -18,6 +18,10 @@ The `tradfri` component supports for the IKEA Trådfri (Tradfri) gateway. The ga
|
|||
|
||||
For this to work, you need to install a modified lib-coap library.
|
||||
|
||||
<p class='note'>
|
||||
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
|
||||
</p>
|
||||
|
||||
Linux:
|
||||
|
||||
```bash
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ comments: false
|
|||
sharing: true
|
||||
footer: true
|
||||
logo: ethernet.png
|
||||
ha_category: Hub
|
||||
ha_category: Utility
|
||||
ha_release: "0.49"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ xiaomi:
|
|||
```
|
||||
|
||||
|
||||
Multiple Gateway
|
||||
Multiple Gateways
|
||||
|
||||
```yaml
|
||||
# 12 characters mac can be obtained from the gateway.
|
||||
|
|
@ -73,12 +73,26 @@ xiaomi:
|
|||
key: xxxxxxxxxxxxxxxx
|
||||
```
|
||||
|
||||
|
||||
|
||||
Search for gateways on specific interface
|
||||
|
||||
```yaml
|
||||
# 12 characters mac can be obtained from the gateway.
|
||||
xiaomi:
|
||||
interface: '192.168.0.1'
|
||||
gateways:
|
||||
- mac: xxxxxxxxxxxx
|
||||
key: xxxxxxxxxxxxxxxx
|
||||
```
|
||||
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **mac** (*Optional*): The MAC of your gateway. Required if you have more than one.
|
||||
- **key** (*Optional*): The key of your gateway. Required if you also want to control lights and switches; sensors and binary sensors will still work.
|
||||
- **discovery_retry** (*Optional*): Amount of times Home Assitant should try to reconnect to the Xiaomi Gateway. Default is 3.
|
||||
- **interface** (*Optional*): Which network interface to use. Default to any.
|
||||
- **interface** (*Optional*): Which network interface to use. Defaults to any.
|
||||
|
||||
## {% linkable_title Services %}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue