Merge branch 'master' into next
Conflicts: source/_components/camera.netatmo.markdown source/_components/rollershutter.wink.markdown source/_components/sensor.netatmo.markdown source/_components/sensor.snmp.markdown source/_posts/2016-06-18-pandora-bt-home-hub-5-and-local-file-camera.markdown source/index.html
This commit is contained in:
Paulus Schoutsen
commit
d8de600fe3
51 changed files with 574 additions and 105 deletions
|
|
@ -240,7 +240,7 @@ Custom slot type for script support.
|
|||
Add a sample utterance:
|
||||
|
||||
```text
|
||||
RunScriptIntent run {Scene}
|
||||
RunScriptIntent run {Script}
|
||||
```
|
||||
|
||||
Then add the intent to your Alexa Section in your HA config file:
|
||||
|
|
|
|||
|
|
@ -10,12 +10,13 @@ footer: true
|
|||
logo: enocean.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.21
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55. Other devices will most likely not work without changing the Home-Asisstant code.
|
||||
|
||||
|
||||
To use your EnOcean device, you first have to set up your [EnOcean hub](../enocean) and then add the following to your `configuration.yaml` file:
|
||||
To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
|
|||
|
|
@ -8,12 +8,24 @@ comments: false
|
|||
sharing: true
|
||||
footer: true
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
|
||||
The `rest` binary sensor platform is consuming a given endpoint which is exposed by a [RESTful API](https://en.wikipedia.org/wiki/Representational_state_transfer) of a device, an application, or a web service. The binary sensor has support for GET and POST requests.
|
||||
|
||||
The JSON messages can contain different values like `1`, `"1"`, `TRUE`, `true`, `on`, or `open`. If the value is nested then use a [template](/topics/templating/).
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "Binary sensor",
|
||||
"state": {
|
||||
"open": "true",
|
||||
"timestamp": "2016-06-20 15:42:52.926733"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file for a GET request:
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: netatmo.png
|
||||
ha_category: Camera
|
||||
ha_release: "0.2x"
|
||||
ha_release: "0.22"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ ha_category: "Voice"
|
|||
---
|
||||
|
||||
|
||||
The conversation component can process sentences into commands for Home Assistant. It is currently limited to parsing commands in the format `turn <Friendly Name> <on/off>`.
|
||||
The conversation component can process sentences into commands for Home Assistant. It is currently limited to parsing commands in the format `turn <Friendly Name> <on/off>`.
|
||||
|
||||
|
||||
To enable the conversion option in your installation, add the following to your `configuration.yaml` file:
|
||||
|
|
@ -22,12 +22,12 @@ To enable the conversion option in your installation, add the following to your
|
|||
conversation:
|
||||
```
|
||||
|
||||
When this component is active and you are using a supported browser voice commands will be activated in the frontend. Browse to [the demo](/demo/) using Chrome to see it in action.
|
||||
When this component is active and you are using a supported browser voice commands will be activated in the frontend. Browse to [the demo](/demo/) using Chrome or Chromium to see it in action.
|
||||
|
||||
<p class='img'>
|
||||
<img src="/images/screenshots/voice-commands.png" />
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
Apple iPhones do not support this feature in any browser.
|
||||
Apple iPhones do not support this feature in any browser.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: avm.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: icloud.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -36,13 +36,13 @@ device_tracker:
|
|||
|
||||
Once tracked, a file will be created in your config dir called `known_devices.yaml`. Edit this file to adjust which devices to be tracked. Here you can also setup a URL for each device to be used as the entity picture and set whether the device will be show in the UI when in the away state.
|
||||
|
||||
Multiple device trackers can be used in parallel, such as [Owntracks](/components/device_tracker.owntracks/) and [Nmap](/components/device_tracker.nmap_scanner/). The state of the device will be determined by the source that reported last. Device tracker will look for global settings (track_new_devices, consider_home and home_interval) under the configuration of the first platform.
|
||||
Multiple device trackers can be used in parallel, such as [Owntracks](/components/device_tracker.owntracks/) and [Nmap](/components/device_tracker.nmap_scanner/). The state of the device will be determined by the source that reported last. Device tracker will look for global settings (`track_new_devices`, `consider_home`, and `home_interval`) under the configuration of the first platform.
|
||||
|
||||
The optional `consider_home` entry is useful for households with Apple iOS devices that go into sleep mode while still at home to conserve battery life. iPhones will occasionally drop off the network and then re-appear. `consider_home` helps prevent false alarms in presence detection when using IP scanners such as nmap.
|
||||
|
||||
To add Nmap tracking just add the MAC address to the OwnTracks or iCloud device `mac:` configuration. To use both OwnTracks and Nmap you could use the following example:
|
||||
|
||||
```
|
||||
```yaml
|
||||
owntracksdevicename:
|
||||
name: Friendly Name!
|
||||
mac: EA:AA:55:E7:C6:94
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ featured: true
|
|||
|
||||
As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (`192.168.1.1/24`) and the range notation (`192.168.1.1-255`).
|
||||
|
||||
If you're on Debian or Ubuntu, you might have to install the packages for arp and nmap. Do so by running `apt-get install net-tools nmap`.
|
||||
If you're on Debian or Ubuntu, you might have to install the packages for `arp` and `nmap`. Do so by running `apt-get install net-tools nmap`. On a Fedora host run `sudo dnf -y install nmap`.
|
||||
|
||||
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ footer: true
|
|||
logo: mqtt.png
|
||||
ha_category: Garage Door
|
||||
ha_release: 0.18
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Configuration variables:
|
|||
|
||||
- **[alias]** (*Required*): Alias for the input.
|
||||
- **name** (*Optional*): Friendly name of the input.
|
||||
- **options** array (*Optional*): List of options to choose from
|
||||
- **options** array: List of options to choose from
|
||||
- **initial** (*Optional*): Initial value when Home Assistant starts.
|
||||
- **icon** (*Optional*): Icon for entry.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ footer: true
|
|||
logo: mqtt.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.15
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `mqtt` lock platform let you control your MQTT enabled locks.
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@ logo: mqtt.png
|
|||
ha_category: Hub
|
||||
featured: true
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ featured: true
|
|||
The Nest component is the main component to integrate all Nest related platforms. Besides this component you will have to setup your thermostat and any connected sensors separately.
|
||||
|
||||
```yaml
|
||||
# Example configurayion.yaml entry
|
||||
# Example configuration.yaml entry
|
||||
nest:
|
||||
username: USERNAME
|
||||
password: PASSWORD
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ footer: true
|
|||
logo: mqtt.png
|
||||
ha_category: Rollershutter
|
||||
ha_release: 0.9
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ ha_category: Rollershutter
|
|||
ha_release: 0.22
|
||||
---
|
||||
|
||||
The Wink rollershutter platform allows you to control your [Wink](http://www.wink.com/) enabled rollershutters. It supports Wink shades / blinds / rollershutters such as the Bali Somfy or Lutron Serena blinds.
|
||||
The `wink` rollershutter platform allows you to control your [Wink](http://www.wink.com/) enabled rollershutters. It supports Wink shades/blinds/rollershutters such as the Bali Somfy or Lutron Serena blinds.
|
||||
|
||||
The Wink API currently doesn't provide status for shades.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: command_line.png
|
||||
ha_category: Sensor
|
||||
ha_release: pre 0.7
|
||||
---
|
||||
|
||||
|
||||
|
|
@ -82,6 +83,16 @@ You can see directly in the frontend (**Developer tools** -> **About**) what rel
|
|||
name: HA release
|
||||
```
|
||||
|
||||
### {% 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.
|
||||
|
||||
```yaml
|
||||
- platform: command_line
|
||||
command: python3 -c "import requests; print(requests.get('http://remote-host/sensor_data.txt').text)"
|
||||
name: File value
|
||||
```
|
||||
|
||||
### {% linkable_title Use an external script %}
|
||||
|
||||
The example is doing the same as the [aREST sensor](/components/sensor.arest/) but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: dweet.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
The `dweet` sensor platform allows you to get details from your devices which are publishing their values to [Dweet.io](https://dweet.io/).
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: eliq.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ footer: true
|
|||
logo: mqtt.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.7
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
layout: page
|
||||
title: "Netatmo Sensor"
|
||||
description: "Instructions how to integrate Netatmo sensors into Home Assistant."
|
||||
date: 2016-06-02 08:10
|
||||
date: 2016-06-23 11:10
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
|
|
@ -31,12 +31,24 @@ sensor:
|
|||
- rain
|
||||
- sum_rain_1
|
||||
- sum_rain_24
|
||||
- wifi_status
|
||||
module_name2:
|
||||
- temperature
|
||||
- battery_vp
|
||||
- min_temp
|
||||
- max_temp
|
||||
rainmeter_name3:
|
||||
- rain
|
||||
- sum_rain_1
|
||||
- sum_rain_24
|
||||
- battery_vp
|
||||
- rf_status
|
||||
windmodule_name4:
|
||||
- WindAngle
|
||||
- WindStrength
|
||||
- GustAngle
|
||||
- GustStrength
|
||||
- rf_status
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
|
@ -52,6 +64,15 @@ 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
|
||||
- **WingStrength**: 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)
|
||||
- **wifi_status**: Wifi status per Base station
|
||||
- **battery_vp**: Current battery status per module.
|
||||
|
||||
### {% linkable_title Find your modules name %}
|
||||
|
||||
|
|
@ -62,6 +83,3 @@ You have to provide these name in your Home Assistant configuration file.
|
|||
<img src='/images/screenshots/netatmo_module.png' />
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
The Home Assistant NetAtmo platform has only be tested with the classic indoor, outdoor module and rainmeter. There is no support for the windmeter module at this time because developers does not own these modules.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -8,9 +8,9 @@ comments: false
|
|||
sharing: true
|
||||
footer: true
|
||||
logo: network-snmp.png
|
||||
ha_category: Sensor
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: "0.21"
|
||||
ha_release: "0.22"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: torque.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a bluetooth OBD2 stick via the Torque mobile application.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: twitch.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ footer: true
|
|||
logo: mqtt.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.7
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `mqtt` switch platform let you control your MQTT enabled light.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ sharing: true
|
|||
footer: true
|
||||
logo: heatmiser.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.10
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue