jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Various markdown, spelling, and grammar fixes #3 (#4510)

Browse Source 
* ✅ Various markdown, spelling, and grammar fixes

* ✅ Various markdown, spelling, and grammar fixes

* ✅ Various markdown, spelling, and grammar fixes
This commit is contained in:
Franck Nijhof 2018-01-25 18:21:05 +01:00 committed by Fabian Affolter
parent 42f9a8e5cd
commit 6224c71c08
98 changed files with 131 additions and 131 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_addons/dhcp_server.markdown
View File

@ -47,7 +47,7 @@ Configuration variables:
 - **range_end** (*Required*): End address for dhcp leases.
 - **broadcast** (*Required*): Network broadcast address.
 - **gateway** (*Required*): A List of gateways.
- **interface** (*Required*): Inteface on that will be listen. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
- **interface** (*Required*): Interface on that will be listen. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
- **hosts** (*Optional*): A list of fixed IPs for devices.
- **name** (*Required*): Name/hostname of your device.
 - **mac** (*Required*): Mac address of your device.

2
source/_components/binary_sensor.bbb_gpio.markdown
View File

@ -33,7 +33,7 @@ Configuration variables:
- **pins** array (*Required*): Array of used pins.
- **pin_name** (*Required*): Pin numbers and corresponding names.
- **name** (*Required*): Friendly name to use for the frontend.
- **bouncetime** (*Optional*): Debounce time for reading input pin defined in miliseconds [ms]. Defaults to `50 ms`.
- **bouncetime** (*Optional*): Debounce time for reading input pin defined in milliseconds [ms]. Defaults to `50 ms`.
- **invert_logic** (*Optional*): If `true`, inverts the input logic to ACTIVE LOW. Default is `false` (ACTIVE HIGH).
- **pull_mode** (*Optional*): Type of internal pull resistor connected to input. Options are `UP` - pull-up resistor and `DOWN` - pull-down resistor. Defaults to `UP`.

2
source/_components/binary_sensor.xiaomi_aqara.markdown
View File

@ -30,7 +30,7 @@ The requirement is that you have setup the [`xiaomi aqara` component](/component
| Smoke Detector | smoke | JTYJ-GD-01LM/BW | on, off | | | |
| Gas Leak Detector | natgas | JTQJ-BF-01LM/BW | on, off | | | |
| Water Leak Sensor | sensor_wleak.aq1 | SJCGQ11LM | on, off | | | |
| Button (1st gen) | switch | WXKG01LM | on (thru long_click_press), off | `click`| `click_type`| `long_click_press`, `long_click_release`, `hold`, `single`, `double` |
| Button (1st gen) | switch | WXKG01LM | on (through long_click_press), off | `click`| `click_type`| `long_click_press`, `long_click_release`, `hold`, `single`, `double` |
| Button (2nd gen) | sensor_switch.aq2 | WXKG11LM | off (always) | `click` | `click_type` | `single`, `double` |
| Aqara Wireless Switch (Single) | 86sw1 | WXKG03LM | off (always) | `click` | `click_type` | `single` |
| Aqara Wireless Switch (Double) | 86sw2 | WXKG02LM | off (always) | `click` | `click_type` | `single`, `both` |

2
source/_components/binary_sensor.zigbee.markdown
View File

@ -13,7 +13,7 @@ ha_release: 0.12
ha_iot_class: "Local Polling"
---
A `zigbee` binary sensor in this context is a device connected to one of the digital input pins on a [ZigBee](http://www.zigbee.org/) module. The states reported by such a device are limited to `on` or `off`. By default, a binary sensor is considered `on` when the ZigBee device's digital input pin is held 'high' and considered `off` when it is held `low`. This behaviour can be inverted by setting the `on_state` configuration variable to `low`.
A `zigbee` binary sensor in this context is a device connected to one of the digital input pins on a [ZigBee](http://www.zigbee.org/) module. The states reported by such a device are limited to `on` or `off`. By default, a binary sensor is considered `on` when the ZigBee device's digital input pin is held 'high' and considered `off` when it is held `low`. This behavior can be inverted by setting the `on_state` configuration variable to `low`.
To enable a digital input pin as binary sensor in your installation, add the following lines to your `configuration.yaml`:

2
source/_components/climate.ecobee.markdown
View File

@ -240,7 +240,7 @@ For 'temp', the current temperature is taken as the target temperature.
When None is provided as parameter, the hold_mode is turned off.
It is not possible to set a vacation hold; such hold has to be
defined on the thermostat directly. However, a vacation hold can be
cancelled.
canceled.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |

4
source/_components/device_tracker.bluetooth_le_tracker.markdown
View File

@ -30,7 +30,7 @@ $ sudo apt install bluetooth libbluetooth-dev pkg-config libboost-python-dev lib
Before you get started with this platform, please note that:
- This platform is incompatible with Windows
- This platform requires access to the bluetooth stack, see [Rootless Setup section](#rootless-setup) for further infomation
- This platform requires access to the bluetooth stack, see [Rootless Setup section](#rootless-setup) for further information
To use the Bluetooth tracker in your installation, add the following to your `configuration.yaml` file:
@ -52,7 +52,7 @@ Some BTLE devices (e.g. fitness trackers) are only visible to the devices that t
## {% linkable_title Rootless Setup %}
Normaly accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 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).
Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 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
$ sudo apt-get install libcap2-bin

6
source/_components/device_tracker.gpslogger.markdown
View File

@ -68,14 +68,14 @@ Add the above URL after you modified it with your settings into the **URL** fiel
- Use the domain that Home Assistant is available on the internet or the public IP address. Can be a local IP address if you are using a VPN setup.
- Only remove `[Port]` if your Home Assistant instance is using port 80. Otherwise set it to 8123.
- For Home Assistant only the above URL, as written, will work - do not add or remove any parameters.
- Make sure to include your [API password](/components/http/) if you have configured a password. Add `&api_password=[Your pasword]` to the end of the URL.
- Make sure to include your [API password](/components/http/) if you have configured a password. Add `&api_password=[Your password]` to the end of the URL.
- You can change the name of your device name by replacing `&device=%SER` with `&device=[Devicename]`.
If your battery drains fast then you can tune the performence of GPSLogger under **Performance** -> **Location providers**
If your battery drains fast then you can tune the performance of GPSLogger under **Performance** -> **Location providers**
<p class='img'>
<img width='300' src='/images/components/gpslogger/performance.png' />
Performance
</p>
A request can be forced from the app to test if everything is working fine. A succesful request will update the `known_devices.yaml` file with the device's serial number.
A request can be forced from the app to test if everything is working fine. A successful request will update the `known_devices.yaml` file with the device's serial number.

2
source/_components/fan.xiaomi_miio.markdown
View File

@ -13,7 +13,7 @@ ha_version: 0.57
ha_iot_class: "Local Polling"
---
The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier 2, Air Purifier 2S andd Air Purifier Pro.
The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier 2, Air Purifier 2S and Air Purifier Pro.
Currently, the supported features are

4
source/_components/frontend.markdown
View File

@ -39,11 +39,11 @@ frontend:
required: true
type: [list, string]
extra_html_url:
description: "List of addtional [resources](/developers/frontend_creating_custom_ui/) to load in `latest` javascript mode."
description: "List of additional [resources](/developers/frontend_creating_custom_ui/) to load in `latest` javascript mode."
required: false
type: list
extra_html_url_es5:
description: "List of addtional [resources](/developers/frontend_creating_custom_ui/) to load in `es5` javascript mode."
description: "List of additional [resources](/developers/frontend_creating_custom_ui/) to load in `es5` javascript mode."
required: false
type: list
development_repo:

2
source/_components/group.markdown
View File

@ -118,7 +118,7 @@ group:
- group.all_scripts
```
## {% linkable_title Group behaviour %}
## {% linkable_title Group behavior %}
When any member of a group is `on` then the group will also be `on`. Similarly with a device tracker, when any member of the group is `home` then the group is `home`.

2
source/_components/hive.markdown
View File

@ -49,7 +49,7 @@ The Hive Home Assistant platform currently supports the following Hive devices:
- Hive Active Heating (including hot water and Hive Multizone)
- Hive Active Light Dimmable
- Hive Active Light Cool to Warm White
- Hive Active Light Colour Changing
- Hive Active Light Color Changing
- Hive Active Plug
- Hive Window or Door Sensor
- Hive Motion Sensor

2
source/_components/image_processing.markdown
View File

@ -22,7 +22,7 @@ If you are running Home Assistant over SSL or from within a container, you will
Alpr entities attribute have a vehicle counter `vehicles` and all found plates as `plates`.
This event is trigger after OpenALPR found a new licence plate.
This event is trigger after OpenALPR found a new license plate.
```yaml
# Example configuration.yaml automation entry

2
source/_components/input_datetime.markdown
View File

@ -68,7 +68,7 @@ A datetime input entity's state exports several attributes that can be useful in
| --------- | ----------- |
| `has_time` | `true` if this entity has a time.
| `has_date` | `true` if this entity has a date.
| `year`<br>`month`<br>`day` | The year, month and day of the date.<br>(only availabel if `has_date: true`)
| `year`<br>`month`<br>`day` | The year, month and day of the date.<br>(only available if `has_date: true`)
| `hour`<br>`minute`<br>`second` | The hour, minute and second of the time.<br>(only available if `has_time: true`)
| `timestamp` | A timestamp representing the time held in the input.<br>If `has_date: true`, this is the UNIX timestamp of the date / time held by the input. Otherwise if only `has_time: true`, this is the number of seconds since midnight representing the time held by the input.

2
source/_components/input_number.markdown
View File

@ -51,7 +51,7 @@ input_number:
required: true
type: float
max:
description: Maxium value.
description: Maximum value.
required: true
type: float
name:

2
source/_components/knx.markdown
View File

@ -82,7 +82,7 @@ knx:
- **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus
- **fire_event_filter** (*Optional*): If `fire_event` is set `fire_event_filter` has to be specified. `fire_event_filter` defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme Assistant event bus.
- **state_updater** (*Optional*): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behaviour.
- **state_updater** (*Optional*): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behavior.
- **time_address** (*Optional*): Broadcast current local time to KNX bus with configured group address.
### {% linkable_title Services %}

2
source/_components/light.hive.markdown
View File

@ -19,7 +19,7 @@ The 'hive' light component integrates your Hive lights into Home Assistant, enab
The Hive light component supports the following Hive products:
- **Hive Active Light Dimmable**
- **Hive Active Light Cool to Warm White**
- **Hive Active Light Colour Changing**
- **Hive Active Light Color Changing**
<p class='note'>

2
source/_components/light.zigbee.markdown
View File

@ -13,7 +13,7 @@ ha_release: 0.12
ha_iot_class: "Local Polling"
---
A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered `on` when the ZigBee device's digital output is held `high` and considered `off` when it is held `low`. This behaviour can be inverted by setting the `on_state` configuration variable to `low`.
A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered `on` when the ZigBee device's digital output is held `high` and considered `off` when it is held `low`. This behavior can be inverted by setting the `on_state` configuration variable to `low`.
To configure a digital output pin as light, add the following to your `configuration.yaml` file:

2
source/_components/lirc.markdown
View File

@ -34,7 +34,7 @@ The configuration is slightly different :
- The former single `lirc` service is replaced with the three systemd services `lircd.service`, `lircmd.service` and `irexec.service`. There is no counterpart to the 0.9.0 `lirc` service which covered all of these. Using a separate transmitter device requires yet another service.
- 0.9.4 defaults to using systemd for controlling the services. This is not just start/stop functionality, systemd is used to implement new features and to address shortcomings in 0.9.0. However, traditional systemV scripts are also installed and could be used although this is less tested and not really documented.
For more infomation have a look at `/usr/share/doc/lirc/README.Debian.gz` where the update process is explained when you have updated from jessie to stretch.
For more information have a look at `/usr/share/doc/lirc/README.Debian.gz` where the update process is explained when you have updated from jessie to stretch.
</p>
### {% linkable_title Configuring LIRC %}

2
source/_components/media_player.denonavr.markdown
View File

@ -67,6 +67,6 @@ A few notes:
- Additional option the control Denon AVR receivers with a builtin web server is using the HTTP interface with denonavr platform.
- denonavr platform supports some additional functionalities like album covers, custom input source names and auto discovery.
- Marantz receivers seem to a have quite simliar interface. Thus if you own one, give it a try.
- Marantz receivers seem to a have quite similar interface. Thus if you own one, give it a try.
[Denon]: /components/media_player.denon/

2
source/_components/media_player.yamaha.markdown
View File

@ -61,7 +61,7 @@ Configuration variables:
volume control and source selection. Playback controls, for instance
play and stop are available for sources that supports it.
- The `play_media` service is implemented for `NET RADIO` source
only. The `media_id` is a `>` separted string of the menu path on
only. The `media_id` is a `>` separated string of the menu path on
the vtuner service. For instance `Bookmarks>Internet>WAMC 90.3 FM`.
### {% linkable_title Example configuration %}

2
source/_components/namecheapdns.markdown
View File

@ -16,7 +16,7 @@ ha_release: 0.56
With the `namecheapdns` component you can automatically update your dynamic DNS entry at [namecheapdns](https://www.namecheap.com/store/domains/freedns/).
<p class='note warning'>
Namecheap only supports IPv4 adresses to update.
Namecheap only supports IPv4 addresses to update.
</p>
To use the component in your installation, add the following to your `configuration.yaml` file:

2
source/_components/notify.facebook.markdown
View File

@ -50,7 +50,7 @@ automation:
- '+919784516314'
```
You can also send messages to users that do not have stored their phone number with Facebook, but this requires a bit more work. The Messenger platform uses page specific user IDs instead of a global user ID. You will need to enable a webhook for the "messages" event in Facebook's developer console. Once a user writes a message to a page, that webhook will then receive the user's page specifc ID as part of the webhook's payload. Below is a simple PHP script that reacts to the message "get my id" and sends a reply containing the user's ID:
You can also send messages to users that do not have stored their phone number with Facebook, but this requires a bit more work. The Messenger platform uses page specific user IDs instead of a global user ID. You will need to enable a webhook for the "messages" event in Facebook's developer console. Once a user writes a message to a page, that webhook will then receive the user's page specific ID as part of the webhook's payload. Below is a simple PHP script that reacts to the message "get my id" and sends a reply containing the user's ID:
```php
<?php

6
source/_components/notify.pushsafer.markdown
View File

@ -34,7 +34,7 @@ notify:
### {% linkable_title Examples %}
Message to two devices with formated text.
Message to two devices with formatted text.
```json
{
@ -53,7 +53,7 @@ Message to two devices with formated text.
}
```
Message to one device with formated text and image from an external URL.
Message to one device with formatted text and image from an external URL.
```json
{
@ -75,7 +75,7 @@ Message to one device with formated text and image from an external URL.
}
```
Message to two devices and one device group with formated text and local image.
Message to two devices and one device group with formatted text and local image.
```json
{

2
source/_components/pilight.markdown
View File

@ -33,7 +33,7 @@ Configuration variables:
- **host** (*Required*): The IP address of the computer running the pilight-daemon, e.g. 192.168.1.32.
- **port** (*Required*): The network port to connect to. The usual port is [5000](https://manual.pilight.org/development/api.html).
- **send_delay** (*Optional*): You can define a send delay as a fraction of seconds if you experience transmission problems when you try to switch multiple switches at once. This can happen when you use a [pilight USB Nano](https://github.com/pilight/pilight-usb-nano) as hardware and switches a whole group of multiple switches on or off. Tested values are between 0.3 and 0.8 seconds depending on the hardware.
- **whitelist** (*Optional*): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbours weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.
- **whitelist** (*Optional*): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbors weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.
In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight [API](https://manual.pilight.org/development/api.html).

2
source/_components/remember_the_milk.markdown
View File

@ -36,7 +36,7 @@ Configuration variables:
{% configuration %}
name:
description: Name of the RTM account, as you can have serveral accounts in RTM. The name must be unique.
description: Name of the RTM account, as you can have several accounts in RTM. The name must be unique.
required: true
type: string
api_key:

2
source/_components/sensor.buienradar.markdown
View File

@ -56,7 +56,7 @@ Configuration variables:
- **groundtemperature**: The current ground temperature (in [C](https://en.wikipedia.org/wiki/Celsius)).
- **windspeed**: The wind speed in [m/s](https://en.wikipedia.org/wiki/M/s).
- **windforce**: The wind speed/force in [Bft](https://en.wikipedia.org/wiki/Beaufort_scale).
- **winddirection**: Where the wind is coming from: N (North),Z (south), NO (Noth-East), etc.
- **winddirection**: Where the wind is coming from: N (North),Z (south), NO (North-East), etc.
- **windazimuth**: Where the wind is coming from in degrees, with true north at 0° and progressing clockwise.
- **pressure**: The sea-level air pressure in [hPa](https://en.wikipedia.org/wiki/Hectopascal).
- **visibility**: Visibility in meters ([m](https://en.wikipedia.org/wiki/Metre)).

2
source/_components/sensor.deutsche_bahn.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Deutsche Bahn"
description: "Instructions how to integrate timetable data for travelling in Germany within Home Assistant."
description: "Instructions how to integrate timetable data for traveling in Germany within Home Assistant."
date: 2015-06-02 21:45
sidebar: true
comments: false

2
source/_components/sensor.dublin_bus_transport.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Dublin Bus Transport"
description: "Instructions how to integrate timetable data for travelling on Dublin Bus within Home Assistant."
description: "Instructions how to integrate timetable data for traveling on Dublin Bus within Home Assistant."
date: 2017-01-09 21:45
sidebar: true
comments: false

2
source/_components/sensor.envirophat.markdown
View File

@ -16,7 +16,7 @@ ha_release: 0.44
The `envirophat` sensor platform allows you to display information collected by an [Enviro pHAT](https://shop.pimoroni.com/products/enviro-phat) add-on board for the Raspberry Pi. The board features a wide range of sensors, such as:
- BMP280 temperature/pressure sensor
- TCS3472 light and RGB colour sensor with two LEDs for illumination
- TCS3472 light and RGB color sensor with two LEDs for illumination
- LSM303D accelerometer/magnetometer sensor
- ADS1015 4-channel 3.3v, analog to digital sensor (ADC)

2
source/_components/sensor.geo_rss_events.markdown
View File

@ -57,7 +57,7 @@ Configuration variables:
- **url** (*Required*): Full URL of the GeoRSS feed.
- **name** (*Optional*): Name of the sensor used in generating the entity id. Default is 'Event Service'.
- **radius** (*Optional*): The distance in kilometres around the Home Assistant's coordinates in which events are considered. Default is: 20km.
- **radius** (*Optional*): The distance in kilometers around the Home Assistant's coordinates in which events are considered. Default is: 20km.
- **categories** (*Optional*): List of event category names found in the GeoRSS feed. A separate sensor is created for each category defined. Default is to join events from all categories into an 'Any' category.
- **unit_of_measurement** (*Optional*): The type of events found in the GeoRSS feed. Default is 'Events'.

2
source/_components/sensor.influxdb.markdown
View File

@ -50,7 +50,7 @@ Configuration variables for the server:
### {% linkable_title Full configuration %}
The example configuration entry bellow create two request to your local InfluxDB instance, one to the database `db1`, the other to `db2`:
The example configuration entry below create two request to your local InfluxDB instance, one to the database `db1`, the other to `db2`:
- `select last(value) as value from "°C" where "name" = "foo"`
- `select min(tmp) as value from "%" where "entity_id" = ''salon'' and time > now() - 1h`

2
source/_components/sensor.lacrosse.markdown
View File

@ -22,7 +22,7 @@ The `lacrosse` sensor platform is using the data provided by a [Jeelink](https:/
## {% linkable_title Setup %}
Since the sensor change their ID after each powercycle/battery change you can check what sensor IDs are availble by using the command-line tool `pylacrosse` from the pylacrosse package.
Since the sensor change their ID after each powercycle/battery change you can check what sensor IDs are available by using the command-line tool `pylacrosse` from the pylacrosse package.
```bash
$ sudo pylacrosse -d /dev/ttyUSB0 scan

2
source/_components/sensor.london_air.markdown
View File

@ -16,7 +16,7 @@ ha_release: 0.52
The `london_air` component [queries](http://api.erg.kcl.ac.uk/AirQuality/Hourly/MonitoringIndex/GroupName=London/Json) the London air quality [data feed](https://www.londonair.org.uk/LondonAir/API/) provided by Kings College London. A single sensor will be added for each `location` ([local authority district or borough](https://en.wikipedia.org/wiki/List_of_London_boroughs)) specified in the configuration file. The state of each sensor is the overall air quality in that borough. Note that only 28 of the 32 boroughs have data available.
Boroughs can have multiple monitoring sites at different geographical positions within the borough, and each of those sites can monitor up to six different kinds of pollutant. The pollutants are described [here](http://api.erg.kcl.ac.uk/AirQuality/Information/Species/Json) and are Carbon Monoxide ([CO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsCO.aspx)), Nitrogen Dioxide ([NO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsNO2.aspx)), Ozone ([O3](http://www.londonair.org.uk/LondonAir/guide/WhatIsO3.aspx)), Sulphur Dioxide ([SO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsSO2.aspx)), PM2.5 & PM10 [particulates](http://www.londonair.org.uk/LondonAir/guide/WhatIsPM.aspx). The `latitude` and `longitude` of each site is accessible through a `data` attribute of the sensor, as are details about the pollutants monitored at that site. The `sites` attribute of a sensor displays how many monitoring sites that sensor covers. The `updated` attribute of a sensor states when the data was last published. Nominally data is published hourly, but in my experience this can vary. To limit the number of requests made by the sensor, a single API request is made every 30 minutes.
Boroughs can have multiple monitoring sites at different geographical positions within the borough, and each of those sites can monitor up to six different kinds of pollutant. The pollutants are described [here](http://api.erg.kcl.ac.uk/AirQuality/Information/Species/Json) and are Carbon Monoxide ([CO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsCO.aspx)), Nitrogen Dioxide ([NO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsNO2.aspx)), Ozone ([O3](http://www.londonair.org.uk/LondonAir/guide/WhatIsO3.aspx)), Sulfur Dioxide ([SO2](http://www.londonair.org.uk/LondonAir/guide/WhatIsSO2.aspx)), PM2.5 & PM10 [particulates](http://www.londonair.org.uk/LondonAir/guide/WhatIsPM.aspx). The `latitude` and `longitude` of each site is accessible through a `data` attribute of the sensor, as are details about the pollutants monitored at that site. The `sites` attribute of a sensor displays how many monitoring sites that sensor covers. The `updated` attribute of a sensor states when the data was last published. Nominally data is published hourly, but in my experience this can vary. To limit the number of requests made by the sensor, a single API request is made every 30 minutes.
To add sensors to Home-assistant for all possible areas/boroughs add the following to your `configuration.yaml` file:

6
source/_components/sensor.nederlandse_spoorwegen.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Nederlandse Spoorwegen"
description: "Instructions how to integrate timetable data for travelling by train in the Netherlands within Home Assistant."
description: "Instructions how to integrate timetable data for traveling by train in the Netherlands within Home Assistant."
date: 2017-10-25 13:35
sidebar: true
comments: false
@ -40,10 +40,10 @@ Configuration variables:
- **email** (*Required*): The email address you used to request the API password.
- **password** (*Required*): The API password provided by the Nederlandse Spoorwegen.
- **routes** array (*Required*): List of travelling routes.
- **routes** array (*Required*): List of traveling routes.
- **name** (*Required*): Name of the route.
- **from** (*Required*): The start station.
- **to** (*Required*): Direction of the travelling.
- **to** (*Required*): Direction of the traveling.
- **via** (*Optional*): Optional other station you wish to visit in between.
The data are coming from [Nederlandse Spoorwegen](https://www.ns.nl/).

2
source/_components/sensor.onewire.markdown
View File

@ -28,7 +28,7 @@ Supported devices:
The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or using dedicated interface adapter (e.g [DS9490R](https://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf)).
#### Raspberry Pi setup
In order ot setup 1-Wire support on Raspberry Pi, you'll need to edit `/boot/config.txt` following [this documentation](https://www.waveshare.com/wiki/Raspberry_Pi_Tutorial_Series:_1-Wire_DS18B20_Sensor#Enable_1-Wire). Don't use the `mount_dir` option.
In order to setup 1-Wire support on Raspberry Pi, you'll need to edit `/boot/config.txt` following [this documentation](https://www.waveshare.com/wiki/Raspberry_Pi_Tutorial_Series:_1-Wire_DS18B20_Sensor#Enable_1-Wire). Don't use the `mount_dir` option.
#### Interface adapter setup
When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](http://owfs.org/). When using an interface adapter and the owfs, the `mount_dir` option must be configured to correspond a directory, where owfs device tree has been mounted.

2
source/_components/sensor.pvoutput.markdown
View File

@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
---
The `pvoutput` sensor platform consumes informations from [PVOutput](http://pvoutput.org/) which were uploaded by your solar photovoltaic (PV) system.
The `pvoutput` sensor platform consumes information from [PVOutput](http://pvoutput.org/) which were uploaded by your solar photovoltaic (PV) system.
To add PVOutput details to your installation, add the following to your `configuration.yaml` file:

2
source/_components/sensor.rest.markdown
View File

@ -196,7 +196,7 @@ sensor:
User-Agent: Home Assistant REST sensor
```
### {% linkable_title Fetch multiple JSON values and present them as attibutes %}
### {% linkable_title Fetch multiple JSON values and present them as attributes %}
[JSON Test](http://www.jsontest.com) returns the current time, date and milliseconds since epoch from [http://date.jsontest.com/](http://date.jsontest.com/).

2
source/_components/sensor.scrape.markdown
View File

@ -102,7 +102,7 @@ sensor:
### {% linkable_title Get the latest podcast episode file URL %}
If you want to get the file URL for the latest episode of your [favourite podcast](https://hasspodcast.io/), so you can pass it on to a compatible media player.
If you want to get the file URL for the latest episode of your [favorite podcast](https://hasspodcast.io/), so you can pass it on to a compatible media player.
```yaml
# Example configuration.yaml entry

2
source/_components/sensor.swiss_public_transport.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Swiss Public Transport"
description: "Instructions how to integrate timetable data for travelling in Switzerland within Home Assistant."
description: "Instructions how to integrate timetable data for traveling in Switzerland within Home Assistant."
date: 2015-06-02 21:45
sidebar: true
comments: false

8
source/_components/sensor.vasttrafik.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Västtrafik Public Transport"
description: "Instructions how to integrate timetable data for travelling in Sweden within Home Assistant."
description: "Instructions how to integrate timetable data for traveling in Sweden within Home Assistant."
date: 2016-10-05 08:45
sidebar: true
comments: false
@ -14,7 +14,7 @@ ha_release: "0.30"
---
The `vasttrafik` sensor will provide you travelling details for the larger Göteborg area in Sweden from the [Västtrafik](https://vasttrafik.se/) public transportation service.
The `vasttrafik` sensor will provide you traveling details for the larger Göteborg area in Sweden from the [Västtrafik](https://vasttrafik.se/) public transportation service.
You must create an application [here](https://developer.vasttrafik.se/portal/#/applications) to obtain a `key` and a `secret`.
@ -34,10 +34,10 @@ Configuration variables:
- **key** (*Required*): The API key to access your Västtrafik account.
- **secret** (*Required*): The API secret to access your Västtrafik account.
- **departures** array (*Required*): List of travelling routes.
- **departures** array (*Required*): List of traveling routes.
- **name** (*Optional*): Name of the route.
- **from** (*Required*): The start station.
- **heading** (*Optional*): Direction of the travelling.
- **heading** (*Optional*): Direction of the traveling.
- **delay** (*Optional*): Delay in minutes. Defaults to 0.
The data are coming from [Västtrafik](https://vasttrafik.se/).

2
source/_components/switch.zigbee.markdown
View File

@ -13,7 +13,7 @@ ha_release: 0.12
ha_iot_class: "Local Polling"
---
A ZigBee switch in this context is a device connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a switch is considered `on` when the ZigBee device's digital output is held `high` and considered `off` when it is held `low`. This behaviour can be inverted by setting the `on_state` configuration variable to `low`.
A ZigBee switch in this context is a device connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a switch is considered `on` when the ZigBee device's digital output is held `high` and considered `off` when it is held `low`. This behavior can be inverted by setting the `on_state` configuration variable to `low`.
To configure a digital output pin as switch, add the following to your `configuration.yaml` file:

6
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 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.
When a timer finishes or gets canceled 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 canceled. 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.
@ -42,7 +42,7 @@ Pick an icon that you can find on [materialdesignicons.com](https://materialdesi
| Event | Description |
| --------------- | ----------- |
| timer.cancelled | Fired when a timer has been cancelled |
| timer.cancelled | Fired when a timer has been canceled |
| timer.finished | Fired when a timer has completed |
## {% linkable_title Services %}
@ -67,7 +67,7 @@ Pause a running timer. This will retain the remaining duration for later continu
#### {% linkable_title Service `timer.cancel` %}
Cancel an active timer. This resets the duration to the last known initial value without firing the `timer.finished` event. If no `entity_id` is given all active timers will be cancelled.
Cancel an active timer. This resets the duration to the last known initial value without firing the `timer.finished` event. If no `entity_id` is given all active timers will be canceled.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |

2
source/_components/volvooncall.markdown
View File

@ -62,7 +62,7 @@ Configuration variables:
- **username** (*Required*): The username associated with your Volvo On Call account.
- **password** (*Required*): The password for your given Volvo On Call account.
- **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.
- **service_url** (*Optional*): The service URL to use for Volvo On Call. Normally not necessary 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).
- **scandinavian_miles** (*Optional*): If set to yes, Scandinavian miles ("mil") are used for distances and fuel range (defaults to no).

2
source/_components/wink.markdown
View File

@ -46,7 +46,7 @@ wink:
### {% linkable_title Full oauth authentication (legacy). %}
This should be used for users that obtained their client_id and client_secret via email from Wink support prior to [developer.wink.com's](https://developer.wink.com) existance.
This should be used for users that obtained their client_id and client_secret via email from Wink support prior to [developer.wink.com's](https://developer.wink.com) existence.
```yaml

2
source/_cookbook/turn_on_light_for_10_minutes_when_motion_detected.markdown
View File

@ -10,7 +10,7 @@ footer: true
ha_category: Automation Examples
---
#### {% linkable_title Turn on lights with a resettable off timer %}
#### {% linkable_title Turn on lights with a resetable off timer %}
This recipe will turn on a light when there is motion and turn off the light when ten minutes has passed without any motion events.

2
source/_data/glossary.yml
View File

@ -39,7 +39,7 @@
- topic: Cookbook
description: "The [Cookbook](/cookbook/) contains a set of configuration examples of Home Assistant from the community."
- topic: Packages
description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configuations together."
description: "[Packages](/docs/configuration/packages/) allow you to bundle different component configurations together."
- topic: Customize
description: "[Customization](/docs/configuration/customizing-devices/) allows you to overwrite the default parameter of your devices in the configuration."
- topic: Zone

2
source/_docs/autostart/init.d.markdown
View File

@ -14,7 +14,7 @@ Home Assistant can run as a daemon within init.d with the script below.
### {% linkable_title 1. Copy script %}
Copy either the deamon script or the Python environment scrip at the end of this page to `/etc/init.d/hass-daemon` depending on your installation.
Copy either the daemon script or the Python environment scrip at the end of this page to `/etc/init.d/hass-daemon` depending on your installation.
After that, set the script to be executable:

2
source/_docs/configuration/basic.markdown
View File

@ -37,7 +37,7 @@ Configuration variables:
### {% linkable_title Password protecting the web interface %}
First, you'll want to add a password for the Home Assistant web interface. Use your favourite text editor to open `configuration.yaml` and edit the `http` section:
First, you'll want to add a password for the Home Assistant web interface. Use your favorite text editor to open `configuration.yaml` and edit the `http` section:
```yaml
http:

2
source/_docs/configuration/group_visibility.markdown
View File

@ -14,7 +14,7 @@ After filling Home Assistant with all your precious home automation devices, you
## {% linkable_title Changing visibility of a group %}
To change visibility of a group, use the service `group.set_visibility`, pass the group name as `entity_id` and use `visible` to decide wheter the group should be shown or hidden.
To change visibility of a group, use the service `group.set_visibility`, pass the group name as `entity_id` and use `visible` to decide whether the group should be shown or hidden.
```yaml
service: group.set_visibility

2
source/_docs/configuration/packages.markdown
View File

@ -81,7 +81,7 @@ Components inside packages can only specify platform entries using configuration
### {% linkable_title Create a packages folder %}
One way to organise packages would be to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages:
One way to organize packages would be to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages:
```yaml
homeassistant:

22
source/_docs/ecosystem/appdaemon/api.markdown
View File

@ -39,7 +39,7 @@ There are several circumstances under which `initialize()` might be called:
- Following a change in the status of Daylight Savings Time
- Following a restart of Home Assistant
In every case, the App is responsible for recreating any state it might need as if it were the first time it was ever started. If `initialize()` is called, the app can safely assume that it is either being loaded for the first time, or that all callbacks and timers have been cancelled. In either case, the APP will need to recreate them. Depending upon the application it may be desirable for the App to establish state such as whether or not a particular light is on, within the `initialize()` function to ensure that everything is as expected or to make immediate remedial action (e.g. turn off a light that might have been left on by mistake when the app was restarted).
In every case, the App is responsible for recreating any state it might need as if it were the first time it was ever started. If `initialize()` is called, the app can safely assume that it is either being loaded for the first time, or that all callbacks and timers have been canceled. In either case, the APP will need to recreate them. Depending upon the application it may be desirable for the App to establish state such as whether or not a particular light is on, within the `initialize()` function to ensure that everything is as expected or to make immediate remedial action (e.g. turn off a light that might have been left on by mistake when the app was restarted).
After the `initialize()` function is in place, the rest of the app consists of functions that are called by the various callback mechanisms, and any additional functions the user wants to add as part of the program logic. Apps are able to subscribe to 2 main classes of events:
@ -539,7 +539,7 @@ self.handle = self.listen_state(self.my_callback, "light.office_1", new = "on",
### {% linkable_title cancel_listen_state() %}
Cancel a `listen_state()` callback. This will mean that the App will no longer be notified for the specific state change that has been cancelled. Other state changes will continue to be monitored.
Cancel a `listen_state()` callback. This will mean that the App will no longer be notified for the specific state change that has been canceled. Other state changes will continue to be monitored.
#### {% linkable_title Synopsis %}
@ -1317,7 +1317,7 @@ self.select_option("input_select.mode", "Day")
### {% linkable_title notify() %}
This is a convenience function for the `notify.notify` service. It will send a notification to your defualt notification service. If you have more than one, use `call_service()` to call the specific notification service you require instead.
This is a convenience function for the `notify.notify` service. It will send a notification to your default notification service. If you have more than one, use `call_service()` to call the specific notification service you require instead.
#### {% linkable_title Synopsis %}
@ -1534,7 +1534,7 @@ The name of the event that caused the callback, e.g. `"MODE_CHANGE"` or `call_se
A dictionary containing any additional information associated with the event.
### {% linkable_title Use of Events for Signalling between Home Assistant and AppDaemon %}
### {% linkable_title Use of Events for Signaling between Home Assistant and AppDaemon %}
Home Assistant allows for the creation of custom events and existing components can send and receive them. This provides a useful mechanism for signaling back and forth between Home Assistant and AppDaemon. For instance, if you would like to create a UI Element to fire off some code in Home Assistant, all that is necessary is to create a script to fire a custom event, then subscribe to that event in AppDaemon. The script would look something like this:
@ -1701,7 +1701,7 @@ time()
#### {% linkable_title Returns %}
A localised Python time object representing the current AppDaemon time.
A localized Python time object representing the current AppDaemon time.
#### {% linkable_title Parameters %}
@ -1725,7 +1725,7 @@ date()
#### {% linkable_title Returns %}
A localised Python time object representing the current AppDaemon date.
A localized Python time object representing the current AppDaemon date.
#### {% linkable_title Parameters %}
@ -1749,7 +1749,7 @@ datetime()
#### {% linkable_title Returns %}
A localised Python datetime object representing the current AppDaemon date and time.
A localized Python datetime object representing the current AppDaemon date and time.
#### {% linkable_title Parameters %}
@ -1764,7 +1764,7 @@ now = self.datetime()
### {% linkable_title convert_utc() %}
Home Assistant provides timestamps of several different sorts that may be used to gain additional insight into state changes. These timestamps are in UTC and are coded as ISO 8601 Combined date and time strings. `convert_utc()` will accept one of these strings and convert it to a localised Python datetime object representing the timestamp
Home Assistant provides timestamps of several different sorts that may be used to gain additional insight into state changes. These timestamps are in UTC and are coded as ISO 8601 Combined date and time strings. `convert_utc()` will accept one of these strings and convert it to a localized Python datetime object representing the timestamp
#### {% linkable_title Synopsis %}
@ -1774,7 +1774,7 @@ convert_utc(utc_string)
#### {% linkable_title Returns %}
`convert_utc(utc_string)` returns a localised Python datetime object representing the timestamp.
`convert_utc(utc_string)` returns a localized Python datetime object representing the timestamp.
#### {% linkable_title Parameters %}
@ -2072,7 +2072,7 @@ Note the timestamps in the log - AppDaemon believes it is now just before sunset
### {% linkable_title Speeding things up %}
Some Apps need to run for periods of a day or two for you to test all aspects. This can be time consuming, but Time Travel can also help here in two ways. The first is by speeding up time. To do this, simply use the `-t` option on the command line. This specifies the amount of time a second lasts while time travelling. The default of course is 1 second, but if you change it to `0.1` for instance, AppDaemon will work 10x faster. If you set it to `0`, AppDaemon will work as fast as possible and, depending in your hardware, may be able to get through an entire day in a matter of minutes. Bear in mind however, due to the threaded nature of AppDaemon, when you are running with `-t 0` you may see actual events firing a little later than expected as the rest of the system tries to keep up with the timer. To set the tick time, start AppDaemon as follows:
Some Apps need to run for periods of a day or two for you to test all aspects. This can be time consuming, but Time Travel can also help here in two ways. The first is by speeding up time. To do this, simply use the `-t` option on the command line. This specifies the amount of time a second lasts while time traveling. The default of course is 1 second, but if you change it to `0.1` for instance, AppDaemon will work 10x faster. If you set it to `0`, AppDaemon will work as fast as possible and, depending in your hardware, may be able to get through an entire day in a matter of minutes. Bear in mind however, due to the threaded nature of AppDaemon, when you are running with `-t 0` you may see actual events firing a little later than expected as the rest of the system tries to keep up with the timer. To set the tick time, start AppDaemon as follows:
```bash
$ appdaemon -t 0.1
@ -2105,4 +2105,4 @@ $ appdaemon -s "2016-06-06 19:16:00" -s "2016-06-06 20:16:00" -t 0
### {% linkable_title A Note on Times %}
Some Apps you write may depend on checking times of events relative to the current time. If you are time travelling this will not work if you use standard python library calls to get the current time and date etc. For this reason, always use the AppDamon supplied `time()`, `date()` and `datetime()` calls, documented earlier. These calls will consult with AppDaemon's internal time rather than the actual time and give you the correct values.
Some Apps you write may depend on checking times of events relative to the current time. If you are time traveling this will not work if you use standard python library calls to get the current time and date etc. For this reason, always use the AppDamon supplied `time()`, `date()` and `datetime()` calls, documented earlier. These calls will consult with AppDaemon's internal time rather than the actual time and give you the correct values.

2
source/_docs/ecosystem/backup/backup_github.markdown
View File

@ -133,7 +133,7 @@ Every time you run this script, you will be prompted for a comment to describe t
[Travis CI](https://travis-ci.org) is a continuous integration testing system that runs every time the code in your repository is updated and allows you to validate that your code works on a fresh install.
- [Authorise Travis CI](https://travis-ci.org/auth) to have access to your github repos.
- [Authorize Travis CI](https://travis-ci.org/auth) to have access to your github repos.
- Create the build script that travis will run to test your repo.
- Create a dummy secrets.yaml for Travis.

2
source/_docs/ecosystem/certificates/lets_encrypt.markdown
View File

@ -88,7 +88,7 @@ Type the following command to list your network interfaces:
$ ifconfig
```
You will receive an ouput similar to the image below:
You will receive an output similar to the image below:
<p class='img'>
<img src='/images/screenshots/ip-set.jpg' />

2
source/_docs/ecosystem/ios/notifications/actions.markdown
View File

@ -32,7 +32,7 @@ In advance of sending a notification:
When sending a notification:
1. Send a notification with `data.push.category` set to a pre-defined notification category identifer.
1. Send a notification with `data.push.category` set to a pre-defined notification category identifier.
2. Push notification delivered to device
3. User opens notification.
3. Action tapped

2
source/_docs/frontend/browsers.markdown
View File

@ -12,7 +12,7 @@ redirect_from: /getting-started/browsers/
Home Assistant requires a web browser to show the frontend and supports all major modern browsers. We don't test the web interface against all available browsers but this page tracks different browsers on various operating systems and should help you to pick a browser which works. The "Release" column contains the release number which were tested. This doen't mean that older or newer releases not work.
If a browser is listed as working but you are still having problems, it is possible that some add-on or extension may be the problem. Some add-ons or extenstion are known to cause issue with the frontend, but it's not possible to test them all. If you are having issues with the frontend displaying correctly, you should disable all your add-ons or extensions and enable them one at a time.
If a browser is listed as working but you are still having problems, it is possible that some add-on or extension may be the problem. Some add-ons or extension are known to cause issue with the frontend, but it's not possible to test them all. If you are having issues with the frontend displaying correctly, you should disable all your add-ons or extensions and enable them one at a time.
We would appreciate if you help to keep this page up-to-date and add feedback.

2
source/_docs/installation/docker.markdown
View File

@ -40,7 +40,7 @@ This will let you access your Home Assistant portal from http://localhost:8123,
### {% linkable_title Synology NAS %}
As Synology within DSM now supports Docker (with a neat UI), you can simply install Home Assistant using docker without the need for command-line. For details about the package (including compatability-information, if your NAS is supported), see https://www.synology.com/en-us/dsm/app_packages/Docker
As Synology within DSM now supports Docker (with a neat UI), you can simply install Home Assistant using docker without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see https://www.synology.com/en-us/dsm/app_packages/Docker
The steps would be:
* Install "Docker" package on your Synology NAS

2
source/_docs/installation/hassbian/customization.markdown
View File

@ -15,7 +15,7 @@ The tool is available by running `hassbian-config`.
### Install scripts
To view the available packages run `hassbian-config show` and `sudo hassbian-config install PACKAGENAME`.
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that's used with Amazon Echo, Google Home and Mycroft.ai.
- Install MariaDB. This script installs MariaDB and it's dependencies for use with the recorder component in Home Assistant. No database or database user is created during this setup and will need to be created manually.
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
- Install Libcec. Adds local [HDMI CEC support][cec]. *This scipt is currently brooken upstream since it currently doesn't build properly for Python >3.4*

2
source/_docs/installation/vagrant.markdown
View File

@ -30,7 +30,7 @@ $ cd home-assistant/virtualization/vagrant
```
<p class='note'>
The following instructions will assume you changed your working directory to be `home-assistant/virtualization/vagrant`. This is mandatory because Vagrant will look for informations about the running VM inside that folder and won't work otherwise
The following instructions will assume you changed your working directory to be `home-assistant/virtualization/vagrant`. This is mandatory because Vagrant will look for information about the running VM inside that folder and won't work otherwise
</p>
<p class='note'>

2
source/_docs/installation/virtualenv.markdown
View File

@ -65,7 +65,7 @@ _(If you're on a Debian based system, you will need to install Python virtual en
### {% linkable_title Notes %}
- In the future, if you want to start Home Assistant manually again, follow step 2, 3 and 5.
- It's recommanded to run Home Assistant as a dedicated user.
- It's recommended to run Home Assistant as a dedicated user.
<p class='info'>
Looking for more advanced guides? Check our [Rasbian guide](/docs/installation/raspberry-pi/) or the [other installation guides](/docs/installation/).

2
source/_docs/scripts.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Script Syntax"
description: "Documention for the Home Assistant Script Syntax."
description: "Documentation for the Home Assistant Script Syntax."
date: 2016-04-24 08:30 +0100
sidebar: true
comments: false

4
source/_docs/z-wave/control-panel.markdown
View File

@ -39,7 +39,7 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
* **Rename Node** sets a node's name - this won't happen immediately, and requires you to restart Home Assistant (not reboot) to set the new name
* **Heal Node** starts healing of the node.(Update neighbour list and update return routes)
* **Heal Node** starts healing of the node.(Update neighbor list and update return routes)
* **Test Node** sends no_op test messages to the node. This could in theory bring back a dead node.
@ -114,7 +114,7 @@ Underneath that you can select any supported configuration parameter to see the
## {% linkable_title Node user codes %}
If your node has user codes, you can set and delete them. The format is raw hex Ascii code. Bellow the input you will see your actual code. For normal nodes this is as follows:
If your node has user codes, you can set and delete them. The format is raw hex Ascii code. Below the input you will see your actual code. For normal nodes this is as follows:
```yaml
\x30 = 0
\x31 = 1

2
source/_docs/z-wave/device-specific.markdown
View File

@ -29,7 +29,7 @@ Home Assistant stores logs from Z-Wave in `OZW_log.txt` in the Home Assistant co
### {% linkable_title Aeotec Z-Stick %}
It's totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don't like this behaviour it can be turned off.
It's totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don't like this behavior it can be turned off.
Use the following example commands from a terminal session on your Pi where your Z-Wave stick is connected.

4
source/_docs/z-wave/installation.markdown
View File

@ -25,7 +25,7 @@ $ sudo /Applications/Python\ x.x/Install\ Certificates.command
```
<p class='note'>
The installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspbery Pi.
The installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspberry Pi.
</p>
## {% linkable_title Configuration %}
@ -198,7 +198,7 @@ Ensure you keep a backup of this key. If you have to rebuild your system and don
## {% linkable_title First Run %}
The (compilation and) installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspbery Pi. When you upgrade Home Assistant and python-openzwave is also upgraded, this will also result in a delay while the new version is compiled and installed.
The (compilation and) installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspberry Pi. When you upgrade Home Assistant and python-openzwave is also upgraded, this will also result in a delay while the new version is compiled and installed.
The first run after adding a device is when the `zwave` component will take time to initialize the entities, some entities may appear with incomplete names. Running a network heal may speed up this process.

2
source/_posts/2015-02-07-looking-at-the-past.markdown
View File

@ -15,7 +15,7 @@ Ever since the launch of Home Assistant you have been able to track the state of
* Recorder component that will record every event to a SQLite database
* History component that will query and aggregate the recorded events
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of today's release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.

2
source/_posts/2015-03-08-new-logo.markdown
View File

@ -7,7 +7,7 @@ date_formatted: March 8, 2015
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Organisation
categories: Organization
---
It is well known that you are either a good programmer or a good designer. It's rare you'll meet someone that is both. That's why it wasn't surprising to anyone that the logo that I made was mediocre &mdash; at best. Luckily, [Jeremy Geltman](http://jeremygeltman.com/) has come to the rescue and contributed a brand new logo for Home Assistant.

2
source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown
View File

@ -132,7 +132,7 @@ char* deviceId = "sensor01"; // Name of the sensor
char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published
int sensorPin = A0; // Pin to which the sensor is connected to
char buf[4]; // Buffer to store the sensor value
int updateInterval = 1000; // Interval in miliseconds
int updateInterval = 1000; // Interval in milliseconds
// MQTT server settings
IPAddress mqttServer(192, 168, 0, 12);

2
source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown
View File

@ -11,7 +11,7 @@ og_image: /images/supported_brands/glances.png
---
<img src='/images/supported_brands/glances.png' style='border:none; box-shadow: none; float: right;' height='80' />
Inspried by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
Inspired by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
<!--more-->

4
source/_posts/2016-04-17-updated-documentation.markdown
View File

@ -1,7 +1,7 @@
---
layout: post
title: "Updated documentation"
description: "We have reorganised our documentation which should make it easier to get started and develop for Home Assistant."
description: "We have reorganized our documentation which should make it easier to get started and develop for Home Assistant."
date: 2016-04-17 23:09:00 UTC
date_formatted: "April 17, 2016"
author: Paulus Schoutsen
@ -14,7 +14,7 @@ One of the main complaints that we receive is something along the lines "I read
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and [called it a website]. Back then we had a whopping [11 components](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown).
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organisation.
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
Today it has been almost 1.5 years since we started the website. We now have [264 components and platforms] under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.

4
source/_posts/2016-04-19-to-infinity-and-beyond.markdown
View File

@ -7,10 +7,10 @@ date_formatted: "April 19, 2016"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Organisation
categories: Organization
---
After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organisation on GitHub][gh-ha].
After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organization on GitHub][gh-ha].
On our journey we've reached many noteworthy milestones:

4
source/_posts/2016-04-21-bluetooth-lg-webos-tvs-and-roombas.markdown
View File

@ -11,9 +11,9 @@ categories: Release-Notes
og_image: /images/blog/2016-04-release-18/social.png
---
It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.
Since the last release we have moved all Home Assistant source code etc into it's own [organisation on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
Since the last release we have moved all Home Assistant source code etc into it's own [organization on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
<a href='/demo/'><img src='/images/blog/2016-04-release-18/media_player.png' style='box-shadow: none; border: 0;' /></a>

4
source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown
View File

@ -20,7 +20,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
When you use OwnTracks in standard _major move_ mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
<!--more-->
@ -31,7 +31,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
[MQTT]: /components/mqtt/#picking-a-broker
[OwnTracks]: /components/device_tracker.owntracks/
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
#### {% linkable_title A. Tell Home Assistant where your beacon is located %}

2
source/_posts/2016-06-23-usb-webcams-and-home-assistant.markdown
View File

@ -35,7 +35,7 @@ crw-rw----+ 1 root video 81, 0 Jun 23 08:05 /dev/video0
crw-rw----+ 1 root video 81, 1 Jun 23 08:36 /dev/video1
```
We need an additional software part to handle the cameras. [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the [RPM Fusion respository](http://rpmfusion.org/) enabled.
We need an additional software part to handle the cameras. [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the [RPM Fusion repository](http://rpmfusion.org/) enabled.
```bash
$ sudo dnf -y install motion

2
source/_posts/2016-07-19-visualizing-your-iot-data.markdown
View File

@ -103,7 +103,7 @@ plt.xlabel('Time line')
plt.savefig('sensor.png')
```
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are splitted into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are split into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
<p class='img'>
<img src='/images/blog/2016-07-reporting/mpl-sensor.png' />

2
source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
View File

@ -12,7 +12,7 @@ categories: Release-Notes
When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can [add it's own page to the frontend][custom-panels]. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you'll come up with!
Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can [add it's own page to the frontend][custom-panels]. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you'll come up with!
We have also seen an exciting trend of people starting to visualize their Internet of Things data using [Jupyter] Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the [blog] post by [@kireyeu] shows an advanced usecase while our [Notebooks][jupyter-notebooks] in the [Home Assistant Notebooks repository][jupyter-repo] cover the basics.

4
source/_posts/2016-08-07-optimizing-the-home-assistant-mobile-web-app.markdown
View File

@ -22,7 +22,7 @@ And thus started my journey to take a critical look at how the Home Assistant ap
I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.
The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. **On my Mac the app starts in 1400 miliseconds and on my Nexus 5x in ~6500 miliseconds (~4.5 times slower!).**
The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. **On my Mac the app starts in 1400 milliseconds and on my Nexus 5x in ~6500 milliseconds (~4.5 times slower!).**
<p class='img'>
<img
@ -30,7 +30,7 @@ The first thing to do is to measure. The Home Assistant front end is a mobile we
alt='Timeline of loading the front end in Home Assistant 0.18.2' />
</p>
Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 miliseconds (-35%) on my Mac and 2400 miliseconds (-63%) on my Nexus 5x. [Check out the demo here.][demo]
Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 milliseconds (-35%) on my Mac and 2400 milliseconds (-63%) on my Nexus 5x. [Check out the demo here.][demo]
<p class='img'>
<img

4
source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
View File

@ -27,10 +27,10 @@ Singleboard computers are very popular to run Home Assistant. To support this fa
There are countless bugfixes included in this release which will make your experience with the `climate` and the `cover` platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to [@turbokongen], [@pvizeli], [@djbanks], [@danielperna84], and others the improvements on the code and the frontend side is continuing...
### {% linkable_title API documentation %}
The [Home Assistant API Documentation](https://dev-docs.home-assistant.io/en/dev/) is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.
The [Home Assistant API Documentation](https://dev-docs.home-assistant.io/en/dev/) is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.
### {% linkable_title Configuration validation %}
The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to [@kellerza], [@fabaff], [@Teagan42], and [@pvizeli] for your effort!
The validation of the configuration is still on-going. Approximately 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to [@kellerza], [@fabaff], [@Teagan42], and [@pvizeli] for your effort!
### {% linkable_title All changes %}

2
source/_posts/2016-10-01-we-have-raspberry-image-now.markdown
View File

@ -1,7 +1,7 @@
---
layout: post
title: "We have a Raspberry Pi image now"
description: "Release of the Rapsberry Pi Image for Home Assistant"
description: "Release of the Raspberry Pi Image for Home Assistant"
date: 2016-10-01 01:00:00 -0400
date_formatted: "October 1, 2016"
author: Fredrik Lindqvist

2
source/_posts/2016-10-02-hacktoberfest.markdown
View File

@ -11,7 +11,7 @@ categories: Community
og_image: /images/blog/2016-10-hacktoberfest/social.png
---
Home Assistant will join this year for [Hacktoberfest], an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
Home Assistant will join this year for [Hacktoberfest], an event organized by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
Why contribute to Home Assistant:

2
source/_posts/2016-10-24-explaining-the-updater.markdown
View File

@ -7,7 +7,7 @@ date_formatted: "October 25, 2016"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Organisation
categories: Organization
---
On Saturday, we released [Home Assistant 0.31][0.31] which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.

2
source/_posts/2017-01-21-home-assistant-governance.markdown
View File

@ -7,7 +7,7 @@ date_formatted: "January 21, 2017"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Organisation
categories: Organization
---
### {% linkable_title UPDATE JAN 28, 2017 %}

2
source/_posts/2017-01-28-face-coffee-wink.markdown
View File

@ -120,7 +120,7 @@ Thanks to [@konikvranik] the [HDMI CEC][cec] integration got a huge update with
- Switch - Pilight: Implement echo config option ([@janLo])
- Core: Support customize in packages ([@kellerza])
- Switch - Flux: Allow disabling setting the brightness ([@rytilahti])
- Media player - Sonos: Add `is_coordinator`, set coordinator after join/unjoin, and no emtpy image ([@pvizeli], [@andrey-git], [@robbiet480])
- Media player - Sonos: Add `is_coordinator`, set coordinator after join/unjoin, and no empty image ([@pvizeli], [@andrey-git], [@robbiet480])
- Climate: Hold mode ([@Duoxilian])
- Switch - TPlink: No longer doing I/O in event bus ([@balloob])
- Light - Insteon local: Improve Insteon configuration ([@wardcraigj])

2
source/_posts/2017-03-11-repurpose-any-android-phone-as-ip-camera.markdown
View File

@ -190,7 +190,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
- Add multi contracts support for Hydroquebec ([@titilambert])
- Add Zwave refresh services ([@andrey-git])
- Add keep-alive feature to the generic thermostat ([@aronsky])
- Fix wake_on_lan for german version of Windows 10 (#6397) ([@siebert])
- Fix wake_on_lan for German version of Windows 10 (#6397) ([@siebert])
- flux led lib ([@danielhiversen])
- Cleanup async handling ([@pvizeli])
- Restore for automation entities ([@kellerza])

2
source/_posts/2017-04-01-thomas-krenn-award.markdown
View File

@ -29,7 +29,7 @@ Create an entry in our [Forum][forum]. Be creative and use your imagination.
- Dead line: April, 23 2017 - 23.59 UTC
- Voting period: April, 24th till April, 30 2017 - 23.59 UTC
The decision of the jury will be final. If there will be a dispute then the Top-5 commiter of the Home Assistant organisation on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the [Forum][forum] and on [Twitter][twitter].
The decision of the jury will be final. If there will be a dispute then the Top-5 committer of the Home Assistant organization on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the [Forum][forum] and on [Twitter][twitter].
Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.

2
source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
View File

@ -37,7 +37,7 @@ Also want to take a moment to thank Austin Andrews aka [Templarian] for his [Mat
## Breaking changes
- We were incorrectly treating groups named `default_view` as default views. Make sure you set `view: true` in the config for these groups. [#251 (frontend)](https://github.com/home-assistant/home-assistant-polymer/pull/251)
- The last release introduced a revamped LIFX platform. We only realised after deploy that this version does not work on Windows. We have added the old LIFX implementation back as `lifx_legacy`.
- The last release introduced a revamped LIFX platform. We only realized after deploy that this version does not work on Windows. We have added the old LIFX implementation back as `lifx_legacy`.
- We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. [#6688]
- Z-Wave cover workaround has been removed. Use device config instead. [#6832]

2
source/_posts/2017-04-15-ios.markdown
View File

@ -24,7 +24,7 @@ I received emails and forum posts almost every day, even when the app would go w
I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
It may not look the way that I wanted it to initially, with beautiful native UI components, but that's okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
Just because the app is released doesn't mean we are at the end of the road. It's only the beginning. There's plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that's pretty hard with how fast the project moves.

2
source/_posts/2017-04-30-hassbian-1.21-its-about-time.markdown
View File

@ -21,7 +21,7 @@ With the release of 1.21 a small problem with the OpenZWave build script wasn't
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the `hassbian-scripts` functionality from 1.1.
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that's used with Amazon Echo, Google Home and Mycroft.ai.
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
- Install Libcec. Adds local [HDMI CEC support][cec].
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.

2
source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown
View File

@ -17,7 +17,7 @@ og_image: /images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.
Saw the [announcement](/blog/2017/04/30/hassbian-1.21-its-about-time/) yesterday for HASSbian 1.21 and got super excited?
Today we'll flash the latest HASSbian to a [Raspbery Pi Zero W](https://www.raspberrypi.org/products/pi-zero/).
Today we'll flash the latest HASSbian to a [Raspberry Pi Zero W](https://www.raspberrypi.org/products/pi-zero/).
**With an added bonus** that besides for an USB cable for power, there's no need for any cables!
What you'll need:

2
source/_posts/2017-09-09-release-53.markdown
View File

@ -48,7 +48,7 @@ This release introduces a new input component: `input_text` contributed by @BioS
## {% linkable_title KNX %}
This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action [here](https://www.youtube.com/watch?v=JI0VJzlGpx4) and see the lights in action below:
This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunneling devices. In the background it uses asyncio communication. Check the climate integration in action [here](https://www.youtube.com/watch?v=JI0VJzlGpx4) and see the lights in action below:
<div class='videoWrapper'>
<iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen></iframe>

2
source/_posts/2017-11-12-tor.markdown
View File

@ -27,7 +27,7 @@ The most amazing part? It is super easy to set up!
## {% linkable_title Setting up Tor %}
Our [documentation](/docs/ecosystem/tor/) provides an detailled guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
Our [documentation](/docs/ecosystem/tor/) provides an detailed guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor`
2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines:

2
source/_posts/2017-11-18-release-58.markdown
View File

@ -19,7 +19,7 @@ The Hass.io release of 0.58 will be delayed by a couple of days because Pascal i
## {% linkable_title Translation update %}
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.
Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!

4
source/_posts/2017-12-03-release-59.markdown
View File

@ -27,14 +27,14 @@ With the Dominos Pizza integration made by [@wardcraigj] your home is now taking
</p>
## {% linkable_title Shopping list tweaks %}
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editting has been made easier.
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editing has been made easier.
## {% linkable_title Entity picker %}
[@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities.
<p class='img'>
<img src='/images/blog/2017-12-0.59/picker.png' alt='Screenshot of the Entity Picker.'>
Screenshot of the of the Enitity Picker.
Screenshot of the of the Entity Picker.
</p>
## {% linkable_title Hass.io Add-ons %}

2
source/developers/architecture.markdown
View File

@ -16,7 +16,7 @@ For more information about each part in this overview, <a href='/blog/2014/12/26
* Home Control is responsible for collecting information and controlling devices.
* Home Automation triggers commands based on user configurations.
* Smart Home triggers commands based on previous behaviour.
* Smart Home triggers commands based on previous behavior.
<p class='img'>
<a href='{{site_root}}/images/architecture/home_automation_landscape.png' name='landscape'>

4
source/developers/development_guidelines.markdown
View File

@ -25,9 +25,9 @@ The maximum line length comes directly from the [PEP8 style guide](https://www.p
Those points may require that you adjust your IDE or editor settings.
## {% linkable_title Our recommandations %}
## {% linkable_title Our recommendations %}
For some cases [PEPs](https://www.python.org/dev/peps/) don't make a statement. This section covers our recommendations about the code style. Those points were collected from the exisiting code and based on what contributors and developers were using the most. This is basically a majority decision, thus you may not agree with it. But we would like to encourage you follow those recommandations to keep the code unified.
For some cases [PEPs](https://www.python.org/dev/peps/) don't make a statement. This section covers our recommendations about the code style. Those points were collected from the existing code and based on what contributors and developers were using the most. This is basically a majority decision, thus you may not agree with it. But we would like to encourage you follow those recommendations to keep the code unified.
### {% linkable_title Quotes %}

2
source/developers/development_submitting.markdown
View File

@ -39,7 +39,7 @@ Submit your improvements, fixes, and new features to Home Assistant one at a tim
* On GitHub, navigate to the main page of the Home Assistant repository.
* In the "Branch" menu, choose the branch that contains your commits (from your fork).
* To the right of the Branch menu, click **New pull request**.
* Use the base branch dropdown menu to select the branch you'd like to merge your changes into, then use the compare branch drop-down menu to choose the topic branch you made your changes in. Make sure the Home Assistant branch matches with your forked branch (`dev`) else you will propose ALL committs between branches.
* Use the base branch dropdown menu to select the branch you'd like to merge your changes into, then use the compare branch drop-down menu to choose the topic branch you made your changes in. Make sure the Home Assistant branch matches with your forked branch (`dev`) else you will propose ALL commits between branches.
* Type a title and complete the provided description for your pull request.
* Click **Create pull request**.

2
source/developers/development_validation.markdown
View File

@ -11,7 +11,7 @@ footer: true
The `configuration.yaml` file contains the configuration options for components and platforms. We use [voluptuous](https://pypi.python.org/pypi/voluptuous) to make sure that the configuration provided by the user is valid. Some entries are optional or could be required to set up a platform or a component. Others must be a defined type or from an already-defined list.
We test the configuration to ensure that users have a great experience and minimise notifications if something is wrong with a platform or component setup before Home Assistant runs.
We test the configuration to ensure that users have a great experience and minimize notifications if something is wrong with a platform or component setup before Home Assistant runs.
Besides [voluptuous](https://pypi.python.org/pypi/voluptuous) default types, many custom types are available. For an overview, take a look at the [config_validation.py](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/config_validation.py) helper.

2
source/developers/documentation/standards.markdown
View File

@ -66,4 +66,4 @@ redirect_from: /getting-started/android/
---
```
Adding a redirect also applies if you move content around in the [documention](/docs/).
Adding a redirect also applies if you move content around in the [documentation](/docs/).

2
source/developers/multiple_instances.markdown
View File

@ -11,7 +11,7 @@ footer: true
# {% linkable_title This has been deprecated and is no longer supported. %}
Home Assistant supports running multiple synchronised instances using a master-slave model. Whenever `events.fire` or `states.set` is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.
Home Assistant supports running multiple synchronized instances using a master-slave model. Whenever `events.fire` or `states.set` is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.
<p class='img'>
<a href='/images/architecture/architecture-remote.png'>

2
source/developers/rest_api.markdown
View File

@ -515,7 +515,7 @@ Requires a JSON object that represents the API to cancel forwarding to.
}
```
It will return a message if event forwarding was cancelled successfully.
It will return a message if event forwarding was canceled successfully.
```json
{