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-05-06 14:15:17 -07:00
commit 4039de28dd
33 changed files with 885 additions and 179 deletions
Download patch file Download diff file Expand all files Collapse all files

16
source/_components/binary_sensor.maxcube.markdown Normal file
View file

@ -0,0 +1,16 @@
---
layout: page
title: "eQ-3 MAX! Cube binary sensors"
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
comments: false
sharing: true
footer: true
logo: maxcube.png
ha_category: Climate
ha_release: "0.40"
ha_iot_class: "Local Polling"
---
See instructions at the [main component](/components/maxcube/).

16
source/_components/climate.maxcube.markdown Normal file
View file

@ -0,0 +1,16 @@
---
layout: page
title: "eQ-3 MAX! Cube binary sensors"
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
comments: false
sharing: true
footer: true
logo: maxcube.png
ha_category: Climate
ha_release: "0.40"
ha_iot_class: "Local Polling"
---
See instructions at the [main component](/components/maxcube/).

2
source/_components/image_processing.opencv.markdown
View file

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
logo: OpenCV_Logo.png
logo: opencv.png
ha_category: Image Processing
featured: false
ha_release: 0.44

6
source/_components/light.limitlessled.markdown
View file

@ -47,8 +47,8 @@ Configuration variables:
- **bridges** array (*Required*):
- **host** (*Required*): IP address of the device, eg. `192.168.1.32`
- **version** (*Optional*): Bridge version (default is `6`). Don't use if you aren't sure.
- **port** (*Optional*): Bridge port. Defaults to 5987.
- **version** (*Optional*): Bridge version (default is `6`).
- **port** (*Optional*): Bridge port. Defaults to 5987. For older bridges than v6 choose `8899`.
- **groups** array (*Required*): The list of available groups.
- **number** (*Required*): Group number (`1`-`4`). Corresponds to the group number on the remote. These numbers may overlap only if the type is different.
- **name** (*Required*): Any name you'd like. Must be unique among all configured groups.
@ -58,7 +58,7 @@ Configuration variables:
Refer to the [light]({{site_root}}/components/light/) documentation for general property usage, but keep in mind the following notes specific to LimitlessLED.
- **RGBWW**
- **RGBWW** (Only supported on v6 bridges)
- *Color*: There are 25,856 color possibilities along the LimitlessLED color spectrum. For colors, hue and saturation can be used, but not lightness. If you select a color with lightness, Home Assistant will calculate the nearest valid LimitlessLED color. In white mode the temperature can be set.
- *Temperature*: There are 101 temperature steps.
- *Brightness*: There are 101 brightness steps.

1
source/_components/media_player.samsungtv.markdown
View file

@ -57,6 +57,7 @@ Currently known supported models:
Currently tested but not working models:
- J5200 - Unable to see state and unable to control
- JU7000 - Unable to see state and unable to control (but port 8001 *is* open)
- JU7500 - Unable to see state and unable to control
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.samsungtv.markdown).

2
source/_components/opencv.markdown
View file

@ -7,7 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
logo: OpenCV_Logo.png
logo: opencv.png
ha_category: Hub
ha_release: 0.44
ha_iot_class: "Local Push"

54
source/_components/plant.markdown Normal file
View file

@ -0,0 +1,54 @@
---
layout: page
title: "Plant Observer"
description: "Automation component to observe the status of your plants."
date: 2017-05-06 08:00
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Other
ha_release: 0.44
---
```yaml
plant:
simulated_plant:
sensors:
moisture: sensor.mqtt_plant_moisture
battery: sensor.mqtt_plant_battery
temperature: sensor.mqtt_plant_temperature
conductivity: sensor.mqtt_plant_conductivity
brightness: sensor.mqtt_plant_brightness
min_moisture: 20
max_moisture: 60
min_battery: 17
min_conductivity: 500
min_temperature: 15
```
## Using plain MQTT sensor to get the data
```yaml
sensor:
- platform: mqtt
name: mqtt_plant_moisture
state_topic: test/simulated_plant
value_template: '{{ value_json.moisture }}'
- platform: mqtt
name: mqtt_plant_battery
state_topic: test/simulated_plant
value_template: '{{ value_json.battery }}'
- platform: mqtt
name: mqtt_plant_temperature
state_topic: test/simulated_plant
value_template: '{{ value_json.temperature }}'
- platform: mqtt
name: mqtt_plant_conductivity
state_topic: test/simulated_plant
value_template: '{{ value_json.conductivity }}'
- platform: mqtt
name: mqtt_plant_brightness
state_topic: test/simulated_plant
value_template: '{{ value_json.brightness }}'
```

0
source/_components/sensor.ios.markdown Normal file
View file

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

@ -21,7 +21,7 @@ To use your Mi Flora plant sensor in your installation, add the following to you
# Example configuration.yaml entry
sensor:
- platform: miflora
mac: "xx:xx:xx:xx:xx:xx"
mac: 'xx:xx:xx:xx:xx:xx'
monitored_conditions:
- temperature
```
@ -50,7 +50,7 @@ A full configuration example could looks the one below:
# Example configuration.yaml entry
sensor:
- platform: miflora
mac: "xx:xx:xx:xx:xx:xx"
mac: 'xx:xx:xx:xx:xx:xx'
name: Flower 1
force_update: false
median: 3

16
source/_components/telegram_bot.markdown
View file

@ -79,3 +79,19 @@ action:
- service: homeassistant.turn_off
entity_id: switch.vision_zm1601eu5_battery_operated_siren_switch_9_0
```
An example to show the use of event_data in the action:
```
- alias: 'Kitchen Telegram Speak'
trigger:
platform: event
event_type: telegram_command
event_data:
command: '/speak'
action:
- service: notify.kitchen_echo
data_template:
message: >
Message from {% raw %}{{ trigger.event.data["from_first"] }}. {% for state in trigger.event.data["args"] %} {{ state }} {% endfor %}{% endraw %}
```

2
source/_components/tts.voicerss.markdown
View file

@ -43,3 +43,5 @@ tts:
codec: mp3
format: 8khz_8bit_mono
```
Please note, some media_players require a certain format. For example the Sonos requires a format of '44khz_16bit_stereo'

2
source/_components/zone.markdown
View file

@ -47,6 +47,8 @@ Configuration variables:
- **icon** (*Optional*): Optional icon to show instead of name.
- **passive** (*Optional*): Optional boolean to only use the zone for automation and hide it from the UI and not use the zone for device tracker name. Defaults to false.
To find your latitude / longtitude of a certain place you can use for example [Google Maps](https://www.google.nl/maps/) or [Bing Maps](https://www.bing.com/maps). Just right click and copy the coordinates from there (Bing) or click on the "What is here?" (Google)
#### {% linkable_title Home zone %}
If no configuration is given, the `zone` component will create a zone for home. This zone will use location given in the `configuration.yaml` file and have a radius of 100 meters. To override this, create a zone configuration and name it **'Home'**.