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 01:06:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Fabian Affolter 2017-10-10 00:39:51 +02:00
commit 5d0a917cdd
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
112 changed files with 1014 additions and 352 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.markdown
View File

@ -9,7 +9,7 @@ This is the source for the [Home-Assistant.io website](https://home-assistant.io
## Setup
Setting up to contribute to documentation and the process for submitting pull requests is [explained here](https://home-assistant.io/developers/website/).
Setting up to contribute to documentation and the process for submitting pull requests is [explained here](https://home-assistant.io/developers/documentation/).
## Site preview

4
_config.yml
View File

@ -139,9 +139,9 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 54
current_minor_version: 55
current_patch_version: 0
date_released: 2017-09-23
date_released: 2017-10-07
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

2
sass/inuitcss/README.md
View File

@ -180,7 +180,7 @@ stone, and you are encouranged to override and experiment with them.
It is tempting to modify their vaules in the inuit.css submodule but this is
**not** the correct method for modifying inuit.css, and in doing so you will
prevent yourself from being able to update inuit.css’ core library. The correct
proceedure is to redefine that variable in `_vars.scss` found in the inuit.css
procedure is to redefine that variable in `_vars.scss` found in the inuit.css
web template. Let’s take an example…
In inuit.css’ `_defaults.scss` we find the following:

2
source/_addons/configurator.markdown
View File

@ -28,7 +28,7 @@ Screenshot of the HASS Configurator.
- Upload and download files.
- Stage and commit changes in Git repositories, create and switch between branches, push to remotes.
- Lists of available triggers, events, entities, conditions and services. Selected element gets inserted into the editor at the last cursor position.
- Restart Home Assitant directly with the click of a button. Reloading groups, automations etc. can be done as well. An API-password is required.
- Restart Home Assistant directly with the click of a button. Reloading groups, automations etc. can be done as well. An API-password is required.
- SSL support.
- Optional authentication and IP filtering for added security.
- Direct links to Home Assistant documentation and icons.

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. Normaly is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
- **interface** (*Required*): Inteface 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/_addons/dnsmasq.markdown
View File

@ -33,4 +33,4 @@ Configuration variables:
- **defaults** (*Required*): A list of dns server to forward default requests.
- **forwards** (*Optional*): A list of domains that will forward to a specific server.
- **hosts** (*Optional*): A list of hosts to resolve it static.
- **interface** (*Optional*): If a interface is set, it listen only on this interface. Need to set for resinos. Normaly is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
- **interface** (*Optional*): If a interface is set, it listen only on this interface. Need to set for resinos. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection.

2
source/_addons/mariadb.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true
---
Set up a [mariadb](https://mariadb.org/) SQL server. It support multible database, users and permission. If you want only connect from inside use `core-mariadb` as host address.
Set up a [mariadb](https://mariadb.org/) SQL server. It supports multiple databases, users and permission settings. If you want to only connect from inside home assistant use `core-mariadb` as the host address.
```json
{

40
source/_addons/rpc_shutdown.markdown Normal file
View File

@ -0,0 +1,40 @@
---
layout: page
title: "RPC Shutdown"
description: "Simple way for remote windows shutdowns."
date: 2017-09-25 14:00
sidebar: true
comments: false
sharing: true
footer: true
---
Allow to shutdown a computer with a service call from Home-Assistant.
```json
{
"computers": [
{
"alias": "test-pc",
"address": "192.168.0.1",
"credentials": "user%password"
}
]
}
```
- **computers** (*Required*): A list of computer object to shutdown from Home-Assistant.
- **computers/alias** (*Required*): Set a alias for this record and that is the name for the input.
- **computers/address** (*Required*): IP address or netbios name of the computer for shutdown.
- **computers/credentials** (*Required*): Credentials for logging into computer. Use a `%` as delimiter of username and password.
## {% linkable_title Home Assistant %}
Use the following inside Home Assistant service call to use it:
```yaml
service: hassio.addon_stdin
data:
addon: core_rpc_shutdown
input: test-pc
```

2
source/_addons/samba.markdown
View File

@ -38,4 +38,4 @@ Configuration variables:
- **map** (*Optional*): Control which folder will be expose. `config` is for Home Assistant configuration folder. `addons` for local custom repositiory. `share` is a folder that can access from add-ons and Home Assistant too. `backup` for access to snapshot files. `ssl` for certificate storage, be careful with this option! Defaults all to `true`, except for `ssl`.
- **username** (*Optional*): The username for logging in if guest login is not used.
- **password** (*Optional*): Password for `username`. An empty password is not supported.
- **interface** (*Optional*): Interface on that will start the share. Normaly is `eth0` for ethernet wired connection and `wlan0` for wireless connection.
- **interface** (*Optional*): Interface on that will start the share. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection.

2
source/_components/alexa.markdown
View File

@ -33,7 +33,7 @@ The built-in Alexa component allows you to integrate Home Assistant into Alexa/A
### {% linkable_title Requirements %}
Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are OK because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. When running Hass.io, using the [Let's Encrypt](/addons/lets_encrypt/) the and [Duck DNS](/addons/duckdns/) add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using [this AWS Lambda proxy for Alexa skills](https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230).
Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are OK because our skills will only run in development mode. Read more on [our blog][blog-lets-encrypt] about how to set up encryption for Home Assistant. When running Hass.io, using the [Let's Encrypt](/addons/lets_encrypt/) and [Duck DNS](/addons/duckdns/) add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using [this AWS Lambda proxy for Alexa skills](https://community.home-assistant.io/t/aws-lambda-proxy-custom-alexa-skill-when-you-dont-have-https/5230).
Additionally, note that at the time of this writing, your Alexa skill endpoint *must* accept requests over port 443 (Home Assistant default to 8123). There are two ways you can handle this:

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

@ -25,7 +25,7 @@ The requirement is that you have setup [Wink](/components/wink/).
- Window/Door sensors
- Motion sensors
- Ring Door bells (No hub required)
- Liquid presense sensors
- Liquid presence sensors
- Z-wave lock key codes
- Lutron connected bulb remote buttons
- Wink Relay buttons and presence detection

31
source/_components/cover.rflink.markdown
View File

@ -12,17 +12,18 @@ ha_category: Cover
ha_release: 0.55
---
The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
The `rflink` cover platform supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
First, you have to set up your [rflink hub](/components/rflink/).
After configuring the RFLink hub covers will be automatically discovered and added. Except the Somfy RTS devices.
### {% setting up a Somfy RTS device%}
### {% linkable_title Setting up a Somfy RTS device %}
You have to add the Somfy RTS manually with the supplied RFlinkLoader (Windows Only)
You have to add the Somfy RTS manually with the supplied RFlinkLoader (Windows only).
Press the Learn button on the original Somfy remote
enter the following code within 3 seconds. Your blinds will go up and down shortly
Press the Learn button on the original Somfy remote enter the following code within 3 seconds. Your blinds will go up and down shortly:
````
10;RTS;02FFFF;0412;3;PAIR;
@ -53,7 +54,7 @@ RTS Record: 14 Address: FFFFFF RC: FFFF
RTS Record: 15 Address: FFFFFF RC: FFFF
````
After configuring the RFLink Somfy RTS you have to add the cover to the configuration like any other RFlink device.
After configuring the RFLink Somfy RTS you have to add the cover to the `configuration.yaml` file like any other RFlink device.
RFLink cover ID's are composed of: protocol, id, and gateway. For example: `RTS_0100F2_0`.
@ -63,16 +64,16 @@ Assigning a name to a cover:
```yaml
# Example configuration.yaml entry
- platform: rflink
devices:
RTS_0100F2_0:
name: SunShade
bofumotor_455201_0f:
name: Sovrumsgardin
cover:
- platform: rflink
devices:
RTS_0100F2_0:
name: SunShade
bofumotor_455201_0f:
name: Sovrumsgardin
```
### Configuration variables:
Configuration variables:
- **automatic_add** (*Optional*): Automatically add new/unconfigured devices to Home Assistant if detected (default: True).
- **devices** (*Optional*): A list of devices with their name to use in the frontend.
@ -80,7 +81,7 @@ Assigning a name to a cover:
- **fire_event** (*Optional*): Set default `fire_event` for Rflink switch devices (see below).
- **signal_repetitions** (*Optional*): Set default `signal_repetitions` for Rflink switch devices (see below).
### Device configuration variables:
Device configuration variables:
- **name** (*Optional*): Name for the device, defaults to Rflink ID.
- **aliases** (*Optional*): Alternative Rflink ID's this device is known by.

4
source/_components/emulated_hue.markdown
View File

@ -96,7 +96,7 @@ homeassistant:
customize:
light.bedroom_light:
# Don't allow light.bedroom_light to be controlled by the emulated Hue bridge
emulated_hue: false
emulated_hue_hidden: false
light.office_light:
# Address light.office_light as "back office light"
emulated_hue_name: "back office light"
@ -104,7 +104,7 @@ homeassistant:
The following are attributes that can be applied in the `customize` section:
- **emulated_hue** (*Optional*): Whether or not the entity should be exposed by the emulated Hue bridge. The default value for this attribute is controlled by the `expose_by_default` option.
- **emulated_hue_hidden** (*Optional*): Whether or not the entity should be exposed by the emulated Hue bridge. Adding `emulated_hue_hidden: false` will expose the entity to Alexa. The default value for this attribute is controlled by the `expose_by_default` option.
- **emulated_hue_name** (*Optional*): The name that the emulated Hue will use. The default for this is the entity's friendly name.
### {% linkable_title Troubleshooting %}

2
source/_components/ffmpeg.markdown
View File

@ -18,7 +18,7 @@ You need the `ffmpeg` binary in your system path. On Debian 8 or Raspbian (Jessi
</p>
<p class='note'>
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fullfilled.
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fulfilled.
</p>
To set it up, add the following information to your `configuration.yaml` file:

6
source/_components/image_processing.opencv.markdown
View File

@ -15,7 +15,7 @@ ha_release: 0.47
[OpenCV](http://www.opencv.org) is an open source computer vision image and video processing library.
Some pre-defined classifiers can be found here: https://github.com/opencv/opencv/tree/master/data
Some pre-defined classifiers can be found [here](https://github.com/opencv/opencv/tree/master/data).
To setup OpenCV with Home Assistant, add the following section to your `configuration.yaml` file:
@ -34,7 +34,7 @@ image_processing:
- **source** array (*Required*): List of image sources.
- **entity_id** (*Required*): A camera entity id to get picture from.
- **name** (*Optional*): This parameter allows you to override the name of your `image_processing` entity.
- **classifier** (*Optional*): Dictionary of name to path to the classifier xml file. If this field is not provided, a face classifier will be downloaded from OpenCV's github repo.
- **classifier** (*Optional*): Dictionary of name to path to the classifier xml file. If this field is not provided, a face classifier will be downloaded from OpenCV's Github repo.
**classifier** may also be defined as a dictionary of names to classifier configurations:
@ -50,4 +50,4 @@ image_processing:
- **scale** (*Optional*): The scale to perform when processing, this is a `float` value that must be greater than or equal to `1.0`, default is `1.1`.
- **neighbors** (*Optional*): The minimum number of neighbors required for a match, default is `4`. The higher this number, the more picky the matching will be; lower the number, the more false positives you may experience.
If you would like to see the regions that OpenCV has detected, add this opencv camera to your config's custom_components/camera directory: [https://gist.github.com/Teagan42/bf4b941b34a79a3e184e149ff1efd82f](https://gist.github.com/Teagan42/bf4b941b34a79a3e184e149ff1efd82f)
If you would like to see the regions that OpenCV has detected, add this OpenCV camera to your config's `custom_components/camera` directory: [https://gist.github.com/Teagan42/bf4b941b34a79a3e184e149ff1efd82f](https://gist.github.com/Teagan42/bf4b941b34a79a3e184e149ff1efd82f)

2
source/_components/input_datetime.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: TODO
ha_release: 0.55
---
The `input_datetime` component allows the user to define date and time values that can be controlled via the frontend and can be used within automations and templates.

3
source/_components/input_number.markdown
View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.16
redirect_from: /components/input_slider/
---
The `input_number` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well.
@ -43,6 +44,8 @@ Configuration variables:
- **initial** (*Optional*): Initial value when Home Assistant starts. Defaults to 0.
- **step** (*Optional*): Step value for the slider. Defaults to 1.
- **mode** (*Optional*): Can specify `box`, or `slider`. Defaults to `slider`.
- **unit_of_measurement** (*Optional*): Unit of measurement in which the value of the slider is expressed in.
- **icon** (*Optional*): Icon to display in front of the box/slider in the frontend. Refer to the [Customizing devices](https://home-assistant.io/docs/configuration/customizing-devices/#possible-values) page for possible values.
## {% linkable_title Automation Examples %}

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

@ -33,7 +33,7 @@ Configuration variables:
- **devices** array (*Required*): A list of lights to use.
- **[mac address]** (*Required*): The bluetooth address of the switch.
- **name** (*Optional*): The custom name to use in the frontend.
- **api_key** (*Required*): The API key to acces the device.
- **api_key** (*Required*): The API key to access the device.
<p class='note'>
If you get an error looking like this:

2
source/_components/lock.nello.markdown
View File

@ -46,7 +46,7 @@ Every time someone rings the bell, a `nello_bell_ring` event will be fired.
Field | Description
----- | -----------
`address` | Postal address of the lock.
`date` | Date when the event occured.
`date` | Date when the event occurred.
`description` | Human readable string describing the event.
`location_id` | Nello ID of the location where the bell has been rung.
`short_id` | Shorter Nello ID.

23
source/_components/media_extractor.markdown
View File

@ -41,20 +41,29 @@ media_extractor:
music: bestaudio[ext=mp3]
```
This configuration sets query for all service calls like: ```{"entity_id": "media_player.my_sonos", "media_content_id": "https://soundcloud.com/bruttoband/brutto-11", "media_content_type": "music"}``` to 'bestaudio' with mp3 extention.
This configuration sets query for all service calls like to 'bestaudio' with the mp3 extension:
```json
{
"entity_id": "media_player.my_sonos",
"media_content_id": "https://soundcloud.com/bruttoband/brutto-11",
"media_content_type": "music"
}
```
Query examples with explanations:
* **bestvideo** - best video only stream
* **best** - best video + audio stream
* **bestaudio[ext=m4a]** - best audio stream with m4a extension
* **worst** - worst video + audio stream
* **bestaudio[ext=m4a]/bestaudio[ext=ogg]/bestaudio** - best m4a audio, otherwise best ogg audio and only then any best audio
* **bestvideo**: Best video only stream
* **best**: Best video + audio stream
* **bestaudio[ext=m4a]**: Best audio stream with m4a extension
* **worst**: Worst video + audio stream
* **bestaudio[ext=m4a]/bestaudio[ext=ogg]/bestaudio**: Best m4a audio, otherwise best ogg audio and only then any best audio
More info about queries [here](https://github.com/rg3/youtube-dl#format-selection)
### {% linkable_title Use the service %}
Go to the "Developer Tools," then to "Call Service," and choose `media_extractor/play_media` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE."
Use <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services** from the **Developer Tools**. Choose `media_extractor` from the dropdown menu **Domain** and `play_media` from **Service**, enter something like the JSON sample from above into the **Service Data** field, and hit **CALL SERVICE**.
This will download the file from the given URL.

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

@ -43,7 +43,7 @@ Configuration variables:
- **port** (*Optional*): The port number. Defaults to 80.
- **password** (*Optional*): PIN code of the Internet Radio. Defaults to 1234.
Some models use a seperate port (2244) for API access, this can be verified by visiting http://[host]:[port]/device.
Some models use a separate port (2244) for API access, this can be verified by visiting http://[host]:[port]/device.
In case your device (friendly name) is called *badezimmer*, an example automation can look something like this:

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

@ -14,7 +14,7 @@ ha_release: 0.37
The [Discord service](https://discordapp.com/) is a platform for the notify component. This allows components to send messages to the user using Discord.
In order to get a token you need to go to the [Discord My Apps page](https://discordapp.com/developers/applications/me) and create a new application. Once the application is ready, create a [bot](https://discordapp.com/developers/docs/topics/oauth2#bots) user (**Create a Bot User**) and activate **Require OAuth2 Code Grant**. Retreive the **Client ID** and the (hidden) **Token** of your bot for later.
In order to get a token you need to go to the [Discord My Apps page](https://discordapp.com/developers/applications/me) and create a new application. Once the application is ready, create a [bot](https://discordapp.com/developers/docs/topics/oauth2#bots) user (**Create a Bot User**) and activate **Require OAuth2 Code Grant**. Retrieve the **Client ID** and the (hidden) **Token** of your bot for later.
When setting up the application you can use this [icon](https://home-assistant.io/demo/favicon-192x192.png).

25
source/_components/recorder.markdown
View File

@ -2,7 +2,7 @@
layout: page
title: "Recorder"
description: "Instructions how to configure the data recorder for Home Assistant."
date: 2016-05-21 09:00
date: 2017-09-24 09:00
sidebar: true
comments: false
sharing: true
@ -27,7 +27,8 @@ recorder:
Configuration variables:
- **purge_days** (*Optional*): Delete events and states older than x days. The purge task runs every 2 days, starting from when Home Assistant is started if you restart your instance more frequently than the purge will never take place.
- **purge_interval** (*Optional*): (days) Enable scheduled purge of older events and states. The purge task runs every x days, starting from when Home Assistant is started. If you restart your instance more frequently, than the purge will never take place. You can use [service](#service) call `recorder.purge` when needed.
- **purge_keep_days** (*Required with `purge_interval`*): Specify number of history days to keep in recorder database after purge.
- **exclude** (*Optional*): Configure which components should be excluded from recordings.
- **entities** (*Optional*): The list of entity ids to be excluded from recordings.
- **domains** (*Optional*): The list of domains to be excluded from recordings.
@ -42,7 +43,8 @@ Define domains and entities to `exclude` (aka. blacklist). This is convenient wh
```yaml
# Example configuration.yaml entry with exclude
recorder:
purge_days: 5
purge_interval: 2
purge_keep_days: 5
db_url: sqlite:///home/user/.homeassistant/test
exclude:
domains:
@ -85,6 +87,19 @@ recorder:
If you only want to hide events from e.g. your history, take a look at the [`history` component](/components/history/). Same goes for logbook. But if you have privacy concerns about certain events or neither want them in history or logbook, you should use the `exclude`/`include` options of the `recorder` component, that they aren't even in your database. That way you can save storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`).
### {% linkable_title Service `purge` %}
Call the service `recorder.purge` to start purge task, which deletes events and states older than x days, according to `keep_days` service data (*Required*)
Automation [action](https://home-assistant.io/getting-started/automation-action/) example:
```yaml
action:
service: recorder.purge
data:
keep_days: 5
```
## Custom database engines
| Database engine | `db_url` |
@ -109,14 +124,14 @@ Not all Python bindings for the chosen database engine can be installed directly
For MariaDB you may have to install a few dependencies. On the Python side we use the `mysqlclient`:
```bash
$ sudo apt-get install libmariadbclient-dev
$ sudo apt-get install libmariadbclient-dev libssl-dev
$ pip3 install mysqlclient
```
For MySQL you may have to install a few dependencies. You can choose between `pymysql` and `mysqlclient`:
```bash
$ sudo apt-get install default-libmysqlclient-dev
$ sudo apt-get install default-libmysqlclient-dev libssl-dev
$ pip3 install mysqlclient
```

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

@ -132,7 +132,7 @@ AQI | Status | Description
201 - 300 | **Very unhealthy** | Health warnings of emergency conditions. The entire population is more likely to be affected
301+ | **Hazardous** | Health alert: everyone may experience more serious health effects
### Air Polution Level
### Air Pollution Level
**Description:** This sensor displays the associated `Status` (from the above
table) for the current AQI.

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

@ -70,7 +70,7 @@ $ python3
{'thing': 'ha-sensor', 'created': '2015-12-10T09:46:08.559Z', 'content': {'humiditiy': 81, 'temperature': 23}}
```
Recieve the latest dweet.
Receive the latest dweet.
```bash
>>> dweepy.get_latest_dweet_for('ha-sensor')

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

@ -17,7 +17,7 @@ The `vera` platform allows you to get data from your [Vera](http://getvera.com/)
They will be automatically discovered if the vera component is loaded.
Please note that some vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that vera will send alerts (email messages ot txts) when they are _armed_ an change state.
Please note that some vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that vera will send alerts (email messages to txts) when they are _armed_ an change state.
Home Assistant will display the state of these sensors regardless of the _armed_ state.

2
source/_components/thethingsnetwork.markdown
View File

@ -21,7 +21,7 @@ The Things network support various integrations to make the data available:
|---|---|
| [MQTT](https://www.thethingsnetwork.org/docs/applications/mqtt/) | |
| [Storage](https://www.thethingsnetwork.org/docs/applications/storage/) | [`thethingsnetwork`](/component/sensor.thethingsnetwork/) |
| [HTTP](https://www.thethingsnetwork.org/docs/applications/http/} | |
| [HTTP](https://www.thethingsnetwork.org/docs/applications/http/) | |
### {% linkable_title Setup %}

2
source/_components/tts.yandextts.markdown
View File

@ -29,7 +29,7 @@ Configuration variables:
- **language** (*Optional*): The language to use. Defaults to `en-US`. Supported `en-US`, `ru-RU`, `uk-UK`, `tr-TR`.
- **codec** (*Optional*): Audio codec. Default is `mp3`. Supported us `mp3`, `wav`, `opus`.
- **voice** (*Optional*): Speaker voice. Default is `zahar`. Supported female voices are `jane`, `oksana`, `alyss`, `omazh` and male voices are `zahar` and `ermil`.
- **emotion** (*Optional*): Speaker emotional intonation. Default is `neutral`. Also supported are `good` (freindly) and `evil` (angry)
- **emotion** (*Optional*): Speaker emotional intonation. Default is `neutral`. Also supported are `good` (friendly) and `evil` (angry)
- **speed** (*Optional*): Speech speed. Default value is `1`. Highest speed is `3` and lowest `0,1`
Please check the [API documentation](https://tech.yandex.com/speechkit/cloud/doc/guide/concepts/tts-http-request-docpage/) for details. It seems that the English version of documentation is outdated. You could request an API key [by email](https://tech.yandex.com/speechkit/cloud/) or [online](https://developer.tech.yandex.ru/).

29
source/_components/upnp.markdown
View File

@ -23,13 +23,34 @@ To integrate this into Home Assistant, add the following section to your `config
```yaml
# Example configuration.yaml entry with custom external portal
upnp:
external_port: 80
ports:
hass: 8000
8080: 8080
```
If you which to have the statistics without having port mapping done through IGD, add the option **port_mapping**.
Configuration variables:
- **external_port** (*Optional*): Expose Home Assistant to the internet over this TCP port. Defaults to Home Assistant configured port.
- **port_mapping** (*Optional*): Disables port mapping maintains the network statistics sensors)
- **unit** (*Optional*): UPnP sensors unit. Valid units are 'Bytes', 'KBytes', 'MBytes' and 'GBytes'.
{% configuration binary_sensor.template %}
ports:
description: Map of ports to map from internal to external. Pass 'hass' as internal port to use the port Home Assistant runs on.
required: false
type: map
default: open same port on external router as that HASS runs locally and forwards it.
port_mapping:
description: If the component should try to map ports.
required: false
type: boolean
default: false
units:
description: Define the units used for the UPNP sensor. Possible values are Bytes, KBytes, MBytes, GBytes.
required: false
type: string
default: Mbytes
local_ip:
description: The local IP address of the computer running Home Assistant.
required: false
type: string
default: Try to auto-detect IP of host.
{% endconfiguration %}

2
source/_cookbook/sonos_say.markdown
View File

@ -51,6 +51,6 @@ automation:
data:
sonos_entity: media_player.office
volume: 0.5
message: 'Your husband comming home!'
message: 'Your husband coming home!'
delay: '00:00:05'
```

17
source/_data/glossary.yml Normal file
View File

@ -0,0 +1,17 @@
- topic: Platform
description: A platform makes the connection to a specific software or hardware platform. The `pushbullet` platform works with the service from pushbullet.com.
- topic: Component
description: "The components provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications."
- topic: Service
description: "[Services](/docs/scripts/service-calls/) are called to perform actions."
- topic: Event
description: When somethings happen.
- topic: Entity
description: An entity is the representation of a single device, unit or web service.
- topic: Device
description: "Usually this is a physical unit which can do or observe something."
- topic: hass
description: "Often used abbreviation for Home Assistant."
- topic: Discovery
description: The automatic setup of zeroconf/mDNS and uPnP devices after they are discovered.

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

@ -46,7 +46,7 @@ If HA does not start, check the log file output for errors at `/var/opt/homeassi
### {% linkable_title Extra: Running commands before hass executes %}
If any commands need to run before executing hass (like loading a virutal environment), put them in PRE_EXEC. This command must end with a semicolon.
If any commands need to run before executing hass (like loading a virtual environment), put them in PRE_EXEC. This command must end with a semicolon.
### {% linkable_title Daemon script %}

8
source/_docs/autostart/systemd.markdown
View File

@ -16,14 +16,14 @@ Newer linux distributions are trending towards using `systemd` for managing daem
$ ps -p 1 -o comm=
```
If the preceding command returns the string `systemd`, you are likely using `systemd`.
If the preceding command returns the string `systemd`, continue with the instructions below.
If you want Home Assistant to be launched automatically, an extra step is needed to setup `systemd`. A service file is needed to control Home Assistant with `systemd`. The template below should be created using a text editor. Note, root permissions via `sudo` will likely be needed. The following should be noted to modify the template:
A service file is needed to control Home Assistant with `systemd`. The template below should be created using a text editor. Note, root permissions via `sudo` will likely be needed. The following should be noted to modify the template:
- `ExecStart` contains the path to `hass` and this may vary. Check with `whereis hass` for the location.
- If running Home Assistant in a Python virtual environment or a Docker container, please skip to section below.
- For most systems, the file is `/etc/systemd/system/home-assistant@[your user].service` with [your user] replaced by the user account that Home Assistant will run as - normally `homeassistant`. In particular, this is the case for Ubuntu 16.04.
- If unfamiliar with command-line text editors, `sudo nano -w [filename]` can be used with `[filename]` replaced with the full path to the file. Ex. `sudo nano -w /etc/systemd/system/home-assistant@[your user].service`. After text entered, press CTRL-X then press Y to save and exit.
- If you're running Home Assistant in a Python virtual environment or a Docker container, please skip to the appropriate template listed below.
```
[Unit]
@ -78,6 +78,8 @@ ExecStopPost=/usr/bin/docker rm -f home-assistant-%i
WantedBy=multi-user.target
```
### Next Steps
You need to reload `systemd` to make the daemon aware of the new configuration.
```bash

2
source/_docs/autostart/upstart.markdown
View File

@ -35,7 +35,7 @@ Upstart will launch init scripts that are located in the directory `/etc/init.d/
#
# Installation:
# 1) If any commands need to run before executing hass (like loading a
# virutal environment), put them in PRE_EXEC. This command must end with
# virtual environment), put them in PRE_EXEC. This command must end with
# a semicolon.
# 2) Set RUN_AS to the username that should be used to execute hass.
# 3) Copy this script to /etc/init.d/

2
source/_docs/configuration/customizing-devices.markdown
View File

@ -61,7 +61,7 @@ homeassistant:
| `homebridge_name` | Name of the entity in `HomeBridge`.
| `hidden` | Set to `true` to hide the entity.
| `homebridge_hidden` | Set to `true` to hide the entity from `HomeBridge`.
| `emulated_hue` | Set to `false` to hide the entity from emulated_hue.
| `emulated_hue_hidden` | Set to `true` to hide the entity from `emulated_hue`.
| `entity_picture` | Url to use as picture for entity.
| `icon` | Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com). Prefix name with `mdi:`, ie `mdi:home`.
| `assumed_state` | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon.

8
source/_docs/configuration/events.markdown
View File

@ -27,8 +27,8 @@ Event `state_changed` is fired when a state changes. Both `old_state` and `new_s
Field | Description
----- | -----------
`entity_id` | Entity ID of the changed entity. Example: `light.kitchen`
`old_state` | The previous state of the entity before it changed. This field is ommitted if the entity is new.
`new_state` | The new state of the entity. This field is ommitted if the entity is removed from the state machine.
`old_state` | The previous state of the entity before it changed. This field is omitted if the entity is new.
`new_state` | The new state of the entity. This field is omitted if the entity is removed from the state machine.
### {% linkable_title Event `time_changed` %}
@ -68,11 +68,11 @@ Field | Description
### {% linkable_title Event `platform_discovered` %}
Event `platform_discovered` is fired when a new platform has been discovered by the discovery component.
Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/components/discovery/) component.
Field | Description
----- | -----------
`service` | The service that is discovered. Example: `zwave`.
`service` | The platform that is discovered. Example: `zwave`.
`discovered` | Dictionary containing discovery information. Example: `{ "host": "192.168.1.10", "port": 8889}`.

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

@ -24,7 +24,7 @@ homeassistant:
The package configuration can include: `switch`, `light`, `automation`, `groups` or the majority of the Home Assistant components.
It can be specified inline or in a seperate YAML file using `!include`.
It can be specified inline or in a separate YAML file using `!include`.
Inline example, main `configuration.yaml`:

4
source/_docs/configuration/platform_options.markdown
View File

@ -10,7 +10,7 @@ footer: true
redirect_from: /topics/platform_options/
---
Any component that is based on the entity component allows various extra options to be set per platform.
Some components or platforms (those that are based on the [entity](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/helpers/entity.py) class) allows various extra options to be set.
### {% linkable_title Entity namespace %}
@ -25,7 +25,7 @@ light:
### {% linkable_title Scan Interval %}
Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` config key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds.
Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` configuration key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds.
```yaml
# Example configuration.yaml entry to poll Hue lights every 10 seconds.

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

@ -51,7 +51,7 @@ script:
{% endif %}{% endraw %}
```
[Jinja2](http://jinja.pocoo.org/) supports a width variety of operations:
[Jinja2](http://jinja.pocoo.org/) supports a wide variety of operations:
- [Mathematical operation](http://jinja.pocoo.org/docs/dev/templates/#math)
- [Comparisons](http://jinja.pocoo.org/docs/dev/templates/#comparisons)

11
source/_docs/configuration/yaml.markdown
View File

@ -28,10 +28,15 @@ notify:
The basics of YAML syntax are block collections and mappings containing key-value pairs. Each item in a collection starts with a `-` while mappings have the format `key: value`. If you specify duplicate keys, the last value for a key is used. This is somewhat similar to a Hashtable or more specifically a dictionary in Python. These can be nested as well.
Note that indentation (just like in Python) is an important part of specifying relationships using YAML. Things that are indented are nested "inside" things that are one level higher. So in the above example, `platform: pushbullet` is a property of (nested inside) the `notify` component.
Note that indentation is an important part of specifying relationships using YAML. Things that are indented are nested "inside" things that are one level higher. So in the above example, `platform: pushbullet` is a property of (nested inside) the `notify` component.
Getting the right indentation can be tricky if you're not using an editor with a fixed width font. Tabs are not allowed to be used for indentation. Convention is to use 2 spaces for each level of indentation.
You can use the online service [YAMLLint](http://www.yamllint.com/) to check if your YAML syntax is correct before loading it into Home Assistant which will save you some time. If you do so, be aware that this is a third-party service and is not maintained by the Home Assistant community. *Please pay attention on not storing private data (passwords, api-keys, etc.) directly in that file.*
Private data can be stored in a [seperate file](/docs/configuration/secrets/) or in [environmental variables](/docs/configuration/yaml/#using-environment-variables), which circumvents this problem of security.
You can use the online service [YAMLLint](http://www.yamllint.com/) to check if your YAML syntax is correct before loading it into Home Assistant which will save you some time. If you do so, be aware that this is a third-party service and is not maintained by the Home Assistant community.
<p class='note'>
Please pay attention on not storing private data (passwords, API keys, etc.) directly in your `configuration.yaml` file. Private data can be stored in a [separate file](/docs/configuration/secrets/) or in [environmental variables](/docs/configuration/yaml/#using-environment-variables), which circumvents this problem of security.
</p>
Text following a `#` are comments and are ignored by the system.

2
source/_docs/ecosystem/appdaemon.markdown
View File

@ -24,7 +24,7 @@ AppDaemon is not meant to replace Home Assistant Automations and Scripts, rather
- Durable variables and state - Variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened.
- All the power of Python - use any of Python's libraries, create your own modules, share variables, refactor and re-use code, create a single App to do everything, or multiple Apps for individual tasks - nothing is off limits!
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatsoever about what it is controlling, reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner. The bulk of the work after that was adding additonal functions to make things that were already possible easier.
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatsoever about what it is controlling, reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner. The bulk of the work after that was adding additional functions to make things that were already possible easier.
# How it Works

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

@ -495,7 +495,7 @@ Note: `old` and `new` can be used singly or together.
##### {% linkable_title duration = <seconds> (optional) %}
If duration is supplied as a parameter, the callback will not fire unless the state listened for is maintained for that number of seconds. This makes the most sense if a specific attribute is specified (or the default os `state` is used), an in conjunction with the `old` or `new` parameters, or both. When the callback is called, it is supplied with the values of `entity`, `attr`, `old` and `new` that were current at the time the actual event occured, since the assumption is that none of them have changed in the intervening period.
If duration is supplied as a parameter, the callback will not fire unless the state listened for is maintained for that number of seconds. This makes the most sense if a specific attribute is specified (or the default os `state` is used), an in conjunction with the `old` or `new` parameters, or both. When the callback is called, it is supplied with the values of `entity`, `attr`, `old` and `new` that were current at the time the actual event occurred, since the assumption is that none of them have changed in the intervening period.
```python
def my_callback(self, **kwargs):
@ -643,7 +643,7 @@ Delay, in seconds before the callback is invoked.
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -677,7 +677,7 @@ A Python `time` object that specifies when the callback will occur. If the time
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -715,7 +715,7 @@ A Python `datetime` object that specifies when the callback will occur.
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -754,7 +754,7 @@ A Python `time` object that specifies when the callback will occur. If the time
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -792,7 +792,7 @@ A Python `time` object that specifies when the callback will occur, the hour com
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -829,7 +829,7 @@ A Python `time` object that specifies when the callback will occur, the hour and
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -871,7 +871,7 @@ After the initial callback has occurred, another will occur every `repeat` secon
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -944,7 +944,7 @@ All of the scheduler calls above support 2 additional optional arguments, `rando
- `random_start` - start of range of the random time
- `random_end` - end of range of the random time
`random_start` must always be numerically lower than `random_end`, they can be negative to denote a random offset before and event, or positive to denote a random offset after an event. The event would be a an absolute or relative time or sunrise/sunset depending on whcih scheduler call you use and these values affect the base time by the spcified amount. If not specified, they will default to `0`.
`random_start` must always be numerically lower than `random_end`, they can be negative to denote a random offset before and event, or positive to denote a random offset after an event. The event would be a an absolute or relative time or sunrise/sunset depending on which scheduler call you use and these values affect the base time by the spcified amount. If not specified, they will default to `0`.
For example:
@ -987,7 +987,7 @@ The time in seconds that the callback should be delayed after sunrise. A negativ
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}
@ -1030,7 +1030,7 @@ The time in seconds that the callback should be delayed after sunrise. A negativ
##### {% linkable_title \*\*kwargs %}
Arbitary keyword parameters to be provided to the callback function when it is invoked.
Arbitrary keyword parameters to be provided to the callback function when it is invoked.
#### {% linkable_title Examples %}

2
source/_docs/ecosystem/appdaemon/configuration.markdown
View File

@ -36,7 +36,7 @@ class = HelloWorld
- `logfile` (optional) is the path to where you want `AppDaemon` to keep its main log. When run from the command line this is not used - log messages come out on the terminal. When running as a daemon this is where the log information will go. In the example above I created a directory specifically for AppDaemon to run from, although there is no reason you can't keep it in the `appdaemon` directory of the cloned repository. If `logfile = STDOUT`, output will be sent to stdout instead of stderr when running in the foreground, if not specified, output will be sent to STDOUT.
- `errorfile` (optional) is the name of the logfile for errors - this will usually be errors during compilation and execution of the apps. If `errorfile = STDERR` errors will be sent to stderr instead of a file, if not specified, output will be sent to STDERR.
- `app_dir` (optional) is the directory the apps are placed in. If not specified, AppDaemon will look first in `~/.homeassistant` then `/etc/appdaemon` for a subdirectory named `apps`
- `threads` - the number of dedicated worker threads to create for running the apps. Note, this will bear no resembelance to the number of apps you have, the threads are re-used and only active for as long as required to tun a particular callback or initialization, leave this set to 10 unless you experience thread starvation
- `threads` - the number of dedicated worker threads to create for running the apps. Note, this will bear no resemblance to the number of apps you have, the threads are re-used and only active for as long as required to tun a particular callback or initialization, leave this set to 10 unless you experience thread starvation
- `latitude`, `longitude`, `elevation`, `timezone` - should all be copied from your Home Assistant configuration file
- `cert_path` (optional) - path to root CA cert directory - use only if you are using self signed certs.

2
source/_docs/ecosystem/appdaemon/tutorial.markdown
View File

@ -35,7 +35,7 @@ So why `AppDaemon`? AppDaemon is not meant to replace Home Assistant Automations
- Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened
- All the power of Python - use any of Python's libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additonal functions to make things that were already possible easier.
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additional functions to make things that were already possible easier.
## {% linkable_title How it Works %}

2
source/_docs/ecosystem/appdaemon/windows.markdown
View File

@ -19,4 +19,4 @@ AppDaemon can be installed exactly as per the instructions for every other versi
## {% linkable_title Windows Under the Linux Subsystem %}
Windows 10 now supports a full Linux bash environment that is capable of running Python. This is essentially an Ubuntu distribution and works extremely well. It is possible to run AppDaemon in exactly the same way as for Linux distributions, and none of the above Windows Caveats apply to this version. This is the reccomended way to run AppDaemon in a Windows 10 and later environment.
Windows 10 now supports a full Linux bash environment that is capable of running Python. This is essentially an Ubuntu distribution and works extremely well. It is possible to run AppDaemon in exactly the same way as for Linux distributions, and none of the above Windows Caveats apply to this version. This is the recommended way to run AppDaemon in a Windows 10 and later environment.

4
source/_docs/ecosystem/backup/backup_dropbox.markdown
View File

@ -18,7 +18,7 @@ You need two parts in order to get it working correctly.
Become the user that run Home Assistant.
- A seperate Python script that syncs a specific folder. Which can be found [here](https://gist.github.com/riemers/31e3350041fd3e47e489cbc811209d6f)
- A separate Python script that syncs a specific folder. Which can be found [here](https://gist.github.com/riemers/31e3350041fd3e47e489cbc811209d6f)
- The excellent [dropbox uploader script](https://github.com/andreafabrizi/Dropbox-Uploader/blob/master/dropbox_uploader.sh) you can grab the .sh file only.
Download those files to a folder of your liking, after that edit both files and change paths accordingly.
@ -46,7 +46,7 @@ Do note, this will **backup your passwords to Dropbox**.
### {% linkable_title Automate the backup %}
So you just made a full backup, next time you want it to be done automaticly. Since your database can change and so do other files over time.
So you just made a full backup, next time you want it to be done automatically. Since your database can change and so do other files over time.
Add it to your crontab, edit the **path/to** part.
```bash

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

@ -30,7 +30,7 @@ Some best practices to consider before putting your configuration on GitHub:
- Extensive use of [secrets.yaml](https://home-assistant.io/topics/secrets/) to hide sensitive information like usernames, passwords, device information, and location
- Exclusion of some files, including `secrets.yaml` and device-specific information using a [`.gitignore`](https://git-scm.com/docs/gitignore) file
- Regularly commiting your configuration to GitHub to make sure that your backup is up to date
- Regularly committing your configuration to GitHub to make sure that your backup is up to date
- Use a README.md to document your configuration and include screenshots of your Home Assistant GUI
### {% linkable_title Step 1: Installing and Initializing Git %}
@ -127,7 +127,7 @@ git push origin master
exit
```
Every time you run this script, you will be prompted for a comment to describe the change(s) that you are commiting. This comment will be displayed beside each changed file on GitHub and will be stored after each commit. You will also be asked to enter your GitHub username and password (or ssh key passphrase if you use [GitHub with ssh](https://help.github.com/categories/ssh/)).
Every time you run this script, you will be prompted for a comment to describe the change(s) that you are committing. This comment will be displayed beside each changed file on GitHub and will be stored after each commit. You will also be asked to enter your GitHub username and password (or ssh key passphrase if you use [GitHub with ssh](https://help.github.com/categories/ssh/)).
### {% linkable_title Step 7: Configuration file testing %}
@ -162,7 +162,7 @@ home_elevation: 0
### {% linkable_title Extra commands %}
You can enter these commands to get a list of the files in your local git repository and a status of files that have changed but not commited yet:
You can enter these commands to get a list of the files in your local git repository and a status of files that have changed but not committed yet:
```bash

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

@ -101,7 +101,7 @@ Change below path to where you placed the `usb_backup.sh` and run the following
### {% linkable_title Auto mount %}
This does not automaticly mount your USB drive at boot. You need to do that manually or add a line to your `/etc/fstab` file.
This does not automatically mount your USB drive at boot. You need to do that manually or add a line to your `/etc/fstab` file.
If your drive is on `/dev/sda1`, you could add a entry to your `/etc/fstab` like so:

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

@ -24,7 +24,7 @@ This guide was added by mf_social on 16/03/2017 and was valid at the time of wri
* You are not currently running anything on port 80 on your network (you'd know if you were).
* If you are not using Home Assistant on a Debian/Raspian/Hassbian system you will be able to convert any of the terminology I use in to the correct syntax for your system.
* You understand that this is a 'guide' covering the general application of these things to the general masses and there are things outside of the scope of it, and it does not cover every eventuality (although I have made some notes where people may stumble). Also, I have used some turns of phrase to make it easier to understand for the novice reader which people of advanced knowledge may say is innacurate. My goal here is to get you through this guide with a satisfactory outcome and have a decent understanding of what you are doing and why, not to teach you advanced internet communication protocols.
* Each step presumes you have fully completed the previous step succesfully, so if you did an earlier step following a different guide, please ensure that you have not missed anything out that may affect the step you have jumped to, and ensure that you adapt any commands to take in to account different file placements from other guides.
* Each step presumes you have fully completed the previous step successfully, so if you did an earlier step following a different guide, please ensure that you have not missed anything out that may affect the step you have jumped to, and ensure that you adapt any commands to take in to account different file placements from other guides.
Steps we will take:
@ -358,11 +358,11 @@ If you were previously using a webapp on your phone/tablet to access your Home A
https://home-assistant.io/docs/frontend/mobile/
```
All done? Accessing your Home Assistant from across the world with your DuckDNS URL and a lovely secure logo on your browser? Ace! Now let's clean up our port forwards so that we are only exposing the parts of our network that are absolutely neccesary to the outside world.
All done? Accessing your Home Assistant from across the world with your DuckDNS URL and a lovely secure logo on your browser? Ace! Now let's clean up our port forwards so that we are only exposing the parts of our network that are absolutely necessary to the outside world.
### {% linkable_title 6 - Clean up port forwards %}
In step 2 we created a port forwarding rule called `ha_test`. This opens port 8123 to the world, and is no longer neccessary.
In step 2 we created a port forwarding rule called `ha_test`. This opens port 8123 to the world, and is no longer necessary.
Go to your router's configuration pages and delete the `ha_test` rule.
@ -402,7 +402,7 @@ $ sudo apt-get install ssl-cert-check
```
<p class='note'>
In cases where, for whatever reason, apt-get installing is not appropriate for your installation you can fetch the ssl-cert-check script from `http://prefetch.net/code/ssl-cert-check` bearing in mind that you will have to modify the command in the sensor code below to run the script from wherever you put it, modify permission if neccessary and so on.
In cases where, for whatever reason, apt-get installing is not appropriate for your installation you can fetch the ssl-cert-check script from `http://prefetch.net/code/ssl-cert-check` bearing in mind that you will have to modify the command in the sensor code below to run the script from wherever you put it, modify permission if necessary and so on.
</p>
To set up a senor add the following to your `configuration.yaml` (remembering to correct the URL for your DuckDNS):
@ -433,7 +433,7 @@ If you are a TWO-RULE person (from step 6), you can automatically renew your cer
There are a number of options for automating the renewal process:
#### Option 1:
Your certificate can be renewed as a 'cron job' - cron jobs are background tasks run by the computer at specified intervals (and are totally independant of Home Assistant). Defining cron is outside of the scope of this guide but you will have had dealings with `crontab` when setting up DuckDNS in step 3
Your certificate can be renewed as a 'cron job' - cron jobs are background tasks run by the computer at specified intervals (and are totally independent of Home Assistant). Defining cron is outside of the scope of this guide but you will have had dealings with `crontab` when setting up DuckDNS in step 3
To set a cron job to run the script at regular intervals:

2
source/_docs/ecosystem/hass-configurator.markdown
View File

@ -42,7 +42,7 @@ There are no dependencies on Python modules that are not part of the standard li
### {% linkable_title Configuration %}
Near the top of the configurator.py-file you will find some global variables you can change to customize the configurator. If you are unfamiliar with Python: when setting variables of the type _string_, you have to write that within quotation marks. The default settings are fine for just checking out the configurator quickly. With more customized setups you should change some settings though.
To keep your settings across updates it is also possible to save settings in an external file. In that case copy [settings.conf](https://github.com/danielperna84/hass-configurator/blob/master/settings.conf) whereever you like and append the full path to the file to the command when starting the configurator. E.g. `sudo .configurator.py /home/homeassistant/.homeassistant/mysettings.conf`. This file is in JSON format. So make sure it has a valid syntax (you can set the editor to JSON to get syntax highlighting for the settings). The major difference to the settings in the py-file is, that `None` becomes `null`.
To keep your settings across updates it is also possible to save settings in an external file. In that case copy [settings.conf](https://github.com/danielperna84/hass-configurator/blob/master/settings.conf) wherever you like and append the full path to the file to the command when starting the configurator. E.g. `sudo .configurator.py /home/homeassistant/.homeassistant/mysettings.conf`. This file is in JSON format. So make sure it has a valid syntax (you can set the editor to JSON to get syntax highlighting for the settings). The major difference to the settings in the py-file is, that `None` becomes `null`.
#### LISTENIP (string)
The IP the service is listening on. By default it is binding to `0.0.0.0`, which is every interface on the system.

2
source/_docs/ecosystem/ios/location.markdown
View File

@ -12,7 +12,7 @@ redirect_from: /ecosystem/ios/location/
## {% linkable_title Location tracking when outside a Home Assistant zone %}
Home Assistant for iOS receives _significant location updates_ from iOS. Whenever an update is received, it is sent to Home Assistant. Roughly, an update is received everytime that your device transfers to a new cellular tower, a significant amount of time has passed (usually a couple hours) or a connection state changes and the system notices your location recently changed.
Home Assistant for iOS receives _significant location updates_ from iOS. Whenever an update is received, it is sent to Home Assistant. Roughly, an update is received every time that your device transfers to a new cellular tower, a significant amount of time has passed (usually a couple hours) or a connection state changes and the system notices your location recently changed.
Apple [defines][apple-location-programming-guide] significant significant-change location updates as:

2
source/_docs/ecosystem/scenegen.markdown
View File

@ -90,7 +90,7 @@ This output can be cut and pasted into your configuration.yaml file as required
Scenegen supports all documented effects for lights including transitions and flash effects, however generally it is easier to run scenegen to get the basic setup and add any effects manually later.
Note that depending on the type of light there may be a delay in actually setting up its parameters and Home Assistant actually recieving that state. For instance, if you set a scene up with the Hue App, Home Assistant won't see those changes for up to 10 seconds. Turning on a ZWave light might not be seen for an entire poll interval. For this reason, its good practice to wait for a while after the scene is setup before running scenegen. Alternatively, perform all setup using the Home Assistant frontend and it will instantly have the required state for capture.
Note that depending on the type of light there may be a delay in actually setting up its parameters and Home Assistant actually receiving that state. For instance, if you set a scene up with the Hue App, Home Assistant won't see those changes for up to 10 seconds. Turning on a ZWave light might not be seen for an entire poll interval. For this reason, its good practice to wait for a while after the scene is setup before running scenegen. Alternatively, perform all setup using the Home Assistant frontend and it will instantly have the required state for capture.
## {% linkable_title Advanced Usage %}

20
source/_docs/glossary.markdown Normal file
View File

@ -0,0 +1,20 @@
---
layout: page
title: "Glossary"
description: "Home Assistant's Glossary."
date: 2017-10-08 08:30
sidebar: true
comments: false
sharing: true
footer: true
---
{% assign entries = site.data.glossary | sort: 'topic' %}
<ul>
{% for entry in entries %}
<li>
<b>{{ entry.topic }}</b>: {{ entry.description | markdownify }}
</li>
{% endfor %}
</ul>

7
source/_docs/installation/hassbian/installation.markdown
View File

@ -14,12 +14,14 @@ The easiest way to install Home Assistant on your Raspberry Pi is by using HASSb
1. [Download the Hassbian image][image-download] (364 MB)
2. Use [Etcher][etcher] to flash the image to your SD card
3. Ensure your Raspberry Pi has wired access to the internet for the entire process or configure your wireless network (details below).
3. Ensure your Raspberry Pi has wired access to the internet for the entire process or configure your wireless network settings **before proceeding to step 4**.
4. Insert SD card to Raspberry Pi and turn it on. Initial installation of Home Assistant will take about 5 minutes.
These instructions are also available as a [video](https://www.youtube.com/watch?v=iIz6XqDwHEk). Additional information is available in this [video](https://www.youtube.com/watch?v=tCGlQSsQ-Mc).
After initial boot an installer will run in the background and takes around 15 minutes to complete, after it has finished you can reach Home Assistant in your browser at [http://hassbian.local:8123]. If you want to login via SSH, the default username is `pi` and password is `raspberry` (please change this by running `passwd`). The Home Assistant configuration is located at `/home/homeassistant/.homeassistant/`.
After initial boot an installer will run in the background and takes around 15 minutes to complete, after it has finished, you will be prompted to login: `hassbian login:`. Installation is complete at this point. The default username is `pi` and the password is `raspberry`.
Open a browser on a device that's connected to the same WiFi network as your Raspberry Pi and point it to Home Assistant at [http://hassbian.local:8123]. If you want to login via SSH, the default username is `pi` and password is `raspberry` (please change this by running `passwd`). The Home Assistant configuration is located at `/home/homeassistant/.homeassistant/`.
If you find that the web page is not reachable after 30 minutes or so, check that you have files in `/home/homeassistant/.homeassistant/`, if there are no files in this location then run the installer manually using this command: `sudo systemctl start install_homeassistant.service`.
@ -45,6 +47,7 @@ network={
psk="YOUR_PASSWORD"
}
```
You may need to adjust the country code depending upon where you are. A list of codes can be found [here](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements).
### {% linkable_title Technical Details %}

6
source/_docs/installation/raspberry-pi-all-in-one.markdown
View File

@ -13,7 +13,7 @@ The [Raspberry Pi All-In-One Installer](https://github.com/home-assistant/fabric
The only requirement is that you have a Raspberry Pi with a fresh installation of [Raspbian](https://www.raspberrypi.org/downloads/raspbian/) connected to your network.
<p class='note'>
Note that as of 2016-11-30 SSH is disabled by default in the official Raspbian images. Adding an empty file called `ssh` to `/boot/` or the FAT32 partition will enable it. More information is on the Raspberry Pi Foundation [Blog](https://www.raspberrypi.org/blog/page/2/?fish#a-security-update-for-raspbian-pixel).
Note that as of 2016-11-30 SSH is disabled by default in the official Raspbian images. Adding an empty file called `ssh` to `/boot/` on the FAT32 partition will enable it. More information is on the Raspberry Pi Foundation [Blog](https://www.raspberrypi.org/blog/page/2/?fish#a-security-update-for-raspbian-pixel).
</p>
Irrespective of whether you use SSH to connect to the Pi from another computer or not, you need SSH to install Home Assistant. So go ahead and enable SSH.
@ -62,7 +62,7 @@ To upgrade the All-In-One setup manually:
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
* Change to homeassistant user `sudo su -s /bin/bash homeassistant`
* Change to virtual enviroment `source /srv/homeassistant/homeassistant_venv/bin/activate`
* Change to virtual environment `source /srv/homeassistant/homeassistant_venv/bin/activate`
* Update Home Assistant `pip3 install --upgrade homeassistant`
* Type `exit` to logout the hass user and return to the `pi` user.
@ -70,7 +70,7 @@ To upgrade the All-In-One setup manually:
**If you deployed Home Assistant via the AiO installer prior to December 2016**
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
* Change to homeassistant user `sudo su -s /bin/bash hass`
* Change to virtual enviroment `source /srv/hass/hass_venv/bin/activate`
* Change to virtual environment `source /srv/hass/hass_venv/bin/activate`
* Update Home Assistant `pip3 install --upgrade homeassistant`
* Type `exit` to logout the hass user and return to the `pi` user.
</div>

2
source/_docs/installation/raspberry-pi.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Manual installation on a Raspberry Pi"
description: "Instructions to install Home Assistant on a Raspberry Pi runnning Raspbian Lite."
description: "Instructions to install Home Assistant on a Raspberry Pi running Raspbian Lite."
date: 2016-09-05 16:00
sidebar: true
comments: false

4
source/_docs/mqtt/discovery.markdown
View File

@ -88,7 +88,7 @@ $ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/set" -m
Setting up a sensor with multiple measurement values requires multiple consecutive configuration topic submissions.
- Configuration topic no1: `homeassistant/sensor/sensorBedroomT/config`
- Configuration payload no1: `{"device_class": "sensor", "name": "Temperature", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "°C", "value_template": "{{ value_json.temperature}}" }`
- Configuration payload no1: `{"device_class": "sensor", "name": "Temperature", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "°C", "value_template": "{% raw %}{{ value_json.temperature}}{% endraw %}" }`
- Configuration topic no2: `homeassistant/sensor/sensorBedroomH/config`
- Configuration payload no2: `{"device_class": "sensor", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{{ value_json.humidity}}" }`
- Configuration payload no2: `{"device_class": "sensor", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{% raw %}{{ value_json.humidity}}{% endraw %}" }`
- Common state payload: `{ "temperature": 23.20, "humidity": 43.70 }`

2
source/_docs/scripts.markdown
View File

@ -77,7 +77,7 @@ delay: {% raw %}'00:{{ states.input_number.minute_delay.state | int }}:00'{% end
```
### {% linkable_title Wait %}
Wait until some things are complete. We support at the moment `wait_template` for waiting until a condition is `true`, see also on [Template-Trigger](/docs/automation/trigger/#template-trigger). The Timeout has same syntax as `delay`. If you set a Timeout for 1 minute and the condition is not satified within that minute, the script will continue.
Wait until some things are complete. We support at the moment `wait_template` for waiting until a condition is `true`, see also on [Template-Trigger](/docs/automation/trigger/#template-trigger). It is possible to set a timeout after which the script will abort its execution if the condition is not satisfied. Timeout has the same syntax as `delay`.
```yaml
# wait until media player have stop the playing

4
source/_docs/tools/scripts.markdown
View File

@ -19,7 +19,7 @@ Test any changes to your `configuration.yaml` file before launching Home Assista
$ hass --script check_config
```
### {% linkable_title Existance of configuration %}
### {% linkable_title Existence of configuration %}
This script checks if the `configuration.yaml` file exists. If the file is not available, one is created.
@ -47,7 +47,7 @@ $ hass --script benchmark async_million_events
### {% linkable_title Old scripts %}
Usally those scripts were only used when a massive update happend and was announced in the release notes.
Usually those scripts were only used when a massive update happened and was announced in the release notes.
- `db_migrator`: Migrate an existing SQLite database to the new schema.
- `influxdb_migrator`: Convert an old InfluxDB to the new format.

2
source/_faq/documentation-tool.markdown
View File

@ -11,4 +11,4 @@ ha_category: Documentation
---
Why are you not using tools X for the documentation? Because the current solution works for us and we see no additional value in using a seperate publishing platform.
Why are you not using tools X for the documentation? Because the current solution works for us and we see no additional value in using a separate publishing platform.

2
source/_faq/missing-documentation.markdown
View File

@ -13,4 +13,4 @@ ha_category: Documentation
Home Assistant is a FAST moving open source project. This means occasionally the official documentation will not be 100% current or complete. Since this is an open source volunteer project, we would encourage anyone who finds gaps in the documentation to click the `edit this page on Github` link in the top right and submit any corrections/enhancements they may find useful.
In the absence of information, many users find it beneficial to look at other people's configurations to find examples of what they want to accomplish in thier own configurations. The easiest way to find these configurations is through this [Github search](https://github.com/search?q=topic%3Ahome-assistant-config&type=Repositories).
In the absence of information, many users find it beneficial to look at other people's configurations to find examples of what they want to accomplish in their own configurations. The easiest way to find these configurations is through this [Github search](https://github.com/search?q=topic%3Ahome-assistant-config&type=Repositories).

9
source/_includes/asides/developers_navigation.html
View File

@ -91,6 +91,7 @@
<ul>
<li>{% active_link /developers/hassio/addon_tutorial/ Tutorial: Making your first add-on %}</li>
<li>{% active_link /developers/hassio/addon_config/ Configuration %}</li>
<li>{% active_link /developers/hassio/addon_communication/ Communication %}</li>
<li>{% active_link /developers/hassio/addon_testing/ Local Testing %}</li>
<li>{% active_link /developers/hassio/addon_publishing/ Publishing %}</li>
<li>{% active_link /developers/hassio/addon_repository/ Repositories %}</li>
@ -106,8 +107,14 @@
<li>{% active_link /developers/server_sent_events/ Server-sent events %}</li>
</ul>
</li>
<li>
{% active_link /developers/documentation/ Website/Documentation %}
<ul>
<li>{% active_link /developers/documentation/standards/ Standards %}</li>
<li>{% active_link /developers/documentation/create_page/ Create a new page %}</li>
</ul>
</li>
<li>{% active_link /developers/helpers/ Online helpers %}</li>
<li>{% active_link /developers/website/ Website/Documentation %}</li>
<li>{% active_link /developers/releasing/ Releasing %}</li>
<li>{% active_link /developers/maintenance/ Maintenance %}</li>
<li>

3
source/_includes/asides/docs_navigation.html
View File

@ -3,7 +3,8 @@
<h1 class="title delta">Topics</h1>
<ul class='divided sidebar-menu'>
<li>
<b>{% active_link /faq/ FAQ %}</b>
<b>{% active_link /faq/ FAQ %}</b> |
<b>{% active_link /docs/glossary/ Glossary %}</b>
</li>
<li>
<b>{% active_link /docs/installation/ Installation %}</b>

2
source/_posts/2014-12-26-home-control-home-automation-and-the-smart-home.markdown
View File

@ -13,7 +13,7 @@ categories: Internet-of-Things
The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
This article will try to explain how they all relate.
The first thing to introduce is the **Internet of Things** (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.
The first thing to introduce is the **Internet of Things** (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.
There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a **hub**.

2
source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
View File

@ -12,7 +12,7 @@ categories: Release-Notes
Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.
The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.
The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.
Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.

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

@ -28,7 +28,7 @@ The history component will be enabled for new users by default. For current user
</p>
<p class='note'>
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.
</p>
<!--more-->

2
source/_posts/2015-02-24-streaming-updates.markdown
View File

@ -12,7 +12,7 @@ categories: Release-Notes
Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
A new toggle has been added to the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
<p class='img'><img src='/images/screenshots/streaming-updates.png' /></p>

2
source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown
View File

@ -10,7 +10,7 @@ comments: true
categories: Release-Notes
---
We discovered two issues annoying enough to warrent the release of 0.7.5:
We discovered two issues annoying enough to warrant the release of 0.7.5:
- Home Assistant package did not include the CloudMQTT certificate.
- A bug in the core caused issues when some platforms are loaded twice.

2
source/_posts/2015-12-07-influxdb-and-grafana.markdown
View File

@ -12,7 +12,7 @@ og_image: /images/blog/2015-12-influxdb/grafana-graph.png
---
<img src='/images/supported_brands/influxdb.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;' width='200' /><img src='/images/supported_brands/grafana.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;' width='200' />
The [InfluxDB](https://influxdb.com/) database is a so-called time series database primarly designed to store sensor data and real-time analytics.
The [InfluxDB](https://influxdb.com/) database is a so-called time series database primarily designed to store sensor data and real-time analytics.
The `influxdb` component makes it possible to transfer all state changes from Home Assistant to an external [InfluxDB](https://influxdb.com/) database.

2
source/_posts/2016-01-29-insteon-lifx-twitter-and-zigbee.markdown
View File

@ -13,7 +13,7 @@ og_image: /images/blog/2016-01-release-12/social.png
Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
I would like to give a shout out to [Greg Dowling (@pavoni)][@pavoni] as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
I would like to give a shout out to [Greg Dowling (@pavoni)][@pavoni] as every release includes new work from him. He is constantly adding support for new platforms or improving the reliability of existing components and platforms. Keep up the good work!
This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See [the demo] to see this in action and read more in the [group documentation][group] how to get started.

2
source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown
View File

@ -111,7 +111,7 @@ mqtt:
broker: localhost
```
Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings/<Device Name>/<Atribute>`
Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings/<Device Name>/<Attribute>`
For example, my Dimmer Z-Wave Lamp is called "Fireplace Lights" in SmartThings. The following topics are published:

2
source/_posts/2016-02-11-classifying-the-internet-of-things.markdown
View File

@ -143,7 +143,7 @@ Controlling a device can, just like state, be done through cloud and/or local co
These devices are not able to be controlled. They will only offer state.
### {% linkable_title Poll State after sending command %}
These devices will require the state to be polled after sending a command to see if a command was successfull.
These devices will require the state to be polled after sending a command to see if a command was successful.
Advantages:

2
source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown
View File

@ -1,7 +1,7 @@
---
layout: post
title: "0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV"
description: "This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionaly was the Wink support improved and CherryPy is the new WSGI server."
description: "This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionally was the Wink support improved and CherryPy is the new WSGI server."
date: 2016-07-01 00:31:00 +0000
date_formatted: "July 1, 2016"
author: Paulus Schoutsen

2
source/_posts/2016-07-28-esp8266-and-micropython-part1.markdown
View File

@ -41,7 +41,7 @@ Leaving...
Now reset the device. You should then be able to use the [REPL (Read Evaluate Print Loop)](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt). On Linux there is `minicom` or `picocom`, on a Mac you can use `screen` (eg. `screen /dev/tty.SLAB_USBtoUART 115200`), and on Windows there is Putty to open a serial connection and get the REPL prompt.
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is neccessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is necessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
```bash
$ sudo minicom -D /dev/ttyUSB0

2
source/_posts/2016-08-16-we-have-apps-now.markdown
View File

@ -38,7 +38,7 @@ So why `AppDaemon`? `AppDaemon` is not meant to replace Home Assistant Automatio
- Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened
- All the power of Python - use any of Python's libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additonal functions to make things that were already possible easier.
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additional functions to make things that were already possible easier.
## {% linkable_title How it Works %}

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

@ -27,7 +27,7 @@ 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 whant 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 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.
### {% 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!

2
source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
View File

@ -12,7 +12,7 @@ categories: Release-Notes
Yes, after only nine days comes 0.30. Don't worry, we will try to keep our usual release cycle and not start to release every day.
We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it.
We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it.
A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It's a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.

2
source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
View File

@ -173,7 +173,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
- Weather: Allow tracking severe weather alerts with [WUnderground] ([@tchellomello])
- Sensor: New support added to track [min/max/mean][min] ([@fabaff])
- Convert EntityComponent to be async ([@pvizeli], [@balloob])
- Z-Wave: Add assocation service ([@turbokongen])
- Z-Wave: Add association service ([@turbokongen])
- Frontend - Services dev tool: persist state and tweak UI ([@justweb1])
- Sensor: Support added for [scraping][scrape] websites ([@fabaff])
- Clean up of tests ([@capellini])

2
source/_posts/2016-12-03-remote-websockets-sonarr.markdown
View File

@ -117,7 +117,7 @@ We are working on a better solution for 0.35.
- Fix InfluxDB without authentication ([@balloob])
- Fix Kodi without authentication ([@balloob])
- Fix incorrect caching of /api/error_log ([@armills])
- Fix incorrect ordering of service calls which could cause delays inbetween turning on multiple entities ([@balloob])
- Fix incorrect ordering of service calls which could cause delays between turning on multiple entities ([@balloob])
- Fix Nest Climate temperature issues ([@technicalpickles])
### {% linkable_title Release 0.34.5 - December 12 %}

2
source/_posts/2016-12-19-thank-you.markdown
View File

@ -13,7 +13,7 @@ og_image:
A year ago [Home Assistant 0.10][0.10] landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that's more than 7 a day!
One of the things that Jon Walker, the founder of the company I work for ([AppFolio]), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Everytime you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.
One of the things that Jon Walker, the founder of the company I work for ([AppFolio]), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.
That's why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it's clear when things go out and people are not afraid to miss a release.

2
source/_posts/2017-01-03-control-my-christmas-tree-stats.markdown
View File

@ -15,7 +15,7 @@ Hello and Happy New Year!
I am not Paulus. My name is Ben. I'm the creator of the [BRUH Automation YouTube channel][bruh]. If you've ever seen any of my videos then you'll know I love home automation and Home Assistant.
I wanted to share some exciting stats from one of my latest projects - [Control My Christmas tree!](https://github.com/bruhautomation/BRUH-Christmas-Tree-2016) For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.
I wanted to share some exciting stats from one of my latest projects - [Control My Christmas tree!](https://github.com/bruhautomation/BRUH-Christmas-Tree-2016) For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publicly accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.
I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!

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

@ -103,7 +103,7 @@ Thanks to [@konikvranik] the [HDMI CEC][cec] integration got a huge update with
- Light - tellstick.py: Tellstick light fix ([@stefan-jonasson])
- Switch - insteon_local.py: only check for devices when not defined in config ([@wardcraigj])
- Notify - Twitter: Allow direct messaging to user ([@fabaff])
- Fan - MQTT: Dont set a speed when fan turns on ([@robbiet480])
- Fan - MQTT: Don't set a speed when fan turns on ([@robbiet480])
- Config: Allow easier customization of whole domain, entity lists, globs ([@andrey-git])
- Sensor - Homematic: Update device support ([@danielperna84])
- Binary sensor - ISS: Add location to attributes and option to show position on the map ([@fabaff])

2
source/_posts/2017-02-04-babyphone.markdown
View File

@ -10,7 +10,7 @@ categories: How-To
og_image: /images/blog/2017-02-babyphone/social.png
---
One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.
One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assistant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.
Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.

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

@ -180,7 +180,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
- twilio component ([@happyleavesaoc])
- Add Z-Wave battery level as a sensor. ([@andrey-git])
- OwnTrack Async ([@pvizeli])
- Fix possibility that have multible topic subscribe mqtt ([@pvizeli])
- Fix possibility that have multiple topic subscribe mqtt ([@pvizeli])
- Migrate mqtt tracker and arwn sensor to async / cleanup owntrack ([@pvizeli])
- Z-Wave prevent I/O event loop ([@balloob])
- Update pwaqi to 3.0 to use public API ([@valentinalexeev])
@ -230,7 +230,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
- Allow configurable conditions for Pi-Hole sensor ([@colinodell])
- Improved iCloud 2FA support. ([@reedriley])
- Update pymyq requirement ([@arraylabs])
- Not always asume manufacturername is present ([@balloob])
- Not always assume manufacturername is present ([@balloob])
- Add first pass at Z-Wave light tests ([@balloob])
- Bugfix mqtt socket memory error ([@pvizeli])
- Increase upper limit on light transitions ([@amelchio])

2
source/_posts/2017-03-28-http-to-mqtt-bridge.markdown
View File

@ -10,7 +10,7 @@ categories: How-To
og_image: /images/blog/2017-03-bridge/social.png
---
The idea of creating [HTTP to MQTT bridge](https://github.com/petkov/http_to_mqtt) appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.
The idea of creating [HTTP to MQTT bridge](https://github.com/petkov/http_to_mqtt) appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.
The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with [Express](https://expressjs.com/) for the server part and [MQTT.js](https://www.npmjs.com/package/mqtt) for the client.

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

@ -10,7 +10,7 @@ categories: Community
og_image: /images/blog/2017-04-award/social.png
---
You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the [Thomas-Krenn-Award][award] put us on the 2nd place. This is an awesome achievment for an independent community project.
You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the [Thomas-Krenn-Award][award] put us on the 2nd place. This is an awesome achievement for an independent community project.
I would like to thanks all contributors. Your endless effort made this possible.

4
source/_posts/2017-04-22-ikea-tradfri--spotify.markdown
View File

@ -149,7 +149,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Upgrade sendgrid to 4.0.0 ([@fabaff] - [#7038]) ([notify.sendgrid docs])
- Missing line name restriction added (fixes #7039) ([@DavidMStraub] - [#7040]) ([sensor.mvglive docs])
- Plug file leak on LIFX unregister ([@amelchio] - [#7031]) ([light.lifx docs])
- Make core to look avilable state of device on servicecall ([@pvizeli] - [#7045])
- Make core to look available state of device on servicecall ([@pvizeli] - [#7045])
- Remove configuration sample ([@fabaff] - [#7048])
- Bugfix wait on start event ([@pvizeli] - [#7013])
- Bugfix slider ([@pvizeli] - [#7047]) ([input_slider docs])
@ -212,7 +212,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Value of 0 should not be considered `unknown`. ([@aequitas] - [#7139])
- Upgrade netdisco ([@balloob] - [#7171])
- Added new services to platform kodi ([@alexmogavero] - [#6426]) ([media_player docs]) ([media_player.kodi docs])
- Supress trackback and upgrade PyMata to 2.14 ([@fabaff] - [#7176]) ([arduino docs])
- Suppress trackback and upgrade PyMata to 2.14 ([@fabaff] - [#7176]) ([arduino docs])
- Disable invalid-sequence-index ([@fabaff] - [#7177])
- Upgrade mypy to 0.501 (was renamed from mypy-lang) ([@fabaff] - [#7117])
- Add condition for API failure ([@sytone] - [#7181])

2
source/_posts/2017-06-04-release-46.markdown
View File

@ -147,7 +147,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Use expected behvaior for above/below ([@armills] - [#7857]) (breaking change)
- log time delay of domain setup in info level ([@azogue] - [#7808])
- Optimize history_stats efficiency and database usage ([@bokub] - [#7858]) ([sensor.history_stats docs])
- dont use default for switch name, so that the object id is used ([@abmantis] - [#7845]) ([switch.broadlink docs]) (breaking change)
- don't use default for switch name, so that the object id is used ([@abmantis] - [#7845]) ([switch.broadlink docs]) (breaking change)
- Disallow ambiguous color descriptors in the light.turn_on schema ([@amelchio] - [#7765]) (breaking change)
- Make monkey patch work in Python 3.6 ([@balloob] - [#7848])
- fix permissions issue for Insteon Local #6558 ([@wardcraigj] - [#7860]) ([insteon_local docs])

2
source/_posts/2017-07-29-release-50.markdown
View File

@ -73,7 +73,7 @@ Straight to 0.50.2. We released 0.50 as 0.50.1 due to an upload error to PyPi.
- Fix TP-Link light brightness issue #8744. ([@gollo] - [#8755])
- Fix typo in script error ([@n8henrie] - [#8754])
- Fix tradfri error spam ([@MartinHjelmare] - [#8738]) ([light.tradfri docs])
- Media Player - Pioneer: Supress exception if host is not available (fixes #8684) ([@fabaff] - [#8732]) ([media_player.pioneer docs])
- Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) ([@fabaff] - [#8732]) ([media_player.pioneer docs])
- Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again ([@azogue] - [#8716]) ([telegram_bot.webhooks docs])
- Fixed sensor issue with Google Wifi routers in bridge mode ([@fronzbot] - [#8710]) ([sensor.google_wifi docs])
- Fix alexa cards ([@balloob] - [#8708]) ([alexa docs])

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

@ -154,7 +154,7 @@ frontend:
- Skip automatic events older than latest data ([@armills] - [#9230]) ([device_tracker.automatic docs])
- title and message was swapped in pushbullet ([@danielhiversen] - [#9241]) ([notify.pushbullet docs])
- Fix possible KeyError ([@MartinHjelmare] - [#9242]) ([mysensors docs])
- WIP: Homematic improvments with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change)
- WIP: Homematic improvements with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change)
- Add available to sonos ([@pvizeli] - [#9243]) ([media_player.sonos docs])
- Make sure Ring binary_sensor state will update only if device_id matches ([@tchellomello] - [#9247]) ([binary_sensor.ring docs])
- Added configurable timeout for receiver HTTP requests | Additional AV… ([@scarface-4711] - [#9244]) ([media_player.denonavr docs])

31
source/_posts/2017-10-06-deprecating-python-3.4-support.markdown Normal file
View File

@ -0,0 +1,31 @@
---
layout: post
title: "Deprecating Python 3.4 support"
description: "Starting release 0.55, Python 3.4 support will be deprecated. Support is planned to be removed at the beginning of 2018."
date: 2017-10-06 0:36 +0000
date_formatted: "October 6, 2017"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Technology
---
Starting with our next release, 0.55, we will deprecate Python 3.4 support. The current plan is to remove support for Python 3.4 at the beginning of 2018.
Python 3.5 was released on September 13th, 2015. It has since then become the default Python installation on the stable releases of Debian, Ubuntu, Raspbian and Hassbian. Our other own operating system, Hass.io, is more advanced and is already running the greatly improved Python 3.6.
The jump to Python 3.5 as a minimum version is driven by the Home Assistant core, which is based on asyncio. Starting with Python 3.5, asyncio got improved support in the language with dedicated keywords `async` and `await`. As this is the proper way of doing async in Python, we're seeing a move by async libraries to either only support the new syntax from the beginning or dropping support for the Python 3.4 approach. Not moving along means an increased maintenance burden as we cannot use the latest releases of our libraries. Next to that it will prevent our users from being able to leverage the bug fixes and performance improvements that come with Python 3.5.
#### Hass.io
If you're running Hass.io, you don't have to do anything. Your system will always stay up to date.
#### Hassbian
If you're running Hassbian it's recommended that you make a backup of your configuration files and restore them on a fresh install. Upgrading an existing installation isn't recommended.
#### Windows
If you're on Windows, you're fine as our minimum version for Windows has been 3.5 for a while now.
#### Other Debian based systems
If you're running a Debian based system , follow [these instructions][dist-upgrade] to upgrade.
[dist-upgrade]: https://linuxconfig.org/raspbian-gnu-linux-upgrade-from-jessie-to-raspbian-stretch-9

383
source/_posts/2017-10-07-release-55.markdown Normal file
View File

@ -0,0 +1,383 @@
---
layout: post
title: "0.55: Tibber, DuckDNS, The Things Network, Owntrack"
description: "Support for Tibber and the Things Network a long with new Owntracks and DuckDNS features"
date: 2017-10-07 10:00:00
date_formatted: "October 7, 2017"
author: Fabian Affolter
author_twitter: fabaff
comments: true
categories: Release-Notes
og_image: /images/blog/2017-10-0.55/components.png
---
<a href='/components/#version/0.55'><img src='/images/blog/2017-10-0.55/components.png' style='border: 0;box-shadow: none;'></a>
Beside the improved Wink support which was contributed by [@w1ll1am23], ships this release a wide variety of new components and platforms. The `input_slider` components has received a makeover by [@BioSehnsucht] and is now [`input_number`][input_number docs]. [@tinloaf] added a feature that allows you to enter dates: [`input_datetime`][input_datetime docs]. Both will help you to improve your automation rules.
## {% linkable_title DuckDNS %}
Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](https://home-assistant.io/addons/duckdns/). 0.55 ships a component for no Hass.io users to get a similar feature.
## {% linkable_title Recorder %}
The purging of data was [improved][recorder docs]. With `purge_interval` you can schedule regular purges of older events and states. In combination you can specify with `purge_keep_days` the amount of days you want to keep. The new service `recorder.purge` allow to handle this task when needed.
## {% linkable_title Owntracks %}
[Owntracks](http://owntracks.org/) is an easy way to track your devices. For some times we have the device tracker which depends on [MQTT][device_tracker.owntracks docs] but thanks to a new feature in Owntracks we can now offer support for HTTP. The [new platform][device_tracker.owntracks_http docs] doesn't require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.
## {% linkable_title Tibber %}
This release introduces a new sensor: [Tibber][sensor.tibber docs]. The sensor provides the current electricity price if you are a [Tibber](https://tibber.com/) customer. This will allow you to make automation for turning off the heater when the electricity price is high or only charge your electric car when the prices are low. We further plan to add support for showing future electricity prices and historic electricity consumption data. Tibber is currently only available in Norway and Sweden
## {% linkable_title The Things Network %}
[The Things Network](https://www.thethingsnetwork.org/) (TTN) is a [LoRaWAN](https://www.thethingsnetwork.org/wiki/LoRaWAN/Home) based network especially designed for IoT devices. With this [integration][thethingsnetwork docs] one can observe the state of devices which are out of range of the local WiFi network as long as they are connected to a TTN gateway.
## {% linkable_title New Platforms %}
- GeoRSS sensor ([@exxamalte] - [#9331]) ([sensor.geo_rss_events docs]) (new-platform)
- Add DuckDNS component ([@balloob] - [#9556]) ([duckdns docs]) (new-platform)
- Add OwnTracks over HTTP ([@balloob] - [#9582]) ([http docs]) ([device_tracker.owntracks docs]) ([device_tracker.owntracks_http docs]) (new-platform)
- Add an input_datetime ([@tinloaf] - [#9313]) ([input_datetime docs]) (new-platform)
- Cover component for RFlink ([@passie] - [#9432]) ([rflink docs]) ([cover.rflink docs]) (new-platform)
- Introducing support to Melnor RainCloud sprinkler systems ([@tchellomello] - [#9287]) ([raincloud docs]) ([binary_sensor.raincloud docs]) ([sensor.raincloud docs]) ([switch.raincloud docs]) (new-platform)
- MQTT climate platform [continuation of #8750] ([@tinloaf] - [#9589]) ([climate.mqtt docs]) (new-platform)
- Add Tibber sensor ([@danielhiversen] - [#9661]) ([sensor.tibber docs]) (new-platform)
- Updating clicksendaudio component based on feedback ([@jeroenterheerdt] - [#9692]) ([notify.clicksendaudio docs]) (new-platform)
- Support for The Things Network ([@fabaff] - [#9627]) ([thethingsnetwork docs]) ([sensor.thethingsnetwork docs]) (new-platform)
## {% linkable_title If you need help... %}
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
## {% linkable_title Reporting Issues %}
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
<!--more-->
## {% linkable_title Breaking Changes %}
- history_graph component: If your component used `history.get_significant_states` function then you need to adjust the string `entitity_id` parameter has been changed to a list of strings `entity_ids` parameter. ([@andrey-git] - [#9472]) ([history_graph docs]) (breaking change)
- UPNP component: The `external_port` configuration option was removed. ([@balloob] - [#9560]) ([upnp docs]) (breaking change)
- New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by "_" and no longer " ". ([@w1ll1am23] - [#9303]) ([wink docs]) ([binary_sensor.wink docs]) ([lock.wink docs]) (breaking change)
- TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. ([@djchen] - [#9607]) ([switch.tplink docs]) (breaking change)
- Renamed `input_slider` to `input_number` which has now a numeric text box option. ([@BioSehnsucht] - [#9494]) ([demo docs]) ([input_number docs]) (breaking change)
- Recorder: Add new purge service and interval. ([@milanvo] - [#9523]) ([recorder docs]) (breaking change)
- OpenCV image processing: Typo in classifier was fixed. ([@arsaboo] - [#9697]) ([image_processing.opencv docs]) (breaking change)
- Tradfri Lights: Async support with resource observation. ([@lwis] - [#7815]) ([tradfri docs]) ([light.tradfri docs]) (breaking change)
## {% linkable_title All changes %}
- flux led lib 0.20 ([@danielhiversen] - [#9533]) ([light.flux_led docs])
- Update AbodePy to 0.11.8 ([@MisterWil] - [#9537]) ([abode docs])
- Bump python_openzwave to 0.4.0.35 ([@arsaboo] - [#9542]) ([zwave docs])
- update usps ([@happyleavesaoc] - [#9540]) ([usps docs]) ([camera.usps docs]) ([sensor.usps docs])
- Bugfix Homematic hub object ([@pvizeli] - [#9544]) ([homematic docs])
- Fix a bunch of typos ([@mika] - [#9545])
- Catch no longer existing process in systemmonitor ([@Tommatheussen] - [#9535]) ([sensor.systemmonitor docs])
- Upgrade pyasn1 to 0.3.6 ([@fabaff] - [#9548])
- Add history_graph component ([@andrey-git] - [#9472]) (breaking change)
- GeoRSS sensor ([@exxamalte] - [#9331]) ([sensor.geo_rss_events docs]) (new-platform)
- Fixed bug with all switch devices being excluded ([@MisterWil] - [#9555]) ([switch.abode docs])
- fix usps? ([@happyleavesaoc] - [#9557]) ([usps docs]) ([sensor.usps docs])
- Added support for ARM_NIGHT for manual_mqtt alarm ([@snjoetw] - [#9358]) ([alarm_control_panel.manual_mqtt docs])
- Various AirVisual bugfixes ([@bachya] - [#9554]) ([sensor.airvisual docs])
- Updated Arlo cameras with new attributes ([@bachya] - [#9565]) ([arlo docs]) ([camera.arlo docs])
- Allow specifying multiple ports for UPNP component ([@balloob] - [#9560]) ([upnp docs]) (breaking change)
- Update yeelight to 0.3.3. ([@pfalcon] - [#9561]) ([light.yeelight docs])
- Add test cases and fix for device_defaults fire_event option. ([@aequitas] - [#9567]) ([light.rflink docs]) ([switch.rflink docs])
- Use simplepush module, enable event, and allow encrypted communication ([@fabaff] - [#9568]) ([notify.simplepush docs])
- Add DuckDNS component ([@balloob] - [#9556]) ([duckdns docs]) (new-platform)
- Clean up OwnTracks ([@balloob] - [#9569]) ([device_tracker.owntracks docs])
- MQTT Cover: Add availability topic and configurable payloads ([@marthoc] - [#9445]) ([cover.mqtt docs])
- Upgrade dsmr_parser to 0.11 ([@fabaff] - [#9576]) ([sensor.dsmr docs])
- Added new statistic attributes ([@sti0] - [#9433]) ([vacuum.xiaomi docs])
- Upgrade youtube_dl to 2017.9.24 ([@fabaff] - [#9575]) ([media_extractor docs])
- Upgrade lyft_rides to 0.2 ([@enriquegh] - [#9578]) ([sensor.lyft docs])
- Increase Comed timeout since it sometimes takes a long time for the API to respond ([@joe248] - [#9536]) ([sensor.comed_hourly_pricing docs])
- Allow customizable turn on action for LG WebOS tv ([@cmsimike] - [#9206]) ([media_player.webostv docs]) (breaking change)
- IMAP Unread sensor updated for async and push ([@amelchio] - [#9562]) ([sensor.imap docs])
- Replace emulated_hue: with emulated_hue_hidden: for consistency. ([@rbflurry] - [#9382]) ([emulated_hue docs])
- Upgrade Sphinx to 1.6.4 ([@fabaff] - [#9584])
- Bump pyatv to 0.3.5 ([@postlund] - [#9586]) ([apple_tv docs]) ([media_player.apple_tv docs])
- New Wink services. pair new device, rename, and delete, add new lock key code. Add water heater support ([@w1ll1am23] - [#9303]) ([wink docs]) ([binary_sensor.wink docs]) ([lock.wink docs]) (breaking change)
- Fixes UPS MyChoice exception ([@bachya] - [#9587]) ([sensor.ups docs])
- FedEx: Adds "packages" as a unit ([@bachya] - [#9588]) ([sensor.fedex docs])
- Cleanup entity & remove warning ([@pvizeli] - [#9606])
- Add OwnTracks over HTTP ([@balloob] - [#9582]) ([http docs]) ([device_tracker.owntracks docs]) ([device_tracker.owntracks_http docs]) (new-platform)
- upgrade python-ecobee-api ([@nkgilley] - [#9612]) ([ecobee docs])
- Change TP-Link Switch power statistics attribute names ([@djchen] - [#9607]) ([switch.tplink docs]) (breaking change)
- Migrate Alexa smart home to registry ([@balloob] - [#9616]) ([alexa.smart_home docs])
- Add an input_datetime ([@tinloaf] - [#9313]) ([input_datetime docs]) (new-platform)
- Cover component for RFlink ([@passie] - [#9432]) ([rflink docs]) ([cover.rflink docs]) (new-platform)
- Introducing support to Melnor RainCloud sprinkler systems ([@tchellomello] - [#9287]) ([raincloud docs]) ([binary_sensor.raincloud docs]) ([sensor.raincloud docs]) ([switch.raincloud docs]) (new-platform)
- Rewrite synology camera by using py-synology package ([@snjoetw] - [#9583]) ([camera.synology docs])
- yeelight: allow turn_off transitions, fixes #9602 ([@rytilahti] - [#9605]) ([light.yeelight docs])
- Move 'voltage' to const ([@fabaff] - [#9621]) ([sensor.pvoutput docs]) ([switch.tplink docs])
- Yamaha MusicCast: check known_hosts ([@jalmeroth] - [#9580]) ([media_player.yamaha_musiccast docs])
- Fixed away_mode for Ecobee thermostat. ([@etsinko] - [#9559]) ([climate.ecobee docs])
- Switched VeraSensor to use category ids ([@alanfischer] - [#9624]) ([sensor.vera docs])
- splunk: Handle datetime objects in event payload ([@philk] - [#9628]) ([splunk docs])
- MQTT climate platform [continuation of #8750] ([@tinloaf] - [#9589]) ([climate.mqtt docs]) (new-platform)
- wunderground: fix supported language codes #9631 ([@szogi] - [#9633]) ([sensor.wunderground docs])
- add myself to codeowners ([@rytilahti] - [#9642])
- raspihats: unmet dependency fix ([@szogi] - [#9638]) ([raspihats docs])
- Fixes broken source links in API docs ([@David-Byrne] - [#9636])
- Move group services into their own YAML ([@balloob] - [#9597]) ([group docs])
- Facebook Messenger notify component: add support for sending messages to specific page user IDs ([@mweimerskirch] - [#9643]) ([notify.facebook docs])
- arlo: Add battery level sensor ([@vickyg3] - [#9637]) ([sensor.arlo docs])
- Add hysteresis attribute to threshold binary sensor ([@hotplot] - [#9596]) ([binary_sensor.threshold docs])
- Upgrade numpy to 1.13.3 ([@fabaff] - [#9646]) ([image_processing.opencv docs])
- Upgrade youtube_dl to 2017.10.01 ([@fabaff] - [#9647]) ([media_extractor docs])
- Upgrade discord.py to 0.16.12 ([@fabaff] - [#9648]) ([notify.discord docs])
- Upgrade netdisco to 1.2.2 ([@fabaff] - [#9649])
- Upgrade influxdb to 4.1.1 ([@fabaff] - [#9652]) ([influxdb docs])
- Upgrade googlemaps to 2.5.1 ([@fabaff] - [#9653]) ([sensor.google_travel_time docs])
- mqtt_statestream: Add options to publish attributes/timestamps ([@mw-white] - [#9645]) ([mqtt_statestream docs])
- Fixed bugs related to exception handling in pythonegardia. Updating package requirement accordingly ([@jeroenterheerdt] - [#9663]) ([alarm_control_panel.egardia docs])
- Update google-api-python-client to 1.6.4 ([@arsaboo] - [#9658]) ([google docs])
- Bump abode to 0.11.9 ([@MisterWil] - [#9660]) ([abode docs])
- Unit tests to improve core coverage ([@armills] - [#9659])
- Upgrade pyitachip2ir to 0.0.7 ([@alanfischer] - [#9669]) ([remote.itach docs])
- Fix typo in cancel_command description ([@FletcherAU] - [#9671])
- Rename input_slider to input_number and add numeric text box option ([@BioSehnsucht] - [#9494]) ([demo docs]) ([input_number docs]) (breaking change)
- Properly handle an invalid end_time ([@alanfischer] - [#9675]) ([history docs])
- Support new feature to push API data to hassio ([@pvizeli] - [#9679]) ([hassio docs])
- Adding ignore capability to Egardia component ([@jeroenterheerdt] - [#9676]) ([alarm_control_panel.egardia docs])
- Fix Google Calendar/oauth2client warning ([@mbrrg] - [#9677]) ([google docs])
- Implement DSMR5 support. ([@aequitas] - [#9686]) ([sensor.dsmr docs])
- Add Tibber sensor ([@danielhiversen] - [#9661]) ([sensor.tibber docs]) (new-platform)
- Add recorder purge service, rework purge timer ([@milanvo] - [#9523]) (breaking change)
- Fix restore state by filter out null value row from DB query ([@milanvo] - [#9690]) ([history docs])
- Updating clicksendaudio component based on feedback ([@jeroenterheerdt] - [#9692]) ([notify.clicksendaudio docs]) (new-platform)
- Refactoring of onewire sensor component ([@bestlibre] - [#9691]) ([sensor.onewire docs])
- HassIO replace config changes ([@pvizeli] - [#9695]) ([hassio docs])
- Fixed typo in opencv ([@arsaboo] - [#9697]) ([image_processing.opencv docs]) (breaking change)
- [light.tradfri] async support with resource observation. ([@lwis] - [#7815]) ([tradfri docs]) ([light.tradfri docs]) (breaking change)
- Create secrets file in default config ([@balloob] - [#9685])
- Support for The Things Network ([@fabaff] - [#9627]) ([thethingsnetwork docs]) ([sensor.thethingsnetwork docs]) (new-platform)
- Deprecate Python 3.4 support ([@balloob] - [#9684])
- Fix coap commit ([@balloob] - [#9712])
- [light.tradfri] Clone all of aiocoap to ensure pinned commit will be present ([@lwis] - [#9713])
[#7815]: https://github.com/home-assistant/home-assistant/pull/7815
[#9206]: https://github.com/home-assistant/home-assistant/pull/9206
[#9287]: https://github.com/home-assistant/home-assistant/pull/9287
[#9303]: https://github.com/home-assistant/home-assistant/pull/9303
[#9313]: https://github.com/home-assistant/home-assistant/pull/9313
[#9331]: https://github.com/home-assistant/home-assistant/pull/9331
[#9358]: https://github.com/home-assistant/home-assistant/pull/9358
[#9382]: https://github.com/home-assistant/home-assistant/pull/9382
[#9432]: https://github.com/home-assistant/home-assistant/pull/9432
[#9433]: https://github.com/home-assistant/home-assistant/pull/9433
[#9445]: https://github.com/home-assistant/home-assistant/pull/9445
[#9472]: https://github.com/home-assistant/home-assistant/pull/9472
[#9494]: https://github.com/home-assistant/home-assistant/pull/9494
[#9523]: https://github.com/home-assistant/home-assistant/pull/9523
[#9533]: https://github.com/home-assistant/home-assistant/pull/9533
[#9535]: https://github.com/home-assistant/home-assistant/pull/9535
[#9536]: https://github.com/home-assistant/home-assistant/pull/9536
[#9537]: https://github.com/home-assistant/home-assistant/pull/9537
[#9540]: https://github.com/home-assistant/home-assistant/pull/9540
[#9542]: https://github.com/home-assistant/home-assistant/pull/9542
[#9544]: https://github.com/home-assistant/home-assistant/pull/9544
[#9545]: https://github.com/home-assistant/home-assistant/pull/9545
[#9548]: https://github.com/home-assistant/home-assistant/pull/9548
[#9554]: https://github.com/home-assistant/home-assistant/pull/9554
[#9555]: https://github.com/home-assistant/home-assistant/pull/9555
[#9556]: https://github.com/home-assistant/home-assistant/pull/9556
[#9557]: https://github.com/home-assistant/home-assistant/pull/9557
[#9559]: https://github.com/home-assistant/home-assistant/pull/9559
[#9560]: https://github.com/home-assistant/home-assistant/pull/9560
[#9561]: https://github.com/home-assistant/home-assistant/pull/9561
[#9562]: https://github.com/home-assistant/home-assistant/pull/9562
[#9565]: https://github.com/home-assistant/home-assistant/pull/9565
[#9567]: https://github.com/home-assistant/home-assistant/pull/9567
[#9568]: https://github.com/home-assistant/home-assistant/pull/9568
[#9569]: https://github.com/home-assistant/home-assistant/pull/9569
[#9575]: https://github.com/home-assistant/home-assistant/pull/9575
[#9576]: https://github.com/home-assistant/home-assistant/pull/9576
[#9578]: https://github.com/home-assistant/home-assistant/pull/9578
[#9580]: https://github.com/home-assistant/home-assistant/pull/9580
[#9582]: https://github.com/home-assistant/home-assistant/pull/9582
[#9583]: https://github.com/home-assistant/home-assistant/pull/9583
[#9584]: https://github.com/home-assistant/home-assistant/pull/9584
[#9586]: https://github.com/home-assistant/home-assistant/pull/9586
[#9587]: https://github.com/home-assistant/home-assistant/pull/9587
[#9588]: https://github.com/home-assistant/home-assistant/pull/9588
[#9589]: https://github.com/home-assistant/home-assistant/pull/9589
[#9596]: https://github.com/home-assistant/home-assistant/pull/9596
[#9597]: https://github.com/home-assistant/home-assistant/pull/9597
[#9605]: https://github.com/home-assistant/home-assistant/pull/9605
[#9606]: https://github.com/home-assistant/home-assistant/pull/9606
[#9607]: https://github.com/home-assistant/home-assistant/pull/9607
[#9612]: https://github.com/home-assistant/home-assistant/pull/9612
[#9616]: https://github.com/home-assistant/home-assistant/pull/9616
[#9621]: https://github.com/home-assistant/home-assistant/pull/9621
[#9624]: https://github.com/home-assistant/home-assistant/pull/9624
[#9627]: https://github.com/home-assistant/home-assistant/pull/9627
[#9628]: https://github.com/home-assistant/home-assistant/pull/9628
[#9633]: https://github.com/home-assistant/home-assistant/pull/9633
[#9636]: https://github.com/home-assistant/home-assistant/pull/9636
[#9637]: https://github.com/home-assistant/home-assistant/pull/9637
[#9638]: https://github.com/home-assistant/home-assistant/pull/9638
[#9642]: https://github.com/home-assistant/home-assistant/pull/9642
[#9643]: https://github.com/home-assistant/home-assistant/pull/9643
[#9645]: https://github.com/home-assistant/home-assistant/pull/9645
[#9646]: https://github.com/home-assistant/home-assistant/pull/9646
[#9647]: https://github.com/home-assistant/home-assistant/pull/9647
[#9648]: https://github.com/home-assistant/home-assistant/pull/9648
[#9649]: https://github.com/home-assistant/home-assistant/pull/9649
[#9652]: https://github.com/home-assistant/home-assistant/pull/9652
[#9653]: https://github.com/home-assistant/home-assistant/pull/9653
[#9658]: https://github.com/home-assistant/home-assistant/pull/9658
[#9659]: https://github.com/home-assistant/home-assistant/pull/9659
[#9660]: https://github.com/home-assistant/home-assistant/pull/9660
[#9661]: https://github.com/home-assistant/home-assistant/pull/9661
[#9663]: https://github.com/home-assistant/home-assistant/pull/9663
[#9669]: https://github.com/home-assistant/home-assistant/pull/9669
[#9671]: https://github.com/home-assistant/home-assistant/pull/9671
[#9675]: https://github.com/home-assistant/home-assistant/pull/9675
[#9676]: https://github.com/home-assistant/home-assistant/pull/9676
[#9677]: https://github.com/home-assistant/home-assistant/pull/9677
[#9679]: https://github.com/home-assistant/home-assistant/pull/9679
[#9684]: https://github.com/home-assistant/home-assistant/pull/9684
[#9685]: https://github.com/home-assistant/home-assistant/pull/9685
[#9686]: https://github.com/home-assistant/home-assistant/pull/9686
[#9690]: https://github.com/home-assistant/home-assistant/pull/9690
[#9691]: https://github.com/home-assistant/home-assistant/pull/9691
[#9692]: https://github.com/home-assistant/home-assistant/pull/9692
[#9695]: https://github.com/home-assistant/home-assistant/pull/9695
[#9697]: https://github.com/home-assistant/home-assistant/pull/9697
[#9712]: https://github.com/home-assistant/home-assistant/pull/9712
[#9713]: https://github.com/home-assistant/home-assistant/pull/9713
[@BioSehnsucht]: https://github.com/BioSehnsucht
[@David-Byrne]: https://github.com/David-Byrne
[@FletcherAU]: https://github.com/FletcherAU
[@MisterWil]: https://github.com/MisterWil
[@Tommatheussen]: https://github.com/Tommatheussen
[@aequitas]: https://github.com/aequitas
[@alanfischer]: https://github.com/alanfischer
[@amelchio]: https://github.com/amelchio
[@andrey-git]: https://github.com/andrey-git
[@armills]: https://github.com/armills
[@arsaboo]: https://github.com/arsaboo
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bestlibre]: https://github.com/bestlibre
[@cmsimike]: https://github.com/cmsimike
[@danielhiversen]: https://github.com/danielhiversen
[@djchen]: https://github.com/djchen
[@enriquegh]: https://github.com/enriquegh
[@etsinko]: https://github.com/etsinko
[@exxamalte]: https://github.com/exxamalte
[@fabaff]: https://github.com/fabaff
[@happyleavesaoc]: https://github.com/happyleavesaoc
[@hotplot]: https://github.com/hotplot
[@jalmeroth]: https://github.com/jalmeroth
[@jeroenterheerdt]: https://github.com/jeroenterheerdt
[@joe248]: https://github.com/joe248
[@lwis]: https://github.com/lwis
[@marthoc]: https://github.com/marthoc
[@mbrrg]: https://github.com/mbrrg
[@mika]: https://github.com/mika
[@milanvo]: https://github.com/milanvo
[@mw-white]: https://github.com/mw-white
[@mweimerskirch]: https://github.com/mweimerskirch
[@nkgilley]: https://github.com/nkgilley
[@passie]: https://github.com/passie
[@pfalcon]: https://github.com/pfalcon
[@philk]: https://github.com/philk
[@postlund]: https://github.com/postlund
[@pvizeli]: https://github.com/pvizeli
[@rbflurry]: https://github.com/rbflurry
[@rytilahti]: https://github.com/rytilahti
[@snjoetw]: https://github.com/snjoetw
[@sti0]: https://github.com/sti0
[@szogi]: https://github.com/szogi
[@tchellomello]: https://github.com/tchellomello
[@tinloaf]: https://github.com/tinloaf
[@vickyg3]: https://github.com/vickyg3
[@w1ll1am23]: https://github.com/w1ll1am23
[abode docs]: https://home-assistant.io/components/abode/
[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
[alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/
[alexa.smart_home docs]: https://home-assistant.io/components/alexa/
[apple_tv docs]: https://home-assistant.io/components/apple_tv/
[arlo docs]: https://home-assistant.io/components/arlo/
[binary_sensor.raincloud docs]: https://home-assistant.io/components/binary_sensor.raincloud/
[binary_sensor.threshold docs]: https://home-assistant.io/components/binary_sensor.threshold/
[binary_sensor.wink docs]: https://home-assistant.io/components/binary_sensor.wink/
[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
[camera.synology docs]: https://home-assistant.io/components/camera.synology/
[camera.usps docs]: https://home-assistant.io/components/camera.usps/
[climate.ecobee docs]: https://home-assistant.io/components/climate.ecobee/
[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
[cover.mqtt docs]: https://home-assistant.io/components/cover.mqtt/
[cover.rflink docs]: https://home-assistant.io/components/cover.rflink/
[demo docs]: https://home-assistant.io/components/demo/
[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
[device_tracker.owntracks_http docs]: https://home-assistant.io/components/device_tracker.owntracks_http/
[duckdns docs]: https://home-assistant.io/components/duckdns/
[ecobee docs]: https://home-assistant.io/components/ecobee/
[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
[google docs]: https://home-assistant.io/components/calendar.google/
[group docs]: https://home-assistant.io/components/group/
[hassio docs]: https://home-assistant.io/hassio/
[history docs]: https://home-assistant.io/components/history/
[homematic docs]: https://home-assistant.io/components/homematic/
[http docs]: https://home-assistant.io/components/http/
[image_processing.opencv docs]: https://home-assistant.io/components/image_processing.opencv/
[influxdb docs]: https://home-assistant.io/components/influxdb/
[input_datetime docs]: https://home-assistant.io/components/input_datetime/
[input_number docs]: https://home-assistant.io/components/input_number/
[light.flux_led docs]: https://home-assistant.io/components/light.flux_led/
[light.rflink docs]: https://home-assistant.io/components/light.rflink/
[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
[lock.wink docs]: https://home-assistant.io/components/lock.wink/
[media_extractor docs]: https://home-assistant.io/components/media_extractor/
[media_player.apple_tv docs]: https://home-assistant.io/components/media_player.apple_tv/
[media_player.webostv docs]: https://home-assistant.io/components/media_player.webostv/
[media_player.yamaha_musiccast docs]: https://home-assistant.io/components/media_player.yamaha_musiccast/
[mqtt_statestream docs]: https://home-assistant.io/components/mqtt_statestream/
[notify.clicksendaudio docs]: https://home-assistant.io/components/notify.clicksendaudio/
[notify.discord docs]: https://home-assistant.io/components/notify.discord/
[notify.facebook docs]: https://home-assistant.io/components/notify.facebook/
[notify.simplepush docs]: https://home-assistant.io/components/notify.simplepush/
[raincloud docs]: https://home-assistant.io/components/raincloud/
[raspihats docs]: https://home-assistant.io/components/raspihats/
[recorder docs]: https://home-assistant.io/components/recorder/
[remote.itach docs]: https://home-assistant.io/components/remote.itach/
[rflink docs]: https://home-assistant.io/components/rflink/
[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
[sensor.comed_hourly_pricing docs]: https://home-assistant.io/components/sensor.comed_hourly_pricing/
[sensor.dsmr docs]: https://home-assistant.io/components/sensor.dsmr/
[sensor.fedex docs]: https://home-assistant.io/components/sensor.fedex/
[sensor.geo_rss_events docs]: https://home-assistant.io/components/sensor.geo_rss_events/
[sensor.google_travel_time docs]: https://home-assistant.io/components/sensor.google_travel_time/
[sensor.imap docs]: https://home-assistant.io/components/sensor.imap/
[sensor.lyft docs]: https://home-assistant.io/components/sensor.lyft/
[sensor.onewire docs]: https://home-assistant.io/components/sensor.onewire/
[sensor.pvoutput docs]: https://home-assistant.io/components/sensor.pvoutput/
[sensor.raincloud docs]: https://home-assistant.io/components/sensor.raincloud/
[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
[sensor.thethingsnetwork docs]: https://home-assistant.io/components/sensor.thethingsnetwork/
[sensor.tibber docs]: https://home-assistant.io/components/sensor.tibber/
[sensor.ups docs]: https://home-assistant.io/components/sensor.ups/
[sensor.usps docs]: https://home-assistant.io/components/sensor.usps/
[sensor.vera docs]: https://home-assistant.io/components/sensor.vera/
[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
[splunk docs]: https://home-assistant.io/components/splunk/
[switch.abode docs]: https://home-assistant.io/components/switch.abode/
[switch.raincloud docs]: https://home-assistant.io/components/switch.raincloud/
[switch.rflink docs]: https://home-assistant.io/components/switch.rflink/
[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
[thethingsnetwork docs]: https://home-assistant.io/components/thethingsnetwork/
[tradfri docs]: https://home-assistant.io/components/tradfri/
[upnp docs]: https://home-assistant.io/components/upnp/
[usps docs]: https://home-assistant.io/components/usps/
[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
[wink docs]: https://home-assistant.io/components/wink/
[zwave docs]: https://home-assistant.io/components/zwave/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[discord]: https://discord.gg/c5DvZ4e
[history_graph docs]: https://home-assistant.io/components/history_graph/

97
source/developers/credits.markdown
View File

@ -2,7 +2,7 @@
layout: page
title: "Credits"
description: "Credits for the developers who contributed to Home Assistant."
date: 2017-10-04 08:40:03 +0000
date: 2017-10-07 22:31:01 +0000
sidebar: true
comments: false
sharing: true
@ -13,13 +13,13 @@ This page contains a list of people who have contributed in one way or another t
### {% linkable_title Author %}
- [Paulus Schoutsen (@balloob)](https://github.com/balloob "5822 total commits to the home-assistant organization, 3482 commits to home-assistant, 1258 commits to home-assistant.github.io, 606 commits to home-assistant-polymer, 244 commits to home-assistant-js, 116 commits to netdisco, 42 commits to home-assistant-js-websocket, 24 commits to hass-release, 12 commits to home-assistant-assets, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 5 commits to LabelBot, 4 commits to hassio, 3 commits to hassio-addons, 2 commits to issue-bot, 2 commits to hassio-addons-example, 2 commits to python-hassbian, 2 commits to lambda-home-assistant-github, 1 commit to home-assistant-notebooks, 1 commit to hassio-build, 1 commit to home-assistant-iOS")
- [Paulus Schoutsen (@balloob)](https://github.com/balloob "5830 total commits to the home-assistant organization, 3489 commits to home-assistant, 1259 commits to home-assistant.github.io, 606 commits to home-assistant-polymer, 244 commits to home-assistant-js, 116 commits to netdisco, 42 commits to home-assistant-js-websocket, 24 commits to hass-release, 12 commits to home-assistant-assets, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 5 commits to LabelBot, 4 commits to hassio, 3 commits to hassio-addons, 2 commits to issue-bot, 2 commits to hassio-addons-example, 2 commits to lambda-home-assistant-github, 2 commits to python-hassbian, 1 commit to home-assistant-notebooks, 1 commit to hassio-build, 1 commit to home-assistant-iOS")
### {% linkable_title Contributors %}
(in alphabetical order)
- [Aaron Bach (@bachya)](https://github.com/bachya "16 total commits to the home-assistant organization, 11 commits to home-assistant, 5 commits to home-assistant.github.io")
- [Aaron Bach (@bachya)](https://github.com/bachya "17 total commits to the home-assistant organization, 12 commits to home-assistant, 5 commits to home-assistant.github.io")
- [Aaron Linville (@linville)](https://github.com/linville "2 total commits to the home-assistant organization, 2 commits to appdaemon")
- [Aaron Morris (@Morrisai)](https://github.com/Morrisai "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Aaron Polley (@xarnze)](https://github.com/xarnze "1 total commits to the home-assistant organization, 1 commit to home-assistant")
@ -29,7 +29,7 @@ This page contains a list of people who have contributed in one way or another t
- [Adam Baxter (@voltagex)](https://github.com/voltagex "2 total commits to the home-assistant organization, 1 commit to home-assistant-polymer, 1 commit to home-assistant")
- [Adam Dullage (@Dullage)](https://github.com/Dullage "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Adam Garcia (@pancho-villa)](https://github.com/pancho-villa "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Adam Mills (@armills)](https://github.com/armills "207 total commits to the home-assistant organization, 133 commits to home-assistant, 35 commits to home-assistant-polymer, 35 commits to home-assistant.github.io, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant")
- [Adam Mills (@armills)](https://github.com/armills "211 total commits to the home-assistant organization, 134 commits to home-assistant, 38 commits to home-assistant.github.io, 35 commits to home-assistant-polymer, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant")
- [Adam Stone (@astone123)](https://github.com/astone123 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Adrian Popa (@mad-ady)](https://github.com/mad-ady "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
- [Adrien Ball (@adrienball)](https://github.com/adrienball "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -56,18 +56,18 @@ This page contains a list of people who have contributed in one way or another t
- [Alfie Day (@Azelphur)](https://github.com/Azelphur "12 total commits to the home-assistant organization, 12 commits to home-assistant")
- [Aliaksandr (@minchik)](https://github.com/minchik "7 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to appdaemon, 2 commits to home-assistant")
- [Allan Glen (@allanglen)](https://github.com/allanglen "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "88 total commits to the home-assistant organization, 57 commits to home-assistant.github.io, 29 commits to home-assistant, 1 commit to hassio-addons, 1 commit to pi-gen")
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "90 total commits to the home-assistant organization, 57 commits to home-assistant.github.io, 31 commits to home-assistant, 1 commit to hassio-addons, 1 commit to pi-gen")
- [amigian74 (@amigian74)](https://github.com/amigian74 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [amorsillo (@AndrewMorsillo)](https://github.com/AndrewMorsillo "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "102 total commits to the home-assistant organization, 74 commits to home-assistant, 26 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
- [Andrea Falcone (@asfalcone)](https://github.com/asfalcone "5 total commits to the home-assistant organization, 5 commits to issue-bot")
- [Andreas Cambitsis (@acambitsis)](https://github.com/acambitsis "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Andreas Jacobsen (@andreasjacobsen93)](https://github.com/andreasjacobsen93 "4 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 1 commit to home-assistant")
- [Andreas Jacobsen (@andreasjacobsen93)](https://github.com/andreasjacobsen93 "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 1 commit to hassio-addons, 1 commit to home-assistant")
- [Andreas Rammhold (@andir)](https://github.com/andir "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
- [Andreas Renberg (@IQAndreas)](https://github.com/IQAndreas "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Andreea-Daniela Ene (@AndreeaEne)](https://github.com/AndreeaEne "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Andrew (@aoakeson)](https://github.com/aoakeson "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
- [Andrew (@aneisch)](https://github.com/aneisch "5 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 1 commit to home-assistant")
- [Andrew (@aoakeson)](https://github.com/aoakeson "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "606 total commits to the home-assistant organization, 475 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 18 commits to home-assistant.github.io")
- [Andrew LeCody (@aceat64)](https://github.com/aceat64 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Andrew Smith (@andrewmichaelsmith)](https://github.com/andrewmichaelsmith "2 total commits to the home-assistant organization, 2 commits to pi-gen")
@ -75,7 +75,7 @@ This page contains a list of people who have contributed in one way or another t
- [Andrew Thigpen (@andythigpen)](https://github.com/andythigpen "33 total commits to the home-assistant organization, 32 commits to home-assistant, 1 commit to home-assistant-js")
- [Andrew Williams (@nikdoof)](https://github.com/nikdoof "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [andrew-curtis (@andrew-curtis)](https://github.com/andrew-curtis "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
- [Andrey (@andrey-git)](https://github.com/andrey-git "174 total commits to the home-assistant organization, 87 commits to home-assistant, 59 commits to home-assistant-polymer, 28 commits to home-assistant.github.io")
- [Andrey (@andrey-git)](https://github.com/andrey-git "177 total commits to the home-assistant organization, 88 commits to home-assistant, 61 commits to home-assistant-polymer, 28 commits to home-assistant.github.io")
- [Andrey Kupreychik (@foxel)](https://github.com/foxel "4 total commits to the home-assistant organization, 4 commits to home-assistant")
- [Andrzej (@andriej)](https://github.com/andriej "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
- [Andréas Lundgren (@adevade)](https://github.com/adevade "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
@ -95,9 +95,11 @@ This page contains a list of people who have contributed in one way or another t
- [arjenfvellinga (@arjenfvellinga)](https://github.com/arjenfvellinga "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Arno (@aetjansen)](https://github.com/aetjansen "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [ArrayLabs (@arraylabs)](https://github.com/arraylabs "7 total commits to the home-assistant organization, 5 commits to home-assistant, 2 commits to home-assistant.github.io")
- [arretx (@arretx)](https://github.com/arretx "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Arthur Leonard Andersen (@leoc)](https://github.com/leoc "9 total commits to the home-assistant organization, 9 commits to home-assistant")
- [Arttu mahlakaarto (@amahlaka)](https://github.com/amahlaka "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
- [ashev (@ashev)](https://github.com/ashev "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Ashton Campbell (@AshtonCampbell)](https://github.com/AshtonCampbell "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
- [Assaf Inbal (@shmuelzon)](https://github.com/shmuelzon "12 total commits to the home-assistant organization, 9 commits to homebridge-homeassistant, 3 commits to home-assistant")
- [Audric Schiltknecht (@chemicalstorm)](https://github.com/chemicalstorm "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Audun Ytterdal (@auduny)](https://github.com/auduny "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -120,10 +122,10 @@ This page contains a list of people who have contributed in one way or another t
- [Benjamin Parzella (@bparzella)](https://github.com/bparzella "1 total commits to the home-assistant organization, 1 commit to pi-gen")
- [Benoit BESSET (@bbesset)](https://github.com/bbesset "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [bergemalm (@bergemalm)](https://github.com/bergemalm "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [bestlibre (@bestlibre)](https://github.com/bestlibre "14 total commits to the home-assistant organization, 7 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to hassio, 1 commit to hassio-build")
- [bestlibre (@bestlibre)](https://github.com/bestlibre "15 total commits to the home-assistant organization, 8 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to hassio, 1 commit to hassio-build")
- [BigMoby (@bigmoby)](https://github.com/bigmoby "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Bill Nelson (@xhostplus)](https://github.com/xhostplus "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [BioSehnsucht (@BioSehnsucht)](https://github.com/BioSehnsucht "9 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant, 2 commits to home-assistant-polymer")
- [BioSehnsucht (@BioSehnsucht)](https://github.com/BioSehnsucht "12 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 3 commits to home-assistant, 2 commits to home-assistant-polymer")
- [Bjarni Ivarsson (@bjarniivarsson)](https://github.com/bjarniivarsson "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant-polymer")
- [bl8rnr (@bl8rnr)](https://github.com/bl8rnr "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Blanyal D'Souza (@blanyal)](https://github.com/blanyal "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
@ -156,23 +158,23 @@ This page contains a list of people who have contributed in one way or another t
- [Caius Cioran (@caiuspb)](https://github.com/caiuspb "3 total commits to the home-assistant organization, 3 commits to home-assistant")
- [Caleb (@finish06)](https://github.com/finish06 "7 total commits to the home-assistant organization, 7 commits to home-assistant")
- [Cameron Bulock (@cbulock)](https://github.com/cbulock "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant")
- [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "88 total commits to the home-assistant organization, 80 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to fabric-home-assistant, 1 commit to homebridge-homeassistant, 1 commit to hassbian-scripts")
- [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "88 total commits to the home-assistant organization, 80 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to fabric-home-assistant, 1 commit to hassbian-scripts, 1 commit to homebridge-homeassistant")
- [carlosmgr (@carlosmgr)](https://github.com/carlosmgr "6 total commits to the home-assistant organization, 6 commits to home-assistant")
- [Carter (@BluGeni)](https://github.com/BluGeni "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
- [cdce8p (@cdce8p)](https://github.com/cdce8p "6 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [cdce8p (@cdce8p)](https://github.com/cdce8p "7 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [Cecron (@Cecron)](https://github.com/Cecron "1 total commits to the home-assistant organization, 1 commit to appdaemon")
- [Cenk Gündoğan (@cgundogan)](https://github.com/cgundogan "1 total commits to the home-assistant organization, 1 commit to libcoap")
- [cgtobi (@cgtobi)](https://github.com/cgtobi "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant")
- [chanders (@chanders)](https://github.com/chanders "2 total commits to the home-assistant organization, 2 commits to hadashboard")
- [Charles Blonde (@CharlesBlonde)](https://github.com/CharlesBlonde "19 total commits to the home-assistant organization, 12 commits to home-assistant, 7 commits to home-assistant.github.io")
- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
- [Charles Spirakis (@srcLurker)](https://github.com/srcLurker "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Chayoung You (@yous)](https://github.com/yous "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Check your git settings! (@invalid-email-address)](https://github.com/invalid-email-address "1 total commits to the home-assistant organization, 1 commit to libcoap")
- [Chema García (@sch3m4)](https://github.com/sch3m4 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Chia-liang Kao (@clkao)](https://github.com/clkao "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Chris (@firstof9)](https://github.com/firstof9 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Chris (@chennin)](https://github.com/chennin "15 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 4 commits to home-assistant")
- [Chris (@firstof9)](https://github.com/firstof9 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Chris Aloi (@ctaloi)](https://github.com/ctaloi "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Chris Baumgartner (@mchrisb03)](https://github.com/mchrisb03 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Chris Huegle (@chuegle)](https://github.com/chuegle "1 total commits to the home-assistant organization, 1 commit to netdisco")
@ -210,6 +212,7 @@ This page contains a list of people who have contributed in one way or another t
- [Dan (@danieljkemp)](https://github.com/danieljkemp "23 total commits to the home-assistant organization, 16 commits to home-assistant, 7 commits to home-assistant.github.io")
- [Dan Chen (@djchen)](https://github.com/djchen "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "14 total commits to the home-assistant organization, 12 commits to home-assistant, 2 commits to home-assistant.github.io")
- [Dan Faulknor (@danielfaulknor)](https://github.com/danielfaulknor "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Dan Ford (@dpford)](https://github.com/dpford "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Dan Ports (@drkp)](https://github.com/drkp "4 total commits to the home-assistant organization, 4 commits to home-assistant")
- [Dan Sarginson (@dansarginson)](https://github.com/dansarginson "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -218,9 +221,9 @@ This page contains a list of people who have contributed in one way or another t
- [Dan Van Brunt (@iDVB)](https://github.com/iDVB "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Dani (@danichispa)](https://github.com/danichispa "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
- [Daniel Escoz (@Darkhogg)](https://github.com/Darkhogg "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "339 total commits to the home-assistant organization, 232 commits to home-assistant, 105 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "341 total commits to the home-assistant organization, 233 commits to home-assistant, 106 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
- [Daniel Matuschek (@usul27)](https://github.com/usul27 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "61 total commits to the home-assistant organization, 33 commits to home-assistant.github.io, 26 commits to home-assistant, 2 commits to hassio-addons")
- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "63 total commits to the home-assistant organization, 34 commits to home-assistant.github.io, 27 commits to home-assistant, 2 commits to hassio-addons")
- [Daniel Peukert (@dpeukert)](https://github.com/dpeukert "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [Daniel Schaal (@schaal)](https://github.com/schaal "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Daniel Stone (@daniel-stoneuk)](https://github.com/daniel-stoneuk "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
@ -229,6 +232,7 @@ This page contains a list of people who have contributed in one way or another t
- [Danijel Stojnic (@danijelst)](https://github.com/danijelst "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Daniyar Yeralin (@yeralin)](https://github.com/yeralin "2 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant, 1 commit to home-assistant")
- [dasos (@dasos)](https://github.com/dasos "10 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.github.io, 1 commit to netdisco")
- [datafx (@datafx)](https://github.com/datafx "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Dave (@d4v3d)](https://github.com/d4v3d "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Dave Banks (@djbanks)](https://github.com/djbanks "3 total commits to the home-assistant organization, 2 commits to appdaemon, 1 commit to home-assistant")
- [Dave J (@kxtcd950)](https://github.com/kxtcd950 "3 total commits to the home-assistant organization, 3 commits to hassbian-scripts")
@ -238,7 +242,7 @@ This page contains a list of people who have contributed in one way or another t
- [David Byrne (@David-Byrne)](https://github.com/David-Byrne "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [David De Sloovere (@DavidDeSloovere)](https://github.com/DavidDeSloovere "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [David Jackson (@David-Jackson)](https://github.com/David-Jackson "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [David McNett (@nugget)](https://github.com/nugget "10 total commits to the home-assistant organization, 5 commits to home-assistant, 5 commits to home-assistant.github.io")
- [David McNett (@nugget)](https://github.com/nugget "10 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 5 commits to home-assistant")
- [David Ohayon (@ohayon)](https://github.com/ohayon "3 total commits to the home-assistant organization, 3 commits to issue-bot")
- [David Straub (@DavidMStraub)](https://github.com/DavidMStraub "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
- [David Wang (@dcwangmit01)](https://github.com/dcwangmit01 "2 total commits to the home-assistant organization, 2 commits to pi-gen")
@ -275,14 +279,13 @@ This page contains a list of people who have contributed in one way or another t
- [Enrique Gonzalez (@enriquegh)](https://github.com/enriquegh "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Eric Clymer (@ericwclymer)](https://github.com/ericwclymer "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Eric Hagan (@ehagan)](https://github.com/ehagan "2 total commits to the home-assistant organization, 1 commit to home-assistant-polymer, 1 commit to home-assistant")
- [Eric Jansen (@ej81)](https://github.com/ej81 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
- [Eric Rolf (@xrolfex)](https://github.com/xrolfex "13 total commits to the home-assistant organization, 13 commits to home-assistant")
- [Eric Thompson (@er0ck)](https://github.com/er0ck "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Erik Eriksson (@molobrakos)](https://github.com/molobrakos "98 total commits to the home-assistant organization, 90 commits to home-assistant, 5 commits to home-assistant.github.io, 3 commits to netdisco")
- [Erik-jan Riemers (@riemers)](https://github.com/riemers "11 total commits to the home-assistant organization, 11 commits to home-assistant.github.io")
- [ettisan (@ettisan)](https://github.com/ettisan "8 total commits to the home-assistant organization, 8 commits to home-assistant")
- [Eugenio Panadero (@azogue)](https://github.com/azogue "68 total commits to the home-assistant organization, 39 commits to home-assistant, 23 commits to home-assistant.github.io, 3 commits to homebridge-homeassistant, 3 commits to home-assistant-polymer")
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4155 total commits to the home-assistant organization, 2588 commits to home-assistant.github.io, 1368 commits to home-assistant, 61 commits to home-assistant-ansible, 29 commits to home-assistant-notebooks, 24 commits to home-assistant-assets, 24 commits to home-assistant-cli, 23 commits to home-assistant-dev-helper, 11 commits to hassio-build, 10 commits to home-assistant-polymer, 8 commits to netdisco, 5 commits to hassio-addons, 2 commits to hassio, 1 commit to home-assistant-js-websocket, 1 commit to organization")
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4168 total commits to the home-assistant organization, 2597 commits to home-assistant.github.io, 1373 commits to home-assistant, 61 commits to home-assistant-ansible, 29 commits to home-assistant-notebooks, 24 commits to home-assistant-cli, 24 commits to home-assistant-assets, 23 commits to home-assistant-dev-helper, 11 commits to hassio-build, 10 commits to home-assistant-polymer, 8 commits to netdisco, 5 commits to hassio-addons, 2 commits to hassio, 1 commit to home-assistant-js-websocket")
- [Fabian Heredia Montiel (@fabianhjr)](https://github.com/fabianhjr "4 total commits to the home-assistant organization, 4 commits to home-assistant")
- [fakezeta (@fakezeta)](https://github.com/fakezeta "7 total commits to the home-assistant organization, 7 commits to home-assistant")
- [Fares Rihani (@anchepiece)](https://github.com/anchepiece "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
@ -293,15 +296,15 @@ This page contains a list of people who have contributed in one way or another t
- [Ferry van Zeelst (@StaticCube)](https://github.com/StaticCube "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant")
- [Finbarr Brady (@fbradyirl)](https://github.com/fbradyirl "8 total commits to the home-assistant organization, 8 commits to home-assistant")
- [Florian Holzapfel (@florianholzapfel)](https://github.com/florianholzapfel "11 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 4 commits to home-assistant, 3 commits to netdisco")
- [Florian Klien (@flowolf)](https://github.com/flowolf "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [florincosta (@florincosta)](https://github.com/florincosta "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Florian Klien (@flowolf)](https://github.com/flowolf "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [florincosta (@florincosta)](https://github.com/florincosta "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
- [Fonta (@f0nt4)](https://github.com/f0nt4 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
- [Franck Nijhof (@frenck)](https://github.com/frenck "10 total commits to the home-assistant organization, 9 commits to home-assistant.github.io, 1 commit to hassio")
- [Franck Nijhof (@frenck)](https://github.com/frenck "13 total commits to the home-assistant organization, 12 commits to home-assistant.github.io, 1 commit to hassio")
- [Frank (@syphernl)](https://github.com/syphernl "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
- [Frantz (@rofrantz)](https://github.com/rofrantz "2 total commits to the home-assistant organization, 2 commits to netdisco")
- [François Martin (@martinfrancois)](https://github.com/martinfrancois "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Frederic Hemberger (@fhemberger)](https://github.com/fhemberger "93 total commits to the home-assistant organization, 93 commits to home-assistant.github.io")
- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "160 total commits to the home-assistant organization, 65 commits to home-assistant.github.io, 63 commits to hassbian-scripts, 27 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer")
- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "163 total commits to the home-assistant organization, 68 commits to home-assistant.github.io, 63 commits to hassbian-scripts, 27 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer")
- [freol35241 (@freol35241)](https://github.com/freol35241 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [froz (@froz)](https://github.com/froz "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [fuga2136 (@fuga2136)](https://github.com/fuga2136 "13 total commits to the home-assistant organization, 13 commits to home-assistant.github.io")
@ -311,7 +314,7 @@ This page contains a list of people who have contributed in one way or another t
- [Gavin Mogan (@halkeye)](https://github.com/halkeye "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Geoff Norton (@kangaroo)](https://github.com/kangaroo "14 total commits to the home-assistant organization, 14 commits to home-assistant")
- [George.M (@nodinosaur)](https://github.com/nodinosaur "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant")
- [Georgi Kirichkov (@kirichkov)](https://github.com/kirichkov "8 total commits to the home-assistant organization, 4 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Georgi Kirichkov (@kirichkov)](https://github.com/kirichkov "9 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant")
- [Georgi Yanev (@jumpalottahigh)](https://github.com/jumpalottahigh "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Georgii Staroselskii (@staroselskii)](https://github.com/staroselskii "1 total commits to the home-assistant organization, 1 commit to pi-gen")
- [Gergely Imreh (@imrehg)](https://github.com/imrehg "16 total commits to the home-assistant organization, 11 commits to home-assistant, 5 commits to home-assistant.github.io")
@ -319,7 +322,7 @@ This page contains a list of people who have contributed in one way or another t
- [Gianpaolo Macario (@gmacario)](https://github.com/gmacario "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Giel Janssens (@gieljnssns)](https://github.com/gieljnssns "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
- [githubbuh (@githubbuh)](https://github.com/githubbuh "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [gitmopp (@gitmopp)](https://github.com/gitmopp "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [gitmopp (@gitmopp)](https://github.com/gitmopp "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [GMFalka (@GMFalka)](https://github.com/GMFalka "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Gopal Kildoliya (@gopalkildoliya)](https://github.com/gopalkildoliya "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io")
- [Graeme Smith (@Instagraeme)](https://github.com/Instagraeme "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
@ -336,7 +339,7 @@ This page contains a list of people who have contributed in one way or another t
- [Hajime Morrita (@omo)](https://github.com/omo "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Hamid (@hamid-elaosta)](https://github.com/hamid-elaosta "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Hao Hu (@howiehu)](https://github.com/howiehu "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [happyleavesaoc (@happyleavesaoc)](https://github.com/happyleavesaoc "107 total commits to the home-assistant organization, 84 commits to home-assistant, 22 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [happyleavesaoc (@happyleavesaoc)](https://github.com/happyleavesaoc "109 total commits to the home-assistant organization, 86 commits to home-assistant, 22 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [Harald Nagel (@haraldnagel)](https://github.com/haraldnagel "8 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to home-assistant.github.io")
- [Hari Menon (@floydpink)](https://github.com/floydpink "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Harris Borawski (@hborawski)](https://github.com/hborawski "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -397,19 +400,20 @@ This page contains a list of people who have contributed in one way or another t
- [Jeff Schroeder (@SEJeff)](https://github.com/SEJeff "17 total commits to the home-assistant organization, 17 commits to home-assistant")
- [Jeff Wilson (@jawilson)](https://github.com/jawilson "24 total commits to the home-assistant organization, 19 commits to home-assistant, 5 commits to home-assistant.github.io")
- [Jeffrey Lin (@linjef)](https://github.com/linjef "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Jens (@jhoepken)](https://github.com/jhoepken "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Jeremiah Wuenschel (@jer)](https://github.com/jer "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Jeremy (@Wutname1)](https://github.com/Wutname1 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Jeroen ter Heerdt (@jeroenterheerdt)](https://github.com/jeroenterheerdt "8 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to home-assistant.github.io")
- [Jeremy Williams (@jwillaz)](https://github.com/jwillaz "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Jeroen ter Heerdt (@jeroenterheerdt)](https://github.com/jeroenterheerdt "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Jerold Albertson (@jeroldalbertson-wf)](https://github.com/jeroldalbertson-wf "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [Jesse Hills (@jesserockz)](https://github.com/jesserockz "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Jesse Newland (@jnewland)](https://github.com/jnewland "14 total commits to the home-assistant organization, 11 commits to home-assistant, 3 commits to hubot-home-assistant")
- [JesseWebDotCom (@JesseWebDotCom)](https://github.com/JesseWebDotCom "16 total commits to the home-assistant organization, 8 commits to home-assistant, 8 commits to home-assistant.github.io")
- [JesseWebDotCom (@JesseWebDotCom)](https://github.com/JesseWebDotCom "16 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 8 commits to home-assistant")
- [jgrieger1 (@jgrieger1)](https://github.com/jgrieger1 "1 total commits to the home-assistant organization, 1 commit to appdaemon")
- [jgriff2 (@jgriff2)](https://github.com/jgriff2 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Jim Rollenhagen (@jimrollenhagen)](https://github.com/jimrollenhagen "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [jnimmo (@jnimmo)](https://github.com/jnimmo "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Joakim Nohlgård (@gebart)](https://github.com/gebart "2 total commits to the home-assistant organization, 2 commits to libcoap")
- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "21 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 10 commits to hassbian-scripts")
- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "23 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 10 commits to hassbian-scripts")
- [Job (@jmvermeulen)](https://github.com/jmvermeulen "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Joe Lee (@xnoodle)](https://github.com/xnoodle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Joe Lu (@snjoetw)](https://github.com/snjoetw "5 total commits to the home-assistant organization, 5 commits to home-assistant")
@ -426,7 +430,6 @@ This page contains a list of people who have contributed in one way or another t
- [John Coggeshall (@coogle)](https://github.com/coogle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [John McLaughlin (@loghound)](https://github.com/loghound "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [John Mihalic (@mezz64)](https://github.com/mezz64 "45 total commits to the home-assistant organization, 31 commits to home-assistant, 12 commits to home-assistant.github.io, 1 commit to hadashboard, 1 commit to home-assistant-polymer")
- [johnappletree (@johnappletree)](https://github.com/johnappletree "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Johnny Chadda (@joch)](https://github.com/joch "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Jon (@JonMurphy)](https://github.com/JonMurphy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Jon Caruana (@joncar)](https://github.com/joncar "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
@ -452,12 +455,10 @@ This page contains a list of people who have contributed in one way or another t
- [Justin Hayes (@GussyH)](https://github.com/GussyH "7 total commits to the home-assistant organization, 7 commits to hadashboard")
- [Justin Weberg (@justweb1)](https://github.com/justweb1 "28 total commits to the home-assistant organization, 13 commits to home-assistant-polymer, 7 commits to hassbot, 4 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to home-assistant-js, 1 commit to hassio")
- [Justyn Shull (@justyns)](https://github.com/justyns "5 total commits to the home-assistant organization, 5 commits to home-assistant")
- [jwillaz (@jwillaz)](https://github.com/jwillaz "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Kai (@luxus)](https://github.com/luxus "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Kane610 (@Kane610)](https://github.com/Kane610 "10 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant, 1 commit to netdisco")
- [Karen Goode (@kfgoode)](https://github.com/kfgoode "4 total commits to the home-assistant organization, 4 commits to home-assistant")
- [karlkar (@karlkar)](https://github.com/karlkar "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [kaustubhphatak (@kaustubhphatak)](https://github.com/kaustubhphatak "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Keaton Taylor (@keatontaylor)](https://github.com/keatontaylor "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Keith (@seedzero)](https://github.com/seedzero "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Keith Lamprecht (@Nixon506E)](https://github.com/Nixon506E "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -465,7 +466,7 @@ This page contains a list of people who have contributed in one way or another t
- [Ken Davidson (@kwdavidson)](https://github.com/kwdavidson "10 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 2 commits to appdaemon")
- [Kevin (@Mister-Espria)](https://github.com/Mister-Espria "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Kevin Christensen (@nivekmai)](https://github.com/nivekmai "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "13 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Kevin Gisi (@gisikw)](https://github.com/gisikw "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [Kevin Gottsman (@gottsman)](https://github.com/gottsman "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
- [Kevin Panaro (@kevinpanaro)](https://github.com/kevinpanaro "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -486,8 +487,7 @@ This page contains a list of people who have contributed in one way or another t
- [Leon99 (@Leon99)](https://github.com/Leon99 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Leonardo Saraiva (@vyper)](https://github.com/vyper "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Lev Aronsky (@aronsky)](https://github.com/aronsky "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Lewis Juggins (@lwis)](https://github.com/lwis "52 total commits to the home-assistant organization, 41 commits to home-assistant, 10 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [lichtteil (@lichtteil)](https://github.com/lichtteil "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Lewis Juggins (@lwis)](https://github.com/lwis "54 total commits to the home-assistant organization, 43 commits to home-assistant, 10 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
- [Lindsay Ward (@lindsaymarkward)](https://github.com/lindsaymarkward "17 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 4 commits to home-assistant")
- [linuxlurak (@linuxlurak)](https://github.com/linuxlurak "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to hadashboard")
- [lrmate (@lrmate)](https://github.com/lrmate "3 total commits to the home-assistant organization, 3 commits to home-assistant")
@ -495,12 +495,11 @@ This page contains a list of people who have contributed in one way or another t
- [LucaSoldi (@LucaSoldi)](https://github.com/LucaSoldi "6 total commits to the home-assistant organization, 6 commits to home-assistant")
- [Lucien Guimier (@guimier)](https://github.com/guimier "1 total commits to the home-assistant organization, 1 commit to libcoap")
- [Lukas (@lukas-hetzenecker)](https://github.com/lukas-hetzenecker "14 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Lukas Barth (@tinloaf)](https://github.com/tinloaf "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Lukas Barth (@tinloaf)](https://github.com/tinloaf "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Luke Armstrong (@lukearmstrong)](https://github.com/lukearmstrong "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Lupin Demid (@lupin-de-mid)](https://github.com/lupin-de-mid "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
- [Luuk (@Maharball1)](https://github.com/Maharball1 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [LvivEchoes (@LvivEchoes)](https://github.com/LvivEchoes "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
- [m4tek (@m4tek)](https://github.com/m4tek "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Maciej Sokołowski (@matemaciek)](https://github.com/matemaciek "1 total commits to the home-assistant organization, 1 commit to hassio-build")
- [Maciej Wasilak (@mwasilak)](https://github.com/mwasilak "1 total commits to the home-assistant organization, 1 commit to libcoap")
- [Magnus Ihse Bursie (@magicus)](https://github.com/magicus "16 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to netdisco, 3 commits to home-assistant.github.io")
@ -515,10 +514,9 @@ This page contains a list of people who have contributed in one way or another t
- [Marc Pabst (@mxtra)](https://github.com/mxtra "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
- [Marc Plano-Lesay (@Kernald)](https://github.com/Kernald "12 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 2 commits to home-assistant")
- [Marcel030nl (@Marcel030nl)](https://github.com/Marcel030nl "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "119 total commits to the home-assistant organization, 65 commits to home-assistant, 54 commits to home-assistant.github.io")
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "122 total commits to the home-assistant organization, 67 commits to home-assistant, 55 commits to home-assistant.github.io")
- [Marcin Jaworski (@yawor)](https://github.com/yawor "12 total commits to the home-assistant organization, 12 commits to appdaemon")
- [Marijn Giesen (@marijngiesen)](https://github.com/marijngiesen "7 total commits to the home-assistant organization, 5 commits to hadashboard, 2 commits to home-assistant.github.io")
- [mariwing (@mariwing)](https://github.com/mariwing "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Mark Huson (@mehuman)](https://github.com/mehuman "11 total commits to the home-assistant organization, 11 commits to home-assistant.github.io")
- [Mark Oude Veldhuis (@markoudev)](https://github.com/markoudev "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Markus Becker (@markushx)](https://github.com/markushx "6 total commits to the home-assistant organization, 6 commits to libcoap")
@ -536,7 +534,7 @@ This page contains a list of people who have contributed in one way or another t
- [Matt N. (@mnoorenberghe)](https://github.com/mnoorenberghe "23 total commits to the home-assistant organization, 15 commits to home-assistant.github.io, 7 commits to home-assistant, 1 commit to home-assistant-polymer")
- [Matt Rogers (@rogersmj)](https://github.com/rogersmj "20 total commits to the home-assistant organization, 20 commits to hadashboard")
- [Matt Schmitt (@schmittx)](https://github.com/schmittx "22 total commits to the home-assistant organization, 15 commits to homebridge-homeassistant, 5 commits to home-assistant, 2 commits to home-assistant.github.io")
- [Matt White (@mw-white)](https://github.com/mw-white "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Matt White (@mw-white)](https://github.com/mw-white "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
- [matt2005 (@matt2005)](https://github.com/matt2005 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Matteo Lampugnani (@t30)](https://github.com/t30 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
- [Matthew Bowen (@mgbowen)](https://github.com/mgbowen "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
@ -572,10 +570,11 @@ This page contains a list of people who have contributed in one way or another t
- [Mike Roberts (@m-roberts)](https://github.com/m-roberts "1 total commits to the home-assistant organization, 1 commit to pi-gen")
- [mikey (@pfista)](https://github.com/pfista "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Mikkel Høgh (@mikl)](https://github.com/mikl "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [milanvo (@milanvo)](https://github.com/milanvo "3 total commits to the home-assistant organization, 3 commits to home-assistant")
- [MinchinWeb (@MinchinWeb)](https://github.com/MinchinWeb "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [miniconfig (@miniconfig)](https://github.com/miniconfig "27 total commits to the home-assistant organization, 20 commits to home-assistant, 7 commits to home-assistant.github.io")
- [Minims (@Minims)](https://github.com/Minims "3 total commits to the home-assistant organization, 3 commits to homebridge-homeassistant")
- [Mister Wil (@MisterWil)](https://github.com/MisterWil "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Mister Wil (@MisterWil)](https://github.com/MisterWil "14 total commits to the home-assistant organization, 9 commits to home-assistant, 5 commits to home-assistant.github.io")
- [Mitesh Patel (@gurumitts)](https://github.com/gurumitts "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Mitko Masarliev (@masarliev)](https://github.com/masarliev "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [mje-nz (@mje-nz)](https://github.com/mje-nz "2 total commits to the home-assistant organization, 2 commits to home-assistant")
@ -590,7 +589,7 @@ This page contains a list of people who have contributed in one way or another t
- [Naren Salem (@naren8642)](https://github.com/naren8642 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Nate (@BillyNate)](https://github.com/BillyNate "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Nathan Flynn (@eperdeme)](https://github.com/eperdeme "1 total commits to the home-assistant organization, 1 commit to hassio-addons")
- [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "18 total commits to the home-assistant organization, 8 commits to home-assistant, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant, 1 commit to home-assistant-polymer, 1 commit to appdaemon")
- [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "18 total commits to the home-assistant organization, 8 commits to home-assistant, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant, 1 commit to appdaemon, 1 commit to home-assistant-polymer")
- [Neil Lathwood (@laf)](https://github.com/laf "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
- [Nelis Willers (@NelisW)](https://github.com/NelisW "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant")
- [NeLLyMerC (@NeLLyMerC)](https://github.com/NeLLyMerC "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
@ -625,7 +624,7 @@ This page contains a list of people who have contributed in one way or another t
- [oznu (@oznu)](https://github.com/oznu "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
- [Parker Moore (@parkr)](https://github.com/parkr "62 total commits to the home-assistant organization, 62 commits to home-assistant.github.io")
- [Pascal Bach (@bachp)](https://github.com/bachp "10 total commits to the home-assistant organization, 9 commits to home-assistant, 1 commit to netdisco")
- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "2023 total commits to the home-assistant organization, 800 commits to hassio, 388 commits to home-assistant, 289 commits to hassio-addons, 273 commits to hassio-build, 255 commits to home-assistant.github.io, 16 commits to hassio-addons-example, 1 commit to home-assistant-js-websocket, 1 commit to netdisco")
- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "2033 total commits to the home-assistant organization, 800 commits to hassio, 390 commits to home-assistant, 291 commits to hassio-addons, 276 commits to hassio-build, 258 commits to home-assistant.github.io, 16 commits to hassio-addons-example, 1 commit to home-assistant-js-websocket, 1 commit to netdisco")
- [patkap (@patkap)](https://github.com/patkap "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Patrick Aikens (@duckpuppy)](https://github.com/duckpuppy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Patrick Easters (@patrickeasters)](https://github.com/patrickeasters "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
@ -672,7 +671,7 @@ This page contains a list of people who have contributed in one way or another t
- [rkabadi (@rkabadi)](https://github.com/rkabadi "17 total commits to the home-assistant organization, 17 commits to home-assistant")
- [Rob Capellini (@capellini)](https://github.com/capellini "3 total commits to the home-assistant organization, 3 commits to home-assistant")
- [Rob Slifka (@rslifka)](https://github.com/rslifka "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1198 total commits to the home-assistant organization, 531 commits to home-assistant-iOS, 255 commits to home-assistant, 247 commits to home-assistant.github.io, 87 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to appdaemon, 3 commits to organization, 3 commits to scenegen, 3 commits to home-assistant-js-websocket, 3 commits to hadashboard, 3 commits to home-assistant-js, 3 commits to home-assistant-cli, 3 commits to hassbot, 2 commits to home-assistant-assets, 2 commits to home-assistant-notebooks, 2 commits to LabelBot, 2 commits to home-assistant-dev-helper, 2 commits to fabric-home-assistant, 2 commits to home-assistant-ansible, 2 commits to micropython-home-assistant, 2 commits to lambda-home-assistant-github")
- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1198 total commits to the home-assistant organization, 531 commits to home-assistant-iOS, 255 commits to home-assistant, 247 commits to home-assistant.github.io, 87 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to scenegen, 3 commits to appdaemon, 3 commits to organization, 3 commits to hadashboard, 3 commits to home-assistant-js-websocket, 3 commits to hassbot, 3 commits to home-assistant-js, 3 commits to home-assistant-cli, 2 commits to lambda-home-assistant-github, 2 commits to home-assistant-notebooks, 2 commits to LabelBot, 2 commits to home-assistant-dev-helper, 2 commits to fabric-home-assistant, 2 commits to home-assistant-ansible, 2 commits to micropython-home-assistant, 2 commits to home-assistant-assets")
- [Robby Grossman (@freerobby)](https://github.com/freerobby "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Robin (@robmarkcole)](https://github.com/robmarkcole "13 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 5 commits to home-assistant")
- [Robin Laurén (@llauren)](https://github.com/llauren "1 total commits to the home-assistant organization, 1 commit to appdaemon")
@ -744,7 +743,7 @@ This page contains a list of people who have contributed in one way or another t
- [tedstriker (@tedstriker)](https://github.com/tedstriker "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
- [Teemu Mikkonen (@T3m3z)](https://github.com/T3m3z "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
- [Teemu Patja (@tpatja)](https://github.com/tpatja "2 total commits to the home-assistant organization, 2 commits to home-assistant")
- [Teemu R. (@rytilahti)](https://github.com/rytilahti "35 total commits to the home-assistant organization, 27 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco")
- [Teemu R. (@rytilahti)](https://github.com/rytilahti "36 total commits to the home-assistant organization, 28 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco")
- [Teguh Sobirin (@tjstyle)](https://github.com/tjstyle "2 total commits to the home-assistant organization, 2 commits to pi-gen")
- [Terry Carlin (@terrycarlin)](https://github.com/terrycarlin "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Theb-1 (@Theb-1)](https://github.com/Theb-1 "5 total commits to the home-assistant organization, 5 commits to home-assistant")
@ -795,7 +794,7 @@ This page contains a list of people who have contributed in one way or another t
- [upsert (@upsert)](https://github.com/upsert "1 total commits to the home-assistant organization, 1 commit to netdisco")
- [Valentin Alexeev (@valentinalexeev)](https://github.com/valentinalexeev "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Valentin VĂLCIU (@axiac)](https://github.com/axiac "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [Vignesh Venkat (@vickyg3)](https://github.com/vickyg3 "3 total commits to the home-assistant organization, 3 commits to home-assistant")
- [Vignesh Venkat (@vickyg3)](https://github.com/vickyg3 "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io")
- [viswa-swami (@viswa-swami)](https://github.com/viswa-swami "9 total commits to the home-assistant organization, 9 commits to home-assistant")
- [Vlad Korniev (@vkorn)](https://github.com/vkorn "5 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to hassio-build")
- [vllungu (@vllungu)](https://github.com/vllungu "3 total commits to the home-assistant organization, 3 commits to libcoap")
@ -811,7 +810,7 @@ This page contains a list of people who have contributed in one way or another t
- [wind-rider (@wind-rider)](https://github.com/wind-rider "5 total commits to the home-assistant organization, 5 commits to home-assistant")
- [Wojciech Bederski (@wuub)](https://github.com/wuub "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
- [wokar (@wokar)](https://github.com/wokar "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.github.io")
- [Wolf-Bastian Pöttner (@BastianPoe)](https://github.com/BastianPoe "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io")
- [Wolf-Bastian Pöttner (@BastianPoe)](https://github.com/BastianPoe "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
- [Wolfgang Malgadey (@wmalgadey)](https://github.com/wmalgadey "4 total commits to the home-assistant organization, 4 commits to home-assistant")
- [XECDesign (@XECDesign)](https://github.com/XECDesign "97 total commits to the home-assistant organization, 97 commits to pi-gen")
- [Xorso (@Xorso)](https://github.com/Xorso "22 total commits to the home-assistant organization, 21 commits to home-assistant, 1 commit to hassio-addons")
@ -828,4 +827,4 @@ This page contains a list of people who have contributed in one way or another t
This page is irregularly updated using the [`credits_generator` tool](https://github.com/home-assistant/home-assistant.github.io/tree/next/credits_generator). If you think that you are missing, please let us know.
<i>This page was last updated Wednesday, October 4th 2017, 8:40:03 am UTC.</i>
<i>This page was last updated Saturday, October 7th 2017, 10:31:01 pm UTC.</i>

121
source/developers/documentation/create_page.markdown Normal file
View File

@ -0,0 +1,121 @@
---
layout: page
title: "Create a new page"
description: "Create a new page for the documentation"
date: 2015-06-17 08:00
sidebar: true
comments: false
sharing: true
footer: true
---
For a platform or component page, the fastest way is to make a copy of an existing page and edit it. The [Component overview](/components/) and the [Examples section](/cookbook/) are generated automatically, so there is no need to add a link to those pages.
Please honor the [Standards](/developers/documentation/standards/) we have for the documentation.
If you start from scratch with a page, you need to add a header. Different sections of the documentation may need different headers.
```text
---
layout: page
title: "Awesome Sensor"
description: "home-assistant.io web presence"
date: 2015-06-17 08:00
sidebar: true
comments: false
sharing: true
footer: true
ha_release: "0.38"
ha_category: Sensor
---
Content...Written in markdown.
{% raw %}### {% linkable_title Linkable Header %}{% endraw %}
...
```
There are [pre-definied variables](https://jekyllrb.com/docs/variables/) available but usually, it's not necessary to use them when writing documentation.
A couple of points to remember:
- Document the needed steps to retrieve API keys or access token for the third party service or device if needed.
- If you're adding a new component, for the `ha_release` part of the header, just increment of the current release. If the current release is 0.37, make `ha_release` 0.38. If it's 0.30 or 0.40 please quote it with `" "`.
- `ha_category:` is needed to list the platform or component in the appropriate category on the website.
### {% linkable_title Configuration %}
Every platform page should contain a configuration sample. This sample must contain only the **required** variables to make it easy to copy and paste it for users into their `configuration.yaml` file.
The **Configuration Variables** section must use the {% raw %}`{% configuration %} ... {% endconfiguration %}`{% endraw %} tag.
```text
{% raw %}
{% configuration %}
api_key:
description: The API key to access the service.
required: true
type: string
name:
description: Name to use in the frontend.
required: false
type: string
{% endconfiguration %}
{% endraw %}
```
- **`description:`**: That the variable is about.
- **`required:`**: If the variable is required.
```text
required: true #=> Required
required: false #=> Optional
required: inclusive #=> Inclusive
required: exclusive #=> Exclusive
required: any string here #=> Any string here
```
- **`type:`**: The type of the variable. Allowed entries: `string`, `int` or `map`. For multiple possibilities use `[string, int]`. If you use `map` then you need to define `keys:` (see the [`template` sensor](/components/sensor.template/) for an example).
### {% linkable_title Embedding Code %}
You can use the [default markdown syntax](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code) to generate syntax highlighted code. For inline code wrap your code in {% raw %}`{% endraw %}.
When you're writing code that is to be executed on the terminal, prefix it with `$`.
### {% linkable_title Templates %}
For the [configuration templating](/topics/templating/) is [Jinja](http://jinja.pocoo.org/) used. Check the [Documentation Standards](/developers/documentation/standards/) for further details.
If you are don't escape templates then they will be rendered and appear blank on the website.
### {% linkable_title HTML %}
The direct usage of HTML is supported but not recommended. The note boxes are an exception.
```html
<p class='note warning'>
You need to enable telnet on your router.
</p>
```
### {% linkable_title Redirects %}
If you rename or move an existing platform or component, create the redirect. Add the old location of the page to the header of the new one.
```text
---
...
redirect_from: /getting-started/android/
---
```
### {% linkable_title Images, icons, and logos %}
The images which are displayed on the pages are stored in various directories according to their purpose. If you want to use a logo and placed `logo:` in the file header then this image should be stored in `source/images/supported_brands`. The background must be transparent.
| Type | Location |
| :----------- |:----------------------------------------------|
| logos | source/images/supported_brands |
| blog | source/images/blog |
| screenshots | source/images/components |
Not everything (product, component, etc.) should have a logo. To show something for internal parts of Home Assistant we are using the [Material Design Icons](https://materialdesignicons.com/).

44
source/developers/documentation/index.markdown Normal file
View File

@ -0,0 +1,44 @@
---
layout: page
title: "Documentation Home Assistant"
description: "home-assistant.io web presence for the documentation"
date: 2015-06-17 08:00
sidebar: true
comments: false
sharing: true
footer: true
redirect: /developers/website/
---
The website you are reading now is the home of Home Assistant: [https://home-assistant.io](https://home-assistant.io). This is the place where we provide documentation and additional details about Home Assistant for end users and developers.
home-assistant.io is built using [Jekyll](http://github.com/mojombo/jekyll) and [these available dependencies](https://pages.github.com/versions/). The pages are written in [markdown](http://daringfireball.net/projects/markdown/). To add a page, you don't need to know about HTML.
You can use the "**Edit this page on GitHub**" link to edit pages without creating a fork. Keep in mind that you can't upload images while working this way.
For larger changes, we suggest that you clone the website repository. This way, you can review your changes locally. The process for working on the website is no different from working on Home Assistant itself. You work on your change and propose it via a pull request.
To test your changes locally, you need to install **Ruby** and its dependencies (gems):
- [Install Ruby](https://www.ruby-lang.org/en/documentation/installation/) if you don't have it already.
- Install `bundler`, a dependency manager for Ruby: `$ gem install bundler`
- In your home-assistant.github.io root directory, run `$ bundle` to install the gems you need.
Short cut for Fedora: `$ sudo dnf -y install gcc-c++ ruby ruby-devel rubygem-bundler rubygem-json && bundle`
Then you can work on the documentation:
- Fork home-assistant.io [git repository](https://github.com/home-assistant/home-assistant.github.io).
- Create/edit/update a page in the directory `source/_components/` for your platform/component.
- Test your changes to home-assistant.io locally: run `rake preview` and navigate to [http://127.0.0.1:4000](http://127.0.0.1:4000)
- Create a Pull Request (PR) against the **next** branch of home-assistant.github.io if your documentation is a new feature, platform, or component.
- Create a Pull Request (PR) against the **current** branch of home-assistant.github.io if you fix stuff, create Cookbook entries, or expand existing documentation.
<p class='note'>
It could be necessary that you run `rake generate` prior to `rake preview` for the very first preview.
</p>
<p class='note'>
Site generated by `rake` is only available locally. If you are developing on a headless machine use port forwarding:
`ssh -L 4000:localhost:4000 user_on_headless_machine@ip_of_headless_machine`
</p>

57
source/developers/documentation/standards.markdown Normal file
View File

@ -0,0 +1,57 @@
---
layout: page
title: "Documentation Standards"
description: "Standards for the creation and maintenance of documentation for Home Assistant."
date: 2017-09-16 03:51
sidebar: true
comments: false
sharing: true
footer: true
---
To ensure that the documentation for Home Assistant is consistent and easy to follow for both novice and expert users, we ask that you follow a very strict set of standards for developing the documentation.
## {% linkable_title General Documentation %}
* The language of the documentation should be American-English.
* Don't put two spaces after a period and avoid the "Oxford comma".
* Be objective and not gender favoring, polarizing, race related or religion inconsiderate.
* The case of brand names, services, protocols, components, and platforms must match its respective counterpart. E.g. "Z-Wave" **not** "Zwave", "Z-wave", "Z Wave" or "ZWave". Also, "Input Select" **not** "input select" or "Input select".
* All headings should use the {% raw %}`{% linkable_title %}`{% endraw %} tag.
## {% linkable_title Component and Platform Pages %}
* The **Configuration Variables** section must use the {% raw %}`{% configuration %}`{% endraw %} tag.
* Configuration variables must document the requirement status.
* Configuration variables must document the default value, if any.
* Configuration variables must document the accepted value types.
* Use `[string, int]` for configuration variables that accept multiple types.
* Use YAML sequence syntax in the sample code if it is supported.
* All examples should be formatted to be included in `configuration.yaml` unless explicitly stated.
* Component and platform names should be a link to their respective documentation pages.
## {% linkable_title Templates %}
* All examples containing Jinja2 templates should be wrapped **outside** of the code markdown with the {% raw %}`{% raw %}`{% endraw %} tag.
* Do not use `states.switch.source.state` in templates. Instead use `states()` and `is_state()`.
* Use double quotes (`"`) for:
* `friendly_name`
* Single-line templates:
* `value_template`
* `level_template`
* `icon_template`
* Children of `data_template`
* Use single quotes (`'`) for:
* Strings inside of templates:
* States
* Entity IDs
* `unit_of_measurement`
* No whitespace around pipe character (`|`) for Jinja2 filters.
* Single whitespace after Jinja2 opening delimiters ({% raw %}`{{`{% endraw %}).
* Single whitespace before Jinja2 closing delimiters ({% raw %}`}}`{% endraw %}).
* Do not quote values for:
* `device_class`
* `platform`
* `condition`
* `service`

34
source/developers/hassio/addon_communication.markdown Normal file
View File

@ -0,0 +1,34 @@
---
layout: page
title: "Add-On Communication"
description: "Describe internal communication Hass.io."
date: 2017-04-30 13:28
sidebar: true
comments: false
sharing: true
footer: true
redirect_from: /hassio/addon_config/
---
It exists diferent ways to communication between add-ons or home-assistant inside Home-Assistant.
## {% linkable_title Network %}
We use a internal network. That allow to speak with every add-on or from Home-Assistant to add-on by name or alias. Only the a add-on they run on Host network are a bit limited. They can speak with all internal add-ons over there name but all other add-on can't speak with the add-on name to this add-on, but alias work wheel. So use the name/alias to communicate inside Hass.io
i.e. use `hassio` to speak with internal API.
## {% linkable_title Home-Assistant %}
A Add-on can speak to [Home-Assistant API][hass-api] with our internal proxy. That make it very easy to speak to this API without you need know the password, port or any other information for the Home-Assistant instance. Use this url: `http://hassio/homeassistant/api` and they will internal redirected to the right place. As next add `homeassistant_api: true` to `config.json`.
It is also possible to speak direct to Home-Assistant instance with name `homeassistant` over our internal Network. But you need know the running config.
We have severals services for Hass.io inside Home-Assistant to execute some task. So you can also use `hassio.addon_stdin` to send data over STDIN to a add-on.
## {% linkable_title Hass.io API %}
To call to our [Hass.io API][hassio-api] add `hassio_api: true` to `config.json`. Now you can use the API over this url: `http://hassio/`.
[hass-api]: https://home-assistant.io/developers/rest_api/
[hassio-api]: https://github.com/home-assistant/hassio/blob/master/API.md

2
source/developers/hassio/addon_config.markdown
View File

@ -86,7 +86,7 @@ The config for an add-on is stored in `config.json`.
"name": "xy",
"version": "1.2",
"slug": "folder",
"description": "long descripton",
"description": "long description",
"arch": ["amd64"],
"url": "website with more information about add-on (ie a forum thread for support)",
"startup": "application",

1
source/developers/hassio/addon_development.markdown
View File

@ -17,6 +17,7 @@ Under the hood, add-ons are Docker images published in [Docker Hub](https://hub.
<ol>
<li><a href='/developers/hassio/addon_tutorial/'>Tutorial: Making your first add-on</a></li>
<li><a href='/developers/hassio/addon_config/'>Configuration</a></li>
<li><a href='/developers/hassio/addon_communication/'>Communication</a></li>
<li><a href='/developers/hassio/addon_testing/'>Local Testing</a></li>
<li><a href='/developers/hassio/addon_publishing/'>Publishing</a></li>
<li><a href='/developers/hassio/addon_repository/'>Repositories</a></li>

2
source/developers/releasing.markdown
View File

@ -36,7 +36,7 @@ This page describes the steps for publishing a new Home Assistant release. Those
1. Create a blog post in the release branch and base it on the text of the PR in the main repository. Add images, additional text, links, etc. if it adds value. Tag each platform/component in a message to documentation.
2. Create missing documentation as stubs.
3. Update `config.yml` with link to the new release blog post and version number (at the bottom of the file).
3. Update `_config.yml` with link to the new release blog post and version number (at the bottom of the file).
4. Merge `current` into release branch (`$ git checkout release-0-40 && git merge current`) to make the PR mergeable.
5. Merge pull request (blog post, updated frontpage, and all new documentation) to `current`. DO NOT SQUASH!
6. Run `credits_generator`.

Some files were not shown because too many files have changed in this diff Show More