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

Merge branch 'current' into next

Browse source
This commit is contained in:
Fabian Affolter 2017-06-30 19:13:55 +02:00
commit 4ba3e3e0c6
No known key found for this signature in database
GPG key ID: DDF3D6F44AAB1336
33 changed files with 344 additions and 150 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/_components/axis.markdown
View file

@ -23,7 +23,7 @@ Home Assistant will automatically discover their presence on your network.
$ sudo apt-get install python3-gi gir1.2-gstreamer-1.0
```
Depending on how you run Home Assistant you might be needed to symlink the `gi` module into your environment.
Depending on how you run Home Assistant, you may need to symlink the `gi` module into your environment.
Hassbian:

1
source/_components/binary_sensor.command_line.markdown
View file

@ -33,6 +33,7 @@ Configuration variables:
- **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
- **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
## {% linkable_title Examples %}

6
source/_components/blink.markdown
View file

@ -36,9 +36,9 @@ Once loaded, your front end will have the following components:
* A camera image for each camera in your system.
* A binary_sensor per camera that indicates whether motion detection is enabled.
* A binary_sensor for the system that indicates if the system is armed or disarmed.
* A sesnor per camera that reports temperature.
* A sensor per camera that reports temperature.
* A sensor per camera that reports battery level.
* A sensor per camera that reports unread notification (ie. detected motion events).
* A sensor per camera that reports unread notification (i.e., detected motion events).
Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. This image can be updated with the `snap_picture` service to force Home Assistant to request an update from Blink's servers. As a note, all of the camera-specific sensors are only polled when a new image is requested from the camera. This means that relying on any of these sensors to provide timely and accurate data is not recommended.
@ -59,7 +59,7 @@ For `arm_system`, the value sent can be either `True` or `False` and will arm an
}
```
Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named "Living Room" and you want to turn off motion detection on that camera, you would call the `arm_camera` service with the following payload:
Arm camera follows a similar structure, but each individual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named "Living Room" and you want to turn off motion detection on that camera, you would call the `arm_camera` service with the following payload:
```json
{

2
source/_components/climate.maxcube.markdown
View file

@ -1,6 +1,6 @@
---
layout: page
title: "eQ-3 MAX! Cube binary sensors"
title: "eQ-3 MAX! Cube thermostat"
description: "Instructions on how to integrate eQ-3 MAX! components with Home Assistant via eQ-3 MAX! Cube."
date: 2017-02-04 22:00
sidebar: true

23
source/_components/device_tracker.snmp.markdown
View file

@ -16,20 +16,23 @@ ha_release: 0.7.5
A lot WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of insances and metrics, like network interfaces, disks, and wifi registrations.
<p class='note warning'>
This device tracker needs SNMP to be enabled on the router.
This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually.
</p>
OID examples:
- Mikrotik: `1.3.6.1.4.1.14988.1.1.1.2.1.1` (confirmed, unknown RouterOS version/model)
- Mikrotik: `1.3.6.1.2.1.4.22.1.2` (confirmed, RouterOS 6.x on RB2011)
- Aruba: `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2` (untested)
- BiPAC 7800DXL: `1.3.6.1.2.1.17.7.1.2.2.1.1` (confirmed on firmware 2.32e)
- OpenWrt: `1.3.6.1.2.1.4.22.1.2` (tested on Chaos Calmer 15.05 firmware, need to install snmpd package)
- pfSense: `1.3.6.1.2.1.4.22.1.2` (tested on 2.2.4-RELEASE, need to enable SNMP service)
- TPLink: `1.3.6.1.2.1.3.1.1.2.19.1` (Archer VR2600v, need to enable SNMP service)
- EdgeRouter `1.3.6.1.2.1.4.22.1.2` (EdgeRouter Lite v1.9.0, need to enable SNMP service)
- Ruckus: `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` (Ruckus ZoneDirector, tested on 9.13.3)
| Brand | Device/Firmware | OID |
|---|---|---|---|
| Mikrotik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` |
| Mikrotik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` |
| Aruba | (untested) | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2` |
| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` |
| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` |
| OpenWrt | Chaos Calmer 15.05 | `1.3.6.1.2.1.4.22.1.2` |
| TP-Link | Archer VR2600v | `1.3.6.1.2.1.3.1.1.2.19.1` |
| TP-Link | Archer VR600 | `1.3.6.1.2.1.3.1.1.2` |
| EdgeRouter | Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` |
| Ruckus | ZoneDirector 9.13.3 | `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` |
To use the SNMP version 1 platform in your installation, add the following to your `configuration.yaml` file:

4
source/_components/input_select.markdown
View file

@ -43,6 +43,10 @@ Configuration variables:
Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
<p class='note'>
Because YAML defines [booleans](http://yaml.org/type/bool.html) as equivalent, any variations of 'On', 'Yes', 'Y', 'Off', 'No', or 'N' (regardless of case) used as option names will be replaced by True and False unless they are defined in quotation marks.
</p>
### {% linkable_title Services %}
This components provide three services to modify the state of the `input_select`:

5
source/_components/sensor.buienradar.markdown
View file

@ -33,8 +33,9 @@ sensor:
Configuration variables:
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **name** (*Optional*): You can specify a name of the component, but do not have to. If you specify a name, the sensors will get an entity name of 'sensor.[name]`[monitored_condition]`, for example: `sensor.lopik_temperature`; if no name is specified the sensors will be called `sensor.br_[monitored_condition]`, for example `sensor.br_temperature`.
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl.
- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl.
- **timeframe** (*Optional*): Minutes to look ahead for precipitation (5..120) [default: 60].
- **monitored_conditions** array (*Required*): One or more conditions to display in the frontend.
- **stationname**: The name of the selected meteo-station.

4
source/_components/sensor.command_line.markdown
View file

@ -31,7 +31,7 @@ Configuration variables:
- **name** (*Optional*): Name of the command sensor.
- **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any.
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
- **scan_interval** (*Optional*): Defines number of seconds for polling interval.
- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
## {% linkable_title Examples %}
@ -104,7 +104,7 @@ sensor:
### {% linkable_title Read value out of a remote text file %}
If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value.
If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value.
```yaml
sensor:

9
source/_components/sensor.netatmo.markdown
View file

@ -52,10 +52,10 @@ Configuration variables:
- **rain**: Estimated rainfall for today in mm.
- **sum_rain_1**: Rainfall in the last hour in mm.
- **sum_rain_24**: Rainfall in mm from 00:00am - 23:59pm.
- **WindAngle**: Wind angle
- **WindStrength**: Wind strength
- **GustAngle**: Wind gust angle
- **GustStrength**: Wind gust strength
- **windangle**: Wind angle
- **windstrength**: Wind strength
- **gustangle**: Wind gust angle
- **guststrength**: Wind gust strength
- **min_temp**: Min temperature for today
- **max_temp**: Max temperature for today
- **rf_status**: Current radio status per module. (90=low, 60=highest)
@ -69,4 +69,3 @@ You can find your modules name in your [online NetAtmo account](https://my.netat
<p class='img'>
<img src='/images/screenshots/netatmo_module.png' />
</p>

5
source/_components/weather.buienradar.markdown
View file

@ -26,8 +26,9 @@ weather:
Configuration variables:
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **longitude**(*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **name** (*Optional*): You can specify a name of the component, but do not have to. If you specify a name, the weather component will get an entity name of 'weather.[name]'; if no name is specified, it will try to set its name to 'weather.BR_[stationname]'. However at the moment in time the entity is created, no data has been retrieved yet, so the entity will get named 'weather.BR_unknown_station'. Later the station name will be known and get updated, but the entity name remains.
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **longitude**(*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **forecast** (*Optional*): 'True' to add a temperature forecast, 'False' to suppress it.