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-11-11 13:02:56 -08:00
commit 9e1043fa21
24 changed files with 391 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/_components/device_tracker.huawei_router.markdown
View file

@ -13,7 +13,7 @@ ha_release: 0.51
---
This component offers presence detection by looking at connected devices to a [Huawei router](http://m.huawei.com/enmobile/enterprise/products/network/access/pon-one/hw-371813.htm).
Currently, this was only tested with the Huawei HG8247H (used by Vodafone Portugal).
Currently, this was only tested with the Huawei HG8247H and HG8247Q Smart Router (used by Vodafone Portugal).
To use a Huawei router in your installation, add the following to your `configuration.yaml` file:

6
source/_components/device_tracker.nmap_tracker.markdown
View file

@ -29,7 +29,7 @@ To use this device tracker in your installation, add the following to your `conf
# Example configuration.yaml entry
device_tracker:
- platform: nmap_tracker
hosts: 192.168.1.1/24
hosts: 192.168.1.0/24
```
Configuration variables:
@ -47,7 +47,7 @@ A full example for the `nmap` tracker could look like the following sample:
# One whole subnet, and skipping two specific IPs.
device_tracker:
- platform: nmap_tracker
hosts: 192.168.1.1/24
hosts: 192.168.1.0/24
home_interval: 10
exclude:
- 192.168.1.12
@ -60,7 +60,7 @@ device_tracker:
device_tracker:
- platform: nmap_tracker
hosts:
- 192.168.1.1/24
- 192.168.1.0/24
- 10.0.0.2
- 10.0.0.15
```

6
source/_components/device_tracker.unifi.markdown
View file

@ -36,3 +36,9 @@ Configuration variables:
- **detection_time** (*Optional*): The Unifi component will not return a device that has not been seen by the controller in the last 180 seconds. You can adjust this threshold with this variable and accepts seconds or `00:00:00` time formats.
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
<p class='note'>
If you decide to install the Unifi Controller on the same system as your Home Assistant, be aware there may be overlap in ports if you have the MQTT component as well.
[Related Issue](https://github.com/home-assistant/home-assistant/issues/10507)
</p>

17
source/_components/frontend.markdown
View file

@ -101,8 +101,12 @@ automation:
### {% linkable_title Manual Theme Selection %}
When themes are enabled in the `configuration.yaml` file, a new option will show up in the Configuration panel under `configuration.yaml` called "Set a theme." You can then choose any installed theme from the dropdown list and it will be applied immediately.
When themes are enabled in the `configuration.yaml` file, a new option will show up in the Configuration panel under **General** called "Set a theme." You can then choose any installed theme from the dropdown list and it will be applied immediately.
<p class='img'>
<img src='/images/frontend/choose-theme.png' />
Set a theme
</p>
## {% linkable_title Loading extra HTML %}
@ -118,4 +122,13 @@ frontend:
- /file2.html
```
Those will be loaded via `<link rel='import' href='{{ extra_url }}' async>` on any page (states and panels)
Those will be loaded via `<link rel='import' href='{{ extra_url }}' async>` on any page (states and panels).
### {% linkable_title Manual Language Selection %}
The browser language is automatically detected. To use a different language, go to **General** in the Configuration panel and select a one from "Choose a Language". It will be applied immediately.
<p class='img'>
<img src='/images/frontend/choose-language.png' />
Choose a Language
</p>

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

@ -113,3 +113,5 @@ automation:
- When running on Raspberry Pi, just note that the maximum speed is limited by its 100 Mbit/s LAN adapter.
- Entries under `monitored_conditions` only control what entities are available under home-assistant, it does not disable the condition from running.
- If ran frequently, this component has the capability of using a very large amount of data. Frequent updates should be avoided on bandwidth capped connections.
- While running, network usage is fully utilized. This may have a negative affect on other devices in use the network such as gaming consoles or streaming boxes.

41
source/_components/timer.markdown
View file

@ -14,7 +14,7 @@ ha_release: 0.57
The `timer` component aims to simplify automations based on (dynamic) durations.
When a timer finishes or gets cancelled the corresponding events are fired. This allows you to diffferentiate if a timer has switched from `active` to `idle` because the given duration has elapsed or it has been cancelled. To control timers in your automations you can use the services mentioned below. When calling the `start` service on a timer that is already running, it resets the duration it will need to finish and restart the timer without triggering any events. This for example makes it easy to create timed lights that get triggered by motion.
When a timer finishes or gets cancelled the corresponding events are fired. This allows you to differentiate if a timer has switched from `active` to `idle` because the given duration has elapsed or it has been cancelled. To control timers in your automations you can use the services mentioned below. When calling the `start` service on a timer that is already running, it resets the duration it will need to finish and restart the timer without triggering any events. This for example makes it easy to create timed lights that get triggered by motion.
<p class='note warning'>
With the current implementation timers don't persist over restarts. After a restart they will be idle again, together with their initial configuration.
@ -92,3 +92,42 @@ Select <img src='/images/screenshots/developer-tool-services-icon.png' alt='serv
}
```
### {% linkable_title Configuration example %}
```yaml
# Example configuration.yaml entry
# Set a timer called test to a duration of 30 seconds:
timer:
test:
duration: '00:00:30'
```
```yaml
# Example automations.yaml entry
- action:
- service: timer.start
entity_id: timer.test
alias: Timerswitch
id: 'Timerstart'
# Timer is started when the switch pumprun is set to on.
trigger:
platform: state
entity_id: switch.pumprun
to: 'on'
# When timer is stopped, the time run out, another message is sent
- action:
- service: notify.nma
data:
message: "Timer stop"
alias: Timerstop
id: 'Timerstop'
trigger:
platform: event
event_type: timer.finished
event_data:
entity_id: timer.test
```

9
source/_components/volvooncall.markdown
View file

@ -25,21 +25,21 @@ volvooncall:
password: password
```
Users registered with Volvo in North America or China will need to specify a service URL:
Users registered with Volvo in North America or China will need to specify a region:
```yaml
# North America
volvooncall:
username: username
password: password
service_url: 'https://vocapi-na.wirelesscar.net/customerapi/rest/v3.0/'
region: na
```
```yaml
# China
volvooncall:
username: username
password: password
service_url: 'https://vocapi-cn.wirelesscar.net/customerapi/rest/v3.0/'
region: cn
```
A more advanced example for setting the vehicle name and selecting what resources to display:
@ -61,7 +61,8 @@ Configuration variables:
- **username** (*Required*): The username associated with your Volvo On Call account.
- **password** (*Required*): The password for your given Volvo On Call account.
- **service_url** (*Optional*): The service URL to use for Volvo On Call (defaults to https://vocapi.wirelesscar.net/customerapi/rest/v3.0/).
- **region** (*Optional*): The region where the Volvo is registered. Needs to be set for users in North America or China.
- **service_url** (*Optional*): The service URL to use for Volvo On Call. Normally not neccessary to specify.
- **name** (*Optional*): Make it possible to provide a name for the vehicles.
- **resources** (*Optional*): A list of resources to display (defaults to all available).

6
source/_components/xiaomi_aqara.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: xiaomi.png
ha_category: Hub
ha_release: "0.50"
ha_release: "0.57"
ha_iot_class: "Local Push"
redirect_from: /components/xiaomi/
---
@ -49,7 +49,7 @@ The `xiaomi_aqara` component allows you to integrate [Xiaomi](http://www.mi.com/
## {% linkable_title Setup %}
Follow the setup process using your phone and Mi-Home app. From here you will be able to retrieve the key from within the app following [this tutorial](https://community.home-assistant.io/t/beta-xiaomi-gateway-integration/8213/1832).
Follow the setup process using your phone and Mi-Home app. From here you will be able to retrieve the key (password) from within the app following [this tutorial](https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)#Adding_the_Xiaomi_Gateway_to_Domoticz).
To enable {{ page.title }} in your installation, add the following to your `configuration.yaml` file:
@ -236,7 +236,7 @@ If you run into trouble initializing the gateway with your app, try another smar
```
That means that Home Assistant is not getting any response from your Xiaomi gateway. Might be a local network problem or your firewall.
- Make sure you have [enabled LAN access](https://community.home-assistant.io/t/beta-xiaomi-gateway-integration/8213/1832).
- Make sure you have [enabled LAN access](https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)#Adding_the_Xiaomi_Gateway_to_Domoticz).
- Turn off the firewall on the system where Home Assistant is running.
- Ensure your router supports multicast as this is a requirement of the Xiaomi GW
- Try to leave the MAC address `mac:` blank.