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:
Paulus Schoutsen 2017-03-11 15:00:11 -08:00
commit 8f86e331e2
18 changed files with 362 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

17
source/_components/android_ip_webcam.markdown
View file

@ -9,19 +9,25 @@ sharing: true
footer: true
logo: android_ip_webcam.png
ha_category: Hub
ha_release: 0.40
ha_release: "0.40"
---
The [Android IP webcam](https://play.google.com/store/apps/details?id=com.pas.webcam) turns your andorid phone into a network camera with multiple viewing options.
The Android IP webcam component turns your Android phone into a network camera with multiple viewing options.
It's setup as a mjpeg camera and all settings as switches inside of Home Assistant. You can also expose the sensors. If you have multiple phones, you can use all options inside a list.
To set it up, add the following information to your `configuration.yaml` file:
To set it up, download [the IP Webcam app][app] and add the following information to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
android_ip_webcam:
<<<<<<< HEAD
- host: 192.168.1.10
=======
# This should be the ip of your phone
- host: 192.168.1.10
name: Entrance
>>>>>>> current
```
Configuration variables:
@ -60,3 +66,8 @@ Settings:
- torch
- whitebalance_lock
- video_recording
<<<<<<< HEAD
=======
[app]: https://play.google.com/store/apps/details?id=com.pas.webcam
>>>>>>> current

2
source/_components/binary_sensor.android_ip_webcam.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: android_ip_webcam.png
ha_category: Binary Sensor
ha_release: 0.40
ha_release: "0.40"
---

16
source/_components/device_tracker.bluetooth_le_tracker.markdown
View file

@ -14,15 +14,15 @@ ha_release: 0.27
---
This tracker discovers new devices on boot and in regular intervals and tracks bluetooth low-energy devices periodically based on interval_seconds value. It is not required to pair the devices with each other!
Devices discovered are stored with 'BLE_' as the prefix for device mac addresses in `known_devices.yaml`.
<p class='note'>
Requires PyBluez. If you are on Raspbian, run the following command to install the needed dependencies. `sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev libboost-thread-dev libglib2.0-dev python-dev`
</p>
This platform requires pybluez to be installed. On Debian based installs, run `sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev libboost-thread-dev libglib2.0-dev python-dev`
<p class='note warning'>
Requires gattlib, which is not compatible with Windows. This tracker won't work on Windows!
</p>
Before you get started with this platform, please note that:
- This platform is incompatible with Windows
- This platform requires root privileges
- Don't use on a Raspberry Pi. It will become unusable slow when using this platform.
To use the Bluetooth tracker in your installation, add the following to your `configuration.yaml` file:
@ -39,10 +39,6 @@ Configuration variables:
As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times.
Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won't see this device.
<p class='note warning'>
BT LE tracking requires root privileges.
</p>
For running Home Assistant as non root user we can give python3 the missing capabilities to access the bluetooth stack. Quite like setting the setuid bit (see [Stack Exchange](http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root) for more information).
```bash

2
source/_components/maxcube.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: maxcube.png
ha_category: DIY
ha_release: 0.40
ha_release: "0.40"
ha_iot_class: "Local Polling"
---

2
source/_components/media_player.frontier_silicon.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
ha_category: Media Player
ha_iot_class: "Local Push"
ha_release: 0.40
ha_release: "0.40"
---
This component provides support for Internet Radios based on the [Frontier Silicon chipset]. Some of the manufacturers which offer products based on these chips include: Hama, Medion, Slivercrest, Auna, Technisat, Revo, Pinnel, etc. These devices will be usually controlled by the [UNDOK] app.

2
source/_components/notify.ciscospark.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: ciscospark.png
ha_category: Notifications
ha_release: 0.40
ha_release: "0.40"
---
The `Cisco Spark` platform allows you to deliver notifications from Home Assistant to [Cisco Spark](https://ciscospark.com/).

8
source/_components/recorder.markdown
View file

@ -32,8 +32,8 @@ Configuration variables:
- **entities** (*Optional*): The list of entity ids to be excluded from recordings.
- **domains** (*Optional*): The list of domains to be excluded from recordings.
- **include** (*Optional*): Configure which components should be included in recordings. If set, all other entities will not be recorded.
- **entities** (*Optional*): The list of entity ids to be included from the history.
- **domains** (*Optional*): The list of domains to be included from the history.
- **entities** (*Optional*): The list of entity ids to be included from recordings.
- **domains** (*Optional*): The list of domains to be included from recordings.
- **db_url** (*Optional*): The URL which point to your database.
@ -59,7 +59,7 @@ Define domains and entities to record by using the `include` configuration (aka.
```yaml
# Example configuration.yaml entry with include
history:
recorder:
include:
domains:
- sensor
@ -71,7 +71,7 @@ Use the `include` list to define the domains/entities to record, and exclude som
```yaml
# Example configuration.yaml entry with include and exclude
history:
recorder:
include:
domains:
- sensor

2
source/_components/sensor.android_ip_webcam.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: android_ip_webcam.png
ha_category: Sensor
ha_release: 0.40
ha_release: "0.40"
---

2
source/_components/sensor.comed_hourly_pricing.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: comed.jpg
ha_category: Energy
ha_release: 0.40
ha_release: "0.40"
ha_iot_class: "Cloud Polling"
---

8
source/_components/sensor.modem_callerid.markdown
View file

@ -7,12 +7,10 @@ sidebar: true
comments: false
sharing: true
footer: true
logo: home-assistant.png
ha_category: Sensor
ha_release: 0.40
ha_release: "0.40"
---
The `modem_callerid` sensor platform uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1).
To enable the sensor, add the following lines to your `configuration.yaml`:
@ -43,7 +41,7 @@ When the sensor detects a new call, it's state changes to 'ring' for each ring a
Some example automations:
```yaml
automation:
{% raw %}automation:
- alias: Notify CallerID
trigger:
platform: state
@ -71,6 +69,6 @@ automation:
action:
service: tts.google_say
data_template:
message: 'Call from {{ states.sensor.modem_callerid.attributes.cid_name }} '
message: 'Call from {{ states.sensor.modem_callerid.attributes.cid_name }} '{% endraw %}
```

2
source/_components/sensor.ring.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: ring.png
ha_category: Sensor
ha_release: 0.40
ha_release: "0.40"
---
The `ring` sensor allows you to integrate your [Ring.com](https://ring.com/) devices in Home Assistant.

2
source/_components/switch.android_ip_webcam.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: android_ip_webcam.png
ha_category: Switch
ha_release: 0.40
ha_release: "0.40"
---