mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge remote-tracking branch 'origin/current' into next
This commit is contained in:
Paulus Schoutsen
commit
8879b5a610
@ -1,4 +1,4 @@
|
||||
[](https://gitter.im/home-assistant/website)
|
||||
[](https://discord.gg/CxqDrfU)
|
||||
[](https://travis-ci.org/home-assistant/home-assistant.github.io)
|
||||
[](http://www.krihelinator.xyz)
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
|
||||
@ -143,12 +143,11 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 48
|
||||
current_patch_version: 0
|
||||
date_released: 2017-07-02
|
||||
current_patch_version: 1
|
||||
date_released: 2017-07-05
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
# Major release:
|
||||
patch_version_notes: "#"
|
||||
patch_version_notes: "#release-0481---july-5"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
||||
|
||||
@ -23,3 +23,7 @@ Configuration variables:
|
||||
|
||||
- **domain** (*Required*): Domain they will proxy run with it.
|
||||
|
||||
<p class='note'>
|
||||
It is possible to deactive port 80 if you need this for things like `emulate_hue`. It exists a the moment no UI function for that, so you need call hass.io API with ssh addon:
|
||||
`curl -d '{"network": {"443/tcp": 443}}' http://172.17.0.2/addons/core_nginx_proxy/options`
|
||||
</p>
|
||||
|
||||
@ -27,6 +27,7 @@ The `alert` component makes use of any of the `notifications` components. To set
|
||||
alert:
|
||||
garage_door:
|
||||
name: Garage is open
|
||||
done_message: Garage is closed
|
||||
entity_id: input_boolean.garage_door
|
||||
state: 'on'
|
||||
repeat: 30
|
||||
@ -39,6 +40,7 @@ alert:
|
||||
Configuration variables:
|
||||
|
||||
- **name** (*Required*): The friendly name of the alert.
|
||||
- **done_message** (*Optional*): A message sent after an alert transitions from `on` to `off`. Is only sent if an alert notification was sent for transitioning from `off` to `on`.
|
||||
- **entity_id** (*Required*): The ID of the entity to watch.
|
||||
- **state** (*Optional*): The problem condition for the entity. Defaults to `on`.
|
||||
- **repeat** (*Required*): Number of minutes before the notification should be repeated. Can be either a number or a list of numbers.
|
||||
|
||||
@ -13,3 +13,7 @@ ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
Integrates Verisure binary sensors into Home Assistant. See the [main component](/components/verisure/) for configuration instructions.
|
||||
|
||||
The following binary sensor types are supported:
|
||||
|
||||
Door & Window
|
||||
|
||||
@ -25,7 +25,7 @@ browser:
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `url` | no | The url to open
|
||||
| `url` | no | The URL to open.
|
||||
|
||||
|
||||
### {% linkable_title Usage %}
|
||||
|
||||
@ -14,7 +14,7 @@ ha_iot_class: "depends"
|
||||
---
|
||||
|
||||
|
||||
The `generic` camera platform allows you to integrate any IP camera or other url into Home Assistant. Templates can be used to generate the urls on the fly.
|
||||
The `generic` camera platform allows you to integrate any IP camera or other URL into Home Assistant. Templates can be used to generate the URLs on the fly.
|
||||
|
||||
Home Assistant will serve the images via its server, making it possible to view your IP camera's while outside of your network. The endpoint is `/api/camera_proxy/camera.[name]`.
|
||||
|
||||
@ -34,7 +34,7 @@ Configuration variables:
|
||||
- **username** (*Optional*): The username for accessing your camera.
|
||||
- **password** (*Optional*): The password for accessing your camera.
|
||||
- **authentication** (*Optional*): Type for authenticating the requests `basic` (default) or `digest`.
|
||||
- **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits refetching of the remote image to when the url changes. Only relevant if using a template to fetch the remote image.
|
||||
- **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits refetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image.
|
||||
- **content_type** (*Optional*): Set the content type for the IP camera if it is not a jpg file (default: `image/jpeg`). Use `image/svg+xml` to add a dynamic svg file.
|
||||
|
||||
<p class='img'>
|
||||
|
||||
@ -12,16 +12,32 @@ ha_category: "Voice"
|
||||
---
|
||||
|
||||
|
||||
The conversation component can process sentences into commands for Home Assistant. It is currently limited to parsing commands in the format `turn <Friendly Name> <on/off>`.
|
||||
The conversation component can process sentences into commands for Home Assistant. It currently has built in functionality to recognize `turn <Friendly Name> <on/off>`, but custom phrases can be added through configuration.
|
||||
|
||||
|
||||
To enable the conversation option in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
# Example base configuration.yaml entry
|
||||
conversation:
|
||||
```
|
||||
|
||||
To add custom phrases to be recognized:
|
||||
```yaml
|
||||
# Example configuration.yaml entry with custom phrasesconversation
|
||||
conversation:
|
||||
boolean_test:
|
||||
sentence: switch boolean # The phrase it will recognize
|
||||
action:
|
||||
service: input_boolean.toggle
|
||||
```
|
||||
|
||||
The action keyword uses [script
|
||||
syntax](https://home-assistant.io/docs/scripts/).
|
||||
|
||||
|
||||
|
||||
|
||||
When this component is active and you are using a supported browser voice commands will be activated in the frontend. Browse to [the demo](/demo/) using Chrome or Chromium to see it in action.
|
||||
|
||||
<p class='img'>
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: knx.png
|
||||
ha_category: DIY
|
||||
ha_category: Cover
|
||||
ha_release: 0.48
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
@ -26,9 +26,12 @@ cover:
|
||||
stop_address: 9/0/1
|
||||
```
|
||||
|
||||
- **name** (*Optional*): A name for this devices used within Home Assistant.
|
||||
- **updown_address** (*Required*): The KNX group address that is used to move the cover up and down.
|
||||
- **stop_address** (*Required*): The group address that is used to stop the cover.
|
||||
- **setposition_address** (*Optional*): The group address that is used to set the position.
|
||||
- **getposition_address** (*Optional*): The group address that is used to read the position.
|
||||
- **name** (*Optional*): A name for this devices used within Home Assistant.
|
||||
|
||||
- **setangle_address** (*Optional*): The group address that is used to set the tilt angle.
|
||||
- **getangle_address** (*Optional*): The group address that is used to read the tilt angle.
|
||||
- **invert_position** (*Optional*): Set this to true if your actuator report fully closed as 100%
|
||||
- **invert_angle** (*Optional*): Set this to true if your actuator reports tilt fully closed as 100%
|
||||
|
||||
@ -13,7 +13,7 @@ ha_iot_class: "Local Push"
|
||||
logo: home-assistant.png
|
||||
---
|
||||
|
||||
The `template` platform can create covers that combine components and provides the ability to run scripts or invoke services for each of the open, close, stop, position, and tilt commands of a cover.
|
||||
The `template` platform can create covers that combine components and provides the ability to run scripts or invoke services for each of the open, close, stop, position, and tilt commands of a cover.
|
||||
|
||||
To enable Template covers in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -65,13 +65,13 @@ cover:
|
||||
value_template: "{% raw %}{{ sensor.garage_door }}{% endraw %}"
|
||||
open_cover:
|
||||
service: switch.turn_on
|
||||
entity_is: switch.garage_door
|
||||
entity_id: switch.garage_door
|
||||
close_cover:
|
||||
service: switch.turn_off
|
||||
entity_is: switch.garage_door
|
||||
entity_id: switch.garage_door
|
||||
stop_cover:
|
||||
service: switch.turn_on
|
||||
entity_is: switch.garage_door
|
||||
entity_id: switch.garage_door
|
||||
icon_template: "{% raw %}{% if not is_state('sensor.garage_door', 'on') %}mdi:garage-open{% else %}mdi:garage{% endif %}{% endraw %}"
|
||||
|
||||
```
|
||||
|
||||
@ -15,6 +15,21 @@ ha_release: 0.44
|
||||
|
||||
The `mikrotik` platform offers presence detection by looking at connected devices to a [Mikrotik Routerboard](http://routerboard.com) based router.
|
||||
|
||||
You need to enable the RouterOS API to use this platform.
|
||||
|
||||
Terminal:
|
||||
|
||||
```bash
|
||||
/ip service
|
||||
set api disabled=no port=8728
|
||||
```
|
||||
|
||||
Web Frontend:
|
||||
|
||||
Go to **IP** -> **Services** -> **API** and enable it.
|
||||
|
||||
Make sure that port 8728 or the port you choose is accessible from your network.
|
||||
|
||||
To use an Mikrotik router in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -31,6 +46,6 @@ Configuration variables:
|
||||
- **host** (*Required*): The IP address of your router.
|
||||
- **username** (*Required*: The username of an user with administrative privileges.
|
||||
- **password** (*Required*): The password for your given admin account.
|
||||
- **port** (*Optional*): Mikrotik API port (see IP -> Services -> api ). Defaults to `8728`.
|
||||
- **port** (*Optional*): Mikrotik API port. Defaults to `8728`.
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
||||
@ -36,7 +36,8 @@ Go the the "Developer Tools", then to "Call Service", and choose `downloader/dow
|
||||
|
||||
This will download the file from the given URL.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `url` | no | The url of the file to download.
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ---------------------------------------------- |
|
||||
| `url` | no | The url of the file to download. |
|
||||
| `subdir` | yes | Download into subdirectory of **download_dir** |
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: insteon.png
|
||||
ha_category: fan
|
||||
ha_category: Fan
|
||||
ha_version: 0.48
|
||||
---
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ Image processing enables Home Assistant to process images from [cameras](/compon
|
||||
For interval control, use `scan_interval` in platform.
|
||||
|
||||
<p class='note'>
|
||||
If you are running Home Assistant over SSL or from within a container, you will have to setup a base url inside the [http component](/components/http/).
|
||||
If you are running Home Assistant over SSL or from within a container, you will have to setup a base URL (`base_url`) inside the [http component](/components/http/).
|
||||
</p>
|
||||
|
||||
## {% linkable_title ALPR %}
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: knx.png
|
||||
ha_category: DIY
|
||||
ha_category: Hub
|
||||
ha_release: 0.24
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
@ -18,6 +18,7 @@ ha_iot_class: "Local Polling"
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- [Binary Sensor](/components/binary_sensor.knx)
|
||||
- [Cover](/components/cover.knx)
|
||||
- [Sensor](/components/sensor.knx)
|
||||
- [Switch](/components/switch.knx)
|
||||
- [Light](/components/light.knx)
|
||||
|
||||
@ -32,7 +32,7 @@ light:
|
||||
set_level:
|
||||
service: script.theater_lights_level
|
||||
data_template:
|
||||
volume_level: "{% raw %}{{brightness}}{% endraw %}"
|
||||
brightness: "{% raw %}{{brightness}}{% endraw %}"
|
||||
level_template: "{% raw %}{{is_state('sensor.theater_brightness.attributes.lux'}}{% endraw %}"
|
||||
```
|
||||
|
||||
@ -103,4 +103,4 @@ light:
|
||||
0
|
||||
{%- endif -%}
|
||||
{% endraw %}
|
||||
```
|
||||
```
|
||||
|
||||
@ -23,6 +23,7 @@ Currently known supported models:
|
||||
- TX-55CX700E
|
||||
- TX-49DX650B
|
||||
- TX-50DX700B
|
||||
- TX-L42ET50
|
||||
|
||||
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io).
|
||||
|
||||
|
||||
@ -19,12 +19,18 @@ If you have a Pandora account, you can control it from Home Assistant with this
|
||||
|
||||
### {% linkable_title Installation of Pianobar %}
|
||||
|
||||
This media player uses the [Pianobar command-line Pandora client](https://github.com/PromyLOPh/pianobar), which you have to install separately. This can be done on a Raspberry Pi 2 with Raspbian Jesse as follows . _(Note: Other platforms may have different installation processes)_
|
||||
This media player uses the [Pianobar command-line Pandora client](https://github.com/PromyLOPh/pianobar), which you have to install separately. This can be done on a Raspberry Pi 2/3 with Raspbian Jessie as follows . _(Note: Other platforms may have different installation processes)_
|
||||
|
||||
Install the following dependencies:
|
||||
The version of pianobar that comes with Jessie has a bug, so you have to build a more recent version. The latest version depends on a recent version of libraries associated with ffmpeg, so you should make sure you go through the backport process documented in [The FFmpeg component](https://home-assistant.io/components/ffmpeg/) before doing this. Install the following basic dependencies:
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install git libao-dev libgcrypt11-dev libfaad-dev libmad0-dev libjson0-dev make pkg-config libav-tools libavcodec-extra libavcodec-dev libcurl4-openssl-dev libavfilter-dev libavformat-dev
|
||||
$ sudo apt-get install git libao-dev libgcrypt11-dev libfaad-dev libmad0-dev libjson0-dev make pkg-config libcurl4-openssl-dev
|
||||
```
|
||||
|
||||
And now install the backported ffmpeg-related libraries (note that if you're using an older version of ffmpeg for other things on this machine, you may encounter issues after doings this):
|
||||
|
||||
```bash
|
||||
$ sudo apt-get -t jessie-backports install libav-tools libavcodec-extra libavcodec-dev libavfilter-dev libavformat-dev
|
||||
```
|
||||
|
||||
Now clone the Pianobar repo and build pianobar:
|
||||
|
||||
@ -59,6 +59,7 @@ Currently tested but not working models:
|
||||
- J5200 - Unable to see state and unable to control
|
||||
- JU7000 - Unable to see state and unable to control (but port 8001 *is* open)
|
||||
- JU7500 - Unable to see state and unable to control
|
||||
- JS9500 - State is always "on" and unable to control (but port 8001 *is* open)
|
||||
|
||||
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.samsungtv.markdown).
|
||||
The first letter (U, P, L, H & K) represent the screen type, e.g. LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size.
|
||||
|
||||
@ -96,12 +96,12 @@ media_player:
|
||||
service: media_player.select_source
|
||||
data_template:
|
||||
entity_id: media_player.receiver
|
||||
source: '{{ source }}'
|
||||
source: '{% raw %}{{ source }}{% endraw %}'
|
||||
volume_set:
|
||||
service: media_player.volume_set
|
||||
data_template:
|
||||
entity_id: media_player.receiver
|
||||
volume_level: '{{ volume_level }}'
|
||||
volume_level: '{% raw %}{{ volume_level }}{% endraw %}'
|
||||
|
||||
attributes:
|
||||
state: switch.living_room_tv
|
||||
|
||||
@ -32,11 +32,11 @@ Configuration variables:
|
||||
- **sender** (*Required*): E-mail address of the sender.
|
||||
- **recipient** (*Required*): E-mail address of the recipient of the notification. This can be a recipient address or a list of addresses for multiple recipients.
|
||||
- **server** (*Optional*): SMTP server which is used to end the notifications. Defaults to `localhost`.
|
||||
- **port** (*Optional*): The port that the SMTP server is using. Defaults to 465.
|
||||
- **port** (*Optional*): The port that the SMTP server is using. Defaults to 587.
|
||||
- **timeout** (*Optional*): The timeout in seconds that the SMTP server is using. Defaults to 5.
|
||||
- **username** (*Optional*): Username for the SMTP account.
|
||||
- **password** (*Optional*): Password for the SMTP server that belongs to the given username. If the password contains a colon it need to be wrapped in apostrophes.
|
||||
- **encryption** (*Optional*): Set mode for encryption, `tls`, `starttls` or `none`. Defaults to `tls`.
|
||||
- **encryption** (*Optional*): Set mode for encryption, `starttls`, `tls` or `none`. Defaults to `starttls`.
|
||||
- **sender_name** (*Optional*): Sets a custom 'sender name' in the emails headers (*From*: Custom name <example@mail.com>).
|
||||
- **debug** (*Optional*): Enables Debug, eg. True or False. Defaults to False.
|
||||
|
||||
|
||||
@ -24,20 +24,34 @@ Supported units:
|
||||
- Harmony Elite
|
||||
|
||||
|
||||
To use your Harmony remote in your installation, add the following to your `configuration.yaml` file:
|
||||
The preferred way to setup the Harmony remote is by enabling the [discovery component](/components/discovery/).
|
||||
|
||||
However, if you want to manually configure the device, you will need to add its settings to your `configuration.yaml`.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
remote:
|
||||
- platform: harmony
|
||||
name: Bedroom
|
||||
host: 10.168.1.13
|
||||
host: 10.168.1.13 # The IP of your hub
|
||||
```
|
||||
|
||||
You can override some default configuration values on a discovered hub (e.g. the `port` or `activity`) by adding
|
||||
a `configuration.yaml` setting. In this case leave the `host` setting empty so the platform will
|
||||
discover the host IP automatically, but set the `name` in the config to match exactly the name you have
|
||||
set for your Hub so the platform knows what Hub you are trying to configure.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with discovery
|
||||
- platform: harmony
|
||||
name: Living Room # This name must match the name you have set on the Hub
|
||||
activity: Watch TV # Overriding the 'activity' setting for this discovered hub
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **name** (*Required*): The hub's name to display in the frontend.
|
||||
- **host** (*Required*): The Harmony device's IP address.
|
||||
- **host** (*Optional*): The Harmony device's IP address. Leave empty for the IP to be discovered automatically.
|
||||
- **port** (*Optional*): The Harmony device's port. Defaults to 5222.
|
||||
- **activity** (*Optional*): Activity to use when turnon service is called without any data.
|
||||
- **scan_interval** (*Optional*): Amount in seconds in between polling for device's current activity. Defaults to 30 seconds.
|
||||
@ -134,12 +148,12 @@ automation:
|
||||
data_template:
|
||||
# using a data template to have if brances for relavant device
|
||||
# Always the same entity_id - the harmony hub
|
||||
entity_id: remote.bedroom
|
||||
entity_id: remote.bedroom
|
||||
# Always the same command - the Pause key
|
||||
command: Pause
|
||||
# select device based upon the activity being undertaken.
|
||||
device: >
|
||||
# when in WATCH TV activity, the pause key relates to a TiVo, which is device 22987101
|
||||
# when in WATCH TV activity, the pause key relates to a TiVo, which is device 22987101
|
||||
{% raw %}{% if is_state("sensor.bedroom", "WATCH TV") %}{% raw %}
|
||||
22987101
|
||||
# when in WATCH APPLE TV activity, the pause key relates to an Apple TV, which is device 23002316
|
||||
|
||||
@ -36,6 +36,8 @@ sensor:
|
||||
Configuration variables:
|
||||
|
||||
- **printers** array (*Required*): List of printers to add.
|
||||
- **host** (*Optional*): IP address of the CUPS print server.
|
||||
- **port** (*Optional*): Port address of the CUPS print server. Defaults to 631.
|
||||
|
||||
|
||||
<p class='note'>
|
||||
|
||||
@ -89,3 +89,7 @@ sensor:
|
||||
- download
|
||||
- upload
|
||||
```
|
||||
|
||||
## {% linkable_title Notes %}
|
||||
|
||||
When running on Raspberry Pi, just note that the maximum speed is limited by its 100 Mbit/s LAN adapter.
|
||||
|
||||
@ -13,7 +13,7 @@ ha_release: "0.10"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a bluetooth OBD2 stick via the Torque mobile application.
|
||||
The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a Bluetooth OBD2 stick via the Torque mobile application.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
To use Torque sensors with your installation, you must configure both the Torque mobile application and Home Assistant.
|
||||
@ -30,7 +30,7 @@ Under the **Logging Preferences** header:
|
||||
Under the **Realtime Web Upload** header:
|
||||
|
||||
- Check **Upload to webserver**.
|
||||
- Enter `http://HOST:PORT/api/torque?api_password=YOUR_PASSWORD` as the **Webserver URL**, where `HOST` and `PORT` are your externally-accessible Home Assistant HTTP host and port and YOUR_PASSWORD is your password.
|
||||
- Enter `http://HOST:PORT/api/torque?api_password=YOUR_PASSWORD` as the **Webserver URL**, where `HOST` and `PORT` are your externally accessible Home Assistant HTTP host and port and YOUR_PASSWORD is your Home Assistant's [API password](/components/http/). It highly recommended that you protect your Home Assistant instance with [SSL/TSL](/docs/ecosystem/certificates/).
|
||||
- Enter an email address in **User Email Address**.
|
||||
- Optionally set the **Web Logging Interval**. The 2-second default may quickly fill up the Home Assistant history database.
|
||||
|
||||
|
||||
@ -34,9 +34,9 @@ sensor:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (Required): The API key for Weather Underground. See above for details.
|
||||
- **pws_id** (Optional): You can enter a Personal Weather Station ID. The current list of Wunderground PWS stations is available [here](https://www.wunderground.com/weatherstation/ListStations.asp). If you do not enter a PWS ID, the current location information (latitude and longitude) from your `configuration.yaml` will be used to display weather conditions.
|
||||
- **lang** (Optional): Specify the language that the API returns. The current list of all Wunderground language codes is available [here](https://www.wunderground.com/weather/api/d/docs?d=language-support). If not specified, it defaults to English (EN).
|
||||
- **api_key** (*Required*): The API key for Weather Underground. See above for details.
|
||||
- **pws_id** (*Optional*): You can enter a Personal Weather Station ID. The current list of Wunderground PWS stations is available [here](https://www.wunderground.com/weatherstation/ListStations.asp). If you do not enter a PWS ID, the current location information (latitude and longitude) from your `configuration.yaml` will be used to display weather conditions.
|
||||
- **lang** (*Optional*): Specify the language that the API returns. The current list of all Wunderground language codes is available [here](https://www.wunderground.com/weather/api/d/docs?d=language-support). If not specified, it defaults to English (EN).
|
||||
- **latitude** (*Optional*): Latitude coordinate to monitor weather of (required if **longitude** is specificed). Defaults to coordinates defined in your `configuration.yaml`.
|
||||
- **longitude** (*Optional*): Longitude coordinate to monitor weather of (required if **latitude** is specified). Defaults to coordinates defined in your `configuration.yaml`.
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
|
||||
|
||||
@ -42,7 +42,7 @@ tts:
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
If you are running Home Assistant over SSL or from within a container, you will have to setup a base url inside the [http component](/components/http/).
|
||||
If you are running Home Assistant over SSL or from within a container, you will have to setup a base URL (`base_url`) inside the [http component](/components/http/).
|
||||
</p>
|
||||
|
||||
## {% linkable_title Service say %}
|
||||
|
||||
@ -22,6 +22,7 @@ We support:
|
||||
* Reading from thermometers and hygrometers integrated in various [devices](/components/sensor.verisure/)
|
||||
* Mouse Detector
|
||||
* [Locks](/components/lock.verisure/)
|
||||
* [Door & Window](/components/binary_sensor.verisure/)
|
||||
|
||||
To integrate Verisure with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
@ -42,5 +43,6 @@ Configuration variables:
|
||||
- **locks** (*Optional*): Set to 1 to show locks, 0 to disable. Default 1.
|
||||
- **thermometers** (*Optional*): Set to 1 to show thermometers, 0 to disable. Default 1.
|
||||
- **mouse** (*Optional*): Set to 1 to show mouse detectors, 0 to disable. Default 1.
|
||||
- **door_window** (*Optional*): Set to 1 to show door and window sensors, 0 to disable. Default 1.
|
||||
- **code_digits** (*Optional*): Number of digits in PIN code. Default 4.
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ volvooncall:
|
||||
password: password
|
||||
```
|
||||
|
||||
Users registered with Volvo in North America or China will need to specify a service url:
|
||||
Users registered with Volvo in North America or China will need to specify a service URL:
|
||||
|
||||
```yaml
|
||||
# North America
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Configuration.yaml by brusc"
|
||||
title: "Configuration.yaml by oakbrad"
|
||||
description: ""
|
||||
date: 2016-03-14 11:45
|
||||
sidebar: true
|
||||
@ -8,6 +8,6 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Example configuration.yaml
|
||||
ha_external_link: https://github.com/brusc/Home-Assistant-Configuration
|
||||
ha_external_link: https://github.com/oakbrad/brad-homeassistant-config
|
||||
---
|
||||
|
||||
@ -14,26 +14,27 @@ By default, Home Assistant will try to detect your location from IP address geol
|
||||
|
||||
```yaml
|
||||
homeassistant:
|
||||
# Omitted values in this section will be auto detected using freegeoip.io
|
||||
|
||||
# Location required to calculate the time the sun rises and sets
|
||||
latitude: 32.87336
|
||||
longitude: 117.22743
|
||||
|
||||
# Impacts weather/sunrise data (altitude above sea level in meters)
|
||||
elevation: 430
|
||||
|
||||
# 'metric' for Metric, 'imperial' for Imperial
|
||||
unit_system: metric
|
||||
|
||||
# Pick yours from here:
|
||||
# http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
|
||||
time_zone: America/Los_Angeles
|
||||
|
||||
# Name of the location where Home Assistant is running
|
||||
name: Home
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **latitude** (*Optional*): Latitude of your location required to calculate the time the sun rises and sets.
|
||||
- **longitude** (*Optional*): Longitude of your location required to calculate the time the sun rises and sets.
|
||||
- **elevation** (*Optional*): Altitude above sea level in meters. Impacts weather/sunrise data.
|
||||
- **unit_system** (*Optional*): `metric` for Metric, `imperial` for Imperial.
|
||||
- **time_zone** (*Optional*): Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
|
||||
- **name** (*Optional*): Name of the location where Home Assistant is running.
|
||||
- **customize** (*Optional*): [Customize](/docs/configuration/customizing-devices/) entities.
|
||||
- **customize_domain** (*Optional*): [Customize](/docs/configuration/customizing-devices/) all entities in a domain.
|
||||
- **customize_glob** (*Optional*): [Customize](/docs/configuration/customizing-devices/) entities matching a pattern.
|
||||
- **whitelist_external_dirs** (*Optional*): List of folders that can be used as sources for sending files.
|
||||
|
||||
### {% linkable_title Password protecting the web interface %}
|
||||
|
||||
First, you'll want to add a password for the Home Assistant web interface. Use your favourite text editor to open `configuration.yaml` and edit the `http` section:
|
||||
|
||||
@ -13,7 +13,7 @@ redirect_from: /getting-started/customizing-devices/
|
||||
By default, all of your devices will be visible and have a default icon determined by their domain. You can customize the look and feel of your front page by altering some of these parameters. This can be done by overriding attributes of specific entities.
|
||||
|
||||
<p class='note'>
|
||||
Be carefull not to forget to place `customize`, `customize_domain`, and `customize_glob` inside `homeassistant:` or it will fail.
|
||||
Be careful not to forget to place `customize`, `customize_domain`, and `customize_glob` inside `homeassistant:` or it will fail.
|
||||
</p>
|
||||
|
||||
```yaml
|
||||
@ -41,23 +41,31 @@ homeassistant:
|
||||
customize_domain:
|
||||
light:
|
||||
icon: mdi:home
|
||||
automation:
|
||||
initial_state: 'on'
|
||||
# Customize entities matching a pattern
|
||||
customize_glob:
|
||||
"light.kitchen_*":
|
||||
icon: mdi:description
|
||||
|
||||
"scene.month_*_colors":
|
||||
hidden: true
|
||||
emulated_hue: false
|
||||
homebridge_hidden: true
|
||||
```
|
||||
|
||||
### {% linkable_title Possible values %}
|
||||
|
||||
| Attribute | Description |
|
||||
| --------- | ----------- |
|
||||
| `friendly_name` | Name of the entity
|
||||
| `friendly_name` | Name of the entity.
|
||||
| `hidden` | Set to `true` to hide the entity.
|
||||
| `entity_picture` | Url to use as picture for entity
|
||||
| `homebridge_hidden` | Set to `true` to hide the entity from `HomeBridge`.
|
||||
| `emulated_hue` | Set to `false` 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.
|
||||
| `device_class` | Sets the class of the device, changing the device state and icon that is displayed on the UI (see below).
|
||||
| `initial_state` | Sets the initial state for automations. `on` or `off`.
|
||||
|
||||
### {% linkable_title Device Class %}
|
||||
|
||||
|
||||
@ -22,9 +22,9 @@ One major advantage of Home Assistant is that it's not dependent on cloud servic
|
||||
|
||||
If you want to allow remote access, consider these additional points:
|
||||
|
||||
- Protect your communication with [TLS/SSL](/docs/ecosystem/certificates/lets_encrypt/)
|
||||
- Protect your communication with [Tor](/cookbook/tor_configuration/)
|
||||
- Protect your communication with a [self-signed certificate](/cookbook/tls_self_signed_certificate/)
|
||||
- Use a [proxy](/cookbook/apache_configuration/)
|
||||
- Protect your communication with [TLS/SSL](/docs/ecosystem/certificates/lets_encrypt/).
|
||||
- Protect your communication with [Tor](/cookbook/tor_configuration/).
|
||||
- Protect your communication with a [self-signed certificate](/cookbook/tls_self_signed_certificate/).
|
||||
- Use a [proxy](/cookbook/apache_configuration/).
|
||||
|
||||
|
||||
|
||||
@ -152,7 +152,7 @@ You'll notice that this example includes a secondary parameter section (under th
|
||||
|
||||
That about wraps it up.
|
||||
|
||||
If you have issues checkout `home-assistant.log` in the configuration directory as well as your indentations. If all else fails, head over to the [Gitter Chatroom](https://gitter.im/balloob/home-assistant) and ask away.
|
||||
If you have issues checkout `home-assistant.log` in the configuration directory as well as your indentations. If all else fails, head over to our [Discord chat server][discord] and ask away.
|
||||
|
||||
### {% linkable_title Debugging multiple configuration files %}
|
||||
|
||||
@ -441,3 +441,5 @@ front_yard:
|
||||
- sensor.mailbox
|
||||
- camera.front_porch
|
||||
```
|
||||
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -18,7 +18,7 @@ All states will always have an entity id, a state and a timestamp when last upda
|
||||
|
||||
Field | Description
|
||||
----- | -----------
|
||||
`state.state` | String representation of the current state of the entity. Example `off`
|
||||
`state.state` | String representation of the current state of the entity. Example `off`.
|
||||
`state.entity_id` | Entity ID. Format: `<domain>.<object_id>`. Example: `light.kitchen`.
|
||||
`state.domain` | Domain of the entity. Example: `light`.
|
||||
`state.object_id` | Object ID of entity. Example: `kitchen`.
|
||||
@ -36,7 +36,7 @@ Attribute | Description
|
||||
`friendly_name` | Name of the entity. Example: `Kitchen Ceiling`.
|
||||
`icon` | Icon to use for the entity in the frontend. Example: `mdi:home`.
|
||||
`hidden` | Boolean if the entity should not be shown in the frontend. Example: `true`.
|
||||
`entity_picture` | Url to a picture that should be used instead of showing the domain icon. Example: `http://example.com/picture.jpg`.
|
||||
`entity_picture` | URL to a picture that should be used instead of showing the domain icon. Example: `http://example.com/picture.jpg`.
|
||||
`assumed_state` | Boolean if the current state is an assumption. [More info](https://home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/#classifiers) Example: `True`.
|
||||
`unit_of_measurement` | The unit of measurement the state is expressed in. Used for grouping graphs or understanding the entity. Example: `°C`.
|
||||
|
||||
|
||||
100
source/_docs/ecosystem/appdaemon.markdown
Normal file → Executable file
100
source/_docs/ecosystem/appdaemon.markdown
Normal file → Executable file
@ -11,3 +11,103 @@ redirect_from: /ecosystem/appdaemon/
|
||||
---
|
||||
|
||||
AppDaemon is a loosely coupled, multithreaded, sandboxed python execution environment for writing automation apps for Home Assistant.
|
||||
|
||||
# Another Take on Automation
|
||||
|
||||
AppDaemon is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table:
|
||||
|
||||
- New paradigm - some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can't
|
||||
- Ease of use - AppDaemon's API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible, experienced Python programmers should feel right at home.
|
||||
- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file
|
||||
- Dynamic - AppDaemon has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to it's loose coupling. However, it is better than that - the user can make changes to code and AppDaemon will automatically reload the code, figure out which Apps were using it and restart them to use the new code with out the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result.
|
||||
- Complex logic - Python's If/Else constructs are clearer and easier to code for arbitrarily complex nested logic
|
||||
- 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.
|
||||
|
||||
# How it Works
|
||||
|
||||
The best way to show what AppDaemon does is through a few simple examples.
|
||||
|
||||
## Sunrise/Sunset Lighting
|
||||
|
||||
Lets start with a simple App to turn a light on every night at sunset and off every morning at sunrise. Every App when first started will have its `initialize()` function called which gives it a chance to register a callback for AppDaemons's scheduler for a specific time. In this case we are using `run_at_sunrise()` and `run_at_sunset()` to register 2 separate callbacks. The argument `0` is the number of seconds offset from sunrise or sunset and can be negative or positive. For complex intervals it can be convenient to use Python's `datetime.timedelta` class for calculations. When sunrise or sunset occurs, the appropriate callback function, `sunrise_cb()` or `sunset_cb()` is called which then makes a call to Home Assistant to turn the porch light on or off by activating a scene. The variables `args["on_scene"]` and `args["off_scene"]` are passed through from the configuration of this particular App, and the same code could be reused to activate completely different scenes in a different version of the App.
|
||||
|
||||
```python
|
||||
import homeassistant.appapi as appapi
|
||||
|
||||
class OutsideLights(appapi.AppDaemon):
|
||||
|
||||
def initialize(self):
|
||||
self.run_at_sunrise(self.sunrise_cb, 0)
|
||||
self.run_at_sunset(self.sunset_cb, 0)
|
||||
|
||||
def sunrise_cb(self, kwargs):
|
||||
self.turn_on(self.args["off_scene"])
|
||||
|
||||
def sunset_cb(self, kwargs):
|
||||
self.turn_on(self.args["on_scene"])
|
||||
|
||||
```
|
||||
|
||||
This is also fairly easy to achieve with Home Assistant automations, but we are just getting started.
|
||||
|
||||
## Motion Light
|
||||
|
||||
Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changes where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callack function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
|
||||
|
||||
```python
|
||||
import homeassistant.appapi as appapi
|
||||
|
||||
class FlashyMotionLights(appapi.AppDaemon):
|
||||
|
||||
def initialize(self):
|
||||
self.listen_state(self.motion, "binary_sensor.drive", new = "on")
|
||||
|
||||
def motion(self, entity, attribute, old, new, kwargs):
|
||||
if self.sun_down():
|
||||
self.turn_on("light.drive")
|
||||
self.run_in(self.light_off, 60)
|
||||
|
||||
def light_off(self, kwargs):
|
||||
self.turn_off("light.drive")
|
||||
```
|
||||
|
||||
This is starting to get a little more complex in Home Assistant automations requiring an Automation rule and two separate scripts.
|
||||
|
||||
Now lets extend this with a somewhat artificial example to show something that is simple in AppDaemon but very difficult if not impossible using automations. Lets warn someone inside the house that there has been motion outside by flashing a lamp on and off 10 times. We are reacting to the motion as before by turning on the light and setting a timer to turn it off again, but in addition, we set a 1 second timer to run `flash_warning()` which when called, toggles the inside light and sets another timer to call itself a second later. To avoid re-triggering forever, it keeps a count of how many times it has been activated and bales out after 10 iterations.
|
||||
|
||||
```python
|
||||
import homeassistant.appapi as appapi
|
||||
|
||||
class MotionLights(appapi.AppDaemon):
|
||||
|
||||
def initialize(self):
|
||||
self.listen_state(self.motion, "binary_sensor.drive", new = "on")
|
||||
|
||||
def motion(self, entity, attribute, old, new, kwargs):
|
||||
if self.self.sun_down():
|
||||
self.turn_on("light.drive")
|
||||
self.run_in(self.light_off, 60)
|
||||
self.flashcount = 0
|
||||
self.run_in(self.flash_warning, 1)
|
||||
|
||||
def light_off(self, kwargs):
|
||||
self.turn_off("light.drive")
|
||||
|
||||
def flash_warning(self, kwargs):
|
||||
self.toggle("light.living_room")
|
||||
self.flashcount += 1
|
||||
if self.flashcount < 10:
|
||||
self.run_in(self.flash_warning, 1)
|
||||
```
|
||||
|
||||
Of course if I wanted to make this App or its predecessor reusable I would have provide parameters for the sensor, the light to activate on motion, the warning light and even the number of flashes and delay between flashes.
|
||||
|
||||
In addition, Apps can write to `AppDaemon`'s logfiles, and there is a system of constraints that allows yout to control when and under what circumstances Apps and callbacks are active to keep the logic clean and simple.
|
||||
|
||||
For full installation instructions, see [README.md](https://github.com/home-assistant/appdaemon/blob/dev/README.md) in the `AppDaemon` repository.
|
||||
|
||||
There is also full documentation for the API and associated configuration in [API.md](https://github.com/home-assistant/appdaemon/blob/dev/API.md).
|
||||
|
||||
|
||||
14
source/_docs/ecosystem/certificates.markdown
Normal file
14
source/_docs/ecosystem/certificates.markdown
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Certificates"
|
||||
description: "Protect your communication with Home Assistant."
|
||||
release_date: 2016-11-13 15:00:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
If you plan to expose your Home Assistant to the internet or want an extra layer of protection in your local network, consider to use SSL/TLS. This way you can protect your communication. Especially sensitive data like usernames and passwords are encrypted between the endpoints.
|
||||
|
||||
Setting up usually requires creating the certificate and configure the [`http`](/components/http/) component.
|
||||
@ -374,8 +374,8 @@ If you have any more for Home Assistant you should delete them now. If you only
|
||||
|
||||
You are now part of one of two groups:
|
||||
|
||||
* If you have BOTH rules you are able to set up auto renewals of you certificates.
|
||||
* If you only have one, you will have to manually change the rule when you want to update your certificate, and then change it back afterwards.
|
||||
* If you have BOTH rules you are able to set up auto renewals of your certificates using port 80 and the standard http challenge, as performed above.
|
||||
* If you only have one, you are still able to set up auto renewals of your certificates, but will have to specify additional options when renewing that will temporarily stop Home Assistant and use port 8123 for certificate renewal.
|
||||
|
||||
Please remember whether you are a ONE-RULE person or a BOTH-RULE person for step 8!
|
||||
|
||||
@ -426,53 +426,11 @@ Got your sensor up and running and where you want it? Top drawer! Nearly there,
|
||||
|
||||
The certbot program we downloaded in step 4 contains a script that will renew your certificate. The script will only obtain a new certificate if the current one has less than 30 days left on it, so running the script more often than is actually needed will not cause any harm.
|
||||
|
||||
If you are a ONE-RULE person (from step 6) you cannot 'automatically' renew your certificates because you will need to change your port forwarding rules before the renewal takes place, and change it back again afterwards.
|
||||
If you are a ONE-RULE person (from step 6), you can automatically renew your certificate with your current port mapping by temporarily stopping Home Assistant and telling certbot to bind port 8123 internally, and using a `tls-sni` challenge so that the Let's Encrypt CA binds port 443 externally. The flags used to specify these additional steps are shown below.
|
||||
|
||||
When you are within 30 days of your certificate's expiry date (you can use the sensor reading from step 7 to tell you this) you will need to complete the following steps:
|
||||
If you are a TWO-RULE person (from step 6), you can automatically renew your certificate using a `http-01` challenge and port 80.
|
||||
|
||||
* Go to your router's configuration pages and edit your port forwarding rule to
|
||||
|
||||
```text
|
||||
Service name - ha_ssl
|
||||
Port Range - 443
|
||||
Local IP - YOUR-HA-IP
|
||||
Local Port - 443
|
||||
Protocol - Both
|
||||
```
|
||||
|
||||
* Save the rule
|
||||
* SSH in to your device running HA.
|
||||
* Change to your HA user (command similar to):
|
||||
|
||||
```bash
|
||||
$ su - s /bin/bash hass
|
||||
```
|
||||
|
||||
* Change to your certbot folder
|
||||
|
||||
```bash
|
||||
$ cd ~/certbot/
|
||||
```
|
||||
|
||||
* Run the renewal command
|
||||
|
||||
```bash
|
||||
$ ./certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
|
||||
```
|
||||
|
||||
* Once succesfully completed, change your port forwarding rule back to
|
||||
|
||||
```text
|
||||
Service name - ha_ssl
|
||||
Port Range - 443
|
||||
Local IP - YOUR-HA-IP
|
||||
Local Port - 8123
|
||||
Protocol - Both
|
||||
```
|
||||
|
||||
* Save the rule
|
||||
|
||||
If you are a BOTH-RULE person, you have a number of options at this point.
|
||||
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
|
||||
@ -492,18 +450,29 @@ $ su - s /bin/bash hass
|
||||
$ crontab -e
|
||||
```
|
||||
|
||||
* Scroll to the bottom of the file and paste in the following line
|
||||
* If you are a TWO-RULE Person: Scroll to the bottom of the file and paste in the following line
|
||||
|
||||
```text
|
||||
30 2 * * 1 ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
|
||||
```
|
||||
|
||||
* If you are a ONE-RULE Person: Scroll to the bottom of the file and paste in the following line
|
||||
|
||||
```text
|
||||
30 2 * * 1 ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges tls-sni-01 --tls-sni-01-port 8123 --pre-hook "sudo systemctl stop home-assistant@homeassistant.service" --post-hook "sudo systemctl start home-assistant@homeassistant.service"
|
||||
```
|
||||
* Let's take a moment to look at the differences here:
|
||||
1. This method uses a `tls-sni` challenge, so the Let's Encrypt CA will attempt to bind port 443 externally (which you have forwarded)
|
||||
2. `--tls-sni-01-port 8123` tells certbot to bind port 8123 internally, which matches with the port forwarding rules that are already in place.
|
||||
3. We define pre-hooks and post-hooks that stop our Home Assistant service before certbot runs, freeing port 8123 for certificate renewal, and restart Home Assistant after renewal is complete.
|
||||
|
||||
* Save the file and exit
|
||||
|
||||
|
||||
#### Option 2:
|
||||
You can set an automation in Home Assistant to run the certbot renewal script.
|
||||
|
||||
Add the following sections to your configuration.yaml
|
||||
Add the following sections to your configuration.yaml if you are a TWO-RULE person
|
||||
|
||||
```yaml
|
||||
shell_command:
|
||||
@ -518,6 +487,7 @@ automation:
|
||||
action:
|
||||
service: shell_command.renew_ssl
|
||||
```
|
||||
If you are a ONE-RULE person, replace the `certbot-auto` command above with `~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges tls-sni-01 --tls-sni-01-port 8123 --pre-hook "sudo systemctl stop home-assistant@homeassistant.service" --post-hook "sudo systemctl start home-assistant@homeassistant.service"`
|
||||
|
||||
#### Option 3:
|
||||
You can manually update the certificate when your certificate is less than 30 days to expiry.
|
||||
@ -542,6 +512,8 @@ $ cd ~/certbot/
|
||||
```bash
|
||||
$ ./certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
|
||||
```
|
||||
|
||||
* If you are a ONE-RULE person, replace the `certbot-auto` command above with `~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges tls-sni-01 --tls-sni-01-port 8123 --pre-hook "sudo systemctl stop home-assistant@homeassistant.service" --post-hook "sudo systemctl start home-assistant@homeassistant.service"`
|
||||
|
||||
So, now were all set up. We have our secured, remotely accesible HA instance and we're on track for keeping our certificates up to date. But what if something goes wrong? What if the automation didn't fire? What if the cron job forgot to run? What if the dog ate my homework? Read on to set up an alert so you can be notified in plenty of time if you need to step in and sort out any failures.
|
||||
|
||||
|
||||
29
source/_docs/ecosystem/hadashboard.markdown
Normal file → Executable file
29
source/_docs/ecosystem/hadashboard.markdown
Normal file → Executable file
@ -10,12 +10,33 @@ footer: true
|
||||
redirect_from: /ecosystem/hadashboard/
|
||||
---
|
||||
|
||||
HADashboard is a dashboard for [Home Assistant](https://home-assistant.io/) that is intended to be wall mounted, and is optimized for distance viewing.
|
||||
HADashboard is a modular, skinnable dashboard for [Home Assistant](https://home-assistant.io/) that is intended to be wall mounted, and is optimized for distance viewing.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hadashboard/dash.png' />
|
||||
Sample Dashboard
|
||||
<img src='/images/hadashboard/dash1.png' />
|
||||
Default Theme
|
||||
</p>
|
||||
|
||||
HADashboard was originally created by the excellent work of [FlorianZ](https://github.com/FlorianZ/hadashboard) for use with the SmartThings Home Automation system, with notable contributions from the [SmartThings Community](https://community.smartthings.com/t/home-automation-dashboard/4926). I would also like to acknowledge contributions made by [zipriddy](https://github.com/zpriddy/SmartThings_PyDash). This is my port of hadashboard to Home Assistant.
|
||||
<p class='img'>
|
||||
<img src='/images/hadashboard/dash2.png' />
|
||||
Obsidian Theme
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hadashboard/dash3.png' />
|
||||
Zen Theme
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hadashboard/dash4.png' />
|
||||
Simply Red Theme
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hadashboard/dash5.png' />
|
||||
Glassic Theme
|
||||
</p>
|
||||
|
||||
|
||||
|
||||
For full installation instructions see [DASHBOARD.md](https://github.com/home-assistant/appdaemon/blob/dev/DASHBOARD.md) in the AppDaemon Repository.
|
||||
|
||||
@ -1,275 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Dashboard Configuration"
|
||||
description: "Dashboard Configuration"
|
||||
release_date: 2016-11-13 15:00:00 -0500
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /ecosystem/hadashboard/dash_config/
|
||||
---
|
||||
|
||||
(All installations)
|
||||
|
||||
Hadashboard is a Dashing application, so make sure to read all the instructions on http://dashing.io to learn how to add widgets to your dashboard, as well as how to create new widgets.
|
||||
|
||||
Make a copy of `dashboards/example.erb` and call it `main.erb`, then edit this file to reference the items you want to display and control and to get the layout that you want. Leave the original `example.erb` intact and unchanged so that you don't run into problems when trying to update using the git commands mentioned later in "Updating the Dashboard".
|
||||
|
||||
The basic anatomy of a widget is this:
|
||||
|
||||
``` html
|
||||
<li data-row="" data-col="1" data-sizex="1" data-sizey="1">
|
||||
<div data-id="office" data-view="Hadimmer" data-title="Office Lamp"></div>
|
||||
</li>
|
||||
```
|
||||
|
||||
- **data-row**, **data-col**: The position of the widget in the grid.
|
||||
- **data-sizex**, **data-sizey**: The size of the widget in terms of grid tile.
|
||||
- **data-id**: The homeassitant entity id without the entity type (e.g. `light.office` becomes `office`).
|
||||
- **data-view**: The type of widget to be used (Haswitch, Hadimmer, Hatemp etc.)
|
||||
- **data-icon**: The icon displayed on the tile. See http://fontawesome.io for an icon cheatsheet.
|
||||
- **data-title**: The title to be displayed on the tile.
|
||||
- ***data-bgcolor*** (optional) - the background color of the widget.
|
||||
|
||||
Note that although it is legal in XML terms to split the inner `<div>` like this:
|
||||
|
||||
``` html
|
||||
<li data-row="" data-col="1" data-sizex="1" data-sizey="1">
|
||||
<div data-id="office"
|
||||
data-view="Hadimmer"
|
||||
data-title="Office Lamp">
|
||||
</div>
|
||||
</li>
|
||||
```
|
||||
|
||||
This may break `hapush`'s parsing of the file, so keep to the line format first presented.
|
||||
|
||||
Please, refer to the Dashing website for instructions on how to change the grid and tile size, as well as more general instructions about widgets, their properties, and how to create new widgets.
|
||||
|
||||
## {% linkable_title Supported Widgets %}
|
||||
|
||||
At this time I have provided support for the following Home Assistant entity types.
|
||||
|
||||
- switch: Widget type **Haswitch**
|
||||
- lock: Widget type **Halock**
|
||||
- devicetracker: Widget type **Hadevicetracker**
|
||||
- light: Widget type **Hadimmer**
|
||||
- cover: Widget type **Hacover**
|
||||
- input_boolean: Widget type **Hainputboolean**
|
||||
- scene: Widget type **Hascene**
|
||||
|
||||
- **data-ontime** (optional): The amount of time the scene icon lights up when pressed, in milliseconds, default 1000.
|
||||
|
||||
### {% linkable_title script %}
|
||||
|
||||
Widget type ***Hascript***
|
||||
|
||||
**data-ontime** (optional): The amount of time the scene icon lights up when pressed, in milliseconds, default 1000.
|
||||
|
||||
### {% linkable_title mode %}
|
||||
|
||||
The `Hamode` widget alows you to run a script on activation and to link it with a specified `input_select` so the button will be highlighted for certain values of that input select. The usecase for this is that I maintain an `input_select` as a flag for the state of the house to simplify other automations. I use scripts to switch between the states, and this feature provides feedback as to the current state by lighting up the appropriate mode button.
|
||||
|
||||
A `Hamode` widget using this feature will look like this:
|
||||
|
||||
```html
|
||||
<li data-row="5" data-col="3" data-sizex="2" data-sizey="1">
|
||||
<div data-id="day" data-view="Hamode" data-title="Good Day" data-icon="sun-o" data-changemode="Day" data-input="house_mode"></div>
|
||||
</li>
|
||||
```
|
||||
|
||||
- **data-changemode**: The value of the `input_select` for which this script button will light up
|
||||
- **data-input**: The `input_select` entity to use (minus the leading entity type)
|
||||
|
||||
### {% linkable_title input_select (read only) %}
|
||||
Widget type **Hainputselect**
|
||||
|
||||
### {% linkable_title sensor %}
|
||||
Widget type **Hasensor**
|
||||
|
||||
Text based output of the value of a particular sensor.
|
||||
|
||||
The Hasensor widget supports an additional paramater `data-unit`. This allows you to set the unit to whatever you want: Centigrade, %, lux or whatever you need for the sensor in question. For a temperature sensor you will need to explicitly include the degree symbol like this:
|
||||
|
||||
```html
|
||||
data-unit="°F"
|
||||
```
|
||||
|
||||
If omitted, no units will be shown.
|
||||
|
||||
### {% linkable_title sensor %}
|
||||
Widget type **Hameter**
|
||||
|
||||
An alternative to the text based `Hasensor` that works for numeric values only.
|
||||
|
||||
The Hameter widget supports an additional paramater `data-unit`. This allows you to set the unit to whatever you want: Centigrade, %, lux or whatever you need for the sensor in question. For a temperature sensor you will need to explicitly include the degree symbol like this:
|
||||
|
||||
```html
|
||||
data-unit="°F"
|
||||
```
|
||||
|
||||
If omitted, no units will be shown.
|
||||
|
||||
### {% linkable_title binary_sensor %}
|
||||
Widget type **Habinary**
|
||||
|
||||
An icon-based option for generic binary sensors. Useful for things like door contact sensors. In addition to the standard widget parameters, Habinary supports two additional parameters:
|
||||
|
||||
- **data-iconon**: the icon to display when the sensor state is "on"
|
||||
- **data-iconoff**: the icon to display when the sensor state if "off"
|
||||
|
||||
If no icons are specified, the widget defaults to a flat gray line for "off" and a green bullseye for "on".
|
||||
|
||||
### {% linkable_title group %}
|
||||
Widget type **Hagroup**.
|
||||
|
||||
The Hagroup widget uses the homeassistant/turn_on and homeassistant/turn_off API call, so certain functionality will be lost. For example, you will not be able to use control groups of locks or dim lights.
|
||||
|
||||
## {% linkable_title Alarm Control Panel %}
|
||||
|
||||
These widgets allow the user to create a working control panel that can be used to control the Manual Alarm Control Panel component (https://home-assistant.io/components/alarm_control_panel.manual). The example dashboard contains an arrangement similar to this:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hadashboard/alarm_panel.png' />
|
||||
The Alarm Panel
|
||||
</p>
|
||||
|
||||
Widget type **Haalarmstatus**
|
||||
|
||||
The Haalarmstatus widget displays the current status of the alarm_control_panel entity. It will also display the code as it is being entered by the user.
|
||||
|
||||
The data-id must be the same as the alarm_control_panel entity_id in Home Assistant.
|
||||
|
||||
Widget type **Haalarmdigit**
|
||||
|
||||
The Haalarmdigit widget is used to create the numeric keypad for entering alarm codes.
|
||||
|
||||
`data-digit` holds the numeric value you wish to enter. The special value of "-" creates a 'clear' button which will wipe the code and return the Haalarmstatus widget display back to the current alarm state.
|
||||
|
||||
`data-alarmentity` holds the data-id of the Haalarmstatus widget, so that the status widget can be correctly updated. It is mandatory for a 'clear' type digit and optional for normal numeric buttons.
|
||||
|
||||
Widget type **Haalarmaction**
|
||||
|
||||
The Haalarmaction widget creates the arm/disarm/trigger buttons. Bear in mind that alarm triggering does not require a code, so you may not want to put this button near the other buttons in case it is pressed accidentally.
|
||||
|
||||
data-action must contain one of the following: arm_home/arm_away/trigger/disarm.
|
||||
|
||||
### {% linkable_title weather (requires DarkSky) %}
|
||||
|
||||
Widget type **Haweather**.
|
||||
|
||||
In order to use the weather widget you must configure the [DarkSky component](/components/sensor.darksky/), and ensure that you configure at least the following monitored conditions in your Home Assistant sensor configuration:
|
||||
|
||||
- temperature
|
||||
- humidity
|
||||
- precip_probability
|
||||
- precip_intensity
|
||||
- wind_speed
|
||||
- pressure
|
||||
- wind_bearing
|
||||
- apparent_temperature
|
||||
- icon
|
||||
|
||||
The `data-id` of the Haweather widget must be set to `weather` or the widget will not work.
|
||||
|
||||
The Hatemp widget supports an additional paramater `data-unit`. This allows you to set the unit to whatever you want: Centigrade, Fahrenheit or even Kelvin if you prefer. You will need to explicitly include the degree symbol like this:
|
||||
|
||||
```html
|
||||
data-unit="°F"
|
||||
```
|
||||
|
||||
If omitted, no units will be shown.
|
||||
|
||||
### {% linkable_title News %}
|
||||
Widget type ***News*** (contributed by [KRiS](https://community.home-assistant.io/users/kris/activity))
|
||||
|
||||
This is an RSS widget that can be used for displaying travel information, news etc. on the dashboard. The RSS feed will update every 60 minutes. To configure this, first it is necessary to add your desired feeds in `homeassistant/lib/ha_conf.rb` in the `$news_feeds` section. By default it comes with 2 sample feeds:
|
||||
|
||||
```ruby
|
||||
$news_feeds = {
|
||||
"Traffic" => "http://api.sr.se/api/rss/traffic/2863",
|
||||
"News" => "http://feeds.bbci.co.uk/news/rss.xml",
|
||||
}
|
||||
```
|
||||
|
||||
You can add as many as you want. The important point is that the key value (e.g. "Traffic" or "News" in the example above is used to tie the feed to your widget in the dashboard file. Here is an example of the Traffic widget that displays the first feed in the list:
|
||||
|
||||
```html
|
||||
<li data-row="3" data-col="2" data-sizex="2" data-sizey="2">
|
||||
<div data-id="Traffic" data-view="News" data-title="Traffic" data-interval="30" data-bgcolor="#643EBF">
|
||||
</li>
|
||||
```
|
||||
The value of thee `data-id` tag must match the key value in the `$news_feeds` configuration.
|
||||
|
||||
- **data-interval** (optional): The time in seconds that each entry in the RSS feed is displayed before the next one is shown, default is 30 seconds.
|
||||
|
||||
|
||||
**The follwing widget types have been deprecated in favor of the more flexible `Hasensor` and `Hameter` widgets. They will be removed in a future release.**
|
||||
|
||||
### {% linkable_title sensor (humidity) %}
|
||||
Widget type **Hahumidity**.
|
||||
|
||||
### {% linkable_title sensor (humidity) %}
|
||||
Widget type **Hahumiditymeter** (contributed by [Shiv Chanders](https://community.home-assistant.io/users/chanders/activity))
|
||||
|
||||
This is an alternative to the the text based humidity widget above, it display the humidity as an animated meter from 0 to 100%.
|
||||
|
||||
### {% linkable_title sensor (luminance) %}
|
||||
Widget type **Halux**.
|
||||
|
||||
### {% linkable_title sensor (temperature) %}
|
||||
Widget type **Hatemp**.
|
||||
|
||||
The Hatemp widget supports an additional paramater `data-unit`. This allows you to set the unit to whatever you want: Centigrade, Fahrenheit or even Kelvin if you prefer. You will need to explicitly include the degree symbol like this:
|
||||
|
||||
```html
|
||||
data-unit="°F"
|
||||
```
|
||||
If omitted, no units will be shown.
|
||||
|
||||
## {% linkable_title Customizing CSS styles %}
|
||||
If you want to customize the styles of your dashboard and widgets, there are two options:
|
||||
|
||||
1. You can edit the application.scss file (and the individual widget .scss files) directly (not recommended; if you pull down updates from the master repository, your changes might conflict/be overwritten)
|
||||
1. __Create override files (recommended)__
|
||||
1. Create a couple of additional files in the _assets/stylesheets_ directory: `_application_custom.scss` and `_variables_custom.scss`.
|
||||
1. Open `application.scss` and go to the bottom of the file. Uncomment the @import line.
|
||||
1. Open `_variables.scss` and go to the bottom of the file. Uncomment the @import line.
|
||||
1. Write your own SASS styles in `_application_custom.scss` (for general style customization) and `_variables_custom.scss` (for colors). You can customize those files without worrying about your changes getting overwritten if you pull down an update. The most you may have to do, if you update, will be to uncomment the @import lines again from steps 2 and 3.
|
||||
|
||||
__Note: The `_variables.scss` file (and your customizations from `_variables_custom.scss`) get imported into nearly every widget's SCSS file, so it is a best practice to define varaibles for colors in `_variables.scss` or `_variables_custom.scss` and reference those variables in the widget SCSS.__
|
||||
|
||||
## {% linkable_title Changes and Restarting %}
|
||||
|
||||
When you make changes to a dashboard, Dashing and `hapush` will both automatically reload and apply the changes without a need to restart.
|
||||
|
||||
Note: The first time you start Dashing, it can take up to a minute for the initial compilation of the pages to occur. You might get a timeout from your browser. If this occurs, be patient and reload. Subsequent reloads will be a lot quicker.
|
||||
|
||||
## {% linkable_title Multiple Pages %}
|
||||
|
||||
It is possible to have multiple pages within a dashboard. To do this, you can add an arbitary number of gridster divisions (you need at least one).
|
||||
|
||||
```html
|
||||
<div class="gridster"> <!-- Main Panel - PAGE 1 -->
|
||||
<some widgets>
|
||||
</div
|
||||
<div class="gridster"> <!-- More Stuff - PAGE 2 -->
|
||||
<more widgets>
|
||||
</div
|
||||
```
|
||||
|
||||
The divisions are implicitly numbered from 1 so it is a good idea to comment them. You can then add a widget to switch between pages like so:
|
||||
|
||||
```html
|
||||
<li data-row="1" data-col="1" data-sizex="1" data-sizey="1">
|
||||
<div data-id="cpage1" data-view="ChangePage" data-icon="cogs" data-title="Upstairs" data-page="3" data-stagger="false" data-fasttransition="true" data-event-click="onClick"></div>
|
||||
</li>
|
||||
```
|
||||
|
||||
- ***data-page*** : The name of the page to switch to
|
||||
|
||||
## {% linkable_title Multiple Dashboards %}
|
||||
You can also have multiple dashboards, by simply adding a new .erb file to the dashboards directory and navigating to the dashboards via `http://<IP address>:3030/dashboard-file-name-without-extension`
|
||||
|
||||
For example, if you want to deploy multiple devices, you could have one dashboard per room and still only use one hadashboard app installation.
|
||||
@ -1,95 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "HAPush"
|
||||
description: "HAPush"
|
||||
release_date: 2016-11-13 15:00:00 -0500
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /ecosystem/hadashboard/hapush/
|
||||
---
|
||||
|
||||
# Installing hapush (Manual install only)
|
||||
|
||||
This is not necessary if you are using Docker as it is already installed.
|
||||
|
||||
When you have the dashboard correctly displaying and interacting with Home Assistant you are ready to install the final component - `hapush`. Without `hapush` the dashboard would not respond to events that happen outside of the hadashboard system. For instance, if someone uses the Home Assistant interface to turn on a light, or even another App or physical switch, there is no way for the Dashboard to reflect this change. This is where `hapush` comes in.
|
||||
|
||||
`hapush` is a python daemon that listens to Home Assistant's Event Stream and pushes changes back to the dashboard to update it in real time. You may want to create a [Virtual Environment](https://docs.python.org/3/library/venv.html) for hapush - at the time of writing there is a conflict in the Event Source versions in use between HA and hapush.
|
||||
|
||||
Before running `hapush` you will need to add some python prerequisites:
|
||||
|
||||
```bash
|
||||
$ sudo pip3 install daemonize
|
||||
$ sudo pip3 install sseclient
|
||||
$ sudo pip3 install configobj
|
||||
```
|
||||
|
||||
Some users are reporting errors with `InsecureRequestWarning`:
|
||||
|
||||
```
|
||||
Traceback (most recent call last):
|
||||
File "./hapush.py", line 21, in <module>
|
||||
from requests.packages.urllib3.exceptions import InsecureRequestWarning
|
||||
ImportError: cannot import name 'InsecureRequestWarning'
|
||||
```
|
||||
|
||||
This can be fixed with:
|
||||
|
||||
```bash
|
||||
$ sudo pip3 install --upgrade requests
|
||||
```
|
||||
|
||||
## {% linkable_title Configuring hapush (all installation methods) %}
|
||||
|
||||
When you have all the prereqs in place, copy the `hapush.cfg.example` file to `hapush.cfg` then edit it to reflect your environment:
|
||||
|
||||
```
|
||||
ha_url = "http://192.168.1.10:8123"
|
||||
ha_key = api_key
|
||||
dash_host = "192.168.1.10:3030"
|
||||
dash_dir = "/srv/hass/src/hadashboard/dashboards"
|
||||
logfile = "/etc/hapush/hapush.log"
|
||||
```
|
||||
|
||||
- `ha_url` is a reference to your home assistant installation and must include the correct port number and scheme (`http://` or `https://` as appropriate)
|
||||
- `ha_key` should be set to your key if you have one, otherwise it can be removed.
|
||||
- `dash_host` should be set to the IP address and port of the host you are running Dashing on (no http or https) - this should be the same machine as you are running `hapush` on.
|
||||
- `dash_dir` is the path on the machine that stores your dashboards. This will be the subdirectory `dashboards` relative to the path you cloned `hadashboard` to. For Docker installs this should be set to `/app/dashboards`
|
||||
- `logfile` is the path to where you want `hapush` to keep its logs. 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 hapush to run from, although there is no reason you can't keep it in the `hapush` subdirectory of the cloned repository. For Docker installs this should be set to `/app/hapush/hapush.log`
|
||||
|
||||
## {% linkable_title Running hapush %}
|
||||
|
||||
For a manual installation you can then run `hapush` from the command-line as follows:
|
||||
|
||||
```bash
|
||||
$ ./hapush.py hapush.cfg
|
||||
```
|
||||
|
||||
For Docker installs, hapush will be started automatically when you run the startup command.
|
||||
|
||||
If all is well, you should start to see `hapush` responding to events as they occur. For a docker installation you should see these messages in `hapush/hapush.log`.
|
||||
|
||||
```bash
|
||||
2016-06-19 10:05:59,693 INFO Reading dashboard: /srv/hass/src/hadashboard/dashboards/main.erb
|
||||
2016-06-19 10:06:12,362 INFO switch.wendy_bedside -> state = on, brightness = 50
|
||||
2016-06-19 10:06:13,334 INFO switch.andrew_bedside -> state = on, brightness = 50
|
||||
2016-06-19 10:06:13,910 INFO script.night -> Night
|
||||
2016-06-19 10:06:13,935 INFO script.night_quiet -> Night
|
||||
2016-06-19 10:06:13,959 INFO script.day -> Night
|
||||
2016-06-19 10:06:13,984 INFO script.evening -> Night
|
||||
2016-06-19 10:06:14,008 INFO input_select.house_mode -> Night
|
||||
2016-06-19 10:06:14,038 INFO script.morning -> Night
|
||||
2016-06-19 10:06:21,624 INFO script.night -> Day
|
||||
2016-06-19 10:06:21,649 INFO script.night_quiet -> Day
|
||||
2016-06-19 10:06:21,674 INFO script.day -> Day
|
||||
2016-06-19 10:06:21,698 INFO script.evening -> Day
|
||||
2016-06-19 10:06:21,724 INFO input_select.house_mode -> Day
|
||||
2016-06-19 10:06:21,748 INFO script.morning -> Day
|
||||
2016-06-19 10:06:31,084 INFO switch.andrew_bedside -> state = off, brightness = 30
|
||||
2016-06-19 10:06:32,501 INFO switch.wendy_bedside -> state = off, brightness = 30
|
||||
2016-06-19 10:06:52,280 INFO sensor.side_multisensor_luminance_25 -> 871.0
|
||||
2016-06-19 10:07:50,574 INFO sensor.side_temp_corrected -> 70.7
|
||||
2016-06-19 10:07:51,478 INFO sensor.side_multisensor_relative_humidity_25 -> 52.0
|
||||
```
|
||||
@ -1,155 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Installation"
|
||||
description: "Installation"
|
||||
release_date: 2016-11-13 15:00:00 -0500
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /ecosystem/hadashboard/installation/
|
||||
---
|
||||
|
||||
Installation can be performed using Docker (Contributed by [marijngiesen](https://github.com/marijngiesen)) or manually if Docker doesn't work for you. We also have a Raspberry Pi version of Docker contributed by [snizzleorg](https://community.home-assistant.io/users/snizzleorg/activity).
|
||||
|
||||
## {% linkable_title Using Docker (Non Raspian) %}
|
||||
|
||||
Assuming you already have Docker installed, installation is fairly easy.
|
||||
|
||||
### {% linkable_title Clone the Repository %}
|
||||
|
||||
Clone the **hadashboard** repository to the current local directory on your machine.
|
||||
|
||||
``` bash
|
||||
$ git clone https://github.com/home-assistant/hadashboard.git
|
||||
```
|
||||
|
||||
Change your working directory to the repository root. Moving forward, we will be working from this directory.
|
||||
|
||||
``` bash
|
||||
$ cd hadashboard
|
||||
```
|
||||
|
||||
### {% linkable_title Build the docker image %}
|
||||
|
||||
```bash
|
||||
$ docker build -t hadashboard .
|
||||
```
|
||||
|
||||
When the build completes, you can run the dashboard with the following command for unix based systems:
|
||||
|
||||
```bash
|
||||
$ docker run --name="hadashboard" -d -v <path_to_hadashboard>/dashboards:/app/dashboards -v <path_to_hadashboard>/lib/ha_conf.rb:/app/lib/ha_conf.rb -v <path_to_hadashboard>/hapush:/app/hapush --net=host hadashboard
|
||||
```
|
||||
|
||||
If you are running docker on windows you should not use the `--net` command and explicitly specify the port, also for security reason `--net=host` should not be used so the following can also be used in unix. This will also set the process to start when the docker process starts so you do not have to worry about reboots. To map the volumes make sure you have ticked the shred drives in the settings. In this example I am using `c:\hadashboard` as the location where the git clone was done and mapping to port 3030 on the host.
|
||||
|
||||
```powershell
|
||||
docker run --restart=always --name="hadashboard" -p 3030:3030 -d -v C:/hadashboard/dashboards:/app/dashboards -v C:/hadashboard/lib/ha_conf.rb:/app/lib/ha_conf.rb -v C:/hadashboard/hapush:/app/hapush hadashboard
|
||||
```
|
||||
|
||||
This will use all of the same configuration files as specified below in the configuration sections, although you will need to make a few changes to the `hapush` configuration to match the docker's filesystem, detailed below.
|
||||
|
||||
By default, the docker instance should pick up your timezone but if you want to explicitly set it you can add an environment variable for your specific zone as follows:
|
||||
|
||||
```bash
|
||||
-e "TZ=Europe/Amsterdam"
|
||||
```
|
||||
|
||||
### {% linkable_title Docker on Raspberry Pi %}
|
||||
|
||||
Raspberry Pi needs to use a different Docker build file so the build command is slightly different:
|
||||
|
||||
```bash
|
||||
$ sudo docker build -f Docker-raspi/Dockerfile -t hadashboard .
|
||||
```
|
||||
|
||||
Apart from that the other steps are identical. Running Docker is pretty slow even on a PI3, be prepared for it to take an hour or two to build all of the extensions and install everything.
|
||||
|
||||
## {% linkable_title Manual Installation %}
|
||||
|
||||
### {% linkable_title Clone the Repository %}
|
||||
Clone the **hadashboard** repository to the current local directory on your machine.
|
||||
|
||||
``` bash
|
||||
$ git clone https://github.com/home-assistant/hadashboard.git
|
||||
```
|
||||
|
||||
Change your working directory to the repository root. Moving forward, we will be working from this directory.
|
||||
|
||||
``` bash
|
||||
$ cd hadashboard
|
||||
```
|
||||
|
||||
### {% linkable_title 2. Install Dashing and prerequirments %}
|
||||
|
||||
Essentially, you want to make sure that you have Ruby installed on your local machine.
|
||||
|
||||
For Debian based distribution do:
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install rubygems
|
||||
```
|
||||
|
||||
Then, install the Dashing gem:
|
||||
|
||||
```bash
|
||||
$ gem install dashing
|
||||
```
|
||||
|
||||
From your repository root, make sure that all dependencies are available. On some systems you may also need to install `bundler`:
|
||||
|
||||
```bash
|
||||
$ gem install bundler
|
||||
```
|
||||
|
||||
When installed run it:
|
||||
|
||||
``` bash
|
||||
$ bundle
|
||||
```
|
||||
|
||||
Bundle will now install all the ruby prerequirements for running dashing. Prerequirements will vary across different machines. So far users have reported requirements for some additional installs to allow the bundle to complete succesfully:
|
||||
|
||||
- ruby-dev - `sudo apt-get install ruby-dev`
|
||||
- node-js - `sudo apt-get install nodejs`
|
||||
- libsqlite3-dev - `sudo apt-get install libsqlite3-dev`
|
||||
- execjs gem - `gem install execjs`
|
||||
|
||||
You will need to research what works on your particular architecture and also bear in mind that version numbers may change over time.
|
||||
|
||||
This is currently running on various versions of Ruby and there are no strong dependencies however your mileage may vary.
|
||||
|
||||
## {% linkable_title Updating configuration (Manual and Docker) %}
|
||||
|
||||
Next, in the `./lib` directory, copy the `ha_conf.rb.example` file to `ha_conf.rb` and edit its settings to reflect your installation, pointing to the machine Home Assistant is running on and adding your API key.
|
||||
|
||||
```ruby
|
||||
$ha_url = "http://192.168.1.10:8123"
|
||||
$ha_apikey = "your key"
|
||||
```
|
||||
|
||||
- `$ha_url` is a reference to your Home Assistant installation and must include the correct port number and scheme (`http://` or `https://` as appropriate)
|
||||
- `$ha_apikey` should be set to your key if you have one, otherwise it can remain blank.
|
||||
|
||||
The file also contains example newsfeeds for the News widget:
|
||||
|
||||
```ruby
|
||||
$news_feeds = {
|
||||
"Traffic" => "http://api.sr.se/api/rss/traffic/2863",
|
||||
"News" => "http://feeds.bbci.co.uk/news/rss.xml",
|
||||
}
|
||||
```
|
||||
|
||||
You can leave these alone for now or if you prefer customize them as described in the News widget section.
|
||||
|
||||
When you are done, you can start a local webserver like this or if you are on docker it should start when you start the container.
|
||||
|
||||
```bash
|
||||
$ dashing start
|
||||
```
|
||||
|
||||
Point your browser to **http://localhost:3030** to access the hadashboard on your local machine, and you should see the supplied default dashboard. If you want to access it remotely ensure you have opened any required firewall rules.
|
||||
|
||||
If the page never finishes loading and shows up all white, edit the dashboard config to match your own setup, instructions in the next step.
|
||||
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Reboot"
|
||||
description: "Reboot"
|
||||
release_date: 2016-11-13 15:00:00 -0500
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /ecosystem/hadashboard/reboot/
|
||||
---
|
||||
|
||||
To run Dashing and `hapush` at reboot, checkout out the sample init scripts in the `./init` directory. These have been tested on a Raspberry Pi - your mileage may vary on other systems.
|
||||
|
||||
Instructions for automatically starting a Docker installation can be found [here](https://docs.docker.com/engine/admin/host_integration/).
|
||||
|
||||
For Docker you may also want to use `docker-compose` - there is a sample compose file in the `./init` directory.
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Updating HADashboard"
|
||||
description: "Updating HADashboard"
|
||||
release_date: 2016-11-13 15:00:00 -0500
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /ecosystem/hadashboard/updating/
|
||||
---
|
||||
|
||||
To update the dashboard after new code has been released, just run the following command to update your copy:
|
||||
|
||||
```bash
|
||||
$ git pull origin
|
||||
```
|
||||
|
||||
For some releases you may also need to rerun the `bundle` command:
|
||||
|
||||
``` bash
|
||||
$ bundle
|
||||
```
|
||||
|
||||
For Docker users, you will also need to rerun the Docker build process.
|
||||
@ -42,7 +42,7 @@ To use the camera it needs to be enabled with the `raspi-config` utility.
|
||||
$ sudo raspi-config
|
||||
```
|
||||
|
||||
Select `Enable camera` choose `<Yes>` and hit `Enter`, then go to `Finish` and you'll be prompted to reboot.
|
||||
Go to `Interfacing Options`, select `Enable camera` choose `<Yes>` and hit `Enter`, then go to `Finish` and you'll be prompted to reboot.
|
||||
|
||||
After this follow the [Raspberry Pi Camera component](/components/camera.rpi_camera/) page.
|
||||
|
||||
|
||||
@ -57,14 +57,6 @@ This is the most private option but requires a bit more work. There are multiple
|
||||
# Example configuration.yaml entry
|
||||
mqtt:
|
||||
broker: 192.168.1.100
|
||||
port: 1883
|
||||
client_id: home-assistant-1
|
||||
keepalive: 60
|
||||
username: USERNAME
|
||||
password: PASSWORD
|
||||
protocol: 3.1
|
||||
tls_insecure: True
|
||||
tls_version: 1.2
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -76,6 +68,7 @@ Configuration variables:
|
||||
- **username** (*Optional*): The username to use with your MQTT broker.
|
||||
- **password** (*Optional*): The corresponding password for the username to use with your MQTT broker.
|
||||
- **protocol** (*Optional*): Protocol to use: 3.1 or 3.1.1. By default it connects with 3.1.1 and falls back to 3.1 if server does not support 3.1.1.
|
||||
- **certificate** (*Optional*): Path to the certificate file, eg. `/home/user/.homeassistant/server.crt`.
|
||||
- **tls_insecure** (*Optional*): Set the verification of the server hostname in the server certificate.
|
||||
- **tls_version** (*Optional*): TLS/SSL protocol version to use. Available options are: `auto`, `1.0`, `1.1`, `1.2`. Defaults to `auto`.
|
||||
|
||||
@ -86,7 +79,7 @@ If you get this error `AttributeError: module 'ssl' has no attribute 'PROTOCOL_T
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
If you are running a mosquitto instance on a different server with proper SSL encryption using a service like letsencrypt you may have to set the certificate to the operating systems own `.crt` certificates file. In the instance of ubuntu this would be `certificate: /etc/ssl/certs/ca-certificates.crt`
|
||||
If you are running a Mosquitto instance on a different server with proper SSL encryption using a service like Let's Encrypt you may have to set the certificate to the operating systems own `.crt` certificates file. In the instance of Ubuntu this would be `certificate: /etc/ssl/certs/ca-certificates.crt`
|
||||
</p>
|
||||
|
||||
### {% linkable_title Public broker %}
|
||||
|
||||
@ -152,28 +152,9 @@
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/ecosystem/appdaemon/ AppDaemon %}
|
||||
<ul>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/installation/ Installation %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/configuration/ Configuration %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/example_apps/ Example Apps %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/running/ Running AppDaemon %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/reboot/ Starting AppDaemon at Reboot %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/operation/ Operation %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/windows/ AppDaemon on Windows %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/updating/ Updating AppDaemon %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/tutorial/ AppDaemon Tutorial %}</li>
|
||||
<li>{% active_link /docs/ecosystem/appdaemon/api/ AppDaemon API Reference %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/ecosystem/hadashboard/ HADashboard %}
|
||||
<ul>
|
||||
<li>{% active_link /docs/ecosystem/hadashboard/installation/ Installation %}</li>
|
||||
<li>{% active_link /docs/ecosystem/hadashboard/dash_config/ Dashboard Configuration %}</li>
|
||||
<li>{% active_link /docs/ecosystem/hadashboard/hapush/ HAPush %}</li>
|
||||
<li>{% active_link /docs/ecosystem/hadashboard/reboot/ Reboot %}</li>
|
||||
<li>{% active_link /docs/ecosystem/hadashboard/updating/ Updating HADashboard %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/ecosystem/notebooks/ Notebooks %}
|
||||
@ -196,7 +177,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Certificates
|
||||
{% active_link /docs/ecosystem/certificates/ Certificates %}
|
||||
<ul>
|
||||
<li>{% active_link /docs/ecosystem/certificates/tls_self_signed_certificate/ Self-signed certificate %}</li>
|
||||
<li>{% active_link /docs/ecosystem/certificates/tls_domain_certificate/ Certificate domain owners %}</li>
|
||||
|
||||
@ -15,7 +15,7 @@ Another month has passed and some great new features have landed in Home Assista
|
||||
This release includes some architectural changes by me. The first is that the frontend is now based on a [NuclearJS](http://optimizely.github.io/nuclear-js/) JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.
|
||||
|
||||
__IP Camera Support__
|
||||
James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.
|
||||
James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a URL can be integrated.
|
||||
|
||||
Home Assistant will route the requests to your camera via the server allowing you to expose IP camera's inside your network via the Home Assistant app.
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ Head over to the [setup instructions](/components/ifttt/) to get started with IF
|
||||
|
||||
<!--more-->
|
||||
|
||||
In each of the following examples, make sure to replace the XXX in the url with your correct host address and api password.
|
||||
In each of the following examples, make sure to replace the XXX in the URL with your correct host address and API password.
|
||||
|
||||
## {% linkable_title Turn off irregation system when not needed %}
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ comments: true
|
||||
categories: Release-Notes
|
||||
---
|
||||
|
||||
It's like someone opened a can of rock solid developers and emptied it above our [chat channel](https://gitter.im/balloob/home-assistant) because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
|
||||
It's like someone opened a can of rock solid developers and emptied it above our [chat channel](https://discord.gg/c5DvZ4e) because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
|
||||
|
||||
See [GitHub](https://github.com/home-assistant/home-assistant/releases/tag/0.7.3) for more detailed release notes.
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ categories: Survey
|
||||
og_image: /images/blog/2015-11-survey/releases.png
|
||||
---
|
||||
|
||||
<img src='/images/blog/2015-11-survey/releases.png' style='float: right; margin-left: 8px; margin-bottom: 8px;' height='120'/>Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that's enough time to have some "only partially representative" data. It's hard to tell how many Home Assistant users are out there. Currently there are 215 members in our [Gitter chat room](https://gitter.im/balloob/home-assistant) and last week [PyPI](https://pypi.python.org/pypi/homeassistant/) counted 5063 downloads.
|
||||
<img src='/images/blog/2015-11-survey/releases.png' style='float: right; margin-left: 8px; margin-bottom: 8px;' height='120'/>Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that's enough time to have some "only partially representative" data. It's hard to tell how many Home Assistant users are out there. Currently there are 215 members on our [Discord chat server](https://discord.gg/c5DvZ4e) and last week [PyPI](https://pypi.python.org/pypi/homeassistant/) counted 5063 downloads.
|
||||
|
||||
The idea was to anonymously collect some details about the usage of the different parts of Home Assistant and a little bit about the environment its running in.
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ But there is more you can do! You can not only host images for customization the
|
||||
|
||||
<!--more-->
|
||||
|
||||
In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://gitter.im/balloob/home-assistant) and even made it into the [issue tracker](https://github.com/home-assistant/home-assistant/issues/1392). The existing solutions ([Smart mirror](http://docs.smart-mirror.io/), [MagicMirror](http://michaelteeuw.nl/tagged/magicmirror), and [HomeMirror](https://github.com/HannahMitt/HomeMirror)) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.
|
||||
In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://discord.gg/c5DvZ4e) and even made it into the [issue tracker](https://github.com/home-assistant/home-assistant/issues/1392). The existing solutions ([Smart mirror](http://docs.smart-mirror.io/), [MagicMirror](http://michaelteeuw.nl/tagged/magicmirror), and [HomeMirror](https://github.com/HannahMitt/HomeMirror)) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.
|
||||
|
||||
There are plenty of ways to achieve this...[RESTful API](/developers/rest_api/), [Python API](/developers/python_api/), or one of the [history components](/components/#history). If it is to be a web page I'm using the [MQTT Eventstream component](/components/mqtt_eventstream/) and [mqttws31.js](http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src).
|
||||
|
||||
|
||||
@ -37,5 +37,5 @@ Paulus
|
||||
|
||||
[gh-ha]: https://github.com/home-assistant/
|
||||
[filling in the blanks]: /developers/platform_example_sensor/#code
|
||||
[chat room]: https://gitter.im/home-assistant/home-assistant
|
||||
[chat room]: https://discord.gg/c5DvZ4e
|
||||
[forums]: https://community.home-assistant.io/
|
||||
|
||||
@ -37,7 +37,7 @@ Muhammed Kilic has created a video how to make your Home Assistant instance acce
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/UM15pRk56h8" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
[chat room]: https://gitter.im/home-assistant/home-assistant
|
||||
[chat room]: https://discord.gg/c5DvZ4e
|
||||
[SceneGen]: https://github.com/acockburn/scenegen
|
||||
[Andrew Cockburn]: https://github.com/acockburn
|
||||
[BRUH Automation]: http://www.bruhautomation.com/
|
||||
|
||||
@ -32,7 +32,7 @@ On the config side, you can now [store your passwords][secrets] in your OS keyri
|
||||
- Sensor: [Fixer.io] now supported ([@fabaff])
|
||||
- Garage door: Control any garage door using [Raspberry Pi GPIO pins] ([@kellerza])
|
||||
- Sensor: [OpenExchangeRates] support added ([@arsaboo])
|
||||
- Notify: [Pushover] now supports target device, sound, url and priority ([@dale3h])
|
||||
- Notify: [Pushover] now supports target device, sound, URL and priority ([@dale3h])
|
||||
- Sensor: [Netatmo] now supports wind, battery and radio signals ([@Jypy])
|
||||
- Log successful and failed login attemps ([@fabaff])
|
||||
- Config: allow [extracting account info][secrets] into OS keyring or separate YAML file ([@kellerza])
|
||||
|
||||
@ -145,11 +145,11 @@ Thanks all for sticking with me to the end. I'll be taking over a lot of Paulus'
|
||||
|
||||
Also, thanks as always to our developer contributors, documentation contributors, but most of all our users! This would've just been a script that Paulus (@balloob) used to control his lights at home if we didn't have your enthusiasm.
|
||||
|
||||
Feel free to let me know what you thought of this blog post and release on Gitter or my [Twitter](https://twitter.com/robbie), or even the [Home Assistant Twitter](https://twitter.com/home_assistant). Did I mention we have a brand new [Facebook page](https://www.facebook.com/homeassistantio) that you should absolutely Like? There's a convenient Facebook Like and Twitter follow button right on the sidebar.
|
||||
Feel free to let me know what you thought of this blog post and release on [Discord](https://discord.gg/c5DvZ4e) or my [Twitter](https://twitter.com/robbie), or even the [Home Assistant Twitter](https://twitter.com/home_assistant). Did I mention we have a brand new [Facebook page](https://www.facebook.com/homeassistantio) that you should absolutely Like? There's a convenient Facebook Like and Twitter follow button right on the sidebar.
|
||||
|
||||
I almost forgot about your 🎁 for reading all the way to here: a 🍪! Hope you enjoy it in good health 😄.
|
||||
|
||||
Talk to you soon on Gitter and in your pull request comments!
|
||||
Talk to you soon on Discord and in your pull request comments!
|
||||
|
||||
-- Robbie
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ The validation of the configuration is still on-going. Approximatly 80 % is done
|
||||
- Custom components extending `BaseNotificationService` need to be aware that `kwargs.get(ATTR_TITLE)` will now return `None` if a title has not been set, and will need to specify `kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT)` if they always require a title.
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant).
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
|
||||
|
||||
|
||||
[@DavidLP]: https://github.com/DavidLP
|
||||
|
||||
@ -110,7 +110,7 @@ Since 0.28 [automation rules](/blog/2016/09/10/notify-group-reload-api-pihole/#r
|
||||
- Nest sensor 'mode' has been renamed to 'operation_mode'
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
|
||||
[nest-issues]: https://github.com/home-assistant/home-assistant/issues/3574
|
||||
[@jabesq]: https://github.com/jabesq
|
||||
|
||||
@ -38,5 +38,5 @@ Are you not a programmer but still want to contribute to Home Assistant? Check o
|
||||
[issues]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
|
||||
[issues-doc]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
|
||||
[dev-env]: /developers/development_environment/
|
||||
[dev-chat]: https://gitter.im/home-assistant/home-assistant/devs
|
||||
[dev-chat]: https://discord.gg/8X8DTH4
|
||||
[dev-forum]: https://community.home-assistant.io/c/development
|
||||
|
||||
@ -123,7 +123,7 @@ sensor
|
||||
- The [aREST][arest] configuration between the [sensor][arest-sensor] and the [switch][arest-switch] platform was aligned.
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bbangert]: https://github.com/bbangert
|
||||
|
||||
@ -208,7 +208,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
|
||||
- The Z-Wave entity ID change mentioned above
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
|
||||
## {% linkable_title Until next time %}
|
||||
|
||||
|
||||
@ -117,7 +117,7 @@ Our website has now an additional category called "Ecosystem". This will become
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
|
||||
[@mweinelt]: https://github.com/mweinelt
|
||||
[@aa755]: https://github.com/aa755
|
||||
|
||||
@ -136,7 +136,7 @@ We are working on a better solution for 0.35.
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you use these communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use these communication channels. Thanks.
|
||||
|
||||
### {% linkable_title Reporting Issues %}
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ categories: Release-Notes
|
||||
og_image: /images/blog/2016-12-0.35/social.png
|
||||
---
|
||||
|
||||
5000 stars on GitHub, 2000 people in out Gitter chatroom and over a million monthly page views. I don't think we could wish for a better place to be at the end of 2016. Feels like an early Christmas present! Our early one for you is 0.35. It's not a single thing inside a nice wrapping, more like several little gifts inside the 0.35 box.
|
||||
5000 stars on GitHub, 2000 people in our [chatroom][discord] and over a million monthly page views. I don't think we could wish for a better place to be at the end of 2016. Feels like an early Christmas present! Our early one for you is 0.35. It's not a single thing inside a nice wrapping, more like several little gifts inside the 0.35 box.
|
||||
|
||||
This will be the last release of 2016 as our developers are taking a well deserved break. We will be back in 2017!
|
||||
|
||||
@ -23,7 +23,7 @@ With the addition of a [text-to-speech][tts] component by [@pvizeli] we have bee
|
||||
## {% linkable_title Call for help with HASSbian (our Raspberry Pi image) %}
|
||||
In an effort to make Home Assistant, we're planning to extend the things that people can do out of the box with HASSbian, our Raspberry Pi image. As you might know, the image is currently maintained by [@Landrash]. However he also spends a lot of time on improving the docs and helping out with a ton of other things.
|
||||
|
||||
So if you know your Linux-foo and would love to contribute to open source, join the [Hassbian developer chat](https://gitter.im/home-assistant/hassbian) and take a stab at one of [our open issues](https://github.com/home-assistant/pi-gen/issues).
|
||||
So if you know your Linux-foo and would love to contribute to open source, join the [developer chat][discord-devs] and take a stab at one of [our open issues](https://github.com/home-assistant/pi-gen/issues).
|
||||
|
||||
## {% linkable_title VLC media player, Broadlink, and GPSLogger %}
|
||||
Let you control [VLC media player][vlc-media] and play sound on connected speakers.
|
||||
@ -64,7 +64,7 @@ The [GPSLogger](https://home-assistant.io/components/device_tracker.gpslogger/)
|
||||
|
||||
### {% linkable_title Release 0.35.1 - December 18 %}
|
||||
|
||||
Some issues have been reported with TTS that will be addressed by 0.35.1. The TTS component had issues linking the media player to the right media file if you were using Docker or SSL certificates. This can be fixed by exposing to your HTTP config what url you use for hosting Home Assistant:
|
||||
Some issues have been reported with TTS that will be addressed by 0.35.1. The TTS component had issues linking the media player to the right media file if you were using Docker or SSL certificates. This can be fixed by exposing to your HTTP config what URL you use for hosting Home Assistant:
|
||||
|
||||
```yaml
|
||||
http:
|
||||
@ -88,7 +88,7 @@ http:
|
||||
- Fix nest component with various KeyError exceptions ([@technicalpickles])
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) 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](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
@ -152,3 +152,5 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[flic]: https://home-assistant.io/components/binary_sensor.flic/
|
||||
[sensehat]: https://home-assistant.io/components/sensor.sensehat/
|
||||
[tts]: https://home-assistant.io/components/tts/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
[discord-devs]: https://discord.gg/8X8DTH4
|
||||
|
||||
@ -99,7 +99,7 @@ The new [image processing component][image] currently works with [number plates]
|
||||
- TTS cache files use now the language abbreviation as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. `HASH_PLATFORM.xxx` -> `HASH_LANG_PLATFORM.xxx`.
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). 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](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
|
||||
@ -27,7 +27,7 @@ Starting today we are announcing a few initiatives to help protect our users, co
|
||||
|
||||
More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we're introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.
|
||||
|
||||
Moving forward this Code of Conduct will be active for all projects within the Home Assistant organisation.
|
||||
Moving forward this Code of Conduct will be active for all projects within the Home Assistant organization.
|
||||
|
||||
[Read the Code of Conduct][coc]
|
||||
|
||||
@ -95,9 +95,11 @@ We have now mostly automated updating the [Credits](/developers/credits/) page s
|
||||
|
||||
## {% linkable_title In closing %}
|
||||
|
||||
We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, Twitter or Gitter.
|
||||
We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, [Twitter][twitter] or [Discord][discord].
|
||||
|
||||
[cla]: /developers/cla/
|
||||
[mjg59]: https://twitter.com/mjg59
|
||||
[gh-cla]: https://cla.github.com/
|
||||
[license]: /developers/license/
|
||||
[twitter]: https://twitter.com/home_assistant
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -137,7 +137,7 @@ Bugfix: [@balloob], [@fabaff], [@freol35241], [@pvizeli], [@Danielhiversen], [@t
|
||||
- Fix Telldus Live dim level error on startup ([@molobrakos])
|
||||
- Fix Sonos group coordinators ([@pvizeli])
|
||||
- UPC Connect: Parse XML outside event loop ([@pvizeli])
|
||||
- Fix Netatmo SSL issue with VPN url ([@jabesq])
|
||||
- Fix Netatmo SSL issue with VPN URL ([@jabesq])
|
||||
- Homematic: Fix bug with UNREACH device state/restore and variables not updating ([@pvizeli])
|
||||
- Sonos: Prevent duplicate entries in favorite list ([@pvizeli])
|
||||
- Fix Schlage Connect deadbolt integration via Z-Wave ([@turbokongen])
|
||||
@ -155,7 +155,7 @@ Bugfix: [@balloob], [@fabaff], [@freol35241], [@pvizeli], [@Danielhiversen], [@t
|
||||
- TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. `HASH_LANG_PLATFORM.xxx` -> `HASH_LANG_OPTIONS_PLATFORM.xxx`, replace *OPTIONS* with `-` on exiting platforms.
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). 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](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
|
||||
@ -50,13 +50,13 @@ With this image there also quite a bit of cleaning of the base system and the sc
|
||||
There's of course more on the horizon and there's even more plans and wishes for how this image will function in the future.
|
||||
On the close horizon from [@Landrash][landrash-github] there a few more script in the works and for tellstick, emulated_hue and for controlling Home Assistant.
|
||||
|
||||
To follow discussions about the development of the HASSbian image or to contribute join the [HASSbian gitter chat][hassbian-gitter].
|
||||
To follow discussions about the development of the HASSbian image or to contribute join our [Discord chat server][discord].
|
||||
|
||||
To get started with the new image, check out the installation instructions in the [getting started section][gs-image].
|
||||
|
||||
[cec]: /components/hdmi_cec/
|
||||
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts
|
||||
[hassbian-avahi]: hassbian.local
|
||||
[hassbian-gitter]: https://gitter.im/home-assistant/hassbian
|
||||
[landrash-github]: https://github.com/Landrash
|
||||
[gs-image]: /getting-started/installation-raspberry-pi-image/
|
||||
[discord]: https://discord.gg/8X8DTH4
|
||||
|
||||
@ -138,7 +138,7 @@ Bugfixes: [@balloob], [@fabaff], [@pvizeli], [@mnoorenberghe] [@Danielhiversen],
|
||||
- The frontend core changes have caused all custom panels to break. Docs have not been updated yet. The gist is that you have to use `this.hass.entities`, `this.hass.callService` and `this.hass.callApi`.
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
@ -226,6 +226,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
|
||||
[event-stream-api]: https://home-assistant.io/developers/server_sent_events/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[websocket-api]: https://home-assistant.io/developers/websocket_api/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -224,7 +224,7 @@ hdmi_cec:
|
||||
[@pvizeli], [@LinuxChristian], [@molobrakos], [@balloob], [@rytilahti], [@fabaff], [@andrey-git], [@aequitas], [@konikvranik], [@Danielhiversen], [@colinodell], [@pschmitt], [@bachp], [@bachp],[@w1ll1am23], [@valentinalexeev], [@robbiet480], [@MartinHjelmare], [@happyleavesaoc], [@tdickman], [@arraylabs], [@lwis], [@titilambert]
|
||||
|
||||
### If you need help...
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
|
||||
### 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.
|
||||
@ -312,6 +312,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[docs-issue]: https://github.com/home-assistant/home-assistant.github.io/issues/1603
|
||||
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[t-shirt]: https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -64,7 +64,7 @@ twilio:
|
||||
- If you are using async custom components, the passed in `async_add_devices` method is now a callback instead of a coroutine function.
|
||||
|
||||
### If you need help...
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
|
||||
### 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.
|
||||
@ -204,7 +204,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
||||
- Fix unnecessary warning for ip bans.yaml ([@balloob])
|
||||
- Better restore_state warnings ([@balloob])
|
||||
- Set new color before turning LIFX bulbs on ([@amelchio])
|
||||
- Don't log username and password in camera url ([@ishults])
|
||||
- Don't log username and password in camera URL ([@ishults])
|
||||
- Ignore deleted mails in IMAP unread count (#6394) ([@amelchio])
|
||||
- Delay zwave updates for 100ms to group them. ([@andrey-git])
|
||||
- Rename _scheduled_update to _update_scheduled ([@andrey-git])
|
||||
@ -301,7 +301,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
||||
[@vroomfonde1]: https://github.com/vroomfonde1
|
||||
[@wardcraigj]: https://github.com/wardcraigj
|
||||
[@zhelev]: https://github.com/zhelev
|
||||
[main chat channel]: https://gitter.im/home-assistant/home-assistant
|
||||
[main chat channel]: https://discord.gg/c5DvZ4e
|
||||
[@dale3h]: https://github.com/dale3h
|
||||
[@CCOSTAN]: https://github.com/CCOSTAN
|
||||
[@skalavala]: https://github.com/skalavala
|
||||
@ -310,7 +310,6 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
||||
[@bassclarinetl2]: https://github.com/bassclarinetl2
|
||||
[@torn8o]: https://github.com/torn8o
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[EFF]: https://www.eff.org
|
||||
[hass-shirt]: https://home-assistant.io/blog/2017/02/22/home-assistant-tshirts-have-arrived/
|
||||
@ -329,3 +328,4 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
||||
[@jnewland]: https://github.com/jnewland
|
||||
[#6702]: https://github.com/home-assistant/home-assistant/pull/6702
|
||||
[#6738]: https://github.com/home-assistant/home-assistant/pull/6738
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -40,7 +40,7 @@ The new format of the changelog which was introduced with 0.40 will provide a li
|
||||
- The frontend is now using [Shadow DOM][shadow] and this could break your custom panels ([#228](https://github.com/home-assistant/home-assistant-polymer/issues/228)).
|
||||
|
||||
## If you need help...
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
|
||||
## 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.
|
||||
@ -347,8 +347,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[shadow]: https://www.w3.org/TR/shadow-dom/
|
||||
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
[@bdurrer]: https://github.com/bdurrer
|
||||
[interview]: https://home-assistant.io/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/
|
||||
|
||||
@ -85,7 +85,7 @@ sensor:
|
||||
```
|
||||
|
||||
## If you need help...
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
|
||||
## 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.
|
||||
@ -225,7 +225,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- light.yeelight: catch i/o related exceptions from the backend lib ([@rytilahti] - [#6952])
|
||||
- Fix current_temperature is rounded ([@aufano] - [#6960])
|
||||
- Preserve customize glob order. ([@andrey-git] - [#6963])
|
||||
- Foscam Camera: Adding exception handling when fetching the camera image to avoid python exception errors when host is not reachable or rather any url error to camera ([@viswa-swami] - [#6964])
|
||||
- Foscam Camera: Adding exception handling when fetching the camera image to avoid python exception errors when host is not reachable or rather any URL error to camera ([@viswa-swami] - [#6964])
|
||||
- Crime Reports sensor ([@happyleavesaoc] - [#6966]) (new-platform)
|
||||
- Update kodi for aiohttp2 ([@armills] - [#6967])
|
||||
- Bugfix time and task coro ([@pvizeli] - [#6968])
|
||||
@ -398,10 +398,10 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[@wardcraigj]: https://github.com/wardcraigj
|
||||
[@wmalgadey]: https://github.com/wmalgadey
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[#7057]: https://github.com/home-assistant/home-assistant/pull/7057
|
||||
[#7106]: https://github.com/home-assistant/home-assistant/pull/7106
|
||||
[#7137]: https://github.com/home-assistant/home-assistant/pull/7137
|
||||
[#7141]: https://github.com/home-assistant/home-assistant/pull/7141
|
||||
[@robbiet480]: https://github.com/robbiet480
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -84,7 +84,7 @@ sensor:
|
||||
```
|
||||
|
||||
## If you need help...
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
|
||||
## 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.
|
||||
@ -116,7 +116,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Bugfix time and task coro ([@pvizeli] - [#6968])
|
||||
- Initial import for HassIO ([@pvizeli] - [#6935])
|
||||
- Preserve customize glob order. ([@andrey-git] - [#6963])
|
||||
- Foscam Camera: Adding exception handling when fetching the camera image to avoid python exception errors when host is not reachable or rather any url error to camera ([@viswa-swami] - [#6964]) ([camera.foscam docs])
|
||||
- Foscam Camera: Adding exception handling when fetching the camera image to avoid python exception errors when host is not reachable or rather any URL error to camera ([@viswa-swami] - [#6964]) ([camera.foscam docs])
|
||||
- light.yeelight: catch i/o related exceptions from the backend lib ([@rytilahti] - [#6952])
|
||||
- From Dusk till Dawn ([@BillyNate] - [#6857]) ([sun docs])
|
||||
- Tests for zwave services ([@armills] - [#6937]) ([zwave docs])
|
||||
@ -487,7 +487,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[zwave docs]: /components/zwave/
|
||||
[zwave.node_entity docs]: /components/zwave.node_entity/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[#7204]: https://github.com/home-assistant/home-assistant/pull/7204
|
||||
[#7214]: https://github.com/home-assistant/home-assistant/pull/7214
|
||||
@ -519,3 +518,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
|
||||
[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/
|
||||
[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -39,12 +39,12 @@ With this image there also quite a bit of cleaning of the base system and the sc
|
||||
- Added libtool and autoconf package. Dependencies for some of the pip packages.
|
||||
- Pi ZeroW should now work with the image.
|
||||
|
||||
To follow discussions about the development of the HASSbian image or to contribute join the [HASSbian gitter chat][hassbian-gitter].
|
||||
To follow discussions about the development of the HASSbian image or to contribute join our [Discord chat server][discord-devs].
|
||||
|
||||
To get started with the new image, check out the installation instructions in the [getting started section][gs-image].
|
||||
|
||||
[cec]: /components/hdmi_cec/
|
||||
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts/
|
||||
[hassbian-config-release]: https://github.com/home-assistant/hassbian-scripts/releases/latest
|
||||
[hassbian-gitter]: https://gitter.im/home-assistant/hassbian
|
||||
[gs-image]: /getting-started/installation-raspberry-pi-image/
|
||||
[discord-devs]: https://discord.gg/8X8DTH4
|
||||
|
||||
@ -24,7 +24,7 @@ And finally, for users of the config panel in the UI, we have fixed the issue wi
|
||||
Enjoy!
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
@ -499,7 +499,6 @@ influxdb:
|
||||
[wink docs]: https://home-assistant.io/components/wink/
|
||||
[zha docs]: https://home-assistant.io/components/zha/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[#7062]: https://github.com/home-assistant/home-assistant/pull/7062
|
||||
[#7468]: https://github.com/home-assistant/home-assistant/pull/7468
|
||||
@ -510,3 +509,4 @@ influxdb:
|
||||
[@pezinek]: https://github.com/pezinek
|
||||
[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/
|
||||
[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -78,7 +78,7 @@ If you are using our [experimental Hass.io image][hass.io], we made a breaking c
|
||||
- Allow fetching hass.io panel without auth ([@balloob] - [#7714]) ([hassio docs])
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
@ -423,7 +423,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[zwave docs]: https://home-assistant.io/components/zwave/
|
||||
[zwave.api docs]: https://home-assistant.io/components/zwave.api/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[#7673]: https://github.com/home-assistant/home-assistant/pull/7673
|
||||
[#7683]: https://github.com/home-assistant/home-assistant/pull/7683
|
||||
@ -435,3 +434,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[hassio docs]: https://home-assistant.io/components/hassio/
|
||||
[media_player.volumio docs]: https://home-assistant.io/components/media_player.volumio/
|
||||
[telegram_bot.__init__ docs]: https://home-assistant.io/components/telegram_bot.__init__/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -55,7 +55,7 @@ sensor:
|
||||
- Disallow ambiguous color descriptors in the light.turn_on schema. This means that you can no longer specify both `xy_color` and `rgb_color`. ([@amelchio] - [#7765]) (breaking change)
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
@ -382,7 +382,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[zoneminder docs]: https://home-assistant.io/components/zoneminder/
|
||||
[zwave docs]: https://home-assistant.io/components/zwave/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[#7780]: https://github.com/home-assistant/home-assistant/pull/7780
|
||||
[#7841]: https://github.com/home-assistant/home-assistant/pull/7841
|
||||
@ -397,3 +396,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/
|
||||
[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
|
||||
[media_player.roku docs]: https://home-assistant.io/components/media_player.roku/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -85,7 +85,7 @@ To run without the monkey patch, start Home Assistant with `HASS_NO_MONKEY=1 has
|
||||
- Add Flexit AC climate platform ([@Sabesto] - [#7871]) ([climate.flexit 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][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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.
|
||||
@ -563,7 +563,6 @@ automation:
|
||||
[zwave docs]: https://home-assistant.io/components/zwave/
|
||||
[zwave blog post]: https://home-assistant.io/blog/2017/06/15/zwave-entity-ids/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[first-commit]: https://home-assistant.io/help/trivia/#first-commit
|
||||
[#8080]: https://github.com/home-assistant/home-assistant/pull/8080
|
||||
@ -575,3 +574,4 @@ automation:
|
||||
[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/
|
||||
[remote.itach docs]: https://home-assistant.io/components/remote.itach/
|
||||
[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -26,11 +26,11 @@ zwave:
|
||||
new_entity_ids: false
|
||||
```
|
||||
|
||||
## Big speed up in querying the history
|
||||
## {% linkable_title Big speed up in querying the history %}
|
||||
|
||||
Thanks to the work by [@cmsimike] in [#8255] you'll see a significant speed up when using the history view. In his local tests queries went from 1 minute to 90ms! ⚡️
|
||||
|
||||
## Snips.ai component
|
||||
## {% linkable_title Snips.ai component %}
|
||||
|
||||
Snips has contributed a component to integrate with their Snips.ai local voice assistant. This will allow you to hook a speaker and a microphone into your Raspberry Pi and make your own local Amazon Echo quickly. See [the docs][snips docs] for further instructions.
|
||||
|
||||
@ -38,7 +38,17 @@ Also a shoutout to [@michaelarnauts] for keeping an eye on our Docker build and
|
||||
|
||||
[issue-polymer]: https://github.com/home-assistant/home-assistant-polymer/issues
|
||||
|
||||
## New Platforms
|
||||
## {% linkable_title Release 0.48.1 - July 5 %}
|
||||
|
||||
- Fix arlo sensors. ([@bergemalm] - [#8333]) ([sensor.arlo docs])
|
||||
- API POST no longer marks the number zero as invalid ([@azogue] - [#8324]) ([api docs])
|
||||
- Fix Snips json schema ([@adrienball] - [#8317]) ([snips docs])
|
||||
- Fix pathlib resolve ([@pvizeli] - [#8311])
|
||||
- Fix harmony ([@balloob] - [#8302]) ([remote.harmony docs])
|
||||
- Fix Arlo startup crash (fixes #8288) ([@fabaff] - [#8290]) ([camera.arlo docs])
|
||||
- Temporary fix for the client_id generation (fixes #8315) ([@fabaff] - [#8336]) ([mqtt docs])
|
||||
|
||||
## {% linkable_title New Platforms %}
|
||||
|
||||
- Add initial support for Shiftr.io ([@fabaff] - [#7974]) ([shiftr docs]) (new-platform)
|
||||
- Upnp properties ([@dgomes] - [#8067]) ([upnp docs]) ([sensor.upnp docs]) (new-platform)
|
||||
@ -58,14 +68,14 @@ Also a shoutout to [@michaelarnauts] for keeping an eye on our Docker build and
|
||||
- Snips ASR and NLU component ([@michaelfester] - [#8156]) ([snips 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][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
...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-->
|
||||
|
||||
## Breaking Changes
|
||||
## {% linkable_title Breaking Changes %}
|
||||
|
||||
- We have added a new option to whitelist folders that can be used as sources for sending files. You will need to use this option if you are using files with the telegram component. ([@pvizeli] - [#8189]) (breaking change)
|
||||
|
||||
@ -110,7 +120,7 @@ light:
|
||||
fade: none
|
||||
```
|
||||
|
||||
## All changes
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- Update numpy 1.13.0 ([@pvizeli] - [#8059]) ([image_processing.opencv docs])
|
||||
- No update in MQTT Binary Sensor #7478 ([@pezinek] - [#8057])
|
||||
@ -509,5 +519,20 @@ light:
|
||||
[weather.buienradar docs]: /components/weather.buienradar/
|
||||
[zwave docs]: /components/zwave/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
[#8290]: https://github.com/home-assistant/home-assistant/pull/8290
|
||||
[#8302]: https://github.com/home-assistant/home-assistant/pull/8302
|
||||
[#8311]: https://github.com/home-assistant/home-assistant/pull/8311
|
||||
[#8317]: https://github.com/home-assistant/home-assistant/pull/8317
|
||||
[#8324]: https://github.com/home-assistant/home-assistant/pull/8324
|
||||
[#8333]: https://github.com/home-assistant/home-assistant/pull/8333
|
||||
[#8336]: https://github.com/home-assistant/home-assistant/pull/8336
|
||||
[@adrienball]: https://github.com/adrienball
|
||||
[@bergemalm]: https://github.com/bergemalm
|
||||
[api docs]: https://home-assistant.io/components/api/
|
||||
[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
|
||||
[mqtt docs]: https://home-assistant.io/components/mqtt/
|
||||
[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
|
||||
[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
|
||||
[snips docs]: https://home-assistant.io/components/snips/
|
||||
|
||||
@ -0,0 +1,90 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant is moving to Discord"
|
||||
description: "The Home Assistant chat community is moving over to Discord."
|
||||
date: 2017-07-03 18:28:01 -0500
|
||||
date_formatted: "July 3, 2017"
|
||||
author: Dale Higgs
|
||||
author_twitter: dale3h
|
||||
comments: true
|
||||
categories: Community
|
||||
---
|
||||
|
||||
Communities grow, things change. We understand that some people don't like change, and that is why we are trying to make our chat transition from Gitter to [Discord][discord] as smooth as possible for everyone. Join us now with [just a click][discord]!
|
||||
|
||||
Click `Read on →` to find out more about why we're moving.
|
||||
|
||||
<!--more-->
|
||||
|
||||
### {% linkable_title Easy to join %}
|
||||
|
||||
Discord is a very easy platform to join. New users can immediately jump into the conversations without first having to create an account. Just provide your name and you're in!
|
||||
|
||||
This is incredibly valuable for us and will make Home Assistant even more accessible than before.
|
||||
|
||||
### {% linkable_title Great apps %}
|
||||
|
||||
One of our least favorite things about Gitter is the quality of apps that they provide for iOS and Android devices. Discord, on the other hand, has the fastest and most feature-rich mobile apps that we've tried! For those of you who like to post pictures to the chatrooms directly from your phone...now you can. It doesn't stop there; they also provide well-polished clients for Windows, macOS and even Linux. If you're more of a browser-based chat client person, their web client will be perfect for you.
|
||||
|
||||
### {% linkable_title Moderation tools %}
|
||||
|
||||
We have been quite lucky so far as to not have much inappropriate behavior (spammers, trolls, etc) in our chatrooms. However, as our community continues to grow, this common issue might come up. Discord has the features that will help us shut this behavior down before it gets out of hand.
|
||||
|
||||
### {% linkable_title Great multiple server support %}
|
||||
|
||||
Do you already have a Discord account? Great! You can use that account to [join in on the conversation][discord] now. One Discord account works with every Discord server. It is extremely easy to switch between servers or join new ones. Discord messages also work across servers, so your personal conversations are not scoped to a single server.
|
||||
|
||||
### {% linkable_title It's hosted %}
|
||||
|
||||
We are big fans of self-hosted apps and services, but everyone knows they require a fair amount of maintenance and attention to keep them running smoothly. Discord is hosted on its own servers, so it's better to let them maintain the service while we keep busy improving Home Assistant to bring you new and exciting features!
|
||||
|
||||
### {% linkable_title Plenty of features %}
|
||||
|
||||
Syntax highlighting, voice chats, ability to search chatrooms, private messaging, and even custom emoji! Discord has a great set of features that will keep us all happy for a long time to come. (Pssst...after you join our server, check out the `:ponder:` emoji!)
|
||||
|
||||
## {% linkable_title Join us! %}
|
||||
|
||||
Are you convinced and ready to make the switch? Join us, we're just [one click away][discord]!
|
||||
|
||||
Not convinced? Please take a moment to reach out to us in the comments below to provide your feedback on this change so that we can help make the switch easier for you and everyone else.
|
||||
|
||||
## {% linkable_title The fine print... %}
|
||||
|
||||
In the process of switching chat platforms we have decided to create what we feel is a very fair set of rules for our chat community. As growth continues, these rules might change. Also be sure to check the [#welcome-rules][discord] channel for the most up-to-date rules for our chat server.
|
||||
|
||||
### {% linkable_title The rules... %}
|
||||
|
||||
#### {% linkable_title Rules: %}
|
||||
|
||||
Please carefully read through these rules **before engaging in conversation.**
|
||||
|
||||
1. **New members: Welcome!** Start by reading over the [FAQ]. Feel free to introduce yourself, as we are all friends here!
|
||||
|
||||
2. If you have a question, please check the [FAQ] and [relevant documentation][docs] before posting.
|
||||
|
||||
3. Do not insult, belittle, or abuse your fellow community members. Any reports of abuse will not be taken lightly and **will lead to a ban.**
|
||||
|
||||
4. Our moderators are kind enough to volunteer their time to help keep this a great community for everyone. Any inappropriate or unconstructive comments toward or about them **will result in a ban.**
|
||||
|
||||
5. [#devs][discord-devs] is for **development discussion only**. [#general][discord-general] is for common discussion, support questions, and lending help to others. Please use the appropriate channel as it pertains to the nature of your discussion.
|
||||
|
||||
6. Spam will not be tolerated, including but not limited to: self-promotion, flooding, codewalls (longer than 15 lines) and unapproved bots.
|
||||
|
||||
These rules are not to be interpreted how you like, there are no "loopholes." Anyone claiming not to be breaking the rules due to it "not being in the rules" will result in the according consequence. If you are unsure about something, please ask either myself (@dale3h) or the community.
|
||||
|
||||
If you have any issues with anything or anyone on the server please PM me (@dale3h) with any relevant details. **I cannot help anyone if I am unaware of any issues.**
|
||||
|
||||
#### {% linkable_title Infractions and Bans: %}
|
||||
|
||||
Bans **will be issued** after one serious infraction or failing to acknowledge warnings of minor infractions. This is non-negotiable.
|
||||
|
||||
Sincerely,
|
||||
|
||||
**Dale Higgs**<br>
|
||||
Community Leader, Home Assistant
|
||||
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
[discord-devs]: https://discord.gg/8X8DTH4
|
||||
[discord-general]: https://discord.gg/pywKZRT
|
||||
[FAQ]: https://home-assistant.io/faq/
|
||||
[docs]: https://home-assistant.io/docs/
|
||||
18
source/_posts/2017-07-05-hasspodcast-ep-3.markdown
Normal file
18
source/_posts/2017-07-05-hasspodcast-ep-3.markdown
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant Podcast #3"
|
||||
description: "Paulus joins us to talk about some stats and the release of 0.47 and Petar tells us all about his Floorplan project for Home Assistant"
|
||||
date: 2017-07-05 00:01:00 +0000
|
||||
date_formatted: "July 05, 2017"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Media
|
||||
og_image: /images/hasspodcast.jpg
|
||||
---
|
||||
|
||||
The third episode of the Home Assistant Podcast is out. Paulus joins to talk about some stats and the release of 0.47 and Petar tells all about his Floorplan project for Home Assistant.
|
||||
|
||||
[Listen online][episode]
|
||||
|
||||
[episode]: https://hasspodcast.io/ha003/
|
||||
@ -16,7 +16,7 @@ A checklist of things to do when you're adding a new component.
|
||||
1. Requirement version pinned: `REQUIREMENTS = ['phue==0.8.1']`
|
||||
2. If requirement hosted on GitHub:
|
||||
- Point at a zip archive of a release tag or commit SHA.
|
||||
- Add version found in zip-archive as hash to url.
|
||||
- Add version found in zip-archive as hash to URL.
|
||||
|
||||
```python
|
||||
REQUIREMENTS = [
|
||||
@ -36,5 +36,5 @@ REQUIREMENTS = [
|
||||
|
||||
### {% linkable_title Component/platform communication %}
|
||||
|
||||
1. If you need to share global data with platforms, use the dictionary `hass.data`.
|
||||
1. If you need to share global data with platforms, use the dictionary `hass.data`. `hass.data[DATA_XY]` while `XY` is the component is preferred over `hass.data[DOMAIN]`.
|
||||
2. If the component fetches data that causes related platform entities to update,
|
||||
|
||||
@ -16,7 +16,7 @@ A checklist of things to do when you're adding a new platform.
|
||||
1. Requirement version pinned: `REQUIREMENTS = ['phue==0.8.1']`
|
||||
2. If requirement hosted on GitHub:
|
||||
- Point at a zip archive of a release tag or commit SHA.
|
||||
- Add version found in zip-archive as hash to url.
|
||||
- Add version found in zip-archive as hash to URL.
|
||||
|
||||
```python
|
||||
REQUIREMENTS = [
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
layout: page
|
||||
title: "Credits"
|
||||
description: "Credits for the developers who contributed to Home Assistant."
|
||||
date: 2017-06-25 10:12:23 +0000
|
||||
date: 2017-07-04 06:40:12 +0000
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
@ -13,7 +13,7 @@ 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 "5474 total commits to the home-assistant organization, 3348 commits to home-assistant, 1132 commits to home-assistant.github.io, 545 commits to home-assistant-polymer, 244 commits to home-assistant-js, 110 commits to netdisco, 40 commits to home-assistant-js-websocket, 14 commits to hass-release, 12 commits to home-assistant-assets, 7 commits to example-custom-config, 7 commits to micropython-home-assistant, 3 commits to LabelBot, 2 commits to lambda-home-assistant-github, 2 commits to hassio, 2 commits to python-hassbian, 2 commits to issue-bot, 1 commit to hassio-addons-example, 1 commit to home-assistant-notebooks, 1 commit to home-assistant-iOS, 1 commit to hassio-addons")
|
||||
- [Paulus Schoutsen (@balloob)](https://github.com/balloob "5508 total commits to the home-assistant organization, 3364 commits to home-assistant, 1138 commits to home-assistant.github.io, 554 commits to home-assistant-polymer, 244 commits to home-assistant-js, 110 commits to netdisco, 40 commits to home-assistant-js-websocket, 16 commits to hass-release, 12 commits to home-assistant-assets, 7 commits to example-custom-config, 7 commits to micropython-home-assistant, 4 commits to LabelBot, 2 commits to lambda-home-assistant-github, 2 commits to issue-bot, 2 commits to python-hassbian, 2 commits to hassio, 1 commit to hassio-addons-example, 1 commit to hassio-addons, 1 commit to home-assistant-iOS, 1 commit to home-assistant-notebooks")
|
||||
|
||||
### {% linkable_title Contributors %}
|
||||
|
||||
@ -26,21 +26,22 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Aaron Polley (@xarnze)](https://github.com/xarnze "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Aaron Wolen (@aaronwolen)](https://github.com/aaronwolen "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Abhishek Anand (@aa755)](https://github.com/aa755 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [abmantis (@abmantis)](https://github.com/abmantis "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [Abílio Costa (@abmantis)](https://github.com/abmantis "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [Achilleas Pipinellis (@axilleas)](https://github.com/axilleas "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Adam (@SilvrrGIT)](https://github.com/SilvrrGIT "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io")
|
||||
- [Adam Allport (@AAllport)](https://github.com/AAllport "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Adam Baxter (@voltagex)](https://github.com/voltagex "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [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 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 "172 total commits to the home-assistant organization, 112 commits to home-assistant, 30 commits to home-assistant.github.io, 26 commits to home-assistant-polymer, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant")
|
||||
- [Adam Mills (@armills)](https://github.com/armills "175 total commits to the home-assistant organization, 113 commits to home-assistant, 30 commits to home-assistant.github.io, 28 commits to home-assistant-polymer, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant")
|
||||
- [ADeeds (@ADeeds)](https://github.com/ADeeds "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [AdithyanI (@AdithyanI)](https://github.com/AdithyanI "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Aditya Shevade (@adibis)](https://github.com/adibis "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Adrian Goins (@oskapt)](https://github.com/oskapt "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Adrien Ball (@adrienball)](https://github.com/adrienball "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Adrien Brault (@adrienbrault)](https://github.com/adrienbrault "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Adrián López (@adrianlzt)](https://github.com/adrianlzt "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Alan Bowman (@alanbowman)](https://github.com/alanbowman "5 total commits to the home-assistant organization, 4 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Alan Fischer (@alanfischer)](https://github.com/alanfischer "9 total commits to the home-assistant organization, 7 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Alan Fischer (@alanfischer)](https://github.com/alanfischer "10 total commits to the home-assistant organization, 8 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Albert Lee (@trisk)](https://github.com/trisk "13 total commits to the home-assistant organization, 8 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
- [Alberto Arias Maestro (@albertoarias)](https://github.com/albertoarias "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Aleksey Gureiev (@alg)](https://github.com/alg "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -59,12 +60,12 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Alexandre Perrin (@kAworu)](https://github.com/kAworu "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Alfie Day (@Azelphur)](https://github.com/Azelphur "12 total commits to the home-assistant organization, 12 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 "63 total commits to the home-assistant organization, 43 commits to home-assistant.github.io, 18 commits to home-assistant, 1 commit to hassio-addons, 1 commit to pi-gen")
|
||||
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "65 total commits to the home-assistant organization, 45 commits to home-assistant.github.io, 18 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")
|
||||
- [Anastasia A. (@Sacret)](https://github.com/Sacret "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Anders Gjendem (@agjendem)](https://github.com/agjendem "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "78 total commits to the home-assistant organization, 55 commits to home-assistant, 21 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "80 total commits to the home-assistant organization, 57 commits to home-assistant, 21 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 Ahrens (@DevvAndreas)](https://github.com/DevvAndreas "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Andreas Cambitsis (@acambitsis)](https://github.com/acambitsis "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -74,7 +75,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "240 total commits to the home-assistant organization, 122 commits to appdaemon, 85 commits to hadashboard, 25 commits to scenegen, 8 commits to home-assistant.github.io")
|
||||
- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "373 total commits to the home-assistant organization, 252 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 8 commits to home-assistant.github.io")
|
||||
- [Andrew LeCody (@aceat64)](https://github.com/aceat64 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Andrew Patton (@acusti)](https://github.com/acusti "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Andrew Starr-Bochicchio (@andrewsomething)](https://github.com/andrewsomething "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -82,7 +83,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 "126 total commits to the home-assistant organization, 70 commits to home-assistant, 32 commits to home-assistant-polymer, 24 commits to home-assistant.github.io")
|
||||
- [Andrey (@andrey-git)](https://github.com/andrey-git "129 total commits to the home-assistant organization, 71 commits to home-assistant, 34 commits to home-assistant-polymer, 24 commits to home-assistant.github.io")
|
||||
- [Andrey Petrov (@anpetrov)](https://github.com/anpetrov "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [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")
|
||||
- [Andy Castille (@Klikini)](https://github.com/Klikini "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
@ -105,11 +106,10 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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")
|
||||
- [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")
|
||||
- [Ashura (@CoalaJoe)](https://github.com/CoalaJoe "5 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Assaf Inbal (@shmuelzon)](https://github.com/shmuelzon "11 total commits to the home-assistant organization, 8 commits to homebridge-homeassistant, 3 commits to home-assistant")
|
||||
- [atorralba (@atorralba)](https://github.com/atorralba "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Aubin Paul (@outlyer)](https://github.com/outlyer "1 total commits to the home-assistant organization, 1 commit 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")
|
||||
- [Audun Ytterdal (@auduny)](https://github.com/auduny "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [aufano (@aufano)](https://github.com/aufano "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Austin (@trainman419)](https://github.com/trainman419 "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Avraham David Gelbfish (@adgelbfish)](https://github.com/adgelbfish "3 total commits to the home-assistant organization, 1 commit to hadashboard, 1 commit to pi-gen, 1 commit to home-assistant.github.io")
|
||||
@ -149,7 +149,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Brendan Berg (@captainnapalm)](https://github.com/captainnapalm "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Brendon Baumgartner (@bbrendon)](https://github.com/bbrendon "10 total commits to the home-assistant organization, 10 commits to home-assistant.github.io")
|
||||
- [Brent Hughes (@bah2830)](https://github.com/bah2830 "26 total commits to the home-assistant organization, 17 commits to home-assistant, 8 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Brent Saltzman (@brent20)](https://github.com/brent20 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Brent Saltzman (@brent20)](https://github.com/brent20 "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Brenton Zillins (@bzillins)](https://github.com/bzillins "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Brian Hopkins (@btotharye)](https://github.com/btotharye "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Brian J King (@brianjking)](https://github.com/brianjking "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
|
||||
@ -165,16 +165,15 @@ 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 "8 total commits to the home-assistant organization, 7 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [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 "84 total commits to the home-assistant organization, 76 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")
|
||||
- [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "84 total commits to the home-assistant organization, 76 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")
|
||||
- [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")
|
||||
- [Cedric Gatay (@CedricGatay)](https://github.com/CedricGatay "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [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")
|
||||
- [ChadCurvin (@ChadCurvin)](https://github.com/ChadCurvin "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [chanders (@chanders)](https://github.com/chanders "2 total commits to the home-assistant organization, 2 commits to hadashboard")
|
||||
- [CHAPELLE Quentin (@quentinchap)](https://github.com/quentinchap "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Charles Blonde (@CharlesBlonde)](https://github.com/CharlesBlonde "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Charles Blonde (@CharlesBlonde)](https://github.com/CharlesBlonde "10 total commits to the home-assistant organization, 6 commits to home-assistant, 4 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")
|
||||
@ -183,22 +182,18 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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")
|
||||
- [Chris LaRose (@cjlarose)](https://github.com/cjlarose "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Chris Monteiro (@cmonteiro128)](https://github.com/cmonteiro128 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Chris Mulder (@chrisvis)](https://github.com/chrisvis "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Chris R. Miller (@mysteriouspants)](https://github.com/mysteriouspants "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Chris Sims (@jcsims)](https://github.com/jcsims "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Chris Smolen (@smolz)](https://github.com/smolz "10 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 4 commits to appdaemon")
|
||||
- [Chris Thorn (@chris-thorn)](https://github.com/chris-thorn "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Christiaan Blom (@Deinara)](https://github.com/Deinara "8 total commits to the home-assistant organization, 7 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Christian Brædstrup (@LinuxChristian)](https://github.com/LinuxChristian "8 total commits to the home-assistant organization, 7 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Christiaan Blom (@Deinara)](https://github.com/Deinara "7 total commits to the home-assistant organization, 7 commits to home-assistant")
|
||||
- [Christian Brædstrup (@LinuxChristian)](https://github.com/LinuxChristian "7 total commits to the home-assistant organization, 7 commits to home-assistant")
|
||||
- [Christian Studer (@cstuder)](https://github.com/cstuder "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [ChristianKuehnel (@ChristianKuehnel)](https://github.com/ChristianKuehnel "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Christoph Wagner (@Christoph-Wagner)](https://github.com/Christoph-Wagner "5 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Christopher Viel (@Chris-V)](https://github.com/Chris-V "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [chrom3 (@chrom3)](https://github.com/chrom3 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [chrysn (@chrysn)](https://github.com/chrysn "65 total commits to the home-assistant organization, 65 commits to libcoap")
|
||||
- [Chun-wei Kuo (@Domon)](https://github.com/Domon "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [chz^3 (@chzchzchz)](https://github.com/chzchzchz "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Ciquattro (@CiquattroFPV)](https://github.com/CiquattroFPV "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [clach04 (@clach04)](https://github.com/clach04 "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
@ -273,8 +268,8 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Erik Eriksson (@molobrakos)](https://github.com/molobrakos "94 total commits to the home-assistant organization, 86 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 "29 total commits to the home-assistant organization, 17 commits to home-assistant, 12 commits to home-assistant.github.io")
|
||||
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "3816 total commits to the home-assistant organization, 2407 commits to home-assistant.github.io, 1248 commits to home-assistant, 59 commits to home-assistant-ansible, 23 commits to home-assistant-dev-helper, 22 commits to home-assistant-notebooks, 21 commits to home-assistant-cli, 17 commits to home-assistant-assets, 10 commits to home-assistant-polymer, 8 commits to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [Eugenio Panadero (@azogue)](https://github.com/azogue "38 total commits to the home-assistant organization, 24 commits to home-assistant, 14 commits to home-assistant.github.io")
|
||||
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "3845 total commits to the home-assistant organization, 2420 commits to home-assistant.github.io, 1264 commits to home-assistant, 59 commits to home-assistant-ansible, 23 commits to home-assistant-dev-helper, 22 commits to home-assistant-notebooks, 21 commits to home-assistant-cli, 17 commits to home-assistant-assets, 10 commits to home-assistant-polymer, 8 commits to netdisco, 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")
|
||||
- [Fabrizio Furnari (@fabfurnari)](https://github.com/fabfurnari "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [fakezeta (@fakezeta)](https://github.com/fakezeta "7 total commits to the home-assistant organization, 7 commits to home-assistant")
|
||||
@ -302,6 +297,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
- [Gert (@Gerto)](https://github.com/Gerto "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -375,7 +371,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Jan Pobořil (@iBobik)](https://github.com/iBobik "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Jan Wh (@janwh)](https://github.com/janwh "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Jan-Preben Mossin (@jpmossin)](https://github.com/jpmossin "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Janne Grunau (@jannau)](https://github.com/jannau "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Janne Grunau (@jannau)](https://github.com/jannau "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Jared Beckham (@jtbeckha)](https://github.com/jtbeckha "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Jared J. (@jjensn)](https://github.com/jjensn "2 total commits to the home-assistant organization, 1 commit to netdisco, 1 commit to home-assistant")
|
||||
- [Jason Carter (@JasonCarter80)](https://github.com/JasonCarter80 "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
@ -387,7 +383,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Jean-Michel Ruiz (@coolcow)](https://github.com/coolcow "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Jean-Philippe Bouillot (@Jypy)](https://github.com/Jypy "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [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 "17 total commits to the home-assistant organization, 14 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Jeff Wilson (@jawilson)](https://github.com/jawilson "19 total commits to the home-assistant organization, 14 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")
|
||||
- [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")
|
||||
@ -419,7 +415,7 @@ 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 Lindley (@jwl17330536)](https://github.com/jwl17330536 "18 total commits to the home-assistant organization, 11 commits to hadashboard, 6 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [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 "37 total commits to the home-assistant organization, 25 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to hadashboard")
|
||||
- [John Mihalic (@mezz64)](https://github.com/mezz64 "38 total commits to the home-assistant organization, 26 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to hadashboard")
|
||||
- [John Williams (@Jaidan)](https://github.com/Jaidan "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [johnappletree (@johnappletree)](https://github.com/johnappletree "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")
|
||||
@ -433,11 +429,12 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Jose Juan Montes (@jjmontesl)](https://github.com/jjmontesl "9 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Joseph Carter (@iKarith)](https://github.com/iKarith "8 total commits to the home-assistant organization, 8 commits to pi-gen")
|
||||
- [Joseph Piron (@eagleamon)](https://github.com/eagleamon "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Josh (@karlw00t)](https://github.com/karlw00t "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Josh Anderson (@andersonshatch)](https://github.com/andersonshatch "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to homebridge-homeassistant")
|
||||
- [Josh Nichols (@technicalpickles)](https://github.com/technicalpickles "24 total commits to the home-assistant organization, 15 commits to home-assistant, 9 commits to home-assistant.github.io")
|
||||
- [Josh Wright (@JshWright)](https://github.com/JshWright "29 total commits to the home-assistant organization, 21 commits to home-assistant, 8 commits to home-assistant.github.io")
|
||||
- [jpcomtois (@jpcomtois)](https://github.com/jpcomtois "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [JudgeDredd (@kentcalero)](https://github.com/kentcalero "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [JudgeDredd (@kentcalero)](https://github.com/kentcalero "7 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Juggels (@Juggels)](https://github.com/Juggels "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Julian Kahnert (@JulianKahnert)](https://github.com/JulianKahnert "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Julien Danjou (@jd)](https://github.com/jd "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -448,7 +445,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Kai (@luxus)](https://github.com/luxus "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Kane610 (@Kane610)](https://github.com/Kane610 "6 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Kane610 (@Kane610)](https://github.com/Kane610 "7 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Karen Goode (@kfgoode)](https://github.com/kfgoode "4 total commits to the home-assistant organization, 4 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")
|
||||
@ -479,6 +476,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [LightIsLife (@LightIsLife)](https://github.com/LightIsLife "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
- [Luar Roji (@cyberplant)](https://github.com/cyberplant "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [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")
|
||||
@ -504,7 +502,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Marc Plano-Lesay (@Kernald)](https://github.com/Kernald "11 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Marcel030nl (@Marcel030nl)](https://github.com/Marcel030nl "6 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "103 total commits to the home-assistant organization, 55 commits to home-assistant, 48 commits to home-assistant.github.io")
|
||||
- [Marcin Jaworski (@yawor)](https://github.com/yawor "10 total commits to the home-assistant organization, 10 commits to appdaemon")
|
||||
- [Marcin Jaworski (@yawor)](https://github.com/yawor "12 total commits to the home-assistant organization, 12 commits to appdaemon")
|
||||
- [Marco Sirabella (@mjsir911)](https://github.com/mjsir911 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [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")
|
||||
@ -542,6 +540,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Michael (@hartmms)](https://github.com/hartmms "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Michael Auchter (@auchter)](https://github.com/auchter "13 total commits to the home-assistant organization, 13 commits to home-assistant")
|
||||
- [Michael Buffington (@elbowdonkey)](https://github.com/elbowdonkey "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Michael Fester (@michaelfester)](https://github.com/michaelfester "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Michael Furtak (@mfurtak)](https://github.com/mfurtak "5 total commits to the home-assistant organization, 5 commits to issue-bot")
|
||||
- [Michael Gilbert (@Zyell)](https://github.com/Zyell "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Michael Heinemann (@heinemml)](https://github.com/heinemml "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -549,43 +548,39 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Michael Luggen (@l00mi)](https://github.com/l00mi "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Michael Requeny (@requenym)](https://github.com/requenym "14 total commits to the home-assistant organization, 14 commits to home-assistant.github.io")
|
||||
- [Michael Shim (@shimeez)](https://github.com/shimeez "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant")
|
||||
- [Michaël Arnauts (@michaelarnauts)](https://github.com/michaelarnauts "50 total commits to the home-assistant organization, 25 commits to home-assistant, 21 commits to home-assistant.github.io, 3 commits to home-assistant-polymer, 1 commit to netdisco")
|
||||
- [Michaël Arnauts (@michaelarnauts)](https://github.com/michaelarnauts "55 total commits to the home-assistant organization, 29 commits to home-assistant, 22 commits to home-assistant.github.io, 3 commits to home-assistant-polymer, 1 commit to netdisco")
|
||||
- [Michel Settembrino (@MS-Informatique)](https://github.com/MS-Informatique "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [micw (@micw)](https://github.com/micw "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Miha Lunar (@SmilyOrg)](https://github.com/SmilyOrg "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Mikayla Hutchinson (@mhutch)](https://github.com/mhutch "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Mike Hennessy (@henworth)](https://github.com/henworth "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Mike Megally (@cmsimike)](https://github.com/cmsimike "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Mike Megally (@cmsimike)](https://github.com/cmsimike "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [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")
|
||||
- [Milas Bowman (@milas)](https://github.com/milas "1 total commits to the home-assistant organization, 1 commit 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")
|
||||
- [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")
|
||||
- [mjj4791 (@mjj4791)](https://github.com/mjj4791 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [mjj4791 (@mjj4791)](https://github.com/mjj4791 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [mnestor (@mnestor)](https://github.com/mnestor "6 total commits to the home-assistant organization, 5 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [Molodax (@Molodax)](https://github.com/Molodax "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Moon Shot (@moonshot)](https://github.com/moonshot "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Morten Lied Johansen (@mortenlj)](https://github.com/mortenlj "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [moskovskiy82 (@moskovskiy82)](https://github.com/moskovskiy82 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [mountainsandcode (@mountainsandcode)](https://github.com/mountainsandcode "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [mtl010957 (@mtl010957)](https://github.com/mtl010957 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Myles Eftos (@madpilot)](https://github.com/madpilot "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Mārtiņš Grunskis (@grunskis)](https://github.com/grunskis "1 total commits to the home-assistant organization, 1 commit to netdisco")
|
||||
- [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 "14 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 6 commits to home-assistant, 2 commits to homebridge-homeassistant")
|
||||
- [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "14 total commits to the home-assistant organization, 6 commits to home-assistant, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant")
|
||||
- [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")
|
||||
- [Nemanja Stefanovic (@nemik)](https://github.com/nemik "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [neonbunny (@neonbunny)](https://github.com/neonbunny "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Ness (@Xx-Ness-xX)](https://github.com/Xx-Ness-xX "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Nicholas Sideras (@nsideras)](https://github.com/nsideras "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Ness (@Xx-Ness-xX)](https://github.com/Xx-Ness-xX "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Nick Sabinske (@quadportnick)](https://github.com/quadportnick "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Nick Touran (@partofthething)](https://github.com/partofthething "37 total commits to the home-assistant organization, 25 commits to home-assistant, 12 commits to home-assistant.github.io")
|
||||
- [Nick Vella (@nvella)](https://github.com/nvella "5 total commits to the home-assistant organization, 4 commits to home-assistant, 1 commit to homebridge-homeassistant")
|
||||
@ -594,7 +589,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Nicolas Martignoni (@martignoni)](https://github.com/martignoni "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Niklas (@niklaswa)](https://github.com/niklaswa "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Nikolas Beutler (@biacz)](https://github.com/biacz "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Nils Uliczka (@darookee)](https://github.com/darookee "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Nils Uliczka (@darookee)](https://github.com/darookee "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [NMA (@nma83)](https://github.com/nma83 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [nodomain (@nodomain)](https://github.com/nodomain "9 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant")
|
||||
- [Nolan Gilley (@nkgilley)](https://github.com/nkgilley "112 total commits to the home-assistant organization, 87 commits to home-assistant, 25 commits to home-assistant.github.io")
|
||||
@ -602,18 +597,17 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Nuno Sousa (@nunofgs)](https://github.com/nunofgs "7 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to homebridge-homeassistant")
|
||||
- [nunojusto (@nunojusto)](https://github.com/nunojusto "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [obgm (@obgm)](https://github.com/obgm "480 total commits to the home-assistant organization, 480 commits to libcoap")
|
||||
- [Olav Alexander Mjelde (@olavxxx)](https://github.com/olavxxx "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [OLD PROFILE! Go to /dennisreimann (@dbloete)](https://github.com/dbloete "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Ole-Kenneth (@olekenneth)](https://github.com/olekenneth "2 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant, 1 commit to home-assistant")
|
||||
- [Ole-Kenneth (@olekenneth)](https://github.com/olekenneth "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
|
||||
- [Oleksii Serdiuk (@leppa)](https://github.com/leppa "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Olimpiu Rob (@olimpiurob)](https://github.com/olimpiurob "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Oliv3rDog (@Oliv3rDog)](https://github.com/Oliv3rDog "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Oliver (@scarface-4711)](https://github.com/scarface-4711 "17 total commits to the home-assistant organization, 10 commits to home-assistant, 6 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Oliver van Porten (@mcdeck)](https://github.com/mcdeck "10 total commits to the home-assistant organization, 10 commits to home-assistant")
|
||||
- [Omar Usman (@omarusman)](https://github.com/omarusman "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Open Home Automation (@open-homeautomation)](https://github.com/open-homeautomation "23 total commits to the home-assistant organization, 19 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Open Home Automation (@open-homeautomation)](https://github.com/open-homeautomation "29 total commits to the home-assistant organization, 21 commits to home-assistant, 8 commits to home-assistant.github.io")
|
||||
- [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 "1510 total commits to the home-assistant organization, 574 commits to hassio, 363 commits to home-assistant, 208 commits to hassio-addons, 175 commits to hassio-build, 174 commits to home-assistant.github.io, 14 commits to hassio-addons-example, 1 commit to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "1554 total commits to the home-assistant organization, 588 commits to hassio, 366 commits to home-assistant, 223 commits to hassio-addons, 181 commits to home-assistant.github.io, 180 commits to hassio-build, 14 commits to hassio-addons-example, 1 commit to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [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 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
@ -624,7 +618,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Pedro Navarro (@pedronavf)](https://github.com/pedronavf "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Pedro Pombeiro (@PombeirP)](https://github.com/PombeirP "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Per Osbäck (@perosb)](https://github.com/perosb "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [Per Sandström (@persandstrom)](https://github.com/persandstrom "119 total commits to the home-assistant organization, 95 commits to home-assistant, 12 commits to home-assistant-polymer, 12 commits to home-assistant.github.io")
|
||||
- [Per Sandström (@persandstrom)](https://github.com/persandstrom "122 total commits to the home-assistant organization, 98 commits to home-assistant, 12 commits to home-assistant-polymer, 12 commits to home-assistant.github.io")
|
||||
- [Pete Peterson (@petey)](https://github.com/petey "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [PetePriority (@PetePriority)](https://github.com/PetePriority "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [petkov (@petkov)](https://github.com/petkov "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -632,12 +626,12 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [pezinek (@pezinek)](https://github.com/pezinek "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Phil (@godloth)](https://github.com/godloth "10 total commits to the home-assistant organization, 10 commits to home-assistant.github.io")
|
||||
- [Phil Haack (@Haacked)](https://github.com/Haacked "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Phil Hawthorne (@philhawthorne)](https://github.com/philhawthorne "11 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Phil Hawthorne (@philhawthorne)](https://github.com/philhawthorne "12 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 5 commits to home-assistant")
|
||||
- [Phileep (@Phileep)](https://github.com/Phileep "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Philip Hofstetter (@pilif)](https://github.com/pilif "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Philip Lundrigan (@philipbl)](https://github.com/philipbl "65 total commits to the home-assistant organization, 56 commits to home-assistant, 9 commits to home-assistant.github.io")
|
||||
- [Philipp Schmitt (@pschmitt)](https://github.com/pschmitt "20 total commits to the home-assistant organization, 13 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [PhracturedBlue (@PhracturedBlue)](https://github.com/PhracturedBlue "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [PhracturedBlue (@PhracturedBlue)](https://github.com/PhracturedBlue "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Pierre Ståhl (@postlund)](https://github.com/postlund "26 total commits to the home-assistant organization, 18 commits to home-assistant, 4 commits to netdisco, 4 commits to home-assistant.github.io")
|
||||
- [pinksocks (@pinksocks)](https://github.com/pinksocks "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Piratonym (@Piratonym)](https://github.com/Piratonym "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -647,6 +641,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [rbflurry (@rbflurry)](https://github.com/rbflurry "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [RBHR (@rbhr)](https://github.com/rbhr "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Reed Riley (@reedriley)](https://github.com/reedriley "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Rene Tode (@ReneTode)](https://github.com/ReneTode "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [René Kliment (@renekliment)](https://github.com/renekliment "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Rev Michael Greb (@mikegrb)](https://github.com/mikegrb "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [rhooper (@rhooper)](https://github.com/rhooper "30 total commits to the home-assistant organization, 25 commits to home-assistant, 3 commits to home-assistant.github.io, 2 commits to hadashboard")
|
||||
@ -657,8 +652,9 @@ 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 "1189 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, 78 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 home-assistant-js, 3 commits to scenegen, 3 commits to appdaemon, 3 commits to home-assistant-js-websocket, 3 commits to home-assistant-cli, 3 commits to hadashboard, 3 commits to organization, 3 commits to hassbot, 2 commits to LabelBot, 2 commits to home-assistant-assets, 2 commits to home-assistant-dev-helper, 2 commits to lambda-home-assistant-github, 2 commits to fabric-home-assistant, 2 commits to micropython-home-assistant, 2 commits to home-assistant-ansible, 2 commits to home-assistant-notebooks")
|
||||
- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1189 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, 78 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 hassbot, 3 commits to hadashboard, 3 commits to home-assistant-js-websocket, 3 commits to home-assistant-js, 3 commits to appdaemon, 3 commits to home-assistant-cli, 3 commits to organization, 2 commits to micropython-home-assistant, 2 commits to home-assistant-notebooks, 2 commits to home-assistant-dev-helper, 2 commits to home-assistant-ansible, 2 commits to lambda-home-assistant-github, 2 commits to LabelBot, 2 commits to fabric-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 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Robin Laurén (@llauren)](https://github.com/llauren "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [Roddie Hasan (@eiddor)](https://github.com/eiddor "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Roi Dayan (@roidayan)](https://github.com/roidayan "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
@ -674,7 +670,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [rubund (@rubund)](https://github.com/rubund "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [RunOnGitHub (@RunOnGitHub)](https://github.com/RunOnGitHub "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Ruslan Kiianchuk (@zoresvit)](https://github.com/zoresvit "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Russell Cloran (@rcloran)](https://github.com/rcloran "7 total commits to the home-assistant organization, 4 commits to homebridge-homeassistant, 3 commits to home-assistant")
|
||||
- [Russell Cloran (@rcloran)](https://github.com/rcloran "8 total commits to the home-assistant organization, 4 commits to homebridge-homeassistant, 4 commits to home-assistant")
|
||||
- [Ryan Borstelmann (@SlothCroissant)](https://github.com/SlothCroissant "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Ryan Bray (@rbray89)](https://github.com/rbray89 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Ryan Daigle (@rwdaigle)](https://github.com/rwdaigle "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
@ -701,6 +697,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Sebastian von Minckwitz (@teodoc)](https://github.com/teodoc "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [sfam (@sfam)](https://github.com/sfam "65 total commits to the home-assistant organization, 58 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-polymer")
|
||||
- [Shawna (@Nightarrow85)](https://github.com/Nightarrow85 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Shiny (@Br3nda)](https://github.com/Br3nda "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [siebert (@siebert)](https://github.com/siebert "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Simon Elsbrock (@else)](https://github.com/else "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Simon Szustkowski (@simonszu)](https://github.com/simonszu "7 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
@ -716,9 +713,9 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Stuart Mumford (@Cadair)](https://github.com/Cadair "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Stéphane Bidoul (ACSONE) (@sbidoul)](https://github.com/sbidoul "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [System Tester (@systemtester)](https://github.com/systemtester "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Sytone (@sytone)](https://github.com/sytone "10 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant-cli, 2 commits to home-assistant")
|
||||
- [Sytone (@sytone)](https://github.com/sytone "11 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant-cli, 2 commits to home-assistant, 1 commit to hassio-build")
|
||||
- [Sören Oldag (@soldag)](https://github.com/soldag "12 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 5 commits to home-assistant")
|
||||
- [Teagan Glenn (@Teagan42)](https://github.com/Teagan42 "58 total commits to the home-assistant organization, 49 commits to home-assistant, 8 commits to home-assistant.github.io, 1 commit to home-assistant-js")
|
||||
- [Teagan Glenn (@Teagan42)](https://github.com/Teagan42 "59 total commits to the home-assistant organization, 49 commits to home-assistant, 9 commits to home-assistant.github.io, 1 commit to home-assistant-js")
|
||||
- [techtrails (@techtrails)](https://github.com/techtrails "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
@ -756,28 +753,31 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Trevor (@tboyce021)](https://github.com/tboyce021 "10 total commits to the home-assistant organization, 7 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Trey Hunner (@treyhunner)](https://github.com/treyhunner "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [trollkarlen (@trollkarlen)](https://github.com/trollkarlen "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [Tsvi Mostovicz (@tsvi)](https://github.com/tsvi "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Tsvi Mostovicz (@tsvi)](https://github.com/tsvi "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Tyler Crumpton (@tylercrumpton)](https://github.com/tylercrumpton "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Tyler Page (@iamtpage)](https://github.com/iamtpage "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Tõnis Tobre (@tobre6)](https://github.com/tobre6 "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
|
||||
- [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")
|
||||
- [viswa-swami (@viswa-swami)](https://github.com/viswa-swami "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [viswa-swami (@viswa-swami)](https://github.com/viswa-swami "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [Vlad Korniev (@vkorn)](https://github.com/vkorn "1 total commits to the home-assistant organization, 1 commit to hassio-build")
|
||||
- [vllungu (@vllungu)](https://github.com/vllungu "3 total commits to the home-assistant organization, 3 commits to libcoap")
|
||||
- [vrs01 (@vrs01)](https://github.com/vrs01 "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [vrs01 (@vrs01)](https://github.com/vrs01 "13 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 5 commits to appdaemon")
|
||||
- [Wagner Sartori Junior (@trunet)](https://github.com/trunet "1 total commits to the home-assistant organization, 1 commit to netdisco")
|
||||
- [Wilco Land (@Wilco89)](https://github.com/Wilco89 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Will Heid (@bassclarinetl2)](https://github.com/bassclarinetl2 "14 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 1 commit to fabric-home-assistant")
|
||||
- [Will Hughes (@insertjokehere)](https://github.com/insertjokehere "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Will W. (@tiktok7)](https://github.com/tiktok7 "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Willems Davy (@joyrider3774)](https://github.com/joyrider3774 "7 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "63 total commits to the home-assistant organization, 45 commits to home-assistant, 18 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
- [Wolfgang Malgadey (@wmalgadey)](https://github.com/wmalgadey "3 total commits to the home-assistant organization, 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 "77 total commits to the home-assistant organization, 77 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")
|
||||
- [Yannick POLLART (@ypollart)](https://github.com/ypollart "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Yannick Simard (@TheRaven)](https://github.com/TheRaven "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Yasin Soliman (@yasinS)](https://github.com/yasinS "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Yum (@goofz)](https://github.com/goofz "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -790,4 +790,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 Sunday, June 25th 2017, 10:12:23 am UTC.</i>
|
||||
<i>This page was last updated Tuesday, July 4th 2017, 6:40:12 am UTC.</i>
|
||||
|
||||
@ -124,4 +124,13 @@ After a start or a restart of Home Assistant the component will be visible in th
|
||||
<img src='/images/screenshots/create-component01.png' />
|
||||
</p>
|
||||
|
||||
In order to expose attributes of your component, you will need to define a method called `state_attributes` which will return a dictionary of attributes:
|
||||
|
||||
```
|
||||
@property
|
||||
def state_attributes(self):
|
||||
"""Return the attributes of the entity."""
|
||||
return self._attributes
|
||||
```
|
||||
|
||||
To get your component included in the Home Assistant releases, follow the steps described in the [Submitting improvements](https://home-assistant.io/developers/#submitting-improvements) section. Basically you only need to move your component in the `homeassistant/component/` directory of your fork and create a Pull Request.
|
||||
|
||||
@ -9,10 +9,18 @@ sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
There are a bunch of online services which can help you if you are developing for Home Assistant or maintaining components. Some of these are directly connected to Pull Requests and the repositories, while others publish details and updates in our [Gitter.im](https://gitter.im/home-assistant/home-assistant/devs) chatroom.
|
||||
There are a bunch of online services which can help you if you are developing for Home Assistant or maintaining components. Some of these are directly connected to Pull Requests and the repositories, while others publish details and updates on our [Discord chat server][discord-devs].
|
||||
|
||||
- [Coveralls](https://coveralls.io/github/home-assistant/home-assistant)
|
||||
- [Travis CI](https://travis-ci.org/home-assistant/home-assistant)
|
||||
- [gemnasium](https://gemnasium.com/github.com/home-assistant/home-assistant)
|
||||
- [Requires.io](https://requires.io/github/home-assistant/home-assistant/requirements/?branch=dev)
|
||||
- [Pivotal Tracker](https://www.pivotaltracker.com/n/projects/1250084)
|
||||
- [Coveralls][coveralls]
|
||||
- [Travis CI][travis-ci]
|
||||
- [gemnasium][gemnasium]
|
||||
- [Requires.io][requires-io]
|
||||
- [Pivotal Tracker][pivotal]
|
||||
|
||||
[coveralls]: https://coveralls.io/github/home-assistant/home-assistant
|
||||
[travis-ci]: https://travis-ci.org/home-assistant/home-assistant
|
||||
[gemnasium]: https://gemnasium.com/github.com/home-assistant/home-assistant
|
||||
[requires-io]: https://requires.io/github/home-assistant/home-assistant/requirements/?branch=dev
|
||||
[pivotal]: https://www.pivotaltracker.com/n/projects/1250084
|
||||
|
||||
[discord-devs]: https://discord.gg/8X8DTH4
|
||||
|
||||
@ -17,4 +17,4 @@ To reload your configuration, go to **Configuration** in your side panel, and ch
|
||||
<img src='/images/screenshots/configuration-validation.png' />
|
||||
</p>
|
||||
|
||||
Now that you saw a glimpse of what is possible, take a look at the [documentation](/docs/), ask your questions in our [forum](https://community.home-assistant.io/), join us for a [chat](https://gitter.im/home-assistant/home-assistant), or report your [issues](https://github.com/home-assistant/home-assistant/issues).
|
||||
Now that you saw a glimpse of what is possible, take a look at the [documentation](/docs/), ask your questions in our [forum](https://community.home-assistant.io/), join us for a [chat](https://discord.gg/c5DvZ4e), or report your [issues](https://github.com/home-assistant/home-assistant/issues).
|
||||
|
||||
@ -55,6 +55,14 @@ If you don't use local build on device or our build script, make sure that the D
|
||||
LABEL io.hass.version="VERSION" io.hass.type="addon" io.hass.arch="armhf|aarch64|i386|amd64"
|
||||
```
|
||||
|
||||
It is possible to use own base image with follow schema:
|
||||
```
|
||||
#amd64:FROM...
|
||||
#i386:FROM...
|
||||
#armhf:FROM...
|
||||
#aarch64:FROM...
|
||||
```
|
||||
|
||||
## {% linkable_title Add-on config %}
|
||||
|
||||
The config for an add-on is stored in `config.json`.
|
||||
@ -98,6 +106,7 @@ The config for an add-on is stored in `config.json`.
|
||||
| options | yes | Default options value of the add-on
|
||||
| schema | yes | Schema for options value of the add-on. It can be `False` to disable schema validation and use custom options.
|
||||
| image | no | For use dockerhub.
|
||||
| timeout | no | Default 10 (second). The timeout to wait until the docker is done or will be killed.
|
||||
| tmpfs | no | Mount a tmpfs file system in `/tmpfs`. Valide format for this option is : `size=XXXu,uid=N,rw`. Size is mandatory, valid units (`u`) are `k`, `m` and `g` and `XXX` has to be replaced by a number. `uid=N` (with `N` the uid number) and `rw` are optional.
|
||||
|
||||
### {% linkable_title Options / Schema %}
|
||||
@ -136,3 +145,4 @@ We support:
|
||||
- float
|
||||
- email
|
||||
- url
|
||||
- port
|
||||
|
||||
@ -11,12 +11,14 @@ footer: true
|
||||
|
||||
There are two different ways of publishing add-ons. One is to publish pre-build containers to Docker Hub and the other option is to have users build the containers locally on their Hass.io instance.
|
||||
|
||||
**Pre-build containers**<br>
|
||||
#### {% linkable_title Pre-build containers %}
|
||||
|
||||
With pre-build containers, the developer is responsible for building the images for each architecture on their machine and push the results out to Docker Hub. This has a lot of advantages for the user. As a user it will only have to download the final container and be up and running once the download finishes. This makes the installation process fast and almost no chance of failure. This is the preferred method.
|
||||
|
||||
We have automated the process of building and publishing add-ons. See below for the instructions.
|
||||
|
||||
**Locally build containers**<br>
|
||||
#### {% linkable_title Locally build containers %}
|
||||
|
||||
Starting Hass.io 0.26, it is possible to distribute add-ons that will be built on the users machine. The advantage is that as a developer it is easy to test an idea and see if people are interested in your add-ons. This method includes installing and potentially compiling code. This means that installing such an add-on is slow and adds more wear and tear to users SD card/hard drive than the above mentioned pre-build solution. It also has a higher chance of failure if one of the dependencies of the container has changed or is no longer available.
|
||||
|
||||
Use this option when you are playing with add-ons and seeing if someone is interested in your work. Once you're an established repository, please migrate to pushing builds to Docker Hub as it greatly improves the user experience. In the future we will mark locally built add-ons in the add-on store to warn users.
|
||||
|
||||
@ -15,7 +15,7 @@ Add-ons repository can contain one or more add-ons. Each add-on is stored in it'
|
||||
|
||||
## Installing a repository
|
||||
|
||||
A user can add a repository by going to the Hass.io panel in Home Assistant, clicking on the store icon in the top right, copy/paste the url of your repostory into the repository textarea and click on "Save".
|
||||
A user can add a repository by going to the Hass.io panel in Home Assistant, clicking on the store icon in the top right, copy/paste the URL of your repostory into the repository textarea and click on "Save".
|
||||
|
||||
## Repository configuration
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ Hass.io images are available for all available Raspberry Pi and intel nuc platfo
|
||||
- [Intel Nuc][nuc]
|
||||
- Flash the downloaded image to an SD card using [Etcher].
|
||||
- Optional - Setup the WiFi or static ip: On the SD-card, edit the `system-connections/resin-sample` file and follow the [ResinOS howto][resinos-network].
|
||||
- Insert SD card to Raspberry Pi and turn it on. On first boot, it downloads the latest version of Home Assistant which can take some time.
|
||||
- Insert SD card to Raspberry Pi and turn it on. On first boot, it downloads the latest version of Home Assistant which takes ~20 minutes (slower/faster depending on the platform).
|
||||
- You will be able to reach your installation at [http://hassio.local:8123][local].
|
||||
|
||||
<p class='note'>
|
||||
|
||||
@ -13,11 +13,11 @@ There are various ways to get in touch with the Home Assistant community. It doe
|
||||
|
||||
### {% linkable_title Communication channels %}
|
||||
|
||||
- [Forum](https://community.home-assistant.io/)
|
||||
- [Gitter Chatroom](https://gitter.im/home-assistant/home-assistant) for general Home Assistant discussions and questions.
|
||||
- Follow us on [Twitter](https://twitter.com/home_assistant), use [@home_assistant](https://twitter.com/home_assistant)
|
||||
- Join the [Google+ community](https://plus.google.com/u/0/b/110560654828510104551/communities/106562234893511202708)
|
||||
- Join the [Reddit subreddit](https://reddit.com/r/homeassistant) in [/r/homeassistant](https://reddit.com/r/homeassistant)
|
||||
- [Forum][forum]
|
||||
- [Discord Chat Server][discord] for general Home Assistant discussions and questions.
|
||||
- Follow us on [Twitter][twitter], use [@home_assistant][twitter]
|
||||
- Join the [Google+ community][google-plus]
|
||||
- Join the [Reddit subreddit][reddit] in [/r/homeassistant][reddit]
|
||||
|
||||
### {% linkable_title Bugs, Feature requests, and alike %}
|
||||
|
||||
@ -65,3 +65,9 @@ There is not currently a site search for Home-Assistant.io but it's in the works
|
||||
### {% linkable_title Roadmap %}
|
||||
|
||||
There is no explicit roadmap available but the public [tracker](https://www.pivotaltracker.com/n/projects/1250084) can give you some insight into what is going on.
|
||||
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[twitter]: https://twitter.com/home_assistant
|
||||
[google-plus]: https://plus.google.com/u/0/b/110560654828510104551/communities/106562234893511202708
|
||||
[reddit]: https://reddit.com/r/homeassistant
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
@ -33,7 +33,7 @@ This sections just contains some random numbers of the Home Assistant eco-system
|
||||
|
||||
| Description | 2015 | 2016 |
|
||||
|---|---|
|
||||
| [Gitter.io](https://gitter.im/home-assistant/home-assistant) | 334 | 2367 |
|
||||
| [Gitter.io](https://discord.gg/c5DvZ4e) | 334 | 2367 |
|
||||
| [Forum posts](https://community.home-assistant.io/) | 352 | 33004 |
|
||||
| [Forum topics](https://community.home-assistant.io/) | 83 | 4863 |
|
||||
| [Forum members](https://community.home-assistant.io/) | 92 | 3931 |
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 74 KiB |
BIN
source/images/hadashboard/dash1.png
Executable file
BIN
source/images/hadashboard/dash1.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 83 KiB |
BIN
source/images/hadashboard/dash2.png
Executable file
BIN
source/images/hadashboard/dash2.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 483 KiB |
BIN
source/images/hadashboard/dash3.png
Executable file
BIN
source/images/hadashboard/dash3.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 605 KiB |
BIN
source/images/hadashboard/dash4.png
Executable file
BIN
source/images/hadashboard/dash4.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 179 KiB |
BIN
source/images/hadashboard/dash5.png
Executable file
BIN
source/images/hadashboard/dash5.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 401 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user