@ -139,12 +139,12 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 55
|
||||
current_patch_version: 1
|
||||
date_released: 2017-10-15
|
||||
current_minor_version: 56
|
||||
current_patch_version: 0
|
||||
date_released: 2017-10-21
|
||||
|
||||
# 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: "#release-0551---october-15"
|
||||
#patch_version_notes: "#release-0551---october-15"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
39
sass/custom/_print.scss
Normal file
@ -0,0 +1,39 @@
|
||||
@media print {
|
||||
|
||||
/* General Overrides */
|
||||
header div.grid__item nav {
|
||||
display: none;
|
||||
}
|
||||
aside#sidebar {
|
||||
display: none;
|
||||
}
|
||||
.grid__item {
|
||||
display: block;
|
||||
width: 100%;
|
||||
}
|
||||
|
||||
/* Components List */
|
||||
div.filter-button-group {
|
||||
display: none;
|
||||
}
|
||||
.hass-option-cards.show-items {
|
||||
display: block;
|
||||
}
|
||||
.hass-option-cards.show-items a.option-card {
|
||||
display: block;
|
||||
opacity: 1;
|
||||
width: 100%;
|
||||
height: auto;
|
||||
min-height: 80px;
|
||||
margin-bottom: 8px;
|
||||
}
|
||||
.hass-option-cards.show-items a.option-card .img-container {
|
||||
float: left;
|
||||
width: 33%;
|
||||
text-align: center;
|
||||
}
|
||||
.hass-option-cards.show-items a.option-card div.title {
|
||||
height: 1.5em;
|
||||
margin-top: 8px;
|
||||
}
|
||||
}
|
@ -2,3 +2,4 @@
|
||||
@import 'custom/paulus';
|
||||
@import 'custom/component_page';
|
||||
@import 'custom/syntax';
|
||||
@import 'custom/print';
|
@ -26,6 +26,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Lock](/components/cover.abode/): Reports on `Door Locks` and can be used to lock and unlock the door.
|
||||
- [Light](/components/light.abode/): Reports on `Dimmer` lights and can be used to dim, change color, or turn the light on and off.
|
||||
- [Switch](/components/switch.abode/): Reports on `Power Switch` devices and can be used to turn the power switch on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them.
|
||||
- [Sensor](/components/sensor.abode/): Reports on `Temperature`, `Humidity`, and `Light` sensors.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
|
31
source/_components/alarm_control_panel.arlo.markdown
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Arlo Control Panel"
|
||||
description: "Instructions how to setup the Netgear Arlo Base Stations as a control panel within Home Assistant."
|
||||
date: 2017-10-05 17:45
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: arlo.png
|
||||
ha_category: Alarm
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
The `arlo` control panel platform allows you to control your [Arlo](https://arlo.netgear.com/) base stations.
|
||||
|
||||
To get your [Arlo](https://arlo.netgear.com/) base stations working within Home Assistant, please follow the instructions for the general [Arlo component](/components/arlo).
|
||||
|
||||
Once you have enabled the [Arlo component](/components/arlo), add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
alarm_control_panel:
|
||||
- platform: arlo
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **home_mode_name**: (*Optional*): Arlo base station does not have a built-in home mode. You can map one of your custom modes to home assistant's home mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app.
|
@ -43,7 +43,7 @@ You can change this, however, using the following procedure. This is a more adva
|
||||
|
||||
1. Log in into your alarm system's control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
|
||||
2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. Also, update the port number 85 or to anything you like. The provided software that you will set up in the next steps runs on port 85 by default. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'.
|
||||
3. On your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, armhome) as well as trigger the alarm in all ways possible to get 100% coverage. **Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
|
||||
3. On your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, armhome) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage. **Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
|
||||
4. Once you have the codes, update your `configuration.yaml`:
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -61,26 +61,30 @@ alarm_control_panel:
|
||||
triggered: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
|
||||
ignore: XXXXXXXXXXXXXXXX
|
||||
```
|
||||
Note that for triggered, arm and disarm multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as ignore (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, armhome, triggered) even when system checks occur.
|
||||
|
||||
5. Start the `egardiaserver.py` script on boot of your Home Assistant machine, for example by using systemd. To use this method, create a shell script named `egardiaserver.sh` that contains the following:
|
||||
Note that for triggered, arm and disarm multiple codes can be entered since each sensor triggers with a different code and each user of the system has its own arm and disarm codes. Also note that your system will do regular system checks which will be reported as well. Since Home Assistant provides no way of handling them properly, you can enter those codes as ignore (again, multiple codes can be used here). The egardia component will ignore these codes and continue returning the old status if it receives any of the codes that are listed as ignore. This is useful for example when you have armed your alarm at night: normally a system check will occur at least once during the night and if that code is not specified anywhere Home Assistant will set the status of the alarm to its default, which is unarmed. This is in fact wrong. Listing the code as ignore changes this behavior and Home Assistant will continue to show the status the alarm is in (disarm, arm, armhome, triggered) even when system checks occur.
|
||||
|
||||
5. Start the `egardiaserver.py` script on boot of your Home Assistant machine, for example by using `systemctl` by `systemd`. To use this method, create a shell script named `egardiaserver.sh` that contains something like the following:
|
||||
|
||||
```bash
|
||||
source /srv/homeassistant/homeassistant_venv/bin/activate
|
||||
python3 /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pythonegardia/egardiaserver.py -host [YOURHOST] -password '[YOURPASSWORD]' -ssl True > /tmp/egardiaserver.log 2>&1
|
||||
$ source /srv/homeassistant/bin/activate
|
||||
$ python3 /srv/homeassistant/lib/python3.5/site-packages/pythonegardia/egardiaserver.py -host [YOURHOST] -password '[YOURPASSWORD]' -ssl True > /tmp/egardiaserver.log 2>&1
|
||||
```
|
||||
|
||||
Mark it as executable (`$ chmod +x`) and run `sudo nano /lib/systemd/system/egardiaserver.service`. Enter the following into the `egardiaserver.service` file:
|
||||
|
||||
```bash
|
||||
[Unit]
|
||||
Description=Egardia Server Service
|
||||
|
||||
[Service]
|
||||
ExecStart=/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pythonegardia/egardiaserver.sh
|
||||
ExecStart=/bin/bash /srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/pythonegardia/egardiaserver.sh
|
||||
StandardOutput=journal+console
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
Alias=egardiaserver.service
|
||||
```
|
||||
|
||||
Save and then run `sudo systemctl enable egardiaserver.service` and `sudo systemctl start egardiaserver.service`.
|
||||
6. Test your setup and enjoy. The component will update if the alarm status changes, including triggers. You can use this to build your own automations and send notifications as you wish.
|
||||
|
@ -21,12 +21,14 @@ The component will accept the following commands from your Alarm Panel via the `
|
||||
- `DISARM`
|
||||
- `ARM_HOME`
|
||||
- `ARM_AWAY`
|
||||
- `ARM_NIGHT`
|
||||
|
||||
When the state of the manual alarm changes, Home Assistant will publish one of the following states to the `state_topic`:
|
||||
|
||||
- 'disarmed'
|
||||
- 'armed_home'
|
||||
- 'armed_away'
|
||||
- 'armed_night'
|
||||
- 'pending'
|
||||
- 'triggered'
|
||||
|
||||
@ -47,6 +49,8 @@ All configuration variables from the base manual alarm platform are available:
|
||||
- **pending_time** (*Optional*): The time in seconds of the pending time before arming the alarm. Default is 60 seconds.
|
||||
- **trigger_time** (*Optional*): The time in seconds of the trigger time in which the alarm is firing. Default is 120 seconds.
|
||||
- **disarm_after_trigger** (*Optional*): If true, the alarm will automatically disarm after it has been triggered instead of returning to the previous state.
|
||||
- **armed_home|armed_away|armed_night|triggered** (*Optional*): State specific settings
|
||||
- **pending_time**: State specific pending time override.
|
||||
|
||||
Additionally, the following MQTT configuration variables are also available:
|
||||
|
||||
@ -56,6 +60,23 @@ Additionally, the following MQTT configuration variables are also available:
|
||||
- **payload_disarm** (*Optional*): The payload to disarm this Alarm Panel. Default is "DISARM".
|
||||
- **payload_arm_home** (*Optional*): The payload to set armed-home mode on this Alarm Panel. Default is "ARM_HOME".
|
||||
- **payload_arm_away** (*Optional*): The payload to set armed-away mode on this Alarm Panel. Default is "ARM_AWAY".
|
||||
- **payload_arm_night** (*Optional*): The payload to set armed-night mode on this Alarm Panel. Default is "ARM_NIGHT".
|
||||
|
||||
In the config example below, armed_home state will have no pending time and triggered state will have a pending time of 20 seconds whereas armed_away state will have a default pending time of 30 seconds.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
alarm_control_panel:
|
||||
- platform: manual_mqtt
|
||||
state_topic: home/alarm
|
||||
command_topic: home/alarm/set
|
||||
pending_time: 30
|
||||
armed_home:
|
||||
pending_time: 0
|
||||
triggered:
|
||||
pending_time: 20
|
||||
trigger_time: 4
|
||||
```
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
@ -70,11 +91,13 @@ To change the state of the alarm, publish one of the following messages to the `
|
||||
- `DISARM`
|
||||
- `ARM_HOME`
|
||||
- `ARM_AWAY`
|
||||
- `ARM_NIGHT`
|
||||
|
||||
To receive state updates from HA, subscribe to the `state_topic`. Home Assistant will publish a new message whenever the state changes:
|
||||
|
||||
- `disarmed`
|
||||
- `armed_home`
|
||||
- `armed_away`
|
||||
- `armed_night`
|
||||
- `pending`
|
||||
- `triggered`
|
||||
|
@ -31,7 +31,7 @@ Configuration variables:
|
||||
|
||||
It is recommended to create a dedicated user on Arlo website to be used within Home Assistant and then share your Arlo cameras.
|
||||
|
||||
Finish its configuration by visiting the [Arlo sensor page](/components/sensor.arlo/) or [Arlo camera page](/components/camera.arlo/).
|
||||
Finish its configuration by visiting the [Arlo sensor page](/components/sensor.arlo/) or [Arlo camera page](/components/camera.arlo/) or [Arlo control panel page](/components/alarm_control_panel.arlo/).
|
||||
|
||||
The Arlo component also provides a service to enable/disable the motion detection sensor. The example below enables the motion detection every time the Home Assistant service starts.
|
||||
|
||||
|
@ -36,3 +36,22 @@ Configuration variables:
|
||||
- **name** (*Required*): Name of the sensor.
|
||||
- **slave** (*Required*): The number of the slave (Optional for TCP and UDP Modbus).
|
||||
- **coil** (*Required*): Coil number.
|
||||
|
||||
It's possible to change the default 30 seconds scan interval for the sensor updates as shown in the [Platform options](/docs/configuration/platform_options/#scan-interval) documentation.
|
||||
|
||||
### {% linkable_title Full example %}
|
||||
|
||||
Example a sensor with a 10 seconds scan interval:
|
||||
|
||||
```yaml
|
||||
binary_sensor:
|
||||
- platform: modbus
|
||||
scan_interval: 10
|
||||
coils:
|
||||
- name: Sensor1
|
||||
slave: 1
|
||||
coil: 100
|
||||
- name: Sensor2
|
||||
slave: 1
|
||||
coil: 110
|
||||
```
|
||||
|
@ -27,8 +27,7 @@ If you want to select a specific sensor, set discovery to False for [netatmo](/c
|
||||
binary_sensor:
|
||||
platform: netatmo
|
||||
home: home_name
|
||||
timeout: 15
|
||||
offset: 90
|
||||
timeout: 90
|
||||
cameras:
|
||||
- camera_name1
|
||||
welcome_sensors:
|
||||
@ -45,8 +44,7 @@ binary_sensor:
|
||||
Configuration variables:
|
||||
|
||||
- **home** (*Optional*): Will use the cameras of this home only.
|
||||
- **timeout** (*Optional*): The Welcome binary sensors will reflect the events from the last X minutes. (default: 15)
|
||||
- **offset** (*Optional*): The Presence binary sensors will stay on for X seconds after detection. (default: 90)
|
||||
- **timeout** (*Optional*): The Welcome/Presence binary sensors will stay on for X seconds after detection. (default: 90)
|
||||
- **cameras** array (*Optional*): Cameras to use. Multiple entities allowed.
|
||||
- 'camera_name': Name of the camera to display.
|
||||
- **welcome_sensors** array (*Optional*): List of monitored conditions.
|
||||
|
33
source/_components/binary_sensor.skybell.markdown
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Skybell Binary Sensor"
|
||||
description: "Instructions on how to integrate your Skybell HD devices within Home Assistant."
|
||||
date: 2017-10-03 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: skybell.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Skybell.com](https://skybell.com/) binary sensors working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
|
||||
|
||||
Once you have enabled the [Skybell component](/components/skybell), add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: skybell
|
||||
monitored_conditions:
|
||||
- button
|
||||
- motion
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
|
||||
- **button**: Return a boolean value when the doorbell button was pressed.
|
||||
- **motion**: Return a boolean value when movement was detected by the Skybell doorbell.
|
@ -183,7 +183,7 @@ Available events are `single`, `double`, `hold`, `long_click_press` and `long_cl
|
||||
|
||||
#### {% linkable_title Xiaomi Cube %}
|
||||
|
||||
Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swing`, `alert`, `free_fall` and `rotate`.
|
||||
Available events are `flip90`, `flip180`, `move`, `tap_twice`, `shake_air`, `swing`, `alert`, `free_fall` and `rotate`. The component stores the last action as the attribute `last_action`.
|
||||
|
||||
```yaml
|
||||
- alias: Cube event flip90
|
||||
|
24
source/_components/camera.skybell.markdown
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Skybell Camera"
|
||||
description: "Instructions on how to integrate your Skybell HD devices within Home Assistant."
|
||||
date: 2017-10-03 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: skybell.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Skybell.com](https://skybell.com/) cameras working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
|
||||
|
||||
Once you have enabled the [Skybell component](/components/skybell), add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
camera:
|
||||
- platform: skybell
|
||||
```
|
96
source/_components/camera.yi.markdown
Normal file
@ -0,0 +1,96 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Yi Home Camera"
|
||||
description: "Instructions on how to integrate a video feed (via FFmpeg) as a camera within Home Assistant."
|
||||
date: 2017-10-10 13:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: yi.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `yi` camera platform allows you to utilize Yi Home Cameras within Home
|
||||
Assistant. Specifically, this platform supports the line of Yi Home Cameras
|
||||
that are based on the Hi3518e Chipset; these include:
|
||||
|
||||
* Yi Home 17CN
|
||||
* Yi 1080p Home
|
||||
* Yi Dome
|
||||
* Yi 1080p Dome
|
||||
|
||||
To successfully implement this platform, the Home Assistant host should be
|
||||
capable of multiple simultaneous reads; for every concurrent Home Assistant
|
||||
user, a connection will be made to the camera every 10 seconds.
|
||||
This should normally not be a problem.
|
||||
|
||||
## {% linkable_title Preparing the Device %}
|
||||
|
||||
### {% linkable_title Installing Alternative Firmware %}
|
||||
|
||||
In order to integrate the camera with Home Assitant, it is necessary to install
|
||||
a custom firmware on the device. Instructions for doing so can be found via the
|
||||
[yi-hack-v3 GitHub project](https://github.com/shadow-1/yi-hack-v3).
|
||||
|
||||
Once installed, please ensure that you have enabled FTP and Telnet on your
|
||||
device.
|
||||
|
||||
<p class='note warning'>
|
||||
Some alternative Yi firmwares enable an experimental RTSP server, which will
|
||||
allow you to connect to your camera via other Home Assistant camera platforms.
|
||||
However, this RTSP server disables the ability to use the supremely-useful Yi
|
||||
Home app. In order to maintain both Home Assistant compatibility _and_ the native
|
||||
app, this platform retrieves videos via FTP.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Changing the FTP Password %}
|
||||
|
||||
Once the custom firmware is installed, a password must be added to the FTP
|
||||
server. To do so:
|
||||
|
||||
1. Telnet into your camera: `telnet <IP ADDRESS>`.
|
||||
2. Enter `root` as the username and `<blank>` as the password.
|
||||
3. Type `passwd` and hit `<Enter>`.
|
||||
4. Enter your new password twice.
|
||||
5. Log out of Telnet.
|
||||
|
||||
## {% linkable_title Configuring the Platform %}
|
||||
|
||||
To enable the platform, add the following lines to your
|
||||
`configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
- platform: yi
|
||||
host: '192.168.1.100'
|
||||
password: my_password_123
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): the IP address or hostname of the camera
|
||||
- **password** (*Required*): the password to the FTP server on the camera (from above)
|
||||
- **username** (*Optional*): the user that can access the FTP server (default: `root`)
|
||||
- **name** (*Optional*): a human-friendly name for the camera
|
||||
- **ffmpeg_arguments** (*Optional*): extra options to pass to `ffmpeg` (e.g. image quality or video filter options)
|
||||
|
||||
## {% linkable_title Image quality %}
|
||||
|
||||
Any option supported by the `ffmpeg` client can be utilized via the
|
||||
`ffmpeg_arguments` configuration parameter.
|
||||
|
||||
One particularly useful adjustment deals with video size. Since Yi videos are
|
||||
fairly large (especially on the 1080p cameras), the following configuration will
|
||||
bring them down to a manageable size:
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
- platform: yi
|
||||
name: My Camera
|
||||
host: '192.168.1.100'
|
||||
password: my_password_123
|
||||
ffmpeg_arguments: '-vf scale=800:450'
|
||||
```
|
18
source/_components/climate.toon.markdown
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Toon"
|
||||
description: "Instructions how to integrate Toon Climate devices within Home Assistant."
|
||||
date: 2017-10-21 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Climate
|
||||
ha_release: 0.56
|
||||
logo: toon.png
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `toon` climate platform allows you to interact with your Toon device.
|
||||
|
||||
The requirement is that you have setup the [`toon`](/components/toon/) component.
|
@ -12,6 +12,7 @@ ha_category: Cover
|
||||
ha_release: 0.55
|
||||
---
|
||||
|
||||
|
||||
The `rflink` cover platform supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
First, you have to set up your [rflink hub](/components/rflink/).
|
||||
|
@ -51,6 +51,8 @@ automation:
|
||||
event_type: automatic_update
|
||||
event_data:
|
||||
type: "ignition:on"
|
||||
vehicle:
|
||||
id: "C_1234567890abcdefc"
|
||||
action:
|
||||
- service: light.turn_off
|
||||
```
|
||||
|
@ -33,5 +33,6 @@ Configuration variables:
|
||||
- **password** (*Required*): The password for your given admin account.
|
||||
- **site_id** (*Optional*): Allows you to specify a `site_id` for device tracking. Defaults to `default`. Found in the URL of the controller (i.e. https://CONTROLLER:PORT/manage/site/SITE_ID/dashboard).
|
||||
- **verify_ssl** (*Optional*): Controls if the SSL certificate running on your Unifi webserver must be trusted by a known Certificate Authority on the server running Home Assistant. Defaults to 'True' but can also be a value that points to your custom cert "path/to/custom_cert.pem".
|
||||
- **detection_time** (*Optional*): The Unifi component will not return a device that has not been seen by the controller in the last 180 seconds. You can adjust this threshold with this variable and accepts seconds or `00:00:00` time formats.
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
102
source/_components/google_assistant.markdown
Normal file
@ -0,0 +1,102 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Google Assistant"
|
||||
description: "Setup for Google Assistant integration"
|
||||
date: 2017-10-17 12:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: google-assistant.png
|
||||
ha_category: Voice
|
||||
featured: true
|
||||
ha_release: 0.56
|
||||
---
|
||||
|
||||
# Google Assistant Docs
|
||||
The Google Assistant component requires a bit more setup than most due to the way Google requires Assistant Apps to be set up.
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
google_assistant:
|
||||
project_id: someproject-2d0b8
|
||||
client_id: [long URL safe random string]
|
||||
access_token: [a different long URL safe random string]
|
||||
exposed_domains:
|
||||
- switch
|
||||
- light
|
||||
- group
|
||||
```
|
||||
|
||||
*Note:* It's very important that you use very long strings for `client_id` and `access_token`. Those are essentially the credentials to your Home Assistant instance.
|
||||
|
||||
*Configuration Variables:*
|
||||
* *expose_by_default* (Optional): Expose devices in all supported domains by default.
|
||||
* *project_id* (Required): Project ID from the Google Developer console (looks like `words-2ab12`)
|
||||
* *client_id* (Required): A long random URL safe string (no spaces or special characters) that will be used for Implicit OAuth.
|
||||
* *access_token* (Required): Another different long random URL safe string.
|
||||
* *exposed_domains* (Optional): An array of Home Assistant domains to expose to Google Assistant.
|
||||
|
||||
You can also customize your devices similar to other components by adding keys to entities:
|
||||
|
||||
```yaml
|
||||
homeassistant:
|
||||
customize:
|
||||
master_bedroom_light:
|
||||
google_assistant: true
|
||||
google_assistant_name: bedroom light
|
||||
bedroom_blinds:
|
||||
aliases:
|
||||
- bedroom shades
|
||||
- bedroom covers
|
||||
```
|
||||
|
||||
*Entity Customization Keys:*
|
||||
* *google_assistant*: True exposes entity, false will hide it
|
||||
* *google_assistant_name*: Can be used to override the primary name of an entity. By default the `friendly_name` of an entity is used.
|
||||
* *aliases*: Provides "nicknames" to Google Assistant. These function as alternate names for an entity that Assistant will understand when spoken.
|
||||
|
||||
### {% linkable_title Setup %}
|
||||
|
||||
1. Install the [gactions CLI](https://developers.google.com/actions/tools/gactions-cli) (you'll use this later)
|
||||
2. Create a new file named `project.json` and replace the `[YOUR HOME ASSISTANT URL]` below with the URL you use to access Home Assistant.
|
||||
Note: This must be an HTTPS URL to work.
|
||||
|
||||
```json
|
||||
{
|
||||
"actions": [{
|
||||
"name": "actions.devices",
|
||||
"deviceControl": {
|
||||
},
|
||||
"fulfillment": {
|
||||
"conversationName": "automation"
|
||||
}
|
||||
}],
|
||||
"conversations": {
|
||||
"automation" :
|
||||
{
|
||||
"name": "automation",
|
||||
"url": "https://[YOUR HOME ASSISTANT URL]/api/google_assistant"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
3. Create a new project in the [developer console](https://console.actions.google.com/).
|
||||
1. Add/Import project
|
||||
2. Go to Build under the Actions SDK box
|
||||
3. Copy the command that looks like:
|
||||
`gactions update --action_package PACKAGE_NAME --project doctest-2d0b8`
|
||||
4. Replace `PACKAGE_NAME` with `project.json` and run that command from the same directory you saved `project.json` in. It should output a URL like `https://console.actions.google.com/project/doctest-2d0b8/overview` Go there.
|
||||
5. You'll need to fill out most of the information on that page, but none of it really matters since you won't be addressing the App directly, only through the Smart Home functionality built into Google Assistant.
|
||||
6. The final item on that page `Account linking` is required for your app to interact with Home Assistant.
|
||||
1. Grant type: `Implicit`
|
||||
2. Client ID: Should be the same as `client_id` from your hass config above
|
||||
3. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth`
|
||||
4. Configure your client. Add scopes for `email` and `name`
|
||||
5. Testing instructions: doesn't matter since you won't submit this app
|
||||
7. Back on the main app draft page. Click `Test Draft`. That will take you to the simulator (which won't work) so just close that window.
|
||||
8. Open the Google Assistant app and go into `Settings > Home Control`
|
||||
9. Click the `+` sign, and near the bottom, you should have `[test] your app name`. Selecting that should lead to you the screen where you can set rooms for your devices or nicknames for your devices.
|
@ -14,9 +14,10 @@ featured: false
|
||||
---
|
||||
|
||||
|
||||
The [Homematic](http://www.homematic.com/) component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
The [Homematic](http://www.homematic.com/) component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
If you are using Homegear with paired [Intertechno](http://intertechno.at/) devices, uni-directional communication is possible as well.
|
||||
|
||||
Device support is available for most of the wired and wireless devices, as well as a few IP devices. If you have a setup with mixed protocols, you have to configure additional hosts with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010.
|
||||
Device support is available for most of the wired and wireless devices, as well as a few IP devices. If you have a setup with mixed protocols, you have to configure additional hosts with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`.
|
||||
|
||||
If you want to see if a specific device you have is supported, head over to the [pyhomematic](https://github.com/danielperna84/pyhomematic/tree/master/pyhomematic/devicetypes) repository and browse through the source code. A dictionary with the device identifiers (e.g. HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute.
|
||||
|
||||
@ -41,7 +42,7 @@ Configuration variables (global):
|
||||
Configuration variables (host):
|
||||
|
||||
- **ip** (*Required*): IP address of CCU/Homegear device.
|
||||
- **port** (*Optional*): Port of CCU/Homegear XML-RPC Server. Default is 2001, use 2000 for wired and 2010 for IP.
|
||||
- **port** (*Optional*): Port of CCU/Homegear XML-RPC Server. Wireless: 2001, wired: 2000, IP: 2010, thermostatgroups: 9292.
|
||||
- **callback_ip** (*Optional*): Set this, if Home Assistant is reachable under a different IP from the CCU (NAT, Docker etc.).
|
||||
- **callback_port** (*Optional*): Set this, if Home Assistant is reachable under a different port from the CCU (NAT, Docker etc.).
|
||||
- **resolvenames** (*Optional*): [`metadata`, `json`, `xml`] Try to fetch device names. Defaults to `false` if not specified.
|
||||
@ -49,6 +50,7 @@ Configuration variables (host):
|
||||
- **password** (*Optional*): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.
|
||||
- **primary** (*Optional*): Set to `true` when using multiple hosts and this host should provide the services and variables.
|
||||
- **variables** (*Optional*): Set to `true` if you want to use CCU2/Homegear variables. Should only be enabled for the primary host. When using a CCU credentials are required.
|
||||
- **path** (*Optional*): Set to `/groups` when using port 9292.
|
||||
|
||||
#### Example configuration with multiple protocols and some other options set:
|
||||
|
||||
@ -71,6 +73,13 @@ homematic:
|
||||
ip:
|
||||
ip: 127.0.0.1
|
||||
port: 2010
|
||||
groups:
|
||||
ip: 127.0.0.1
|
||||
port: 9292
|
||||
resolvenames: json
|
||||
username: Admin
|
||||
password: secret
|
||||
path: /groups
|
||||
```
|
||||
|
||||
### {% linkable_title The `resolvenames` option %}
|
||||
|
@ -76,10 +76,10 @@ knx:
|
||||
fire_event_filter: ["1/0/*", "6/2,3,4-6/*"]
|
||||
```
|
||||
|
||||
* **fire_event** (Optional) if set to True, platform will write all received KNX messages to event bus
|
||||
* **fire_event_filter** If `fire_event` is set `fire_event_filter` has to be specified. `fire_event_filter` defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HASS event bus.
|
||||
|
||||
* **fire_event** (*Optional*): If set to True, platform will write all received KNX messages to event bus
|
||||
* **fire_event_filter** (*Optional*): If `fire_event` is set `fire_event_filter` has to be specified. `fire_event_filter` defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HASS event bus.
|
||||
|
||||
* **state_updater** (*Optional*): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behaviour.
|
||||
|
||||
Service
|
||||
-------
|
||||
@ -92,8 +92,8 @@ Service: send
|
||||
Service Data: {"address": "1/0/15", "payload": 0}
|
||||
```
|
||||
|
||||
* **address** : KNX group address
|
||||
* **payload** : payload, either an integer or an array of integers
|
||||
* **address**: KNX group address
|
||||
* **payload**: Payload, either an integer or an array of integers
|
||||
|
||||
|
||||
|
||||
|
24
source/_components/light.skybell.markdown
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Skybell Light"
|
||||
description: "Instructions on how to integrate your Skybell HD devices within Home Assistant."
|
||||
date: 2017-10-03 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: skybell.png
|
||||
ha_category: Light
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Skybell.com](https://skybell.com/) LED light working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
|
||||
|
||||
Once you have enabled the [Skybell component](/components/skybell), add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
light:
|
||||
- platform: skybell
|
||||
```
|
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: tesla.png
|
||||
ha_category: Lock
|
||||
ha_iot_class: "Coud Push"
|
||||
ha_iot_class: "Cloud Push"
|
||||
ha_release: 0.53
|
||||
---
|
||||
|
||||
|
19
source/_components/map.markdown
Executable file
@ -0,0 +1,19 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Map"
|
||||
description: "Offers a map to show tracked devices."
|
||||
date: 2017-10-11 10:01
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: "Other"
|
||||
---
|
||||
|
||||
This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/components/device_tracker/) documentation.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
map:
|
||||
```
|
49
source/_components/media_player.monoprice.markdown
Normal file
@ -0,0 +1,49 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Monoprice 6-Zone Amplifier"
|
||||
description: "Instructions on how to integrate Monoprice 6-Zone Home Audio Controller into Home Assistant."
|
||||
date: 2017-10-02 11:45
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: monoprice.svg
|
||||
ha_category: Media Player
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `monoprice` platform allows you to control [Monoprice 6-Zone Amplifier](https://www.monoprice.com/product?p_id=10761) using a serial connection.
|
||||
|
||||
To add a Monoprice device to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
- platform: monoprice
|
||||
port: /dev/ttyUSB0
|
||||
zones:
|
||||
11:
|
||||
name: Main Bedroom
|
||||
12:
|
||||
name: Living Room
|
||||
13:
|
||||
name: Kitchen
|
||||
14:
|
||||
name: Bathroom
|
||||
15:
|
||||
name: Dining Room
|
||||
16:
|
||||
name: Guest Bedroom
|
||||
sources:
|
||||
1:
|
||||
name: Sonos
|
||||
5:
|
||||
name: Chromecast
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **port** (*Required*): The serial port to which Monoprice amplifier is connected
|
||||
- **zones** (*Required*): This is the list of zones available. Valid zones are 11,12,13,14,15,16. In case multiple Monoprice devices are stacked together the list of valid zones is extended by 21,22,23,24,25,26 for the second device and 31,32,33,34,35,36 for the third device. Each zone must have a name assigned to it.
|
||||
- **sources** (*Required*): The list of sources available. Valid source numbers are 1,2,3,4,5,6. Each source number corresponds to the input number on the Monoprice amplifier. Similar to zones, each source must have a name assigned to it.
|
@ -33,6 +33,7 @@ Configuration variables:
|
||||
- **type** (*Required*): Type of the connection to Modbus.
|
||||
- **host** (*Required*): The IP address of your Modbus device, eg. 192.168.1.1.
|
||||
- **port** (*Required*): The port for the communication.
|
||||
- **timeout** (*Optional*): Timeout for slave response in seconds. (default: 3)
|
||||
|
||||
For a serial connection:
|
||||
|
||||
@ -57,6 +58,7 @@ Configuration variables:
|
||||
- **stopbits** (*Required*): The stopbits for the serial connection.
|
||||
- **bytesize** (*Required*): The bytesize for the serial connection.
|
||||
- **parity** (*Required*): The parity for the serial connection.
|
||||
- **timeout** (*Optional*): Timeout for slave response in seconds. (default: 3)
|
||||
|
||||
### {% linkable_title Services %}
|
||||
|
||||
|
47
source/_components/namecheapdns.markdown
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
layout: page
|
||||
title: "NamecheapDNS"
|
||||
description: "Keep your namecheap dynamic DNS up to date"
|
||||
date: 2017-10-11 20:16
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: namecheap.png
|
||||
ha_category: Utility
|
||||
featured: false
|
||||
ha_release: 0.56
|
||||
---
|
||||
|
||||
With the namecheapDNS component you can automatically update your dynamic DNS entry.
|
||||
|
||||
<p class='note warning'>
|
||||
Namecheap only supports IPv4 adresses to update.
|
||||
</p>
|
||||
|
||||
To use the component in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
namecheapdns:
|
||||
host: @
|
||||
domain: example.com
|
||||
access_token: 0123_Dynamic_DNS_Password
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The host part or "subdomain" part you want to update (If you want your domain leave the @ sign)
|
||||
required: true
|
||||
type: string
|
||||
domain:
|
||||
description: Your namecheap TLD (example.com).
|
||||
required: true
|
||||
type: string
|
||||
access_token:
|
||||
description: The namecheap "Dynamic DNS Password" you can find under the "Advanced DNS" Tab
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
See the [How do I set up a Host for Dynamic DNS?](https://www.namecheap.com/support/knowledgebase/article.aspx/43/11/how-do-i-set-up-a-host-for-dynamic-dns) for further instructions
|
46
source/_components/notify.clickatell.markdown
Normal file
@ -0,0 +1,46 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Clikatell SMS"
|
||||
description: "Instructions on how to add Clickatell notifications to Home Assistant."
|
||||
date: 2017-10-09 00:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: clickatell.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.56
|
||||
---
|
||||
|
||||
|
||||
The `clickatell` platform uses [Clickatell](https://clickatell.com) to deliver SMS notifications from Home Assistant.
|
||||
|
||||
### Get your Clickatell API Credentials
|
||||
Go to your [Clickatell SMS Platform Portal](https://portal.clickatell.com/#/) section and create a new SMS integration. There are three screens of information required to creater an integration. Please ensure the following:
|
||||
|
||||
1. Give the new Integration an identification name
|
||||
2. ensure it is set for 'production' use
|
||||
3. select 'HTTP' as your API type
|
||||
4. Ensure that the you select for the messaging type to be 'one way messaging'
|
||||
5. Be aware of the international number format option as this impacts the structure of the phone numbers you provide
|
||||
6. Once you have completed entering your details an API key is generated. Copy the API key
|
||||
|
||||
### Configuration
|
||||
To add Clickatell to your installation, add the following to your Home Assistant `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
notify:
|
||||
- platform: clickatell
|
||||
name: USER_DEFINED_NAME
|
||||
api_key: CLICKATELL_API_KEY
|
||||
recipient: PHONE_NO
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
* **name** (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is `Clickatell`. The notifier will bind to the service notify.NOTIFIER_NAME.
|
||||
* **api_key** (Required): Your `API Key`.
|
||||
* **recipient** (Required): Your phone no. This is where you want to send your notification SMS messages. eg: `61444333444`
|
||||
|
||||
|
||||
To use notifications, please see the [getting started with automation page](https://home-assistant.io/getting-started/automation/).
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: "ClickSend"
|
||||
title: "ClickSend text-to-speech"
|
||||
description: "Instructions on how to add ClickSend text-to-speech (TTS) notifications to Home Assistant."
|
||||
date: 2017-10-04 00:00
|
||||
sidebar: true
|
||||
@ -10,10 +10,11 @@ footer: true
|
||||
logo: clicksend.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.55
|
||||
redirect_from: /components/notify.clicksendaudio/
|
||||
---
|
||||
|
||||
|
||||
The `clicksendaudio` platform uses [ClickSend](https://clicksend.com) to deliver text-to-speech (TTS) notifications from Home Assistant.
|
||||
The `clicksend_tts` platform uses [ClickSend](https://clicksend.com) to deliver text-to-speech (TTS) notifications from Home Assistant.
|
||||
|
||||
Go to your [ClickSend Dashboard](https://dashboard.clicksend.com) section and create your new project. After creating your project, you should now be able to obtain your `username` and `api_key`.
|
||||
|
||||
@ -21,7 +22,7 @@ To add ClickSend to your installation, add the following to your Home Assistant
|
||||
|
||||
```yaml
|
||||
notify:
|
||||
- platform: clicksend
|
||||
- platform: clicksend_tts
|
||||
name: ClickSend
|
||||
username: CLICKSEND_USERNAME
|
||||
api_key: CLICKSEND_API_KEY
|
@ -33,24 +33,33 @@ Configuration variables:
|
||||
|
||||
### {% linkable_title Getting ready for Chrome %}
|
||||
|
||||
- Create new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard).
|
||||
- Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain.
|
||||
- After that, go to [https://console.firebase.google.com](https://console.firebase.google.com) and select import Google project, select the project you created.
|
||||
- Then, click the cogwheel on top left and select "Project settings".
|
||||
- Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID'.
|
||||
1. Create new project at [https://console.cloud.google.com/home/dashboard](https://console.cloud.google.com/home/dashboard).
|
||||
2. Go to [https://console.cloud.google.com/apis/credentials/domainverification](https://console.cloud.google.com/apis/credentials/domainverification) and verify your domain.
|
||||
3. After that, go to [https://console.firebase.google.com](https://console.firebase.google.com) and select import Google project, select the project you created.
|
||||
4. Then, click the cogwheel on top left and select "Project settings".
|
||||
5. Select 'Cloud Messaging' tab, listed beneath Project Credentials will be your 152 character 'Server Key' and 12 digit ID 'Sender ID'.
|
||||
|
||||
#### {% linkable_title Verify your domain with Hass.io %}
|
||||
|
||||
1. For verifying your domain you need to download a file in step 2.
|
||||
2. Create a dictionary named "www" in you Hass.io configuration dictionary.
|
||||
3. Place the file (something like this: google*.html) in the "www" directory.
|
||||
4. You can open it by going to **https://yourdomain/local/exact_file_name.html**
|
||||
5. Proceed with step 3.
|
||||
|
||||
### {% linkable_title Requirements %}
|
||||
|
||||
The `html5` platform can only function if all of the following requirements are met:
|
||||
(On Hass.io these requirements are already met.)
|
||||
|
||||
* You are using Chrome and/or Firefox on any desktop platform, ChromeOS, or Android.
|
||||
* You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android.
|
||||
* Your Home Assistant instance is exposed to the world.
|
||||
* If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.
|
||||
* `pywebpush` must be installed. `libffi-dev`, `libpython-dev`, and `libssl-dev` must be installed prior to `pywebpush` (i.e. `pywebpush` probably won't automatically install).
|
||||
* You have configured SSL for your Home Assistant. It doesn't need to be configured in Home Assistant though, i.e. you can be running [NGINX](/ecosystem/nginx/) in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed).
|
||||
* You are willing to accept the notification permission in your browser.
|
||||
|
||||
|
||||
### {% linkable_title Setting up %}
|
||||
|
||||
Assuming you have already added the platform to your configuration:
|
||||
@ -62,6 +71,7 @@ Assuming you have already added the platform to your configuration:
|
||||
5. Assuming you accept, that's all there is to it!
|
||||
6. (Optional, but highly recommended!) Open the `html5_push_registrations.conf` file in your configuration directory. You will see a new entry for the browser you just added. Rename it from `unnamed device` to a name of your choice, which will make it easier to identify later. _Do not change anything else in this file!_ You need to restart Home Assistant after making any changes to the file.
|
||||
|
||||
|
||||
### {% linkable_title Usage %}
|
||||
|
||||
The `html5` platform accepts a standard notify payload. However, there are also some special features built in which you can control in the payload.
|
||||
@ -93,7 +103,7 @@ Chrome supports notification actions, which are configurable buttons that arrive
|
||||
|
||||
#### {% linkable_title Data %}
|
||||
|
||||
Any parameters that you pass in the notify payload that aren't valid for use in the HTML5 notification (`actions`, `badge`, `body`, `dir`, `icon`, `lang`, `renotify`, `requireInteraction`, `tag`, `timestamp`, `vibrate`) will be sent back to you in the [callback events](#automating-notification-events).
|
||||
Any parameters that you pass in the notify payload that aren't valid for use in the HTML5 notification (`actions`, `badge`, `body`, `dir`, `icon`, `image`, `lang`, `renotify`, `requireInteraction`, `tag`, `timestamp`, `vibrate`) will be sent back to you in the [callback events](#automating-notification-events).
|
||||
|
||||
```json
|
||||
{
|
||||
@ -183,13 +193,13 @@ During the lifespan of a single push notification, Home Assistant will emit a fe
|
||||
|
||||
Common event payload parameters are:
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| `action` | The `action` key that you set when sending the notification of the action clicked. Only appears in the `clicked` event. |
|
||||
| `data` | The data dictionary you originally passed in the notify payload, minus any parameters that were added to the HTML5 notification (`actions`, `badge`, `body`, `dir`, `icon`, `lang`, `renotify`, `requireInteraction`, `tag`, `timestamp`, `vibrate`). |
|
||||
| `tag` | The unique identifier of the notification. Can be overridden when sending a notification to allow for replacing existing notifications. |
|
||||
| `target` | The target that this notification callback describes. |
|
||||
| `type` | The type of event callback received. Can be `received`, `clicked` or `closed`. |
|
||||
| Parameter | Description |
|
||||
|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| `action` | The `action` key that you set when sending the notification of the action clicked. Only appears in the `clicked` event. |
|
||||
| `data` | The data dictionary you originally passed in the notify payload, minus any parameters that were added to the HTML5 notification (`actions`, `badge`, `body`, `dir`, `icon`, `image`, `lang`, `renotify`, `requireInteraction`, `tag`, `timestamp`, `vibrate`). |
|
||||
| `tag` | The unique identifier of the notification. Can be overridden when sending a notification to allow for replacing existing notifications. |
|
||||
| `target` | The target that this notification callback describes. |
|
||||
| `type` | The type of event callback received. Can be `received`, `clicked` or `closed`. |
|
||||
|
||||
You can use the `target` parameter to write automations against a single `target`. For more granularity, use `action` and `target` together to write automations which will do specific things based on what target clicked an action.
|
||||
|
||||
|
56
source/_components/notify.rocketchat.markdown
Normal file
@ -0,0 +1,56 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Rocket.Chat"
|
||||
description: "Instructions on how to add Rocket.Chat notifications to Home Assistant."
|
||||
date: 2017-09-23 20:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: rocketchat.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.56
|
||||
---
|
||||
|
||||
|
||||
The `rocketchat` platform allows you to send messages to your [Rocket.Chat](https://rocket.chat/) instance from Home Assistant.
|
||||
|
||||
To add Rocket.Chat to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- platform: rocketchat
|
||||
name: NOTIFIER_NAME
|
||||
url: https://rocketchat.example.com
|
||||
username: USERNAME
|
||||
password: PASSWORD
|
||||
room: my-awesome-room
|
||||
```
|
||||
|
||||
- **name** (*Optional*): Name displayed in the frontend. The notifier will bind to the service `notify.NOTIFIER_NAME`.
|
||||
- **url** (*Required*): The URL of your Rocket.Chat instance.
|
||||
- **username** (*Required*): The Rocket.Chat username.
|
||||
- **password** (*Required*): The Rocker.Chat password.
|
||||
- **room** (*Required*): The chat room name to send messages to.
|
||||
|
||||
### {% linkable_title script.yaml example %}
|
||||
|
||||
```yaml
|
||||
rocketchat_notification:
|
||||
sequence:
|
||||
- service: notify.NOTIFIER_NAME
|
||||
data:
|
||||
message: "Message to Rocket.Chat from Home Assistant!"
|
||||
data:
|
||||
emoji: ":smirk:"
|
||||
```
|
||||
|
||||
#### {% linkable_title Message variables %}
|
||||
|
||||
- **message** (*Required*): Message to be displayed.
|
||||
- **data** (*Optional*): Dictionary containing any of the variables defined in the
|
||||
[Rocket.Chat docs](https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage#message-object-example)
|
||||
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
|
@ -35,6 +35,7 @@ Configuration variables:
|
||||
- **recipient** (*Required*): The Jabber ID (JID) that will receive the messages.
|
||||
- **tls** (*Optional*): Allow to disable TLS. Defaults to `true`.
|
||||
- **verify** (*Optional*): Allow disabling SSL certificate validity check (e.g., self-signed certificate). Defaults to `true`.
|
||||
- **room** (*Optional*): Room's name (e.g., example@conference.jabber.org). If set, send a message to chatroom instead of the sender.
|
||||
|
||||
All Jabber IDs (JID) must include the domain. Make sure that the password matches the account provided as sender.
|
||||
|
||||
|
20
source/_components/sensor.abode.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Abode Sensor"
|
||||
description: "Instructions how to integrate Abode sensors into Home Assistant."
|
||||
date: 2017-10-05 14:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: abode.jpg
|
||||
ha_release: 0.56
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
The `abode` sensor platform allows you to monitor your [Abode](https://goabode.com/) sensors.
|
||||
|
||||
This platform supports Abode `Temperature`, `Humidity`, and `Light` sensors.
|
||||
|
||||
The requirement is that you have setup your [Abode hub](/components/abode/).
|
@ -45,6 +45,7 @@ sensor:
|
||||
latitude: 42.81212
|
||||
longitude: 108.12422
|
||||
radius: 500
|
||||
show_on_map: false
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -58,6 +59,8 @@ defined under the `homeassistant` key in `configuration.yaml` will be used
|
||||
defined under the `homeassistant` key in `configuration.yaml` will be used
|
||||
- **radius** (*Optional*): the radius (in meters) around the latitude/longitude to
|
||||
search for the nearest city; defaults to `1000`
|
||||
- **show_on_map** (*Optional*): whether to show a marker on the map at the specified
|
||||
location; defaults to `true`
|
||||
|
||||
## {% linkable_title Configuring the Platform via City/State/Country %}
|
||||
|
||||
@ -74,6 +77,7 @@ sensor:
|
||||
city: southend-on-sea
|
||||
state: essex
|
||||
country: uk
|
||||
show_on_map: false
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -84,6 +88,8 @@ Configuration variables:
|
||||
- **city** (*Optional*): the city to monitor
|
||||
- **state** (*Optional*): the state/region to monitor
|
||||
- **country** (*Optional*): the country to monitor
|
||||
- **show_on_map** (*Optional*): whether to show a marker on the map at the specified
|
||||
location; defaults to `true`
|
||||
|
||||
To easily determine the proper values for a particular location, use the
|
||||
[AirVisual region directory](https://airvisual.com/world). Once you browse to the particular city you want,
|
||||
|
@ -66,6 +66,7 @@ Configuration variables:
|
||||
- **apparent_temperature_max**: Today's expected apparent high temperature.
|
||||
- **apparent_temperature_min**: Today's expected apparent low temperature.
|
||||
- **precip_intensity_max**: Today's expected maximum intensity of precipitation.
|
||||
- **uv_index**: The current UV index.
|
||||
- **units** (*Optional*): Specify the unit system. Default to `si` or `us` based on the temperature preference in Home Assistant. Other options are `auto`, `us`, `si`, `ca`, and `uk2`.
|
||||
`auto` will let Dark Sky decide the unit system based on location.
|
||||
- **update_interval** (*Optional*): Minimum time interval between updates. Default is 2 minutes. Supported formats:
|
||||
|
@ -56,3 +56,27 @@ Configuration variables:
|
||||
- **offset** (*Optional*): Final offset (output = scale * value + offset), default 0
|
||||
- **precision** (*Optional*): Number of valid decimals, default 0
|
||||
- **data_type** (*Optional*): Response representation (int, float). If float selected, value will be converted to IEEE 754 floating point format. default int
|
||||
|
||||
It's possible to change the default 30 seconds scan interval for the sensor updates as shown in the [Platform options](/docs/configuration/platform_options/#scan-interval) documentation.
|
||||
|
||||
### {% linkable_title Full example %}
|
||||
|
||||
Example a temperature sensor with a 10 seconds scan interval:
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: modbus
|
||||
scan_interval: 10
|
||||
registers:
|
||||
- name: Room_1
|
||||
slave: 10
|
||||
register: 0
|
||||
register_type: holding
|
||||
update_interval: 2.5
|
||||
unit_of_measurement: °C
|
||||
count: 1
|
||||
scale: 0.1
|
||||
offset: 0
|
||||
precision: 1
|
||||
data_type: int
|
||||
```
|
||||
|
@ -35,7 +35,7 @@ Configuration variables:
|
||||
- **name** (*Optional*): The name of the sensor.
|
||||
- **state_topic** (*Optional*): The topic that contains all subtopics for the rooms.
|
||||
- **timeout** (*Optional*): The time in seconds after which a room presence state is considered old. An example: device1 is reported at scanner1 with a distance of 1. No further updates are sent from scanner1. After 5 seconds scanner2 reports device1 with a distance of 2. The old location info is discarded in favor of the new scanner2 information as the timeout has passed.
|
||||
- **away_timeout** (*Optional*): The time in seconds after which the state should be set to `away` if there were no updates. `0` disables the check and is the default.
|
||||
- **away_timeout** (*Optional*): The time in seconds after which the state should be set to `not_home` if there were no updates. `0` disables the check and is the default.
|
||||
|
||||
Example JSON that should be published to the room topics:
|
||||
|
||||
|
@ -44,3 +44,12 @@ Configuration variables:
|
||||
- 'ipv4_in': Amount of inbound IPv4 packets per second
|
||||
- 'ipv4_out': Amount of outbound IPv4 packets per second
|
||||
- 'disk_free': Free disk space
|
||||
- 'cpu_iowait': CPU spent spent waiting for IO operations
|
||||
- 'cpu_user': CPU time spent executing user tasks
|
||||
- 'cpu_system': CPU time spent executing system tasks
|
||||
- 'cpu_softirq': CPU time spent servicing soft interrupts
|
||||
- 'cpu_guest': CPU time spent on guest tasks (such as VMs)
|
||||
- 'uptime': Time (in seconds) since last boot
|
||||
- 'packets_received': Amount of packets received
|
||||
- 'packets_sent': Amount of packets sent
|
||||
- 'connections': Total active connections
|
||||
|
@ -15,7 +15,9 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `plex` sensor platform will monitor activity on a given [Plex Media Server](https://plex.tv/). It will create a sensor that shows the number of currently watching users as the state. If you click the sensor for more details it will show you who is watching what.
|
||||
|
||||
If your Plex server is on the same local network as Home Assistant, all you need to provide in the `configuration.yaml` is the host or IP address. If you want to access a remote Plex server, you must provide the Plex username, password, and optionally the server name of the remote Plex server. If no server name is given it will use the first server listed. If you use the username and password, all servers in that account are monitored.
|
||||
If your Plex server is on the same local network as Home Assistant, all you need to provide in the `configuration.yaml` is the host or IP address. If you want to access a remote Plex server, you must provide the Plex username, password, and optionally the server name of the remote Plex server. If no server name is given it will use the first server listed. If you use the username and password, all servers in that account are monitored.
|
||||
|
||||
If you don't know your token, see [Finding your account token / X-Plex-Token](https://support.plex.tv/hc/en-us/articles/204059436).
|
||||
|
||||
If you want to enable the plex sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
@ -33,4 +35,4 @@ Configuration variables:
|
||||
- **username** (*Optional*): The username for the remote Plex server.
|
||||
- **password** (*Optional*): The password for your given account on the remote Plex server.
|
||||
- **server** (*Optional*): The name of your remote Plex server.
|
||||
|
||||
- **token** (*Optional*): X-Plex-Token of your remote Plex server.
|
||||
|
55
source/_components/sensor.serial.markdown
Normal file
@ -0,0 +1,55 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Serial Sensor"
|
||||
description: "Instructions how to integrate data from serial connected sensors into Home Assistant."
|
||||
date: 2017-10-13 07:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `serial` sensor platform is using the data provided by a device connected to the serial port of the system where Home Assistant is running. With [`ser2net`](http://ser2net.sourceforge.net/) and [`socat`](http://www.dest-unreach.org/socat/) would it also work for sensors connected to a remote system.
|
||||
|
||||
To check what kind of data is arriving at your serial port, use a command-line tool like `minicom` or `picocom` on Linux, on a macOS you can use `screen` or on Windows `putty`.
|
||||
|
||||
```bash
|
||||
$ sudo minicom -D /dev/ttyACM0
|
||||
```
|
||||
|
||||
To setup a serial sensor to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: serial
|
||||
port: /dev/ttyACM0
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
port:
|
||||
description: Local serial port where the sensor is connected and access is granted.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: Friendly name to use for the frontend. Default to "Serial sensor".
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
## {% linkable_title `value_template` for Template sensor %}
|
||||
|
||||
### {% linkable_title TMP36 %}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
"{{ (((states('sensor.serial_sensor') | float * 5 / 1024 ) - 0.5) * 100) | round(1) }}"
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
31
source/_components/sensor.skybell.markdown
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Skybell Sensor"
|
||||
description: "Instructions on how to integrate your Skybell HD devices within Home Assistant."
|
||||
date: 2017-10-03 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: skybell.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Skybell.com](https://skybell.com/) sensors working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
|
||||
|
||||
Once you have enabled the [Skybell component](/components/skybell), add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: skybell
|
||||
monitored_conditions:
|
||||
- chime_level
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
|
||||
- **chime_level**: Return a value between 0-3, indicating no chime, low, medium, and high respectively.
|
@ -16,11 +16,15 @@ ha_release: "0.30"
|
||||
|
||||
The `statistics` sensor platform is consuming the state from other sensors. Beside the maximal and the minimal value also the total, the mean, the median, the variance, and the standard deviation are as attributes available. If it's a binary sensor then only the state changes are counted.
|
||||
|
||||
It can take time till the sensor starts to work because a couple of attributes need more than one value to do the calculation.
|
||||
If you are running the [recorder](/components/recorder/) component, on startup the data is read from the database. So after a restart of the platform, you will immediately have data available. If you're using the [history](/components/history/) component, this will automatically also start the recoder component on startup.
|
||||
If you are *not* running the `recorder` component, it can take time till the sensor starts to work because a couple of attributes need more than one value to do the calculation.
|
||||
|
||||
To enable the statistics sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# enable the recorder component (optional)
|
||||
recorder:
|
||||
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: statistics
|
||||
|
18
source/_components/sensor.toon.markdown
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Toon"
|
||||
description: "Instructions how to integrate Toon Climate devices within Home Assistant."
|
||||
date: 2017-10-21 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_release: 0.56
|
||||
logo: toon.png
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `toon` sensor platform allows you to observe your Toon device.
|
||||
|
||||
The requirement is that you have setup the [`toon`](/components/toon/) component.
|
@ -27,6 +27,7 @@ sensor:
|
||||
- 'current_status'
|
||||
- 'download_speed'
|
||||
- 'upload_speed'
|
||||
- 'active_torrents'
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -40,6 +41,7 @@ Configuration variables:
|
||||
- **current_status**: The status of your Transmission daemon.
|
||||
- **download_speed**: The current download speed.
|
||||
- **upload_speed**: The current upload speed.
|
||||
- **active_torrents**: The current number of active torrents.
|
||||
|
||||
|
||||
To use the monitoring, your transmission client needs to allow remote access. If you are running the graphical transmission client (transmission-gtk) go to **Edit** -> **Preferences** and choose the tab **Remote**. Check **Allow remote access**, enter your username and your password, and uncheck the network restriction as needed.
|
||||
|
39
source/_components/sensor.travisci.markdown
Normal file
@ -0,0 +1,39 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Travis-CI Sensor"
|
||||
description: "Instructions on how to integrate the test build results reported by Travis-CI within Home Assistant."
|
||||
date: 2017-09-04 10:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: travisci.svg
|
||||
ha_category: Sensor
|
||||
ha_release: "0.56"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
With this sensor platform, you will be able to integrate the test build results reported by [Travis-CI](https://travis-ci.org/) working within Home Assistant.
|
||||
|
||||
To enable this platform, please add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: travisci
|
||||
github_token: 123456789
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): GitHub [access token](https://github.com/settings/applications) with the following scopes: *read:org*, *user:email*, *repo_deployment*, *repo:status*, *write:repo_hook*.
|
||||
- **branch** (*Optional*): Determine which default branch should be used by the **state** condition. Defaults to *master*.
|
||||
- **scan_interval** (*Optional*): How frequently to query for new data. Defaults to 30 seconds.
|
||||
- **monitored_conditions** array (*Optional*): Conditions to display in the frontend. If not specified, all conditions below will be enabled by default. The following conditions can be monitored.
|
||||
- **last_build_id**: Turn the last build job ID.
|
||||
- **last_build_duration**: Return the time elapsed in seconds to run the last test job.
|
||||
- **last_build_finished_at**: Return the timestamp of when the last test job finished.
|
||||
- **last_build_started_at**: Return the timestamp of when the last test job started.
|
||||
- **last_build_state**: Return the state from the latest test job/PR. The conditions can be: 'passed', 'failed' or 'started'.
|
||||
- **state**: Return the build test from the branch specified at by **branch** parameter.
|
||||
- **repository:** array (*Optional*): Name from the GitHub repositories to be monitored. If not specified, all GitHub repositories linked to Travis-CI will be enabled by default.
|
30
source/_components/sensor.uptime.markdown
Normal file
@ -0,0 +1,30 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Uptime Sensor"
|
||||
description: "Instructions how to integrate an uptime sensor into Home Assistant."
|
||||
date: 2017-10-13 10:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Pushing"
|
||||
logo: home-assistant.png
|
||||
ha_release: 0.56
|
||||
---
|
||||
|
||||
|
||||
The `uptime` sensor platform displays the time since the last Home Assistant restart.
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: uptime
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **name** (*Optional*): Name of the sensor. Defaults to `Uptime`.
|
||||
- **unit_of_measurement** (*Optional*): Units for uptime measurement in either `days` or `hours`. Defaults to `days`.
|
34
source/_components/skybell.markdown
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Skybell"
|
||||
description: "Instructions on how to integrate your Skybell HD devices within Home Assistant."
|
||||
date: 2017-10-03 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: skybell.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `skybell` implementation allows you to integrate your [Skybell.com](https://skybell.com) doorbells in Home Assistant.
|
||||
|
||||
Currently only the Skybell HD is supported by this platform.
|
||||
|
||||
To enable devices set up with your [Skybell.com](https://skybell.com/) account, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
skybell:
|
||||
username: you@example.com
|
||||
password: secret
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **username** (*Required*): The username for accessing your Skybell account.
|
||||
- **password** (*Required*): The password for accessing your Skybell account.
|
||||
|
||||
Finish your configuration by visiting the [Skybell binary sensor](/components/binary_sensor.skybell/), [Skybell camera](/components/camera.skybell/), [Skybell light](/components/light.skybell/), [Skybell sensor](/components/sensor.skybell/), or [Skybell switch](/components/switch.skybell/) documentation.
|
33
source/_components/switch.skybell.markdown
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Skybell Switch"
|
||||
description: "Instructions on how to integrate your Skybell HD devices within Home Assistant."
|
||||
date: 2017-10-03 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: skybell.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Skybell.com](https://skybell.com/) switches working within Home Assistant, please follow the instructions for the general [Skybell component](/components/skybell).
|
||||
|
||||
Once you have enabled the [Skybell component](/components/skybell), add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: skybell
|
||||
monitored_conditions:
|
||||
- do_not_disturb
|
||||
- motion_sensor
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
|
||||
- **do_not_disturb**: Control the state of your doorbells indoor chime.
|
||||
- **motion_sensor**: Control the state of your doorbells motion sensor.
|
20
source/_components/switch.tesla.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Tesla Switch"
|
||||
description: "Instructions on how to integrate Tesla charging switch into Home Assistant."
|
||||
date: 2017-09-19 12:20
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: tesla.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Cloud Push"
|
||||
ha_release: 0.54
|
||||
---
|
||||
|
||||
The `Tesla` platform allows you to control your [Tesla](https://www.tesla.com/) charger (enable/disable charging) from within Home Assistant.
|
||||
|
||||
The switch platform will be automatically configured if Tesla component is configured.
|
||||
|
||||
For more configuration information see the [Tesla component](/components/tesla/) documentation.
|
18
source/_components/switch.toon.markdown
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Toon"
|
||||
description: "Instructions how to integrate Toon Climate devices within Home Assistant."
|
||||
date: 2017-10-21 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Switch
|
||||
ha_release: 0.56
|
||||
logo: toon.png
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `toon` switch platform allows you to control your Toon device.
|
||||
|
||||
The requirement is that you have setup the [`toon`](/components/toon/) component.
|
@ -28,4 +28,3 @@ The requirement is that you have setup [Wink](/components/wink/).
|
||||
- iHome smart plug (No Wink hub required)
|
||||
- Wink switch groups (User created groups of switches)
|
||||
|
||||
|
||||
|
36
source/_components/switch.xiaomi_miio.markdown
Normal file
@ -0,0 +1,36 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Xiaomi Smart WiFi Socket and Smart Power Strip"
|
||||
description: "Instructions how to integrate your Xiaomi Smart WiFi Socket aka Plug or Xiaomi Smart Power Strip within Home Assistant."
|
||||
date: 2017-08-26 10:18
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: xiaomi.png
|
||||
ha_category: Switch
|
||||
ha_version: 0.56
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `xiaomi_miio` switch platform allows you to control the state of your Xiaomi Smart WiFi Socket aka Plug or Xiaomi Smart Power Strip.
|
||||
|
||||
Currently, the supported features are `on`, `off`. If the device provides the current load, it will be reported.
|
||||
|
||||
Please follow the instructions on [Retrieving the Access Token](/components/vacuum.xiaomi/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
|
||||
|
||||
To add a plug to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entries
|
||||
switch:
|
||||
- platform: xiaomi_miio
|
||||
name: Original Xiaomi Mi Smart WiFi Socket
|
||||
host: 192.168.130.59
|
||||
token: YOUR_TOKEN
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
- **host** (*Required*): The IP of your plug.
|
||||
- **token** (*Required*): The API token of your plug.
|
||||
- **name** (*Optional*): The name of your plug.
|
@ -22,6 +22,7 @@ This component provides the following platforms:
|
||||
- Device tracker - to track location of your car
|
||||
- Lock - Door lock. Enables you to control Tesla's door lock
|
||||
- Climate - HVAC control. Allow you to control (turn on/off, set target temperature) your Tesla's HVAC system.
|
||||
- Switch - Charger switch. Allow you to start/stop charging.
|
||||
|
||||
To use Tesla in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
37
source/_components/toon.markdown
Normal file
@ -0,0 +1,37 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Toon"
|
||||
description: "Instructions how to integrate Toon within Home Assistant."
|
||||
date: 2017-10-21 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Hub
|
||||
ha_release: 0.56
|
||||
logo: toon.png
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `toon` component platform can be used to control your Toon thermostat. This component adds a climate device for your Toon thermostat and sensors for power and gas consumption. The component also auto-detects any smart plugs, solar panels and smoke detectors connected to Toon and adds sensors and switches for them.
|
||||
|
||||
For the `toon` component to work, you'll need an active Toon subscription with Eneco. The component uses your Mijn Eneco credentials to control your thermostat through the [toonopafstand](https://toonopafstand.eneco.nl) website.
|
||||
|
||||
To use your Toon thermostat in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
toon:
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **username** (*Required*): Username for Mijn Eneco.
|
||||
- **password** (*Required*): Password for Mijn Eneco.
|
||||
|
||||
Toon is a smart thermostat delivered by the Eneco power company in The Netherlands. It can measure energy consumption (power and gas), but also the amount of energy generated in case solar panels are connected to it. Toon also acts as a z-wave hub for supported Fibaro devices like the wall plug and the smoke detector. This component uses the [toonlib library](https://github.com/costastf/toonlib) by Costas Tyfoxylos that connects to the unofficial API on [https://toonopafstand.eneco.nl](https://toonopafstand.eneco.nl).
|
||||
|
||||
The current version of this component supports setting any of the four built-in programs and setting the temperature manually. It polls the Toon API at 30 second intervals so the status is relatively fresh without overloading the API.
|
||||
|
@ -14,44 +14,8 @@ ha_iot_class: "Local Polling"
|
||||
ha_release: 0.43
|
||||
---
|
||||
|
||||
The `tradfri` component supports for the IKEA Trådfri (Tradfri) gateway. The gateway can control lights connected to it and Home Assistant will automatically discover its presence on your network.
|
||||
The `tradfri` component supports for the IKEA Trådfri (Tradfri) gateway. The gateway can control lights connected to it and Home Assistant will automatically discover its presence on your network.
|
||||
|
||||
For this to work, you need to install a modified lib-coap library.
|
||||
|
||||
<p class='note warning'>
|
||||
This component does **not** work on Windows, as the modified lib-coap doesn't exists for Windows.
|
||||
</p>
|
||||
<p class='note'>
|
||||
If you are using [Hass.io](/hassio/) then just move forward to the configuration as all requirements are already fulfilled.
|
||||
</p>
|
||||
|
||||
Linux:
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libtool
|
||||
$ sudo apt-get install autoconf
|
||||
|
||||
$ git clone --depth 1 --recursive -b dtls https://github.com/home-assistant/libcoap.git
|
||||
$ cd libcoap
|
||||
$ ./autogen.sh
|
||||
$ ./configure --disable-documentation --disable-shared --without-debug CFLAGS="-D COAP_DEBUG_FD=stderr"
|
||||
$ make
|
||||
$ sudo make install
|
||||
```
|
||||
|
||||
macOS:
|
||||
|
||||
```bash
|
||||
$ brew install libtool
|
||||
$ brew install autoconf
|
||||
$ brew install automake
|
||||
$ git clone --depth 1 --recursive -b dtls https://github.com/home-assistant/libcoap.git
|
||||
$ cd libcoap
|
||||
$ ./autogen.sh
|
||||
$ ./configure --disable-documentation --disable-shared --without-debug CFLAGS="-D COAP_DEBUG_FD=stderr"
|
||||
$ make
|
||||
$ make install
|
||||
```
|
||||
You will be prompted to configure the gateway through the Home Assistant interface, Enter the security key when prompted and click configure
|
||||
|
||||
<p class='note'>
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Xiaomi Mi Robot Vacuum"
|
||||
description: "Instructions how to integrate your Xiaomi Mi Robot Vacuum within Home Assistant."
|
||||
description: "Instructions on how to integrate your Xiaomi Mi Robot Vacuum within Home Assistant."
|
||||
date: 2017-05-05 18:11
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -13,16 +13,29 @@ ha_release: 0.51
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `xiaomi miio` vacuum platform allows you to control the state of your [Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/).
|
||||
The `xiaomi miio` vacuum platform allows you to control the state of your
|
||||
[Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/).
|
||||
|
||||
Current supported features are `turn_on`, `pause`, `stop`, `return_to_home`, `turn_off` (stops goes to dock), `locate`, `clean_spot`, `set_fanspeed` and even remote control your robot.
|
||||
Currently supported features are:
|
||||
|
||||
Please follow the instructions on [Retrieving the Access Token](/components/vacuum.xiaomi/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
|
||||
- `turn_on`
|
||||
- `pause`
|
||||
- `stop`
|
||||
- `return_to_home`
|
||||
- `turn_off` (stop all activity and return to dock)
|
||||
- `locate`
|
||||
- `clean_spot`
|
||||
- `set_fanspeed`
|
||||
- remote control of your robot.
|
||||
|
||||
To add a vacuum to your installation, add the following to your `configuration.yaml` file:
|
||||
Please follow [Retrieving the Access Token](/components/vacuum.xiaomi/#retrieving-the-access-token) to retrieve the API token used in
|
||||
`configuration.yaml`.
|
||||
|
||||
## {% linkable_title Configuring the Platform %}
|
||||
|
||||
To add a vacuum to your installation, add the following to `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
vacuum:
|
||||
- platform: xiaomi_miio
|
||||
host: 192.168.1.2
|
||||
@ -35,77 +48,99 @@ Configuration variables:
|
||||
- **token** (*Required*): The API token of your robot.
|
||||
- **name** (*Optional*): The name of your robot.
|
||||
|
||||
### {% linkable_title Platform services %}
|
||||
## {% linkable_title Platform Services %}
|
||||
|
||||
In addition to all [`vacuum` component services](/components/vacuum#component-services) (`turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`, `set_fanspeed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the botvac.
|
||||
In addition to [all of the services provided by the `vacuum` component]
|
||||
]) (`turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`,
|
||||
`set_fanspeed` and `send_command`), the `xiaomi` platform introduces specific
|
||||
services to access the remote control mode of the robot. These are:
|
||||
|
||||
These are: `xiaomi_remote_control_start`, `xiaomi_remote_control_stop`, `xiaomi_remote_control_move` and `xiaomi_remote_control_move_step`.
|
||||
- `xiaomi_remote_control_start`
|
||||
- `xiaomi_remote_control_stop`
|
||||
- `xiaomi_remote_control_move`
|
||||
- `xiaomi_remote_control_move_step`
|
||||
|
||||
#### {% linkable_title Service `vacuum/xiaomi_remote_control_start` %}
|
||||
### {% linkable_title Service `vacuum/xiaomi_remote_control_start` %}
|
||||
|
||||
Start the remote control mode of the vacuum cleaner. You can then move it with `remote_control_move`, when done call `remote_control_stop`.
|
||||
Start the remote control mode of the robot. You can then move it with
|
||||
`remote_control_move`; when done, call `remote_control_stop`.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
| `entity_id` | yes | Only act on specific robot; default targets all |
|
||||
|
||||
#### {% linkable_title Service `vacuum/xiaomi_remote_control_stop` %}
|
||||
### {% linkable_title Service `vacuum/xiaomi_remote_control_stop` %}
|
||||
|
||||
Exit the remote control mode of the vacuum cleaner.
|
||||
Exit the remote control mode of the robot.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
| `entity_id` | yes | Only act on specific robot; default targets all |
|
||||
|
||||
#### {% linkable_title Service `vacuum/xiaomi_remote_control_move` %}
|
||||
### {% linkable_title Service `vacuum/xiaomi_remote_control_move` %}
|
||||
|
||||
Remote control the vacuum cleaner, make sure you first set it in remote control mode with `remote_control_start`.
|
||||
Remote control the robot. Please ensure you first set it in remote control
|
||||
mode with `remote_control_start`.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
| `velocity` | no | Speed, between -0.29 and 0.29. |
|
||||
| `rotation` | no | Rotation, between -179 degrees and 179 degrees. |
|
||||
| `duration` | no | Parameter affecting the duration of the movement. |
|
||||
| `entity_id` | yes | Only act on specific robot; default targets all |
|
||||
| `velocity` | no | Speed: between -0.29 and 0.29 |
|
||||
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
|
||||
| `duration` | no | The number of seconds that the robot should move for |
|
||||
|
||||
|
||||
#### {% linkable_title Service `vacuum/xiaomi_remote_control_move_step` %}
|
||||
### {% linkable_title Service `vacuum/xiaomi_remote_control_move_step` %}
|
||||
|
||||
Use this call to enter the remote control mode, make one move, and stop and exit the remote control mode.
|
||||
Enter remote control mode, make one move, stop, and exit remote control mode.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
| `velocity` | no | Speed, between -0.29 and 0.29. |
|
||||
| `rotation` | no | Rotation, between -179 degrees and 179 degrees. |
|
||||
| `duration` | no | Parameter affecting the duration of the movement. |
|
||||
| `entity_id` | yes | Only act on specific robot; default targets all |
|
||||
| `velocity` | no | Speed: between -0.29 and 0.29. |
|
||||
| `rotation` | no | Rotation: between -179 degrees and 179 degrees. |
|
||||
| `duration` | no | The number of seconds that the robot should move for |
|
||||
|
||||
### {% linkable_title Attributes %}
|
||||
## {% linkable_title Attributes %}
|
||||
|
||||
In addition to all [`vacuum` component attributes] (`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, `status`, `params`), the `xiaomi` platform introduces specific attributes to get information of the botvac.
|
||||
In addition to [all of the attributes provided by the `vacuum` component](https://home-assistant.io/components/vacuum/#attributes),
|
||||
(`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, `status`, and
|
||||
`params`), the `xiaomi` platform introduces specific attributes. These are:
|
||||
|
||||
These are: `cleaning_time`, `do_not_disturb`, `main_brush_left`, `side_brush_left`, `filter_left`, `cleaning_count`, `total_cleaned_area` and `total_cleaning_time`.
|
||||
- `cleaning_time`
|
||||
- `do_not_disturb`
|
||||
- `main_brush_left`
|
||||
- `side_brush_left`
|
||||
- `filter_left`
|
||||
- `cleaning_count`
|
||||
- `total_cleaned_area`
|
||||
- `total_cleaning_time`
|
||||
|
||||
The following table shows the units of measurement for the single attributes.
|
||||
The following table shows the units of measurement for each attribute:
|
||||
|
||||
| Attribute | Unit of measurement | Description |
|
||||
|---------------------------|---------------------|-------------------------------------------------------|
|
||||
| `do_not_disturb` | | DND mode on / off |
|
||||
| `cleaning_time` | minutes | Last / actual cleaning time in minutes |
|
||||
| `cleaned_area` | square meter | Last / actual cleaned area in square meter |
|
||||
| `cleaned_area` | square meter | Last / actual cleaned area in square meters |
|
||||
| `main_brush_left` | hours | Hours left until a change of the main brush is needed |
|
||||
| `side_brush_left` | hours | Hours left until a change of the side brush is needed |
|
||||
| `filter_left` | hours | Hours left until a change of the filter is needed |
|
||||
| `cleaning_count` | | Number of total cleaning passage |
|
||||
| `total_cleaned_area` | square meter | Total cleaned area in square meter |
|
||||
| `cleaning_count` | | Number of total cleaning cycles |
|
||||
| `total_cleaned_area` | square meter | Total cleaned area in square meters |
|
||||
| `total_cleaning_time` | minutes | Total cleaning time in minutes |
|
||||
|
||||
### {% linkable_title Retrieving the Access Token %}
|
||||
## {% linkable_title Retrieving the Access Token %}
|
||||
|
||||
<p class='note'>
|
||||
This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuum and Xiaomi Philips Light. The Xiaomi Gateway uses another security method and requires a `key` (16 alphanumeric chars) which can be obtained easily via a hidden menu item at the Mi-Home app.
|
||||
This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot
|
||||
Vacuum and Xiaomi Philips Lights. The Xiaomi Gateway uses another security
|
||||
method and requires a `key` (16 alphanumeric chars), which can be obtained
|
||||
easily via a hidden menu item at the Mi-Home app.
|
||||
</p>
|
||||
|
||||
#### {% linkable_title Windows and Android %}
|
||||
|
||||
Follow the pairing process using your phone and Mi-Home app. You will be able to retrieve the token from a SQLite file inside your phone.
|
||||
|
||||
Before you begin you need to install `libffi-dev` and `libssl-dev` by running the command below. This is needed for `python-mirobo` to be installed correctly.
|
||||
@ -123,8 +158,6 @@ $ source /srv/homeassistant/bin/activate
|
||||
|
||||
To fetch the token follow these instructions depending on your mobile phone platform.
|
||||
|
||||
#### {% linkable_title Windows and Android %}
|
||||
|
||||
1. Configure the robot with the Mi-Home app.
|
||||
2. Enable developer mode and USB debugging on the Android phone and plug it into the computer.
|
||||
3. Get and install the [ADB tool for Windows](https://developer.android.com/studio/releases/platform-tools.html).
|
||||
@ -152,10 +185,44 @@ $ java.exe -jar ../android-backup-extractor/abe.jar unpack backup.ab backup.tar
|
||||
|
||||
#### {% linkable_title Linux and Android (rooted!) %}
|
||||
|
||||
1. Configure the light with the Mi-Home app.
|
||||
Follow the pairing process using your phone and Mi-Home app. You will be able to retrieve the token from a SQLite file inside your phone.
|
||||
|
||||
Before you begin you need to install `libffi-dev` and `libssl-dev` by running the command below. This is needed for `python-mirobo` to be installed correctly.
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libffi-dev libssl-dev
|
||||
```
|
||||
|
||||
If your Home Assistant installation is running in a [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant), make sure you activate it by running the commands below.
|
||||
|
||||
```bash
|
||||
$ sudo su -s /bin/bash homeassistant
|
||||
$ source /srv/homeassistant/bin/activate
|
||||
```
|
||||
|
||||
To fetch the token follow these instructions depending on your mobile phone platform.
|
||||
|
||||
1. Configure the robot with the Mi-Home app.
|
||||
2. Enable developer mode, USB debugging and root permission only for ADB on the Android phone and plug it into the computer.
|
||||
3. Get ADB f.e. `apt-get install android-tools-adb`
|
||||
4. `adb devices` should list your device
|
||||
5. `adb root` (does work for development builds only: ones with `ro.debuggable=1`)
|
||||
6. `adb shell`
|
||||
7. `echo "select name,localIP,token from devicerecord;" | sqlite3 /data/data/com.xiaomi.smarthome/databases/miio2.db` returns a list of all registered devices including IP address and token.
|
||||
|
||||
#### {% linkable_title iOS %}
|
||||
|
||||
1. Configure the robot with the Mi-Home app.
|
||||
2. Using iTunes, create an unencrypted backup of your iPhone.
|
||||
3. Install [iBackup Viewer](Get ADB f.e. `apt-get install android-tools-adb`), open it, and open your backup.
|
||||
4. Open the "Raw Data" module.
|
||||
5. Navigate to `com.xiaomi.mihome`.
|
||||
6. Search for a file that looks like this: `123456789_mihome.sqlite` – note that `_mihome.sqlite` is *not* the correct file.
|
||||
7. Save this file to your filesystem.
|
||||
8. Install [DB Browser for SQLite](http://sqlitebrowser.org/).
|
||||
9. Open DB Browser and load the `.sqlite` file you saved from your backup.
|
||||
10. Click on the `Execute SQL` tab.
|
||||
11. Input and run this query: `SELECT ZTOKEN FROM ZDEVICE WHERE ZNAME = "Mi Robot Vacuum"`
|
||||
12. Copy the returned 32-digit hexadecimal string to your clipboard.
|
||||
13. Open `Terminal` and execute this command: `echo '0: <YOUR HEXADECIMAL STRING>' | xxd -r -p | openssl enc -d -aes-128-ecb -nopad -nosalt -K 00000000000000000000000000000000`
|
||||
14. Use the resulting string as your token.
|
||||
|
@ -145,3 +145,153 @@ Home Assistant entity_ids for Wink devices are based on the Wink device's name.
|
||||
The Wink hub, by default, can only be accessed via the cloud. This means it requires an active internet connection and you will experience delays when controlling and updating devices (~3s).
|
||||
</p>
|
||||
|
||||
|
||||
### Custom Wink devices and their services
|
||||
|
||||
- GoControl siren and strobe
|
||||
- Dome siren/chime/strobe
|
||||
|
||||
|
||||
### {% linkable_title Service `set_siren_auto_shutoff` %}
|
||||
|
||||
You can use the service wink/set_siren_auto_shutoff to set how long the siren will sound before shuting off.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `auto_shutoff` | no | Int. One of [None, -1, 30, 60, 120] (None and -1 are forever. Use None for gocontrol, and -1 for Dome)
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of siren.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
set_all_sirens_to_one_minute_auto_shutoff:
|
||||
sequence:
|
||||
- service: wink.set_siren_auto_shutoff
|
||||
data:
|
||||
auto_shutoff: 60
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
The following services only work with the Dome siren/chime.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Service `set_chime_volume` %}
|
||||
|
||||
You can use the service wink/set_chime_volume to set the volume for the chime on your Dome siren/chime.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `volume` | no | String. One of ["low", "medium", "high"]
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of siren/chime.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
set_chime_volume_to_low_for_all_chimes
|
||||
sequence:
|
||||
- service: wink.set_chime_volume
|
||||
data:
|
||||
volume: "low"
|
||||
```
|
||||
|
||||
### {% linkable_title Service `set_siren_volume` %}
|
||||
|
||||
You can use the service wink/set_chime_volume to set the volume for the chime on your Dome siren/chime.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `volume` | no | String. One of ["low", "medium", "high"]
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of siren/chime.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
set_siren_volume_to_low_for_all_sirens
|
||||
sequence:
|
||||
- service: wink.set_siren_volume
|
||||
data:
|
||||
volume: "low"
|
||||
```
|
||||
|
||||
### {% linkable_title Service `enable_chime` %}
|
||||
|
||||
You can use the service wink/enable_chime to set the tone and enable the chime on your Dome siren/chime.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `tone` | no | String. One of ["doorbell", "fur_elise", "doorbell_extended", "alert", "william_tell", "rondo_alla_turca", "police_siren", "evacuation", "beep_beep", "beep", "inactive"]
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of siren/chime.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
execute_doorbell
|
||||
sequence:
|
||||
- service: wink.enable_chime
|
||||
data:
|
||||
tone: "doorbell"
|
||||
```
|
||||
|
||||
### {% linkable_title Service `set_siren_tone` %}
|
||||
|
||||
You can use the service wink/set_siren_tone to set the tone on your Dome siren. This tone will be used the next time the siren is executed.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `tone` | no | String. One of ["doorbell", "fur_elise", "doorbell_extended", "alert", "william_tell", "rondo_alla_turca", "police_siren", "evacuation", "beep_beep", "beep"]
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of siren/chime.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
set_siren_to_alert:
|
||||
sequence:
|
||||
- service: wink.set_siren_tone
|
||||
data:
|
||||
tone: "alert"
|
||||
```
|
||||
|
||||
### {% linkable_title Service `set_siren_strobe_enabled` %}
|
||||
|
||||
You can use the service wink/set_siren_strobe_enabled to enable or disable the strobe when the siren is executed.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `enabled` | no | Boolean. True or False.
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of siren/chime.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
disable_siren_strobe:
|
||||
sequence:
|
||||
- service: wink.set_siren_strobe_enabled
|
||||
data:
|
||||
enabled: False
|
||||
```
|
||||
|
||||
### {% linkable_title Service `set_chime_strobe_enabled` %}
|
||||
|
||||
You can use the service wink/set_chime_strobe_enabled to enable or disable the strobe when the chime is executed.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `enabled` | no | Boolean. True or False.
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of chime/chime.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
script:
|
||||
disable_chime_strobe:
|
||||
sequence:
|
||||
- service: wink.set_chime_strobe_enabled
|
||||
data:
|
||||
enabled: False
|
||||
```
|
||||
|
@ -23,22 +23,22 @@ notify:
|
||||
name: pushbullet
|
||||
```
|
||||
|
||||
- A **component** provides the core logic for some functionality (like `notify` provides sending notifications).
|
||||
- A **component** provides the core logic for some functionality (like `notify` provides sending notifications).
|
||||
- A **platform** makes the connection to a specific software or hardware platform (like `pushbullet` works with the service from pushbullet.com).
|
||||
|
||||
The basics of YAML syntax are block collections and mappings containing key-value pairs. Each item in a collection starts with a `-` while mappings have the format `key: value`. If you specify duplicate keys, the last value for a key is used.
|
||||
The basics of YAML syntax are block collections and mappings containing key-value pairs. Each item in a collection starts with a `-` while mappings have the format `key: value`. If you specify duplicate keys, the last value for a key is used. This is somewhat similar to a Hashtable or more specifically a dictionary in Python. These can be nested as well.
|
||||
|
||||
Note that indentation is an important part of specifying relationships using YAML. Things that are indented are nested "inside" things that are one level higher. So in the above example, `platform: pushbullet` is a property of (nested inside) the `notify` component.
|
||||
|
||||
Getting the right indentation can be tricky if you're not using an editor with a fixed width font. Tabs are not allowed to be used for indentation. Convention is to use 2 spaces for each level of indentation.
|
||||
|
||||
You can use the online service [YAMLLint](http://www.yamllint.com/) to check if your YAML syntax is correct before loading it into Home Assistant which will save you some time. If you do so, be aware that this is a thrid-party service and is not maintained by the Home Assistant community.
|
||||
You can use the online service [YAMLLint](http://www.yamllint.com/) to check if your YAML syntax is correct before loading it into Home Assistant which will save you some time. If you do so, be aware that this is a third-party service and is not maintained by the Home Assistant community.
|
||||
|
||||
<p class='note'>
|
||||
Please pay attention on not storing private data (passwords, API keys, etc.) directly in your `configuration.yaml` file. Private data can be stored in a [separate file](/docs/configuration/secrets/) or in [environmental variables](/docs/configuration/yaml/#using-environment-variables), which circumvents this problem of security.
|
||||
</p>
|
||||
|
||||
Text following a **#** are comments and are ignored by the system.
|
||||
Text following a `#` are comments and are ignored by the system.
|
||||
|
||||
The next example shows an [input_select](/components/input_select) component that uses a block collection for the options values.
|
||||
The other properties (like name) are specified using mappings. Note that the second line just has `threat:` with no value on the same line. Here threat is the name of the input_select and the values for it are everything nested below it.
|
||||
@ -56,7 +56,7 @@ input_select:
|
||||
initial: 0
|
||||
```
|
||||
|
||||
The following example shows nesting a collection of mappings in a mapping. In Home Assistant, this would create two sensors that each use the MQTT platform but have different values for their `state_topic` (one of the properties used for MQTT sensors).
|
||||
The following example shows nesting a collection of mappings in a mapping. In Home Assistant, this would create two sensors that each use the MQTT platform but have different values for their `state_topic` (one of the properties used for MQTT sensors).
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
|
@ -1,8 +1,8 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave"
|
||||
description: "Instructions how to integrate your existing Z-Wave within Home Assistant."
|
||||
date: 2016-02-27 19:59
|
||||
description: "Using Z-Wave with Home Assistant."
|
||||
date: 2017-09-21 10:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
@ -10,252 +10,25 @@ footer: true
|
||||
redirect_from: /getting-started/z-wave/
|
||||
---
|
||||
|
||||
[Z-Wave](http://www.z-wave.com/) integration for Home Assistant allows you to observe and control connected Z-Wave devices. Z-Wave support requires a [supported Z-Wave USB stick or module](https://github.com/OpenZWave/open-zwave/wiki/Controller-Compatibility-List) to be plugged into the host.
|
||||
[Z-Wave](http://www.z-wave.com/) integration for Home Assistant allows you to observe and control connected Z-Wave devices. Z-Wave support requires a [supported Z-Wave USB stick or module](/docs/z-wave/controllers/)) to be plugged into the host.
|
||||
|
||||
There is currently support for climate, covers, lights, locks, sensors, switches, and thermostats. All will be picked up automatically after configuring this platform.
|
||||
|
||||
Before configuring the Z-Wave setup, please take a moment and read [this article](https://drzwave.blog/2017/01/20/seven-habits-of-highly-effective-z-wave-networks-for-consumers/) to understand the most common pitfalls of Z-Wave networks.
|
||||
Before configuring the Z-Wave setup, please take a moment and read [this article](https://drzwave.blog/2017/01/20/seven-habits-of-highly-effective-z-wave-networks-for-consumers/) to understand the most common pitfalls of Z-Wave networks.
|
||||
|
||||
### {% linkable_title Installation %}
|
||||
## {% linkable_title What is Z-Wave %}
|
||||
|
||||
There is one dependency you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems):
|
||||
Z-Wave is a wireless communication protocol designed for home automation. It uses a low power, and low bandwidth, mesh network that allows devices that aren't within direct range of each other to communicate indirectly, via other nodes. Any device that's permanently powered (not battery powered) will help build the mesh, if you don't have enough powered devices, or you locate these poorly, your mesh will be unreliable.
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libudev-dev
|
||||
```
|
||||
When installing on macOS you may have to also run the command below ahead of time, replace "x.x" with the version of Python you have installed.
|
||||
There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components.
|
||||
|
||||
```bash
|
||||
sudo /Applications/Python\ x.x/Install\ Certificates.command
|
||||
```
|
||||
The Z-Wave standard was improved with Z-Wave Plus, and if you only use Z-Wave plus devices then you will gain the full benefits.
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
## {% linkable_title What do you need to use Z-Wave %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
zwave:
|
||||
usb_path: /dev/ttyUSB0
|
||||
```
|
||||
There are 2 basic things you'll need to use Z-Wave, a Z-Wave [controller](/docs/z-wave/controllers/) and one or more [devices](/docs/z-wave/devices/).
|
||||
|
||||
Configuration variables:
|
||||
### {% linkable_title Regional differences %}
|
||||
|
||||
- **usb_path** (*Optional*): The port where your device is connected to your Home Assistant host.
|
||||
- **network_key** (*Optional*): The 16-byte network key in the form `"0x01,0x02..."` used in order to connect securely to compatible devices.
|
||||
- **config_path** (*Optional*): The path to the Python OpenZWave configuration files. Defaults to the 'config' that is installed by python-openzwave
|
||||
- **autoheal** (*Optional*): Allows disabling auto Z-Wave heal at midnight. Defaults to True.
|
||||
- **polling_interval** (*Optional*): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.
|
||||
- **device_config** (*Optional*): This attribute contains node-specific override values:
|
||||
- **polling_intensity** (*Optional*): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2=every other time, etc). If not specified then your device will not be polled.
|
||||
- **ignored** (*Optional*): Ignore this entity completely. It won't be shown in the Web Interface and no events are generated for it.
|
||||
- **refresh_value** (*Optional*): Enable refreshing of the node value. Only the light component uses this. Defaults to False.
|
||||
- **delay** (*Optional*): Specify the delay for refreshing of node value. Only the light component uses this. Defaults to 2 seconds.
|
||||
- **invert_openclose_buttons** (*Optional*): Inverts function of the open and close buttons for the cover domain. Defaults to `False`.
|
||||
- **debug** (*Optional*): Print verbose z-wave info to log. Defaults to `False`.
|
||||
- **new_entity_ids** (*Optional*): Switch to new entity_id generation. Defaults to `True`.
|
||||
There are 12 different regions for Z-Wave devices, which relates to the frequency the devices use. There is overlap between the regions, but you should ensure that you buy devices for your region. Wikipedia has a list of the [frequencies used](https://en.wikipedia.org/wiki/Z-Wave#Radio_frequencies).
|
||||
|
||||
To find the path of your Z-Wave USB stick or module, run:
|
||||
|
||||
```bash
|
||||
$ ls /dev/ttyUSB*
|
||||
```
|
||||
|
||||
Or, if there is no result, try to find detailed USB connection info with:
|
||||
```bash
|
||||
$ dmesg | grep USB
|
||||
```
|
||||
|
||||
Or, on some other systems (such as Raspberry Pi), use:
|
||||
|
||||
```bash
|
||||
$ ls /dev/ttyACM*
|
||||
|
||||
# If Home Assistant (`hass`) runs with another user (e.g. *homeassistant* on Hassbian) give access to the stick with:
|
||||
$ sudo usermod -a -G dialout homeassistant
|
||||
```
|
||||
|
||||
Or, on some other systems (such as Pine 64), use:
|
||||
|
||||
```bash
|
||||
$ ls /dev/ttyS*
|
||||
```
|
||||
|
||||
Or, on macOS, use:
|
||||
|
||||
```bash
|
||||
$ ls /dev/cu.usbmodem*
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
Depending on what's plugged into your USB ports, the name found above may change. You can lock in a name, such as `/dev/zwave`, by following [these instructions](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/).
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
After installing and configuring Z-Wave, Home Assistant will try to install required Python Z-Wave libraries during startup (if they are not already installed). This process might take anywhere between 5 to 25 minutes depending upon various factors. Please be patient, and let it run! This happens only once and the subsequent restarts will have no impact in performance.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Adding Devices %}
|
||||
|
||||
To add a Z-Wave device to your system, go to the Z-Wave panel in the Home Assistant frontend and click the Add Node button in the Z-Wave Network Management card. This will place the controller in inclusion mode, after which you should activate your device to be included by following the instructions provided with the device.
|
||||
|
||||
<p class='note'>
|
||||
Some Z-Wave controllers, like Aeotec ZW090 Z-Stick Gen5, have ability to add devices to the network using their own contol buttons. This method should be avoided as it is prone to errors. Devices added to the Z-Wave network using this method may not function well.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Adding Security Devices %}
|
||||
|
||||
Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the *network_key* configuration variable to use a network key before adding these devices.
|
||||
|
||||
An easy script to generate a random key:
|
||||
```bash
|
||||
cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g'
|
||||
```
|
||||
|
||||
### {% linkable_title Battery Powered Devices %}
|
||||
|
||||
Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.
|
||||
|
||||
### {% linkable_title Events %}
|
||||
|
||||
#### {% linkable_title zwave.network_complete %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is complete, meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery-powered devices on the network.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is complete
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_complete
|
||||
```
|
||||
|
||||
#### {% linkable_title zwave.network_ready %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is ready for use. Between `zwave.network_start` and `zwave.network_ready` Home Assistant will feel sluggish when trying to send commands to Z-Wave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered, all awake nodes have been queried and sleeping nodes will be queried when they awake.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is ready
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_ready
|
||||
```
|
||||
|
||||
#### {% linkable_title zwave.network_start %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is set up to be started.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is starting
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_start
|
||||
```
|
||||
|
||||
#### {% linkable_title zwave.network_stop %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is stopping.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is stopping
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_stop
|
||||
```
|
||||
|
||||
#### {% linkable_title zwave.node_event %}
|
||||
Home Assistant will trigger an event when command_class_basic changes value on a node. This can be virtually anything, so tests have to be made to determine what value equals what. You can use this for automations.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
- alias: Minimote Button Pressed
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.node_event
|
||||
event_data:
|
||||
entity_id: zwave.aeon_labs_minimote_1
|
||||
basic_level: 255
|
||||
```
|
||||
|
||||
The *object_id* and *basic_level* of all triggered events can be seen in the console output.
|
||||
|
||||
#### {% linkable_title zwave.scene_activated %}
|
||||
|
||||
Some devices can also trigger scene activation events, which can be used in automation scripts (for example, the press of a button on a wall switch):
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation:
|
||||
- alias: Turn on Desk light
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.scene_activated
|
||||
event_data:
|
||||
entity_id: zwave.zwaveme_zme_wallcs_secure_wall_controller_8
|
||||
scene_id: 11
|
||||
```
|
||||
|
||||
Some devices (like the HomeSeer wall switches) allow you to do things like double, and triple click the up and down buttons and fire an event. These devices will also send `scene_data` to differentiate the events. This is an example of double clicking the on/up button:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation
|
||||
- alias: 'Dining room dimmer - double tap up'
|
||||
trigger:
|
||||
- event_type: zwave.scene_activated
|
||||
platform: event
|
||||
event_data:
|
||||
entity_id: zwave.dining_room_cans
|
||||
scene_id: 1
|
||||
scene_data: 3
|
||||
```
|
||||
|
||||
The *object_id* and *scene_id* of all triggered events can be seen in the console output.
|
||||
|
||||
For more information on HomeSeer devices and similar devices, please see the [device specific page](https://home-assistant.io/docs/z-wave/device-specific/#homeseer-switches).
|
||||
|
||||
### {% linkable_title Services %}
|
||||
|
||||
The `zwave` component exposes multiple services to help maintain the network.
|
||||
|
||||
| Service | Description |
|
||||
| ------- | ----------- |
|
||||
| add_node | Put the Z-Wave controller in inclusion mode. Allows one to add a new device to the Z-Wave network.|
|
||||
| add_node_secure | Put the Z-Wave controller in secure inclusion mode. Allows one to add a new device with secure communications to the Z-Wave network. |
|
||||
| cancel_command | Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decide you are not going to do it, then this must be used to stop the inclusion/exclusion command. |
|
||||
| change_association | Add or remove an association in the Z-Wave network |
|
||||
| heal_network | Tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
|
||||
| print_config_parameter | Prints Z-Wave node's config parameter value to the log. |
|
||||
| print_node | Print all state of Z-Wave node. |
|
||||
| refresh_entity| Refresh Z-Wave entity by refreshing dependent values.|
|
||||
| refresh_node| Refresh Z-Wave node. |
|
||||
| remove_node | Put the Z-Wave controller in exclusion mode. Allows one to remove a device from the Z-Wave network.|
|
||||
| rename_node | Sets a node's name. Requires a `node_id` and `name` field. |
|
||||
| rename_value | Sets a value's name. Requires a `node_id`, `value_id`, and `name` field. |
|
||||
| remove_failed_node | Remove a failed node from the network. The Node should be on the controller's Failed Node List, otherwise this command will fail.|
|
||||
| replace_failed_node | Replace a failed device with another. If the node is not in the controller's Failed Node List, or the node responds, this command will fail.|
|
||||
| reset_node_meters | Reset a node's meter values. Only works if the node supports this. |
|
||||
| set_config_parameter | Lets the user set a config parameter to a node. NOTE: Use the parameter option's `label` string as the `value` for list parameters (e.g. `"value": "Off"`). For all other parameters use the relevant integer `value` (e.g. `"value": 1`). |
|
||||
| set_poll_intensity | Lets the user set the polling intensity of a value. Changes the polling intensity without the need of a restart. This does not persist over restarts. To keep the setting over restarts, use the Z-Wave entity-card to set the config also.
|
||||
| soft_reset | Tells the controller to do a "soft reset." This is not supposed to lose any data, but different controllers can behave differently to a "soft reset" command.|
|
||||
| start_network | Starts the Z-Wave network.|
|
||||
| stop_network | Stops the Z-Wave network.|
|
||||
| test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead."|
|
||||
|
||||
The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the `zwave` component. The option defaults to `true` but can be disabled by setting `autoheal` to false. Using the `soft_reset` function with some Z-Wave controllers can cause the Z-Wave network to hang. If you're having issues with your Z-Wave network, try disabling this automation.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation:
|
||||
- alias: soft reset at 2:30am
|
||||
trigger:
|
||||
platform: time
|
||||
at: '2:30:00'
|
||||
action:
|
||||
service: zwave.soft_reset
|
||||
|
||||
- alias: heal at 2:31am
|
||||
trigger:
|
||||
platform: time
|
||||
at: '2:31:00'
|
||||
action:
|
||||
service: zwave.heal_network
|
||||
```
|
||||
|
36
source/_docs/z-wave/adding.markdown
Normal file
@ -0,0 +1,36 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Devices - Adding and Removing"
|
||||
description: "How to add and remove Z-Wave devices."
|
||||
date: 2016-02-27 19:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
To add (include) a Z-Wave [device](/docs/z-wave/devices/) to your system, go to the [Z-Wave control panel](/docs/z-wave/control-panel/) in the Home Assistant frontend and click the **Add Node** button in the *Z-Wave Network Management* card. This will place the controller in inclusion mode, after which you should activate your device to be included by following the instructions provided with the device.
|
||||
|
||||
<p class='warning'>
|
||||
Don't use the OpenZWave control panel (OZWCP), or the physical button on a controller, to add or remove devices. Many devices will only send the information about their capabilities at the time you include them. If you use the OpenZWave control panel, or the button on a device, then Home Assistant won't have that information. Using the physical button on a controller will also result in a non-security inclusion being performed, which may limit the features the device supports.
|
||||
</p>
|
||||
|
||||
When you add a device, it may initially appear without a specific entity ID (eg `zwave.__`) and without other identifying information. Running a *Heal* should help speed this process up, and you'll need to run a *Heal* anyway so that all the devices in your Z-Wave network learn about the new device. You *might* need to restart Home Assistant (not reboot the system) to have the entity ID fully visible.
|
||||
|
||||
## {% linkable_title Adding Security Devices %}
|
||||
|
||||
Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the *network_key* configuration variable to use a network key before adding these devices. Some devices only expose their full capabilities when included this way, you should always read the manual for your device to find out the recommended inclusion method.
|
||||
|
||||
An easy script to generate a random key:
|
||||
```bash
|
||||
cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//'
|
||||
```
|
||||
|
||||
<p class='warning'>
|
||||
Ensure you keep a backup of this key. If you have to rebuild your system and don't have a backup of this key, you won't be able to reconnect to any security devices. This may mean you have to do a factory reset on those devices, and your controller, before rebuilding your Z-Wave network.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Removing Devices %}
|
||||
|
||||
To remove (exclude) a Z-Wave device from your system, go to the Z-Wave control panel in the Home Assistant frontend and click the **Remove Node** button in the *Z-Wave Network Management* card. This will place the controller in exclusion mode, after which you should activate your device to be excluded by following the instructions provided with the device.
|
||||
|
106
source/_docs/z-wave/control-panel.markdown
Normal file
@ -0,0 +1,106 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Control Panel"
|
||||
description: "How to use the Z-Wave control panel."
|
||||
date: 2017-09-21 12:49
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /getting-started/z-wave-panel/
|
||||
---
|
||||
|
||||
## {% linkable_title Z-Wave Network Management %}
|
||||
|
||||
Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices from your network.
|
||||
|
||||
* **Add Node** puts the controller into inclusion mode, so you can include (add) a device to your Z-Wave network
|
||||
* **Add Node Secure** puts the controller into secure inclusion mode (this requires that you've created a [security key](/docs/z-wave/adding#sdding-security-devices))
|
||||
* **Remove Node** puts the controller into exclusion mdoe, so you can exclude (remove) a device. Note that you can exclude a non-secure device that's been added to another network
|
||||
* **Cancel Command** cancels any of the above
|
||||
|
||||
* **Heal Network** tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing.
|
||||
* **Start Network** starts the Z-Wave network
|
||||
* **Stop Network** stops the Z-Wave network
|
||||
* **Soft Reset** tells the controller to do a "soft reset." This is not supposed to lose any data, but different controllers can behave differently to a "soft reset" command, and may cause the Z-Wave network to hang.
|
||||
* **Test Network** tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead".
|
||||
|
||||
## {% linkable_title Z-Wave Node Management %}
|
||||
|
||||
* **Refresh Node** refreshes the information on the node and its entities. If used on a battery powered device, the device will first need to wake for this to work.
|
||||
* **Remove Failed Node** will remove a failed node from the network. The node needs to be on the controller's Failed Node List (marked as `is_failed: true`), otherwise this command will fail.
|
||||
* **Replace Failed Node** will replace a failed device with another. If the node is not in the controller's Failed Node List, or the node responds, this command will fail.
|
||||
* **Print Node** prints all state of Z-Wave node to the console log
|
||||
|
||||
* **Rename Node** sets a node's name
|
||||
|
||||
<p class='note'>
|
||||
Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.
|
||||
</p>
|
||||
|
||||
#### {% linkable_title Entities of this node %}
|
||||
|
||||
This is a dropdown where you can select all the entities of this node. Once selected you can then use:
|
||||
|
||||
* **Refresh Entity** to refresh just that entity's values
|
||||
* **Entity Attributes** to display the attributes of that entity (eg it's friendly name, the ID of the node, etc)
|
||||
|
||||
Here you can mark a device as requiring polling (before 0.55 this was displayed at the top), so the controller is aware of changes because the device doesn't send updates itself. Do see the information on [polling here](/docs/z-wave/polling/), since excessive polling can break your Z-Wave network.
|
||||
|
||||
You can also exclude a Z-Wave devices from Home Assistant. You can do that if you have a device that you need to have on the Z-Wave network, but you don't want it to appear in Home Assistant, or if you've got a device that's failed and you're unable to exclude it.
|
||||
|
||||
### {% linkable_title Node Information %}
|
||||
|
||||
This will display the Z-Wave related information about the node:
|
||||
|
||||
* **averageRequestRTT** The average Round Trip Time (RTT) of requests sent to the node, in milliseconds. A value of 250, for example, is a quarter of a second.
|
||||
* **averageResponseRTT** The average Round Trip Time of responses to requests
|
||||
* **battery_level** *Battery powered devices only* - the battery level, which may be rounded to the nearest 10
|
||||
* **capabilities** A comma separated list of the capabilities of the device
|
||||
* **friendly_name** The name you specified to be displayed
|
||||
* **is_awake** Whether the device is awake or not
|
||||
* **is_failed** Whether the device has been marked as failed. The controller won't try to contact failed devices.
|
||||
* **is_info_received** True once the controller has received the node information from the node.
|
||||
* **is_ready** When you start the network (or Home Assistant) it will take a short while before all devices are ready, this shows which aren't yet ready.
|
||||
* **is_zwave_plus** True for any Z-Wave Plus devices (note that controllers always report *false*, regardless of whether they are Plus devices or not)
|
||||
* **lastRequestRTT** The Round Trip Time of the last request
|
||||
* **lastResponseRTT** The Round Trip Time of the response to the last request
|
||||
* **manufacturer_name** The name of the manufacturer, as supplied by OpenZWave
|
||||
* **max_baud_rate** The maximum bandwidth the device supports, most modern devices will support 40,000 or higher
|
||||
* **new_entity_id** In 0.47, Home Assistant introduced a new naming convention for entities, this shows the new naming convention
|
||||
* **node_id** The unique node ID of this node
|
||||
* **node_name** The base name of this node, this is used to build the entity ID of all entities of this node
|
||||
* **old_entity_id** If `new_entity_ids: false` has been configured, then this is the entity_id that will be used. Support for this will be removed in the future
|
||||
* **product_name** The product name of the device, as supplied by OpenZWave
|
||||
* **query_stage** The query stage for this device (see [here](/docs/z-wave/query-stage/) for details)
|
||||
* **receivedCnt** The number of messages received from the device
|
||||
* **receivedDups** The number of duplicate messages received from the device
|
||||
* **receivedTS** The date and time the last message was received from the devices
|
||||
* **receivedUnsolicited** How many unsolicited messages were received
|
||||
* **retries** How many retries have been made to send messages to this node
|
||||
* **sentCnt** How many messages have been sent to the node
|
||||
* **sentFailed** How many messages that were sent weren't acknowledged
|
||||
* **sentTS** The date and time the last message was sent to the ndoe
|
||||
* **wake_up_interval** *Battery powered devices only* - the wakeup interval of the device, in seconds
|
||||
|
||||
### {% linkable_title Node Values %}
|
||||
|
||||
Allows you to rename the entities of the node. For example, maybe for the sensor `front_door`, you want to rename the value `seismic_intensity` to `shake`. The `entity_id` for that sensor will then change from `sensor.front_door_seismic_intensity` to `sensor.front_door_shake`.
|
||||
|
||||
### {% linkable_title Node group associations %}
|
||||
|
||||
Where the device supports the *Association* command class, this will allow you to associate the device with another. OpenZWave will automatically associate the device with the controller, to provide instant updates when the device doesn't support the *Hail* command class.
|
||||
|
||||
You can use this to enable one device to directly control another. This is primarily useful for remote controls that operate lights or switches, or where you want to have multiple devices operate as one.
|
||||
|
||||
There may be multiple groups, that are used for different purposes. The manual of your device will explain what each group is for.
|
||||
|
||||
### {% linkable_title Node config options %}
|
||||
|
||||
You can set the *wakeup* interval (in seconds) of the device, this is shown for all devices that can be battery powered, even if they are currently mains powered. The wakeup interval only applies when those devices are battery powered.
|
||||
|
||||
Underneath that you can select any supported configuration parameter to see the current setting. You can then change this and select **Set Config Parameter** to updated it. Battery powered devices will be updated the next time they wake.
|
||||
|
||||
## {% linkable_title OZW Log %}
|
||||
|
||||
Select **Refresh** to display the log if you need it to check activities.
|
@ -7,23 +7,23 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /getting-started/z-wave-controllers/
|
||||
---
|
||||
|
||||
Z-Wave is a popular home automation protocol that is not always straightforward to setup. This page will try to help you make sense of it all.
|
||||
|
||||
<p class='note'>
|
||||
Upon first run, the `zwave` component will take time to initialize entities and entities may appear with incomplete names. Running a network heal may expedite this process.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Supported Z-Wave USB Sticks & Hardware Modules %}
|
||||
|
||||
You need to have a [supported Z-Wave USB stick or module](https://github.com/OpenZWave/open-zwave/wiki/Controller-Compatibility-List) installed.
|
||||
|
||||
| Device | Works on Linux | Works on Windows | Works on OSX |
|
||||
|-------------------------|----------------|------------------|--------------|
|
||||
| Aeotec Z-Stick | ✓ | | |
|
||||
| Aeotec Z-Stick Series 2 | ✓ | | |
|
||||
| Aeotec Z-Stick Series 5 | ✓ | | ✓ |
|
||||
| Pine64 Z-Wave Module | ✓ | | |
|
||||
| Razberry GPIO Module | ✓ | | |
|
||||
| Seluxit ViaSens 100 | | | |
|
||||
| Sigma Designs UZB Stick | | | |
|
||||
| Tricklestar | | | |
|
||||
| Vision USB Stick | | | |
|
||||
| ZWave.me UZB1 | ✓ | | |
|
||||
|
||||
## {% linkable_title Stick Alternatives %}
|
||||
@ -32,3 +32,13 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
|
||||
|
||||
- [Vera](/components/vera/)
|
||||
- [Wink](/components/wink/)
|
||||
|
||||
## {% linkable_title Controller Notes %}
|
||||
|
||||
### {% linkable_title Aoetec Stick %}
|
||||
|
||||
By default this will turn on "disco lights", which you can turn off by following the instructions in the [device specific page](/docs/z-wave/device-specific/#aeon-z-stick)
|
||||
|
||||
### {% linkable_title Razberry Board %}
|
||||
|
||||
You need to disable the on-board Bluetooth since the board requires the use of the hardware UART (and there's only one on the Pi3). You do this by following the instructions in the [device specific page](/docs/z-wave/device-specific/#razberry-board)
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Device Specific Settings"
|
||||
description: "Extended instructions how to setup Z-Wave."
|
||||
description: "Notes for specific Z-Wave devices."
|
||||
date: 2016-03-24 08:49 -0700
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -10,43 +10,50 @@ footer: true
|
||||
redirect_from: /getting-started/z-wave-device-specific/
|
||||
---
|
||||
|
||||
## {% linkable_title Motion or alarm sensors %}
|
||||
## {% linkable_title Device Categories %}
|
||||
|
||||
### {% linkable_title Motion or alarm sensors %}
|
||||
|
||||
In order for Home Assistant to recognize the sensor properly, you will need to change its configuration from `Basic Set (default)` to `Binary Sensor report` or `Alarm report`.
|
||||
These devices will either show as a binary sensor or a sensor called `Alarm xxxx` and will report a numeric value. Test to see what value is what. Sometimes this is noted in the device manual.
|
||||
|
||||
As of version 0.30 you can set the settings of a Z-Wave device through the dev_service page of Home Assistant with the service: `zwave/set_config_parameter`.
|
||||
You can set the settings of the Z-Wave device through the Z-Wave control panel.
|
||||
|
||||
The following parameters can be entered:
|
||||
- **node_id** (*Required*): The node_id of the device that you are going to set a parameter to.
|
||||
- **parameter** (*Required*): The index number of the parameter to be set. Refer to device manual or zwcfg_[home_id].xml
|
||||
- **value** (*Required*): The value to set the parameter to. Refer to device manual or zwcfg_[home_id].xml
|
||||
- **size** (*Optional*): The size of the value. It is normally not needed to specify this parameter, but in some cases it's needed. Check OZW.log for details on this.
|
||||
### {% linkable_title Locks and other secure devices %}
|
||||
|
||||
You should check OZW.log to see if your new setting has been set.
|
||||
These devices require a network key to be set for the Z-Wave network before they are paired, using the **Add Node Secure** option.
|
||||
|
||||
Example entry in dev-service, setting binary reports for an Aeotec Multisensor 6:
|
||||
Home Assistant stores logs from Z-Wave in `OZW.log` in the Home Assistant config directory, when you pair a secure device you should see communication from the node with lines starting with `info: NONCES` in `OZW.log` when the device is paired successfully with a secure connection.
|
||||
|
||||
### {% linkable_title Specific Devices %}
|
||||
|
||||
```yaml
|
||||
# Example entry in dev-service
|
||||
{
|
||||
"node_id": 42,
|
||||
"parameter": 5,
|
||||
"value": 2
|
||||
}
|
||||
### {% linkable_title Aeotec Z-Stick %}
|
||||
|
||||
It's totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don't like this behaviour it can be turned off.
|
||||
|
||||
Use the following example commands from a terminal session on your Pi where your Z-Wave stick is connected.
|
||||
|
||||
Turn off "Disco lights":
|
||||
|
||||
```bash
|
||||
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00
|
||||
```
|
||||
|
||||
## {% linkable_title Locks and other secure devices %}
|
||||
Turn on "Disco lights":
|
||||
|
||||
These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZWave's `options.xml` which is located in OpenZWave's directory. This should also be the same directory as `config_path:` in your `configuration.yaml`. If it's not, make sure you have the same values in all the files you are using.
|
||||
The option is commented out by default in `options.xml` and is a default key. Make your own unique key. The key is in Hexadecimals.
|
||||
It is best to pair these devices in OpenZWave Control Panel or another Z-Wave tool that can show you logs while pairing. Home Assistant stores logs from Z-Wave in `OZW.log` in the Home Assistant config directory.
|
||||
You should see communication from the node with lines starting with `info: NONCES` in `OZW.log` when the device is paired successfully with a secure connection. If you use OpenZWave Control Panel to pair, test the device before you save the configuration.
|
||||
Make sure you copy the newly saved `zwcfg_[home_id].xml`into your Home Assistant configuration directory.
|
||||
```bash
|
||||
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00
|
||||
```
|
||||
|
||||
### {% linkable_title Razberry Board %}
|
||||
|
||||
##### {% linkable_title Aeon Minimote %}
|
||||
You need to disable the on-board Bluetooth since the board requires the use of the hardware UART (and there's only one on the Pi3). You do this by adding the following to the end of `/boot/config.txt`, then rebooting:
|
||||
|
||||
```
|
||||
dtoverlay=pi3-disable-bt
|
||||
```
|
||||
|
||||
### {% linkable_title Aeon Minimote %}
|
||||
|
||||
Here's a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into `automation.yaml`.
|
||||
|
||||
@ -124,8 +131,7 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl
|
||||
scene_id: 8
|
||||
```
|
||||
|
||||
|
||||
##### {% linkable_title HomeSeer Switches %}
|
||||
### {% linkable_title HomeSeer Switches %}
|
||||
|
||||
For the HomeSeer devices specifically, you may need to update the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
|
||||
|
||||
|
74
source/_docs/z-wave/devices.markdown
Normal file
@ -0,0 +1,74 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Devices"
|
||||
description: "What you need to know about Z-Wave devices."
|
||||
date: 2017-09-21 11:49
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /getting-started/z-wave-devices/
|
||||
---
|
||||
|
||||
## {% linkable_title Devices, Nodes, Entities, what? %}
|
||||
|
||||
The *device* is the hardware, and also used when referring to the node and all its entities. There are 3 main types of devices:
|
||||
|
||||
* [Controllers](/docs/z-wave/controllers) - all Z-Wave networks need to have one of these, though some may have two (a primary and a secondary)
|
||||
* Sensors - devices that tell you about the environment, these could be flood sensors, motion sensors, temperature sensors and so on
|
||||
* Actors or actuators - devices that change their environment, for example light switches, dimmers, thermostats (many of these will also have a sensor function)
|
||||
|
||||
Many sensors and actors can directly control other devices through a capability called *association*, without the use of an automation, these are known as *routing slaves*. This will be a very simple control, such as turning a light on when a motion sensor is activated, and off when it stops detecting motion.
|
||||
|
||||
The *node* is the presence of the device on the Z-Wave mesh. Once you've added a device to Home Assistant, the node is represented by an `entity_id` that starts with `zwave`.
|
||||
|
||||
The *entity* is an individual component of the node. It may be a sensor that you read from, or a control that you operate. For any node, there will be at least one entity (for the node itself) and if it exposes any controls or sensors there will be at least one entity per control or sensor. The [entities](/docs/z-wave/entities) that are created depend on the Command Class the device supports.
|
||||
|
||||
## {% linkable_title Z-Wave, Plus, Security 2 %}
|
||||
|
||||
There have been 2 extensions to the Z-Wave protocol. Using these requires that your controller supports these extensions, but devices are backwards compatible.
|
||||
|
||||
### {% linkable_title Z-Wave Plus %}
|
||||
|
||||
The key improvements are:
|
||||
|
||||
* Improved battery life (50% increase)
|
||||
* Improved range (50% increase) if all your devices are Z-Wave Plus
|
||||
* Higher bandwidth and improved noise immunity if all your devices are Z-Wave Plus
|
||||
* Improved self-healing and fault tolerance
|
||||
|
||||
### {% linkable_title Z-Wave Security 2 %}
|
||||
|
||||
From 2 April 2017 all newly approved Z-Wave devices will have to support the Security 2 (S2) framework. At the time of writing this (September 2017) OpenZWave does not support the S2 framework.
|
||||
|
||||
## {% linkable_title Device power %}
|
||||
|
||||
Your Z-Wave mesh network is built with the devices that are mains powered (whether directly, or via a USB adapter), these relay traffic for other nodes, building the network. These devices are always awake and you can query them, or send configuration changes, at any time.
|
||||
|
||||
Battery powered devices spend most of their time asleep, unable to relay traffic, to be queried, or receive changes. Changes sent while a device is asleep will be queued and sent the next time the device wakes. Details of the default wake interval, and how to manually wake the device (if supported) will be detailed in the devices's manual. Some battery powered devices (primarily locks and thermostats) support beaming (the *Beam* command class) that allows them to be remotely woken. This does require that all devices in the network responsible for relaying the commands between the controller and the device also support beaming.
|
||||
|
||||
<p class='note'>
|
||||
The Z-Wave capability *routing* doesn't mean the device routes traffic, it actually means that it's able to control other devices. You'll see this capability on most remotes and switches.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Instant Status %}
|
||||
|
||||
Older designs of Z-Wave devices may not support *Instant Status* (the *Hail* command class), because of a patent that was held by Lutron Electronics. Some manufacturers paid to use it, others didn't and so those devices may not report on changes. That patent expired in 2016, so new designs should support this.
|
||||
|
||||
As long as your device lists Hail or Association in its Controlled Command Classes, then you'll get instant status updates. Devices that list Central Scene in their Controlled Command Classes in theory will also work this way, once OpenZWave supports the Central Scene class. You can check your device on the [Z-Wave alliance](https://products.z-wavealliance.org/) site, looking at the **Command Classes** link, then at the **Controlled Command Classes** section.
|
||||
|
||||
## {% linkable_title Polling %}
|
||||
|
||||
Where a device doesn't send updates on status changes to the controller, you can work around this by using a thing called Polling. That causes the controller to ask the device to provide an update on all its sensors and states. This will cause a lot of traffic on the network, and if you poll too many devices too quickly, you can effectively break your Z-Wave network. Polling should only be used where there is no other choice, and you should use as large a polling interval as possible. Ideally you should replace the device.
|
||||
|
||||
For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled, if a device can receive and acknowledge the poll within one second, then it will take 10 seconds to complete the polling list, which leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic.
|
||||
|
||||
## {% linkable_title Central Scene support %}
|
||||
|
||||
The Central Scene command class isn't yet supported in OpenZWave (there is [work in progress](https://github.com/OpenZWave/open-zwave/pull/1125) to provide it it), though Home Assistant has introduced some support with [change 9178](https://github.com/home-assistant/home-assistant/pull/9178) which was part of 0.53 and [documented here](/docs/z-wave/device-specific/#homeseer-switches).
|
||||
|
||||
## {% linkable_title Is my device supported %}
|
||||
|
||||
You can check to see if OpenZWave supports your particular device by looking at the [OpenZWave github](https://github.com/OpenZWave/open-zwave/tree/master/config). Be aware that being listed here doesn't mean that it will be supported in Home Assistant, since the version of OpenZWave used by Home Assistant will often lag the github by a few months.
|
||||
|
||||
Even if your device isn't listed there, it's likely that it will still work as expected as long as the device complies with the Z-Wave standards. The OpenZWave wiki describes how [you can add support](https://github.com/OpenZWave/open-zwave/wiki/Adding-Devices) for your device if it isn't listed.
|
179
source/_docs/z-wave/entities.markdown
Normal file
@ -0,0 +1,179 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Entity Naming"
|
||||
description: "A summary of common entity names."
|
||||
date: 2017-09-21 10:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
This is a work in progress, based upon reports in the forum, the author's own devices, and reading of various documentation. It will be incomplete, so if you have a device that isn't reported here, or have a device that reports a different value, please provide a report in the [Z-Wave section](https://community.home-assistant.io/c/configuration/zwave) of the forum or the #zwave channel on [Discord](https://discord.gg/RkajcgS).
|
||||
</p>
|
||||
|
||||
## {% linkable_title Binary Sensor %}
|
||||
|
||||
Devices that support the Binary Sensor command class will create one (or more) entities starting with `binary_sensor`. For example, if the node is `door_sensor` then the binary sensor entity will be `binary_sensor.door_sensor`.
|
||||
|
||||
These will normally be `on` when the sensor is active, otherwise they will be `off`. Some devices use `on` for closed, and some use `on` for open, and some devices allow you to change how they report.
|
||||
|
||||
## {% linkable_title Alarm %}
|
||||
|
||||
This is for a single purpose sensor, multi sensors are explained under Multi Sensor.
|
||||
|
||||
Devices (usually sensors) that support the Alarm command class will create entities starting with `sensor`, and with some generic suffixes, and a suffix that relates to the supported alarm class. For example, the smoke detector `lounge` will have an entity `sensor.lounge_smoke`, and possibly also `sensor.lounge_alarm_type` and `sensor.lounge_alarm_level`. If the device creates a `binary_sensor` entity, it is recommended to use that rather then the `sensor` entity.
|
||||
|
||||
### {% linkable_title Alarm Type %}
|
||||
|
||||
- **alarm_type**: Reports the type of the sensor
|
||||
- **0**: General purpose
|
||||
- **1**: Smoke sensor
|
||||
- **2**: Carbon Monoxide (CO) sensor
|
||||
- **3**: Carbon Dioxide (CO2) sensor
|
||||
- **4**: Heat sensor
|
||||
- **5**: Water leak sensor
|
||||
- **6**: Access control
|
||||
|
||||
### {% linkable_title Alarm Level %}
|
||||
|
||||
The meaning of the `alarm_level` entity depends on the nature of the alarm sensor
|
||||
|
||||
#### {% linkable_title Smoke, CO, and CO2 %}
|
||||
|
||||
- **1**: Detection - will include a Node Location Report
|
||||
- **2**: Detection (unknown location)
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Heat %}
|
||||
|
||||
- **1**: Overheat detected - will include a Node Location Report
|
||||
- **2**: Overheat detected (unknown location)
|
||||
- **3**: Rapid temperature rise - will include a Node Location Report
|
||||
- **4**: Rapid temperature rise (unknown location)
|
||||
- **5**: Underheat detection - will include a Node Location Report
|
||||
- **6**: Underheat detection (unknown location)
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Water leak %}
|
||||
|
||||
- **1**: Water leak detected - will include a Node Location Report
|
||||
- **2**: Water leak detected (unknown location)
|
||||
- **3**: Water level dropped - will include a Node Location Report
|
||||
- **4**: Water level dropped (unknown location)
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Access control %}
|
||||
|
||||
- **1**: Manual lock
|
||||
- **2**: Manual unlock
|
||||
- **3**: RF lock
|
||||
- **4**: RF unlock
|
||||
- **5**: Keypad lock - will include the User Identifier of the User Code Report
|
||||
- **6**: Keypad unlock - will include the User Identifier of the User Code Report
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Burglar %}
|
||||
|
||||
- **1**: Intrusion - will include a Node Location Report
|
||||
- **2**: Intrusion (unknown location)
|
||||
- **3**: Tampering (case opened)
|
||||
- **4**: Tampering (invalid code)
|
||||
- **5**: Glass break - will include a Node Location Report
|
||||
- **6**: Glass break (invalid code)
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Power Management %}
|
||||
|
||||
- **1**: Power applied
|
||||
- **2**: AC disconnected
|
||||
- **3**: AC re-connected
|
||||
- **4**: Surge detection
|
||||
- **5**: Voltage drop or drift
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title System Alarm %}
|
||||
|
||||
- **1**: System hardware failure
|
||||
- **2**: System software failure
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Emergency Alarm %}
|
||||
|
||||
- **1**: Contact Police
|
||||
- **2**: Contact Fire Service
|
||||
- **3**: Contact Medical Service
|
||||
- **254**: Unknown event
|
||||
|
||||
#### {% linkable_title Alarm Clock %}
|
||||
|
||||
- **1**: Wake up
|
||||
- **254**: Unknown event
|
||||
|
||||
### {% linkable_title Access Control %}
|
||||
|
||||
- **access_control**: These *may* vary between brands
|
||||
- **22**: Open
|
||||
- **23**: Closed
|
||||
- **254**: Deep sleep
|
||||
- **255**: Case open
|
||||
|
||||
If your device has an `access_control` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](omponents/binary_sensor.template/) to create one:
|
||||
|
||||
```
|
||||
sensor:
|
||||
- platform: template
|
||||
sensors:
|
||||
YOUR_SENSOR:
|
||||
sensor_class: opening
|
||||
friendly_name: "Friendly name here"
|
||||
value_template: >-
|
||||
{%- if is_state('sensor.YOUR_SENSOR_access_control', '22') -%}
|
||||
open
|
||||
{%- else -%}
|
||||
closed
|
||||
{%- endif -%}
|
||||
```
|
||||
|
||||
### {% linkable_title Burglar %}
|
||||
|
||||
- **burglar**: These *may* vary between brands
|
||||
- **0**: Not active
|
||||
- **2**: Smoke (?)
|
||||
- **3**: Tamper
|
||||
- **8**: Motion
|
||||
- **22**: Open
|
||||
- **23**: Closed
|
||||
- **254**: Deep sleep
|
||||
- **255**: Case open
|
||||
|
||||
If your device has an `burglar` entity, but not a `binary_sensor` equivalent, you can use a [template binary sensor](omponents/binary_sensor.template/) to create one:
|
||||
|
||||
```
|
||||
sensor:
|
||||
- platform: template
|
||||
sensors:
|
||||
YOUR_SENSOR:
|
||||
sensor_class: motion
|
||||
friendly_name: "Friendly name here"
|
||||
value_template: >-
|
||||
{%- if is_state('sensor.YOUR_SENSOR_burglar', '8') -%}
|
||||
on
|
||||
{%- else -%}
|
||||
off
|
||||
{%- endif -%}
|
||||
```
|
||||
|
||||
### {% linkable_title Source Node ID %}
|
||||
|
||||
- **sourcenodeid**: Reports the sensor that generated the alarm - this is only valid for Zensor Net based devices
|
||||
|
||||
## {% linkable_title Multisensor %}
|
||||
|
||||
Multi sensor devices will create a number of entities, one for each sensor, potentially a `binary_sensor` entity, and probably also `alarm_type` and `alarm_level` entities.
|
||||
|
||||
These are all generally self explanatory, however it's worth noting:
|
||||
|
||||
- **ultraviolet** sensors will usually report zero indoors, as UVB is blocked by glass
|
||||
- **luminance** sensors should report in [Lux](https://en.wikipedia.org/wiki/Lux)
|
106
source/_docs/z-wave/events.markdown
Normal file
@ -0,0 +1,106 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Events"
|
||||
description: "Events generated by the Z-Wave component."
|
||||
date: 2017-09-21 10:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
## {% linkable_title zwave.network_complete %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is complete, meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery-powered devices on the network.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is complete
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_complete
|
||||
```
|
||||
|
||||
## {% linkable_title zwave.network_ready %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is ready for use. Between `zwave.network_start` and `zwave.network_ready` Home Assistant will feel sluggish when trying to send commands to Z-Wave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered, all awake nodes have been queried and sleeping nodes will be queried when they awake.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is ready
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_ready
|
||||
```
|
||||
|
||||
## {% linkable_title zwave.network_start %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is set up to be started.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is starting
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_start
|
||||
```
|
||||
|
||||
## {% linkable_title zwave.network_stop %}
|
||||
|
||||
Home Assistant will trigger an event when the Z-Wave network is stopping.
|
||||
|
||||
```yaml
|
||||
- alias: Z-Wave network is stopping
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.network_stop
|
||||
```
|
||||
|
||||
## {% linkable_title zwave.node_event %}
|
||||
Home Assistant will trigger an event when command_class_basic changes value on a node. This can be virtually anything, so tests have to be made to determine what value equals what. You can use this for automations.
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
- alias: Minimote Button Pressed
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.node_event
|
||||
event_data:
|
||||
entity_id: zwave.aeon_labs_minimote
|
||||
basic_level: 255
|
||||
```
|
||||
|
||||
The *entity_id* and *basic_level* of all triggered events can be seen in the console output.
|
||||
|
||||
## {% linkable_title zwave.scene_activated %}
|
||||
|
||||
Some devices can also trigger scene activation events, which can be used in automation scripts (for example, the press of a button on a wall switch):
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation:
|
||||
- alias: Turn on Desk light
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.scene_activated
|
||||
event_data:
|
||||
entity_id: zwave.zwaveme_zme_wallcs_secure_wall_controller
|
||||
scene_id: 11
|
||||
```
|
||||
|
||||
Some devices (like the HomeSeer wall switches) allow you to do things like double, and triple click the up and down buttons and fire an event. These devices will also send `scene_data` to differentiate the events. This is an example of double clicking the on/up button:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation
|
||||
- alias: 'Dining room dimmer - double tap up'
|
||||
trigger:
|
||||
- event_type: zwave.scene_activated
|
||||
platform: event
|
||||
event_data:
|
||||
entity_id: zwave.dining_room_cans
|
||||
scene_id: 1
|
||||
scene_data: 3
|
||||
```
|
||||
|
||||
The *entity_id* and *scene_id* of all triggered events can be seen in the console output.
|
||||
|
||||
For more information on HomeSeer devices and similar devices, please see the [device specific page](/docs/z-wave/device-specific/#homeseer-switches).
|
165
source/_docs/z-wave/installation.markdown
Normal file
@ -0,0 +1,165 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave"
|
||||
description: "Installation of the Z-Wave component."
|
||||
date: 2017-09-21 10:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /getting-started/z-wave-installation/
|
||||
---
|
||||
|
||||
As of version 0.45, Home Assistant automatically installs python-openzwave from PyPI as needed. This also introduced the integrated Z-Wave control panel, removing the need for the OpenZWave control panel.
|
||||
|
||||
There is one dependency you will need to have installed ahead of time (included in `systemd-devel` on Fedora/RHEL systems):
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libudev-dev
|
||||
```
|
||||
|
||||
When installing on macOS you may have to also run the command below ahead of time, replace "x.x" with the version of Python (`$ python3 --version`) you have installed.
|
||||
|
||||
```bash
|
||||
$ sudo /Applications/Python\ x.x/Install\ Certificates.command
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
The installation of python-openzwave can take half an hour or more on a Raspbery Pi.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
zwave:
|
||||
usb_path: /dev/ttyUSB0
|
||||
```
|
||||
|
||||
{% configuration zwave %}
|
||||
usb_path:
|
||||
description: The port where your device is connected to your Home Assistant host.
|
||||
required: false
|
||||
type: string
|
||||
default: /zwaveusbstick
|
||||
network_key:
|
||||
description: The 16-byte network key in the form `"0x01, 0x02..."` used in order to connect securely to compatible devices.
|
||||
required: false
|
||||
type: string
|
||||
default: None
|
||||
config_path:
|
||||
description: The path to the Python OpenZWave configuration files.
|
||||
required: false
|
||||
type: string
|
||||
default: the 'config' that is installed by python-openzwave
|
||||
autoheal:
|
||||
description: Allows disabling auto Z-Wave heal at midnight.
|
||||
required: false
|
||||
type: boolean
|
||||
default: True
|
||||
polling_interval:
|
||||
description: The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.
|
||||
required: false
|
||||
type: integer
|
||||
default: 60000
|
||||
debug:
|
||||
description: Print verbose z-wave info to log.
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
new_entity_ids:
|
||||
description: Switch to new entity_id generation.
|
||||
required: false
|
||||
type: boolean
|
||||
default: True
|
||||
device_config:
|
||||
description: This attribute contains node-specific override values. (For releases prior to 0.39 this variable is called **customize**) See [Customizing devices and services](/docs/configuration/customizing-devices/) for the format.
|
||||
required: false
|
||||
type: string, list
|
||||
keys:
|
||||
ignored:
|
||||
description: Ignore this entity completely. It won't be shown in the Web Interface and no events are generated for it.
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
polling_intensity:
|
||||
description: Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2=every other time, etc). If not specified then your device will not be polled.
|
||||
required: false
|
||||
type: integer
|
||||
default: 0
|
||||
refresh_value:
|
||||
description: Enable refreshing of the node value. Only the light component uses this.
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
delay:
|
||||
description: Specify the delay for refreshing of node value. Only the light component uses this.
|
||||
required: false
|
||||
type: integer
|
||||
default: 2
|
||||
invert_openclose_buttons:
|
||||
description: Inverts function of the open and close buttons for the cover domain.
|
||||
required: false
|
||||
type: boolean
|
||||
default: False
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Finding the controller path on Linux %}
|
||||
|
||||
To find the path of your Z-Wave USB stick or module, connect it to your system and run:
|
||||
|
||||
```bash
|
||||
$ ls -ltr /dev/tty*|tail -n 1
|
||||
```
|
||||
|
||||
That will give you a line that looks something like this:
|
||||
|
||||
```bash
|
||||
crw-rw---- 1 root dialout 204, 64 Sep 21 10:25 /dev/ttyUSB0
|
||||
```
|
||||
|
||||
Where the date and time displayed is approximately the time you connected the USB stick or module (it may also be something like `/dev/ttyAMA0` or `/dev/ttyACM0`). The number will be zero for the first device connected, and higher numbers for later devices.
|
||||
|
||||
Or, if there is no result, try to find detailed USB connection info with:
|
||||
|
||||
```bash
|
||||
$ dmesg | grep USB
|
||||
```
|
||||
|
||||
If Home Assistant (`hass`) runs with another user (e.g. *homeassistant* on Hassbian) give access to the stick with:
|
||||
|
||||
```bash
|
||||
$ sudo usermod -a -G dialout homeassistant
|
||||
```
|
||||
|
||||
<p class='Note'>
|
||||
The output from `ls -ltr` above contains the following information
|
||||
The device type is `c` (character special) and permissions are `rw-rw----`, meaning only the owner and group can read and write to it, there is only `1` link to the file, it is owned by `root` and can be accessed by the group `dialout`, it has a major device number of `204`, and a minor device number of `64`, the device was connected at `10:25` on `21 September`, and the device is `/dev/ttyUSB0`.
|
||||
</p>
|
||||
|
||||
#### {% linkable_title Creating a Persistent Device Path %}
|
||||
|
||||
Depending on what's plugged into your USB ports, the name found above may change. You can lock in a name, such as `/dev/zwave`, by following [these instructions](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/).
|
||||
|
||||
### {% linkable_title Finding the controller path on macOS %}
|
||||
|
||||
On macOS you can find the USB stick with:
|
||||
|
||||
```bash
|
||||
$ ls /dev/cu.usbmodem*
|
||||
```
|
||||
|
||||
### {% linkable_title Network Key %}
|
||||
|
||||
Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the *network_key* configuration variable to use a network key before adding these devices.
|
||||
|
||||
An easy script to generate a random key:
|
||||
```bash
|
||||
cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//'
|
||||
```
|
||||
|
||||
Ensure you keep a backup of this key. If you have to rebuild your system and don't have a backup of this key, you won't be able to reconnect to any security devices. This may mean you have to do a factory reset on those devices, and your controller, before rebuilding your Z-Wave network.
|
||||
|
||||
## {% linkable_title First Run %}
|
||||
|
||||
Upon first run, the `zwave` component will take time to initialize entities and entities may appear with incomplete names. Running a network heal may speed up this process.
|
32
source/_docs/z-wave/query-stage.markdown
Normal file
@ -0,0 +1,32 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Query Stage"
|
||||
description: "What are the Query Stages."
|
||||
date: 2017-09-21 11:49
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
| Stage | Description |
|
||||
|------------------------|--------------------------------------------------------------------|
|
||||
| None | Query process hasn't started for this node |
|
||||
| ProtocolInfo | Retrieve protocol information |
|
||||
| Probe | Ping device to see if alive |
|
||||
| WakeUp | Start wake up process if a sleeping node |
|
||||
| ManufacturerSpecific1 | Retrieve manufacturer name and product ids if ProtocolInfo lets us |
|
||||
| NodeInfo | Retrieve info about supported, controlled command classes |
|
||||
| NodePlusInfo | Retrieve ZWave+ info and update device classes |
|
||||
| SecurityReport | Retrieve a list of Command Classes that require Security |
|
||||
| ManufacturerSpecific2 | Retrieve manufacturer name and product ids |
|
||||
| Versions | Retrieve version information |
|
||||
| Instances | Retrieve information about multiple command class instances |
|
||||
| Static | Retrieve static information (doesn't change) |
|
||||
| CacheLoad | Ping a device upon restarting with cached config for the device |
|
||||
| Associations | Retrieve information about associations |
|
||||
| Neighbors | Retrieve node neighbor list |
|
||||
| Session | Retrieve session information (changes infrequently) |
|
||||
| Dynamic | Retrieve dynamic information (changes frequently) |
|
||||
| Configuration | Retrieve configurable parameter information (only done on request) |
|
||||
| Complete | Query process is completed for this node |
|
59
source/_docs/z-wave/services.markdown
Normal file
@ -0,0 +1,59 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Services"
|
||||
description: "Services exposed by the Z-Wave component."
|
||||
date: 2017-09-21 10:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
The `zwave` component exposes multiple services to help maintain the network. All of these are available through the Z-Wave control panel.
|
||||
|
||||
| Service | Description |
|
||||
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| add_node | Put the Z-Wave controller in inclusion mode. Allows you to add a new device to the Z-Wave network. |
|
||||
| add_node_secure | Put the Z-Wave controller in secure inclusion mode. Allows you to add a new device with secure communications to the Z-Wave network. |
|
||||
| cancel_command | Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decide you are not going to do it, then this must be used to stop the inclusion/exclusion command. |
|
||||
| change_association | Add or remove an association in the Z-Wave network |
|
||||
| heal_network | Tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
|
||||
| print_config_parameter | Prints Z-Wave node's config parameter value to the (console) log. |
|
||||
| print_node | Print all states of Z-Wave node. |
|
||||
| refresh_entity | Refresh the Z-Wave entity by refreshing dependent values. |
|
||||
| refresh_node | Refresh the Z-Wave node. |
|
||||
| remove_node | Put the Z-Wave controller in exclusion mode. Allows you to remove a device from the Z-Wave network. |
|
||||
| rename_node | Sets a node's name. Requires a `node_id` and `name` field. |
|
||||
| rename_value | Sets a value's name. Requires a `node_id`, `value_id`, and `name` field. |
|
||||
| remove_failed_node | Remove a failed node from the network. The Node should be on the controller's Failed Node List, otherwise this command will fail. |
|
||||
| replace_failed_node | Replace a failed device with another. If the node is not in the controller's Failed Node List, or the node responds, this command will fail. |
|
||||
| reset_node_meters | Reset a node's meter values. Only works if the node supports this. |
|
||||
| set_config_parameter | Lets the user set a config parameter to a node. NOTE: Use the parameter option's `label` string as the `value` for list parameters (e.g. `"value": "Off"`). For all other parameters use the relevant integer `value` (e.g. `"value": 1`). |
|
||||
| soft_reset | Tells the controller to do a "soft reset." This is not supposed to lose any data, but different controllers can behave differently to a "soft reset" command. |
|
||||
| start_network | Starts the Z-Wave network. |
|
||||
| stop_network | Stops the Z-Wave network. |
|
||||
| test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead." |
|
||||
|
||||
The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the `zwave` component. The option defaults to `true` but can be disabled by setting `autoheal` to false. If you're having issues with your Z-Wave network, try disabling this automation.
|
||||
|
||||
<p class='note'>
|
||||
Using the `soft_reset` function with some Z-Wave controllers can cause the Z-Wave network to hang.
|
||||
</p>
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation:
|
||||
- alias: test at 2:30am
|
||||
trigger:
|
||||
platform: time
|
||||
at: '2:30:00'
|
||||
action:
|
||||
service: zwave.test_network
|
||||
|
||||
- alias: heal at 2:32am
|
||||
trigger:
|
||||
platform: time
|
||||
at: '2:32:00'
|
||||
action:
|
||||
service: zwave.heal_network
|
||||
```
|
@ -1,31 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Z-Wave Settings"
|
||||
description: "Extended instructions how to setup Z-Wave."
|
||||
date: 2016-03-24 08:49 -0700
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /getting-started/z-wave-settings/
|
||||
---
|
||||
|
||||
You may wish to modify the Z-Wave settings in your `ozw*.xml` file (stored in the `.homeassistant` configuration directory), or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize [Open-Zwave Control Panel](https://github.com/OpenZWave/open-zwave-control-panel). Alternatively, use [Domoticz](https://www.domoticz.com/), which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image.
|
||||
|
||||
The reasoning for using these tools is that your Z-Wave controller stores the values and data that are used to control the network. The XML file in the `.homeassistant` configuration directory acts as a settings/values cache for the Z-Wave network, so modifying it directly won't change the network values. The [Open-Zwave Control Panel](https://github.com/OpenZWave/open-zwave-control-panel) writes values directly to the network and will provide you with an updated `.xml` file to overwrite in your `.homeassistant` configuration directory. This is the most foolproof way to make modifications to your Z-Wave devices.
|
||||
|
||||
It's totally normal for your Z-Wave stick (Aeon Aeotec Z-Stick Gen5 for example) to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don't like this behaviour it can be turned off.
|
||||
|
||||
Use the following example commands from a terminal session on your Pi where your Z-Wave stick is connected.
|
||||
|
||||
Turn off "Disco lights":
|
||||
|
||||
```bash
|
||||
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00
|
||||
```
|
||||
|
||||
Turn on "Disco lights":
|
||||
|
||||
```bash
|
||||
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00
|
||||
```
|
@ -32,7 +32,7 @@
|
||||
<meta name="twitter:description" content="{{ fb_description | truncate:200 }}">
|
||||
<meta name="twitter:image" content="{{ social_image }}">
|
||||
|
||||
<link href="{{ root_url }}/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
|
||||
<link href="{{ root_url }}/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="{{ root_url }}{{ site.subscribe_rss }}" rel="alternate" title="{{ site.title }}" type="application/atom+xml">
|
||||
<link rel='shortcut icon' href='{{ root_url }}/images/favicon.ico' />
|
||||
<link rel='icon' type='image/png' href='{{ root_url }}/images/favicon-192x192.png' sizes='192x192' />
|
||||
|
@ -26,6 +26,6 @@ If you're running Hassbian it's recommended that you make a backup of your confi
|
||||
If you're on Windows, you're fine as our minimum version for Windows has been 3.5 for a while now.
|
||||
|
||||
#### Other Debian based systems
|
||||
If you're running a Debian based system , follow [these instructions][dist-upgrade] to upgrade.
|
||||
If you're running a Debian based system, follow [these instructions][dist-upgrade] to upgrade.
|
||||
|
||||
[dist-upgrade]: https://linuxconfig.org/raspbian-gnu-linux-upgrade-from-jessie-to-raspbian-stretch-9
|
||||
|
@ -16,10 +16,10 @@ og_image: /images/blog/2017-10-0.55/components.png
|
||||
Beside the improved Wink support which was contributed by [@w1ll1am23], ships this release a wide variety of new components and platforms. The `input_slider` components has received a makeover by [@BioSehnsucht] and is now [`input_number`][input_number docs]. [@tinloaf] added a feature that allows you to enter dates: [`input_datetime`][input_datetime docs]. Both will help you to improve your automation rules.
|
||||
|
||||
## {% linkable_title DuckDNS %}
|
||||
Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](https://home-assistant.io/addons/duckdns/). 0.55 ships a component for no Hass.io users to get a similar feature.
|
||||
Using Home Assistant with [DuckDNS](http://www.duckdns.org) for Dynamic DNS (DDNS or DynDNS) is an [old story](https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/). DuckDNS is also integrated in [Hass.io](https://home-assistant.io/addons/duckdns/). 0.55 ships a component for non Hass.io users to get a similar feature.
|
||||
|
||||
## {% linkable_title Recorder %}
|
||||
The purging of data was [improved][recorder docs]. With `purge_interval` you can schedule regular purges of older events and states. In combination you can specify with `purge_keep_days` the amount of days you want to keep. The new service `recorder.purge` allow to handle this task when needed.
|
||||
The purging of data was [improved][recorder docs]. With `purge_interval` you can schedule regular purges of older events and states. In combination you can specify with `purge_keep_days` the amount of days you want to keep. The new service `recorder.purge` allows you to handle this task when needed.
|
||||
|
||||
## {% linkable_title Owntracks %}
|
||||
[Owntracks](http://owntracks.org/) is an easy way to track your devices. For some times we have the device tracker which depends on [MQTT][device_tracker.owntracks docs] but thanks to a new feature in Owntracks we can now offer support for HTTP. The [new platform][device_tracker.owntracks_http docs] doesn't require a MQTT broker but sends messages directly as HTTP requests to Home Assistant.
|
||||
|
531
source/_posts/2017-10-21-release-56.markdown
Normal file
@ -0,0 +1,531 @@
|
||||
---
|
||||
layout: post
|
||||
title: "0.56: Skybell, Google Actions, Travis CI and Toon"
|
||||
description: "Support for Tibber and the Things Network a long with new Owntracks and DuckDNS features"
|
||||
date: 2017-10-21 10:00:00
|
||||
date_formatted: "October 21, 2017"
|
||||
author: Fabian Affolter
|
||||
author_twitter: fabaff
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2017-10-0.56/components.png
|
||||
---
|
||||
|
||||
<a href='/components/#version/0.56'><img src='/images/blog/2017-10-0.56/components.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
|
||||
We reached another milestone aka number: 10000. GitHub is assigning numbers to pull requests and issues and the "10000" is a [PR](https://github.com/home-assistant/home-assistant/pull/10000). Our ratio is around 1/3 issues and 2/3 pull requests. To be more precise: 64% pull requests and 36% issues.
|
||||
|
||||
If you haven't noticed, there is now a [glossary](https://home-assistant.io/docs/glossary/) that collects some Home Assistant relevant terms. Talking about the documentation: [@DubhAd](https://github.com/DubhAd) rewrote large parts of the [Z-Wave section](https://home-assistant.io/docs/z-wave/). More structure to get started and to find details during the setup and the configuration.
|
||||
|
||||
## {% linkable_title Google Assistant / Google Home integration %}
|
||||
This release includes a new component to integrate Home Assistant with Google Assistant by [Phil Kates][@philk]. We integrate via the Smart Home API, this means that you will be able to control your devices in Home Assistant via any device that has Google Assistant. Learn more in [the documentation][googleactions docs].
|
||||
|
||||
## {% linkable_title Hacktoberfest %}
|
||||
[Hacktoberfest](https://home-assistant.io/blog/2017/09/29/hacktoberfest/) is still on and so far we have received a lot improvements. We can't make any promises to review everything by the end of October, but we are trying to make sure that you will get your t-shirt.
|
||||
|
||||
## {% linkable_title Map %}
|
||||
The [map][map docs] is now its own component. Similar to [configuration (`config:`)](https://home-assistant.io/components/config/), it will not show up without adding it to your `configuration.yaml` file.
|
||||
|
||||
```yaml
|
||||
map:
|
||||
```
|
||||
|
||||
## {% linkable_title Travis CI %}
|
||||
Why not observe your [Travis CI](https://travis-ci.org) jobs with Home Assistant? [@tchellomello] created a [Travis CI][sensor.travisci docs] sensor which allows one to check on the current state of Travis jobs. Now you can make sure that the [coffee](https://home-assistant.io/blog/2017/01/28/face-coffee-wink/#first-coffee-maker-supported) is ready when the build passed.
|
||||
|
||||
## {% linkable_title New Platforms %}
|
||||
|
||||
- Add Arlo alarm control panel component ([@vickyg3] - [#9711]) ([alarm_control_panel.arlo docs]) (new-platform)
|
||||
- Abode Temp, Humidity, and Light Sensor ([@MisterWil] - [#9709]) ([abode docs]) ([sensor.abode docs]) (new-platform)
|
||||
- Introducing support to Travis-CI ([@tchellomello] - [#9701]) ([sensor.travisci docs]) (new-platform)
|
||||
- Skybell ([@MisterWil] - [#9681]) ([skybell docs]) ([binary_sensor.skybell docs]) ([camera.skybell docs]) ([light.skybell docs]) ([sensor.skybell docs]) ([switch.skybell docs]) (new-platform)
|
||||
- Xiaomi Smart WiFi Socket and Smart Power Strip integration ([@syssi] - [#9138]) ([switch.xiaomi_plug docs]) (new-platform)
|
||||
- Add notification platform for Rocket.Chat ([@webworxshop] - [#9553]) ([notify.rocketchat docs]) (new-platform)
|
||||
- Tesla bug fixes. ([@zabuldon] - [#9774]) ([tesla docs]) ([binary_sensor.tesla docs]) ([climate.tesla docs]) ([lock.tesla docs]) ([sensor.tesla docs]) ([switch.tesla docs]) (new-platform)
|
||||
- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)
|
||||
- Support for Yi cameras ([@bachya] - [#9787]) ([camera.yi docs]) (new-platform)
|
||||
- Add namecheap DNS component ([@Munsio] - [#9821]) ([namecheapdns docs]) (new-platform)
|
||||
- Uptime sensor ([@fronzbot] - [#9856]) ([sensor.uptime docs]) (new-platform)
|
||||
- Cloud connection via aiohttp ([@balloob] - [#9860]) (new-platform)
|
||||
- Google Actions for Assistant ([@philk] - [#9632]) ([googleactions docs]) ([http docs]) (new-platform)
|
||||
- A new platform for controlling Monoprice 6-Zone amplifier ([@etsinko] - [#9662]) ([media_player.monoprice docs]) (new-platform)
|
||||
- Add serial sensor ([@fabaff] - [#9861]) ([sensor.serial docs]) (new-platform)
|
||||
- Add Toon support ([@Boltgolt] - [#9483]) ([toon docs]) ([climate.toon docs]) ([sensor.toon docs]) ([switch.toon docs]) (new-platform)
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our very active [forums](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.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## {% linkable_title Breaking Changes %}
|
||||
|
||||
- Simplify track_same_state ([@balloob] - [#9795]) ([automation.numeric_state docs]) ([automation.state docs]) ([binary_sensor.template docs]) (breaking change)
|
||||
- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)
|
||||
- Fix ISY994 fan platform overwriting state property ([@balloob] - [#9817]) (breaking change)
|
||||
- Changing name of clicksendaudio component to clicksend_tts ([@jeroenterheerdt] - [#9859]) ([notify.clicksend_tts docs]) (breaking change)
|
||||
- Fix load of components without any config from packages ([@azogue] - [#9901]) (breaking change)
|
||||
- Fix the resource naming in the UI ([@cgtobi] - [#9916]) ([sensor.systemmonitor docs]) (breaking change)
|
||||
- Align away state tag with device_trackers ([@PeteBa] - [#9884]) ([sensor.mqtt_room docs]) (breaking change)
|
||||
- Moved siren to Wink from switch ([@w1ll1am23] - [#9879]) ([wink docs]) ([switch.wink docs]) (breaking change)
|
||||
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- fixed duplicate words ([@flowolf] - [#9705]) ([light.hue docs]) ([light.mqtt_json docs]) ([media_player.denon docs]) ([media_player.dunehd docs])
|
||||
- move icon battery function from util to helpers ([@happyleavesaoc] - [#9708]) ([vacuum docs]) ([sensor.android_ip_webcam docs]) ([sensor.fitbit docs]) ([sensor.ios docs]) ([sensor.raincloud docs]) ([vacuum.dyson docs]) ([vacuum.mqtt docs])
|
||||
- Updating helper's icon_for_battery_level location ([@tchellomello] - [#9594]) ([sensor.ring docs])
|
||||
- Upgrade pyhomematic, add path setting and HM-CC-VG-1 support ([@danielperna84] - [#9707]) ([homematic docs])
|
||||
- bump the version and catch all exceptions to avoid showing backtraces… ([@rytilahti] - [#9720]) ([climate.eq3btsmart docs])
|
||||
- More netdata sensors ([@fronzbot] - [#9719]) ([sensor.netdata docs])
|
||||
- Upgrade pysnmp to 4.3.10 ([@fabaff] - [#9722]) ([device_tracker.snmp docs]) ([sensor.snmp docs])
|
||||
- arlo: Add alarm control panel component ([@vickyg3] - [#9711]) ([alarm_control_panel.arlo docs]) (new-platform)
|
||||
- Abode Temp, Humidity, and Light Sensor ([@MisterWil] - [#9709]) ([abode docs]) ([sensor.abode docs]) (new-platform)
|
||||
- Arlo clean-up ([@fabaff] - [#9725]) ([arlo docs]) ([alarm_control_panel.arlo docs]) ([camera.arlo docs]) ([sensor.arlo docs])
|
||||
- Introducing support to Travis-CI ([@tchellomello] - [#9701]) ([sensor.travisci docs]) (new-platform)
|
||||
- Add show_on_map config option to AirVisual ([@bachya] - [#9654]) ([sensor.airvisual docs])
|
||||
- Move 'show_on_map' to const ([@fabaff] - [#9727]) ([binary_sensor.iss docs]) ([sensor.airvisual docs])
|
||||
- Bump release to 0.56.0dev ([@fabaff] - [#9726])
|
||||
- Add andrey-git to codeowners ([@andrey-git] - [#9718])
|
||||
- Fix: Last Played Media Title persists in plex ([@ryanm101] - [#9664]) ([media_player.plex docs])
|
||||
- Event trigger nested conditions ([@armills] - [#9732]) ([automation.event docs])
|
||||
- Rewrite Alexa Smart-Home skill to v3 ([@pvizeli] - [#9699]) ([alexa.smart_home docs])
|
||||
- Fix I/O in event loop by Arlo alarm control panel ([@balloob] - [#9738]) ([alarm_control_panel.arlo docs])
|
||||
- Make Arlo battery_level icon dynamic ([@tchellomello] - [#9747]) ([sensor.arlo docs])
|
||||
- Fix for TypeError in synology camera ([@snjoetw] - [#9754]) ([camera.synology docs])
|
||||
- switch.tplink, light.tplink: bump the pyhs100 version and adapt to api changes ([@rytilahti] - [#9454]) ([light.tplink docs]) ([switch.tplink docs])
|
||||
- RFC: Use bind_hass for helpers ([@balloob] - [#9745])
|
||||
- Skybell ([@MisterWil] - [#9681]) ([skybell docs]) ([binary_sensor.skybell docs]) ([camera.skybell docs]) ([light.skybell docs]) ([sensor.skybell docs]) ([switch.skybell docs]) (new-platform)
|
||||
- add myself to yeelight owners, too ([@rytilahti] - [#9759])
|
||||
- Update CODEOWNERS ([@danielhiversen] - [#9760])
|
||||
- Adding my contributions ([@bachya] - [#9761])
|
||||
- Initializing statistics sensor with data from database ([@ChristianKuehnel] - [#9753]) ([sensor.statistics docs])
|
||||
- Match test requirements by full package name. ([@andrey-git] - [#9764])
|
||||
- yeelight: implement min_mireds and max_mireds, fixes #9509 ([@rytilahti] - [#9763]) ([light.yeelight docs])
|
||||
- Bump raincloudy version 0.0.3 ([@tchellomello] - [#9767]) ([raincloud docs]) ([sensor.raincloud docs])
|
||||
- Xiaomi Smart WiFi Socket and Smart Power Strip integration ([@syssi] - [#9138]) ([switch.xiaomi_plug docs]) (new-platform)
|
||||
- fix for LocationParseError in netgear platform ([@etsinko] - [#9683]) ([device_tracker docs]) ([device_tracker.netgear docs])
|
||||
- Expose time module in Python Scripts ([@balloob] - [#9736]) ([python_script docs])
|
||||
- Add notification platform for Rocket.Chat. ([@webworxshop] - [#9553]) ([notify.rocketchat docs]) (new-platform)
|
||||
- Updating pythonegardia package requirement to .22 because of fixed bug in passing default value for parameter SSL for egardiaserver ([@jeroenterheerdt] - [#9770]) ([alarm_control_panel.egardia docs])
|
||||
- Adding myself as codeowner for egardia alarm control panel. ([@jeroenterheerdt] - [#9772])
|
||||
- WIP: Fix Arlo Camera blocking IO ([@bachya] - [#9758]) ([camera.arlo docs])
|
||||
- Tesla bug fixes. ([@zabuldon] - [#9774]) ([tesla docs]) ([binary_sensor.tesla docs]) ([climate.tesla docs]) ([lock.tesla docs]) ([sensor.tesla docs]) ([switch.tesla docs]) (new-platform)
|
||||
- Fix off by one error in arwn platform ([@sdague] - [#9781]) ([sensor.arwn docs])
|
||||
- missing is_closed ( rflink cover fix ) ([@passie] - [#9776]) ([cover.rflink docs])
|
||||
- Wink dome siren support ([@w1ll1am23] - [#9667]) ([wink docs]) ([switch.wink docs])
|
||||
- Bump rxv library to 0.5.1 ([@sdague] - [#9784]) ([media_player.yamaha docs])
|
||||
- Communication timeout support in modbus hub. ([@ziotibia81] - [#9780]) ([modbus docs])
|
||||
- [light.tradfri] Fix transition time ([@lwis] - [#9785]) ([light.tradfri docs])
|
||||
- OwnTracks: Fix handler is None checking ([@balloob] - [#9794]) ([device_tracker.owntracks docs])
|
||||
- Simplify track_same_state ([@balloob] - [#9795]) ([automation.numeric_state docs]) ([automation.state docs]) ([binary_sensor.template docs]) (breaking change)
|
||||
- Optimize event matcher ([@balloob] - [#9798])
|
||||
- Resolving bug that prevents ssl_verify option for Unifi device_tracker ([@GenericStudent] - [#9788]) ([device_tracker.unifi docs])
|
||||
- Upgrade pyasn1 to 0.3.7 and pyasn1-modules to 0.1.5 ([@fabaff] - [#9810])
|
||||
- Split map panel out into its own component ([@cgarwood] - [#9814]) ([map docs]) (breaking change) (new-platform)
|
||||
- Restore home-assistant-polymer pointer from #9720 ([@armills] - [#9825])
|
||||
- Fix ISY994 fan platform overwriting state property ([@balloob] - [#9817]) (breaking change)
|
||||
- Wait_template - support for 'trigger.entity_id' and data_template values ([@cdce8p] - [#9807])
|
||||
- Adds image attribute to html5 notify (#9832) ([@cgarwood] - [#9835]) ([notify.html5 docs])
|
||||
- OwnTracks: Handle lwt message ([@balloob] - [#9831]) ([device_tracker.owntracks docs])
|
||||
- Upgrade libnacl ([@fabaff] - [#9769]) ([device_tracker.owntracks docs])
|
||||
- Fixed reporting of vera UV sensors ([@alanfischer] - [#9838]) ([sensor.vera docs])
|
||||
- Update CODEOWNERS */axis.py ([@Kane610] - [#9823])
|
||||
- fix climate services (missing indentation, wrongly formatted example) ([@rytilahti] - [#9805])
|
||||
- Run initial generation for development mode ([@armills] - [#9826])
|
||||
- Add service descriptions ([@cgarwood] - [#9806]) ([__init__ docs])
|
||||
- Bugfix: Include MQTT schema ([@tinloaf] - [#9802]) ([climate.mqtt docs])
|
||||
- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
|
||||
- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841])
|
||||
- New PR ([@bachya] - [#9787]) ([camera.yi docs]) (new-platform)
|
||||
- Do not auto-install credstash ([@balloob] - [#9844])
|
||||
- Add namecheap DNS component ([@Munsio] - [#9821]) ([namecheapdns docs]) (new-platform)
|
||||
- Remove namecheap dns service ([@balloob] - [#9845]) ([namecheapdns docs])
|
||||
- Use the Last Seen attribute in unify ([@rbflurry] - [#8998]) ([device_tracker.unifi docs])
|
||||
- Add CAPSman master to mikrotik presence detection ([@icovada] - [#9729]) ([device_tracker.mikrotik docs])
|
||||
- File permissions fix ([@cgarwood] - [#9847]) ([map docs])
|
||||
- HassIO - TimeZone / Host services ([@pvizeli] - [#9846]) ([hassio docs])
|
||||
- Changing name of clicksendaudio component to clicksend_tts ([@jeroenterheerdt] - [#9859]) ([notify.clicksend_tts docs]) (breaking change)
|
||||
- Upgrade youtube_dl to 2017.10.12 ([@fabaff] - [#9862]) ([media_extractor docs])
|
||||
- Uptime sensor ([@fronzbot] - [#9856]) ([sensor.uptime docs]) (new-platform)
|
||||
- Darksky enhancements ([@rdbahm] - [#9851]) ([sensor.darksky docs])
|
||||
- Upgrade psutil to 5.4.0 ([@fabaff] - [#9869]) ([sensor.systemmonitor docs])
|
||||
- minimal fixes in the owntracks mqtt device tracker ([@azogue] - [#9866]) ([device_tracker.owntracks docs])
|
||||
- Cloud connection via aiohttp ([@balloob] - [#9860]) (new-platform)
|
||||
- handle OWM API error calls ([@azogue] - [#9865]) ([sensor.openweathermap docs]) ([weather.openweathermap docs])
|
||||
- Upgrade paho-mqtt to 1.3.1 ([@fabaff] - [#9874]) ([mqtt docs]) ([shiftr docs])
|
||||
- Fix for TypeError in synology camera ([@snjoetw] - [#9754]) ([camera.synology docs])
|
||||
- missing is_closed ( rflink cover fix ) ([@passie] - [#9776]) ([cover.rflink docs])
|
||||
- [light.tradfri] Fix transition time ([@lwis] - [#9785]) ([light.tradfri docs])
|
||||
- OwnTracks: Fix handler is None checking ([@balloob] - [#9794]) ([device_tracker.owntracks docs])
|
||||
- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841])
|
||||
- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
|
||||
- Fix #9839 ([@pschmitt] - [#9880]) ([media_player.liveboxplaytv docs])
|
||||
- Upgrade python-telegram-bot to 8.1.1 ([@azogue] - [#9882]) ([telegram_bot docs])
|
||||
- Xknx improvements ([@Julius2342] - [#9871]) ([knx docs]) ([climate.knx docs])
|
||||
- zha: Update to bellows 0.4.0 ([@rcloran] - [#9890]) ([zha docs]) ([sensor.zha docs])
|
||||
- Changing clicksendaudio to clicksend_tts in .coveragerc ([@jeroenterheerdt] - [#9900])
|
||||
- Added super attributes to Wink binary sensors ([@w1ll1am23] - [#9824]) ([binary_sensor.wink docs])
|
||||
- Release 0.55.2 ([@pvizeli] - [#9904])
|
||||
- Dependemcy version bump. ([@zabuldon] - [#9899]) ([device_tracker.mikrotik docs])
|
||||
- Update osramlightify.py ([@Bahnburner] - [#9905]) ([light.osramlightify docs])
|
||||
- Fixes ([@bachya] - [#9912]) ([switch.rainmachine docs])
|
||||
- Fix load of components without any config from packages ([@azogue] - [#9901]) (breaking change)
|
||||
- Fixes ([@bachya] - [#9911]) ([sensor.airvisual docs])
|
||||
- add last_action for xiaomi cube ([@danielhiversen] - [#9897]) ([binary_sensor.xiaomi_aqara docs])
|
||||
- Added support for Denon AVR-4810. ([@scarface-4711] - [#9887]) ([media_player.denonavr docs])
|
||||
- Recorder: Extra check to incoming connections which could be not sqlite3 ones ([@azogue] - [#9867])
|
||||
- Fix the resource naming in the UI ([@cgtobi] - [#9916]) ([sensor.systemmonitor docs]) (breaking change)
|
||||
- Update xiaomi_aqara.py ([@danielhiversen] - [#9920]) ([sensor.xiaomi_aqara docs])
|
||||
- Fix the resource naming in the UI ([@cgtobi] - [#9927]) ([sensor.glances docs])
|
||||
- Add transmission sensor: number of active torrents ([@mclem] - [#9914]) ([sensor.transmission docs])
|
||||
- Google Actions for Assistant ([@philk] - [#9632]) ([googleactions docs]) ([http docs]) (new-platform)
|
||||
- Allow flexible relayer url ([@balloob] - [#9939]) ([cloud.iot docs])
|
||||
- update async_timeout from v1.4.0 tp v2.0.0 ([@TopdRob] - [#9938])
|
||||
- Bump py-synology to 0.1.5 ([@arsaboo] - [#9932]) ([camera.synology docs])
|
||||
- Update aioimaplib from v0.7.12 to v0.7.13 ([@TopdRob] - [#9930]) ([sensor.imap docs])
|
||||
- A new platform for controlling Monoprice 6-Zone amplifier ([@etsinko] - [#9662]) ([media_player.monoprice docs]) (new-platform)
|
||||
- Align away state tag with device_trackers ([@PeteBa] - [#9884]) ([sensor.mqtt_room docs]) (breaking change)
|
||||
- Add serial sensor ([@fabaff] - [#9861]) ([sensor.serial docs]) (new-platform)
|
||||
- Fix missing timeout for Netatmo binary sensor ([@jabesq] - [#9850]) ([binary_sensor.netatmo docs])
|
||||
- Xiaomi config validation ([@danielhiversen] - [#9941]) ([xiaomi_aqara docs])
|
||||
- using defusedxml ElementTree for safer parsing of untrusted XML data ([@danielwelch] - [#9934]) ([device_tracker.upc_connect docs])
|
||||
- notify.xmpp - Add support for MUC ([@ldvc] - [#9931]) ([notify.xmpp docs])
|
||||
- FFmpeg 1.8 ([@pvizeli] - [#9944]) ([ffmpeg docs]) ([camera.ffmpeg docs]) ([camera.onvif docs]) ([camera.yi docs])
|
||||
- Changed returned attribute from "Game" to "game" ([@itchaboy] - [#9945]) ([sensor.steam_online docs])
|
||||
- Move 'lights' to const.py ([@fabaff] - [#9929]) ([abode docs]) ([vera docs]) ([light.template docs]) ([switch.flux docs])
|
||||
- Update directpy to 0.2 ([@arsaboo] - [#9948])
|
||||
- Update enocean to 0.40 ([@arsaboo] - [#9949]) ([enocean docs])
|
||||
- Update hikvision to 1.2 ([@arsaboo] - [#9953]) ([switch.hikvisioncam docs])
|
||||
- Update fritzhome to 1.0.3 ([@arsaboo] - [#9951]) ([switch.fritzdect docs])
|
||||
- Update fritzconnection to 0.6.5 ([@arsaboo] - [#9950]) ([device_tracker.fritz docs]) ([sensor.fritzbox_callmonitor docs]) ([sensor.fritzbox_netmonitor docs])
|
||||
- Upgraded pyhomematic ([@danielperna84] - [#9956]) ([homematic docs])
|
||||
- Add emeter attributes ([@gollo] - [#9903]) ([light.tplink docs])
|
||||
- Use default clientsession to stream synology video ([@snjoetw] - [#9959]) ([camera.synology docs])
|
||||
- Update ffmpeg 1.9 ([@pvizeli] - [#9963])
|
||||
- Improve SSL certs used by aiohttp ([@balloob] - [#9958]) ([cloud.iot docs])
|
||||
- Fix async probs ([@pvizeli] - [#9924])
|
||||
- Add Toon support ([@Boltgolt] - [#9483]) ([toon docs]) ([climate.toon docs]) ([sensor.toon docs]) ([switch.toon docs]) (new-platform)
|
||||
- [tradfri] Update pytradfri, simplify dependencies. ([@lwis] - [#9875]) ([tradfri docs]) ([light.tradfri docs]) ([sensor.tradfri docs])
|
||||
- Moved siren to Wink from switch ([@w1ll1am23] - [#9879]) ([wink docs]) ([switch.wink docs]) (breaking change)
|
||||
- Remove async_update ([@pvizeli] - [#9997])
|
||||
|
||||
[#8998]: https://github.com/home-assistant/home-assistant/pull/8998
|
||||
[#9138]: https://github.com/home-assistant/home-assistant/pull/9138
|
||||
[#9454]: https://github.com/home-assistant/home-assistant/pull/9454
|
||||
[#9483]: https://github.com/home-assistant/home-assistant/pull/9483
|
||||
[#9553]: https://github.com/home-assistant/home-assistant/pull/9553
|
||||
[#9594]: https://github.com/home-assistant/home-assistant/pull/9594
|
||||
[#9632]: https://github.com/home-assistant/home-assistant/pull/9632
|
||||
[#9654]: https://github.com/home-assistant/home-assistant/pull/9654
|
||||
[#9662]: https://github.com/home-assistant/home-assistant/pull/9662
|
||||
[#9664]: https://github.com/home-assistant/home-assistant/pull/9664
|
||||
[#9667]: https://github.com/home-assistant/home-assistant/pull/9667
|
||||
[#9681]: https://github.com/home-assistant/home-assistant/pull/9681
|
||||
[#9683]: https://github.com/home-assistant/home-assistant/pull/9683
|
||||
[#9699]: https://github.com/home-assistant/home-assistant/pull/9699
|
||||
[#9701]: https://github.com/home-assistant/home-assistant/pull/9701
|
||||
[#9705]: https://github.com/home-assistant/home-assistant/pull/9705
|
||||
[#9707]: https://github.com/home-assistant/home-assistant/pull/9707
|
||||
[#9708]: https://github.com/home-assistant/home-assistant/pull/9708
|
||||
[#9709]: https://github.com/home-assistant/home-assistant/pull/9709
|
||||
[#9711]: https://github.com/home-assistant/home-assistant/pull/9711
|
||||
[#9718]: https://github.com/home-assistant/home-assistant/pull/9718
|
||||
[#9719]: https://github.com/home-assistant/home-assistant/pull/9719
|
||||
[#9720]: https://github.com/home-assistant/home-assistant/pull/9720
|
||||
[#9722]: https://github.com/home-assistant/home-assistant/pull/9722
|
||||
[#9725]: https://github.com/home-assistant/home-assistant/pull/9725
|
||||
[#9726]: https://github.com/home-assistant/home-assistant/pull/9726
|
||||
[#9727]: https://github.com/home-assistant/home-assistant/pull/9727
|
||||
[#9729]: https://github.com/home-assistant/home-assistant/pull/9729
|
||||
[#9732]: https://github.com/home-assistant/home-assistant/pull/9732
|
||||
[#9736]: https://github.com/home-assistant/home-assistant/pull/9736
|
||||
[#9738]: https://github.com/home-assistant/home-assistant/pull/9738
|
||||
[#9745]: https://github.com/home-assistant/home-assistant/pull/9745
|
||||
[#9747]: https://github.com/home-assistant/home-assistant/pull/9747
|
||||
[#9753]: https://github.com/home-assistant/home-assistant/pull/9753
|
||||
[#9754]: https://github.com/home-assistant/home-assistant/pull/9754
|
||||
[#9758]: https://github.com/home-assistant/home-assistant/pull/9758
|
||||
[#9759]: https://github.com/home-assistant/home-assistant/pull/9759
|
||||
[#9760]: https://github.com/home-assistant/home-assistant/pull/9760
|
||||
[#9761]: https://github.com/home-assistant/home-assistant/pull/9761
|
||||
[#9763]: https://github.com/home-assistant/home-assistant/pull/9763
|
||||
[#9764]: https://github.com/home-assistant/home-assistant/pull/9764
|
||||
[#9767]: https://github.com/home-assistant/home-assistant/pull/9767
|
||||
[#9769]: https://github.com/home-assistant/home-assistant/pull/9769
|
||||
[#9770]: https://github.com/home-assistant/home-assistant/pull/9770
|
||||
[#9772]: https://github.com/home-assistant/home-assistant/pull/9772
|
||||
[#9774]: https://github.com/home-assistant/home-assistant/pull/9774
|
||||
[#9776]: https://github.com/home-assistant/home-assistant/pull/9776
|
||||
[#9780]: https://github.com/home-assistant/home-assistant/pull/9780
|
||||
[#9781]: https://github.com/home-assistant/home-assistant/pull/9781
|
||||
[#9784]: https://github.com/home-assistant/home-assistant/pull/9784
|
||||
[#9785]: https://github.com/home-assistant/home-assistant/pull/9785
|
||||
[#9787]: https://github.com/home-assistant/home-assistant/pull/9787
|
||||
[#9788]: https://github.com/home-assistant/home-assistant/pull/9788
|
||||
[#9794]: https://github.com/home-assistant/home-assistant/pull/9794
|
||||
[#9795]: https://github.com/home-assistant/home-assistant/pull/9795
|
||||
[#9798]: https://github.com/home-assistant/home-assistant/pull/9798
|
||||
[#9802]: https://github.com/home-assistant/home-assistant/pull/9802
|
||||
[#9805]: https://github.com/home-assistant/home-assistant/pull/9805
|
||||
[#9806]: https://github.com/home-assistant/home-assistant/pull/9806
|
||||
[#9807]: https://github.com/home-assistant/home-assistant/pull/9807
|
||||
[#9810]: https://github.com/home-assistant/home-assistant/pull/9810
|
||||
[#9814]: https://github.com/home-assistant/home-assistant/pull/9814
|
||||
[#9817]: https://github.com/home-assistant/home-assistant/pull/9817
|
||||
[#9821]: https://github.com/home-assistant/home-assistant/pull/9821
|
||||
[#9823]: https://github.com/home-assistant/home-assistant/pull/9823
|
||||
[#9824]: https://github.com/home-assistant/home-assistant/pull/9824
|
||||
[#9825]: https://github.com/home-assistant/home-assistant/pull/9825
|
||||
[#9826]: https://github.com/home-assistant/home-assistant/pull/9826
|
||||
[#9831]: https://github.com/home-assistant/home-assistant/pull/9831
|
||||
[#9835]: https://github.com/home-assistant/home-assistant/pull/9835
|
||||
[#9838]: https://github.com/home-assistant/home-assistant/pull/9838
|
||||
[#9841]: https://github.com/home-assistant/home-assistant/pull/9841
|
||||
[#9842]: https://github.com/home-assistant/home-assistant/pull/9842
|
||||
[#9844]: https://github.com/home-assistant/home-assistant/pull/9844
|
||||
[#9845]: https://github.com/home-assistant/home-assistant/pull/9845
|
||||
[#9846]: https://github.com/home-assistant/home-assistant/pull/9846
|
||||
[#9847]: https://github.com/home-assistant/home-assistant/pull/9847
|
||||
[#9850]: https://github.com/home-assistant/home-assistant/pull/9850
|
||||
[#9851]: https://github.com/home-assistant/home-assistant/pull/9851
|
||||
[#9856]: https://github.com/home-assistant/home-assistant/pull/9856
|
||||
[#9859]: https://github.com/home-assistant/home-assistant/pull/9859
|
||||
[#9860]: https://github.com/home-assistant/home-assistant/pull/9860
|
||||
[#9861]: https://github.com/home-assistant/home-assistant/pull/9861
|
||||
[#9862]: https://github.com/home-assistant/home-assistant/pull/9862
|
||||
[#9865]: https://github.com/home-assistant/home-assistant/pull/9865
|
||||
[#9866]: https://github.com/home-assistant/home-assistant/pull/9866
|
||||
[#9867]: https://github.com/home-assistant/home-assistant/pull/9867
|
||||
[#9869]: https://github.com/home-assistant/home-assistant/pull/9869
|
||||
[#9871]: https://github.com/home-assistant/home-assistant/pull/9871
|
||||
[#9874]: https://github.com/home-assistant/home-assistant/pull/9874
|
||||
[#9875]: https://github.com/home-assistant/home-assistant/pull/9875
|
||||
[#9879]: https://github.com/home-assistant/home-assistant/pull/9879
|
||||
[#9880]: https://github.com/home-assistant/home-assistant/pull/9880
|
||||
[#9882]: https://github.com/home-assistant/home-assistant/pull/9882
|
||||
[#9884]: https://github.com/home-assistant/home-assistant/pull/9884
|
||||
[#9887]: https://github.com/home-assistant/home-assistant/pull/9887
|
||||
[#9890]: https://github.com/home-assistant/home-assistant/pull/9890
|
||||
[#9897]: https://github.com/home-assistant/home-assistant/pull/9897
|
||||
[#9899]: https://github.com/home-assistant/home-assistant/pull/9899
|
||||
[#9900]: https://github.com/home-assistant/home-assistant/pull/9900
|
||||
[#9901]: https://github.com/home-assistant/home-assistant/pull/9901
|
||||
[#9903]: https://github.com/home-assistant/home-assistant/pull/9903
|
||||
[#9904]: https://github.com/home-assistant/home-assistant/pull/9904
|
||||
[#9905]: https://github.com/home-assistant/home-assistant/pull/9905
|
||||
[#9911]: https://github.com/home-assistant/home-assistant/pull/9911
|
||||
[#9912]: https://github.com/home-assistant/home-assistant/pull/9912
|
||||
[#9914]: https://github.com/home-assistant/home-assistant/pull/9914
|
||||
[#9916]: https://github.com/home-assistant/home-assistant/pull/9916
|
||||
[#9920]: https://github.com/home-assistant/home-assistant/pull/9920
|
||||
[#9924]: https://github.com/home-assistant/home-assistant/pull/9924
|
||||
[#9927]: https://github.com/home-assistant/home-assistant/pull/9927
|
||||
[#9929]: https://github.com/home-assistant/home-assistant/pull/9929
|
||||
[#9930]: https://github.com/home-assistant/home-assistant/pull/9930
|
||||
[#9931]: https://github.com/home-assistant/home-assistant/pull/9931
|
||||
[#9932]: https://github.com/home-assistant/home-assistant/pull/9932
|
||||
[#9934]: https://github.com/home-assistant/home-assistant/pull/9934
|
||||
[#9938]: https://github.com/home-assistant/home-assistant/pull/9938
|
||||
[#9939]: https://github.com/home-assistant/home-assistant/pull/9939
|
||||
[#9941]: https://github.com/home-assistant/home-assistant/pull/9941
|
||||
[#9944]: https://github.com/home-assistant/home-assistant/pull/9944
|
||||
[#9945]: https://github.com/home-assistant/home-assistant/pull/9945
|
||||
[#9948]: https://github.com/home-assistant/home-assistant/pull/9948
|
||||
[#9949]: https://github.com/home-assistant/home-assistant/pull/9949
|
||||
[#9950]: https://github.com/home-assistant/home-assistant/pull/9950
|
||||
[#9951]: https://github.com/home-assistant/home-assistant/pull/9951
|
||||
[#9953]: https://github.com/home-assistant/home-assistant/pull/9953
|
||||
[#9956]: https://github.com/home-assistant/home-assistant/pull/9956
|
||||
[#9958]: https://github.com/home-assistant/home-assistant/pull/9958
|
||||
[#9959]: https://github.com/home-assistant/home-assistant/pull/9959
|
||||
[#9963]: https://github.com/home-assistant/home-assistant/pull/9963
|
||||
[#9997]: https://github.com/home-assistant/home-assistant/pull/9997
|
||||
[@Bahnburner]: https://github.com/Bahnburner
|
||||
[@Boltgolt]: https://github.com/Boltgolt
|
||||
[@ChristianKuehnel]: https://github.com/ChristianKuehnel
|
||||
[@GenericStudent]: https://github.com/GenericStudent
|
||||
[@Julius2342]: https://github.com/Julius2342
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@MisterWil]: https://github.com/MisterWil
|
||||
[@Munsio]: https://github.com/Munsio
|
||||
[@PeteBa]: https://github.com/PeteBa
|
||||
[@TopdRob]: https://github.com/TopdRob
|
||||
[@alanfischer]: https://github.com/alanfischer
|
||||
[@andrey-git]: https://github.com/andrey-git
|
||||
[@armills]: https://github.com/armills
|
||||
[@arsaboo]: https://github.com/arsaboo
|
||||
[@azogue]: https://github.com/azogue
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@cgarwood]: https://github.com/cgarwood
|
||||
[@cgtobi]: https://github.com/cgtobi
|
||||
[@danielhiversen]: https://github.com/danielhiversen
|
||||
[@danielperna84]: https://github.com/danielperna84
|
||||
[@danielwelch]: https://github.com/danielwelch
|
||||
[@etsinko]: https://github.com/etsinko
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@flowolf]: https://github.com/flowolf
|
||||
[@fronzbot]: https://github.com/fronzbot
|
||||
[@gollo]: https://github.com/gollo
|
||||
[@happyleavesaoc]: https://github.com/happyleavesaoc
|
||||
[@icovada]: https://github.com/icovada
|
||||
[@itchaboy]: https://github.com/itchaboy
|
||||
[@jabesq]: https://github.com/jabesq
|
||||
[@jeroenterheerdt]: https://github.com/jeroenterheerdt
|
||||
[@ldvc]: https://github.com/ldvc
|
||||
[@lwis]: https://github.com/lwis
|
||||
[@mclem]: https://github.com/mclem
|
||||
[@passie]: https://github.com/passie
|
||||
[@philk]: https://github.com/philk
|
||||
[@pschmitt]: https://github.com/pschmitt
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@rbflurry]: https://github.com/rbflurry
|
||||
[@rcloran]: https://github.com/rcloran
|
||||
[@rdbahm]: https://github.com/rdbahm
|
||||
[@ryanm101]: https://github.com/ryanm101
|
||||
[@rytilahti]: https://github.com/rytilahti
|
||||
[@scarface-4711]: https://github.com/scarface-4711
|
||||
[@sdague]: https://github.com/sdague
|
||||
[@snjoetw]: https://github.com/snjoetw
|
||||
[@syssi]: https://github.com/syssi
|
||||
[@tchellomello]: https://github.com/tchellomello
|
||||
[@tinloaf]: https://github.com/tinloaf
|
||||
[@vickyg3]: https://github.com/vickyg3
|
||||
[@w1ll1am23]: https://github.com/w1ll1am23
|
||||
[@webworxshop]: https://github.com/webworxshop
|
||||
[@zabuldon]: https://github.com/zabuldon
|
||||
[@ziotibia81]: https://github.com/ziotibia81
|
||||
[__init__ docs]: https://home-assistant.io/components/__init__/
|
||||
[abode docs]: https://home-assistant.io/components/abode/
|
||||
[alarm_control_panel.arlo docs]: https://home-assistant.io/components/alarm_control_panel.arlo/
|
||||
[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
|
||||
[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
|
||||
[arlo docs]: https://home-assistant.io/components/arlo/
|
||||
[automation.event docs]: https://home-assistant.io/docs/automation/trigger/#event-trigger
|
||||
[automation.numeric_state docs]: https://home-assistant.io/docs/automation/trigger/#numeric-state-trigger
|
||||
[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
|
||||
[binary_sensor.iss docs]: https://home-assistant.io/components/binary_sensor.iss/
|
||||
[binary_sensor.netatmo docs]: https://home-assistant.io/components/binary_sensor.netatmo/
|
||||
[binary_sensor.skybell docs]: https://home-assistant.io/components/binary_sensor.skybell/
|
||||
[binary_sensor.template docs]: https://home-assistant.io/components/binary_sensor.template/
|
||||
[binary_sensor.tesla docs]: https://home-assistant.io/components/binary_sensor.tesla/
|
||||
[binary_sensor.wink docs]: https://home-assistant.io/components/binary_sensor.wink/
|
||||
[binary_sensor.xiaomi_aqara docs]: https://home-assistant.io/components/binary_sensor.xiaomi_aqara/
|
||||
[camera.arlo docs]: https://home-assistant.io/components/camera.arlo/
|
||||
[camera.ffmpeg docs]: https://home-assistant.io/components/camera.ffmpeg/
|
||||
[camera.onvif docs]: https://home-assistant.io/components/camera.onvif/
|
||||
[camera.skybell docs]: https://home-assistant.io/components/camera.skybell/
|
||||
[camera.synology docs]: https://home-assistant.io/components/camera.synology/
|
||||
[camera.yi docs]: https://home-assistant.io/components/camera.yi/
|
||||
[climate.eq3btsmart docs]: https://home-assistant.io/components/climate.eq3btsmart/
|
||||
[climate.knx docs]: https://home-assistant.io/components/climate.knx/
|
||||
[climate.mqtt docs]: https://home-assistant.io/components/climate.mqtt/
|
||||
[climate.tesla docs]: https://home-assistant.io/components/climate.tesla/
|
||||
[climate.toon docs]: https://home-assistant.io/components/climate.toon/
|
||||
[cloud.iot docs]: https://home-assistant.io/components/cloud.iot/
|
||||
[cover.rflink docs]: https://home-assistant.io/components/cover.rflink/
|
||||
[device_tracker docs]: https://home-assistant.io/components/device_tracker/
|
||||
[device_tracker.fritz docs]: https://home-assistant.io/components/device_tracker.fritz/
|
||||
[device_tracker.mikrotik docs]: https://home-assistant.io/components/device_tracker.mikrotik/
|
||||
[device_tracker.netgear docs]: https://home-assistant.io/components/device_tracker.netgear/
|
||||
[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
|
||||
[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
|
||||
[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/
|
||||
[device_tracker.upc_connect docs]: https://home-assistant.io/components/device_tracker.upc_connect/
|
||||
[enocean docs]: https://home-assistant.io/components/enocean/
|
||||
[ffmpeg docs]: https://home-assistant.io/components/ffmpeg/
|
||||
[googleactions docs]: https://home-assistant.io/components/googleactions/
|
||||
[hassio docs]: https://home-assistant.io/components/hassio/
|
||||
[homematic docs]: https://home-assistant.io/components/homematic/
|
||||
[http docs]: https://home-assistant.io/components/http/
|
||||
[knx docs]: https://home-assistant.io/components/knx/
|
||||
[light.hue docs]: https://home-assistant.io/components/light.hue/
|
||||
[light.mqtt_json docs]: https://home-assistant.io/components/light.mqtt_json/
|
||||
[light.osramlightify docs]: https://home-assistant.io/components/light.osramlightify/
|
||||
[light.skybell docs]: https://home-assistant.io/components/light.skybell/
|
||||
[light.template docs]: https://home-assistant.io/components/light.template/
|
||||
[light.tplink docs]: https://home-assistant.io/components/light.tplink/
|
||||
[light.tradfri docs]: https://home-assistant.io/components/light.tradfri/
|
||||
[light.yeelight docs]: https://home-assistant.io/components/light.yeelight/
|
||||
[lock.tesla docs]: https://home-assistant.io/components/lock.tesla/
|
||||
[map docs]: https://home-assistant.io/components/map/
|
||||
[media_extractor docs]: https://home-assistant.io/components/media_extractor/
|
||||
[media_player.denon docs]: https://home-assistant.io/components/media_player.denon/
|
||||
[media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/
|
||||
[media_player.dunehd docs]: https://home-assistant.io/components/media_player.dunehd/
|
||||
[media_player.liveboxplaytv docs]: https://home-assistant.io/components/media_player.liveboxplaytv/
|
||||
[media_player.monoprice docs]: https://home-assistant.io/components/media_player.monoprice/
|
||||
[media_player.plex docs]: https://home-assistant.io/components/media_player.plex/
|
||||
[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/
|
||||
[modbus docs]: https://home-assistant.io/components/modbus/
|
||||
[mqtt docs]: https://home-assistant.io/components/mqtt/
|
||||
[namecheapdns docs]: https://home-assistant.io/components/namecheapdns/
|
||||
[notify.clicksend_tts docs]: https://home-assistant.io/components/notify.clicksend_tts/
|
||||
[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
|
||||
[notify.rocketchat docs]: https://home-assistant.io/components/notify.rocketchat/
|
||||
[notify.xmpp docs]: https://home-assistant.io/components/notify.xmpp/
|
||||
[python_script docs]: https://home-assistant.io/components/python_script/
|
||||
[raincloud docs]: https://home-assistant.io/components/raincloud/
|
||||
[sensor.abode docs]: https://home-assistant.io/components/sensor.abode/
|
||||
[sensor.airvisual docs]: https://home-assistant.io/components/sensor.airvisual/
|
||||
[sensor.android_ip_webcam docs]: https://home-assistant.io/components/sensor.android_ip_webcam/
|
||||
[sensor.arlo docs]: https://home-assistant.io/components/sensor.arlo/
|
||||
[sensor.arwn docs]: https://home-assistant.io/components/sensor.arwn/
|
||||
[sensor.darksky docs]: https://home-assistant.io/components/sensor.darksky/
|
||||
[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
|
||||
[sensor.fritzbox_callmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_callmonitor/
|
||||
[sensor.fritzbox_netmonitor docs]: https://home-assistant.io/components/sensor.fritzbox_netmonitor/
|
||||
[sensor.glances docs]: https://home-assistant.io/components/sensor.glances/
|
||||
[sensor.imap docs]: https://home-assistant.io/components/sensor.imap/
|
||||
[sensor.ios docs]: https://home-assistant.io/components/sensor.ios/
|
||||
[sensor.mqtt_room docs]: https://home-assistant.io/components/sensor.mqtt_room/
|
||||
[sensor.netdata docs]: https://home-assistant.io/components/sensor.netdata/
|
||||
[sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/
|
||||
[sensor.raincloud docs]: https://home-assistant.io/components/sensor.raincloud/
|
||||
[sensor.ring docs]: https://home-assistant.io/components/sensor.ring/
|
||||
[sensor.serial docs]: https://home-assistant.io/components/sensor.serial/
|
||||
[sensor.skybell docs]: https://home-assistant.io/components/sensor.skybell/
|
||||
[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
|
||||
[sensor.statistics docs]: https://home-assistant.io/components/sensor.statistics/
|
||||
[sensor.steam_online docs]: https://home-assistant.io/components/sensor.steam_online/
|
||||
[sensor.systemmonitor docs]: https://home-assistant.io/components/sensor.systemmonitor/
|
||||
[sensor.tesla docs]: https://home-assistant.io/components/sensor.tesla/
|
||||
[sensor.toon docs]: https://home-assistant.io/components/sensor.toon/
|
||||
[sensor.tradfri docs]: https://home-assistant.io/components/sensor.tradfri/
|
||||
[sensor.transmission docs]: https://home-assistant.io/components/sensor.transmission/
|
||||
[sensor.travisci docs]: https://home-assistant.io/components/sensor.travisci/
|
||||
[sensor.uptime docs]: https://home-assistant.io/components/sensor.uptime/
|
||||
[sensor.vera docs]: https://home-assistant.io/components/sensor.vera/
|
||||
[sensor.xiaomi_aqara docs]: https://home-assistant.io/components/sensor.xiaomi_aqara/
|
||||
[sensor.zha docs]: https://home-assistant.io/components/sensor.zha/
|
||||
[shiftr docs]: https://home-assistant.io/components/shiftr/
|
||||
[skybell docs]: https://home-assistant.io/components/skybell/
|
||||
[switch.flux docs]: https://home-assistant.io/components/switch.flux/
|
||||
[switch.fritzdect docs]: https://home-assistant.io/components/switch.fritzdect/
|
||||
[switch.hikvisioncam docs]: https://home-assistant.io/components/switch.hikvisioncam/
|
||||
[switch.rainmachine docs]: https://home-assistant.io/components/switch.rainmachine/
|
||||
[switch.skybell docs]: https://home-assistant.io/components/switch.skybell/
|
||||
[switch.tesla docs]: https://home-assistant.io/components/switch.tesla/
|
||||
[switch.toon docs]: https://home-assistant.io/components/switch.toon/
|
||||
[switch.tplink docs]: https://home-assistant.io/components/switch.tplink/
|
||||
[switch.wink docs]: https://home-assistant.io/components/switch.wink/
|
||||
[switch.xiaomi_plug docs]: https://home-assistant.io/components/switch.xiaomi_plug/
|
||||
[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
|
||||
[tesla docs]: https://home-assistant.io/components/tesla/
|
||||
[toon docs]: https://home-assistant.io/components/toon/
|
||||
[tradfri docs]: https://home-assistant.io/components/tradfri/
|
||||
[vacuum docs]: https://home-assistant.io/components/vacuum/
|
||||
[vacuum.dyson docs]: https://home-assistant.io/components/vacuum.dyson/
|
||||
[vacuum.mqtt docs]: https://home-assistant.io/components/vacuum.mqtt/
|
||||
[vera docs]: https://home-assistant.io/components/vera/
|
||||
[weather.openweathermap docs]: https://home-assistant.io/components/weather.openweathermap/
|
||||
[wink docs]: https://home-assistant.io/components/wink/
|
||||
[xiaomi_aqara docs]: https://home-assistant.io/components/xiaomi_aqara/
|
||||
[zha docs]: https://home-assistant.io/components/zha/
|
||||
|
@ -2,7 +2,7 @@
|
||||
layout: page
|
||||
title: "Credits"
|
||||
description: "Credits for the developers who contributed to Home Assistant."
|
||||
date: 2017-10-07 22:31:01 +0000
|
||||
date: 2017-10-21 20:19:43 +0000
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
@ -13,23 +13,24 @@ 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 "5830 total commits to the home-assistant organization, 3489 commits to home-assistant, 1259 commits to home-assistant.github.io, 606 commits to home-assistant-polymer, 244 commits to home-assistant-js, 116 commits to netdisco, 42 commits to home-assistant-js-websocket, 24 commits to hass-release, 12 commits to home-assistant-assets, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 5 commits to LabelBot, 4 commits to hassio, 3 commits to hassio-addons, 2 commits to issue-bot, 2 commits to hassio-addons-example, 2 commits to lambda-home-assistant-github, 2 commits to python-hassbian, 1 commit to home-assistant-notebooks, 1 commit to hassio-build, 1 commit to home-assistant-iOS")
|
||||
- [Paulus Schoutsen (@balloob)](https://github.com/balloob "5857 total commits to the home-assistant organization, 3502 commits to home-assistant, 1270 commits to home-assistant.github.io, 607 commits to home-assistant-polymer, 244 commits to home-assistant-js, 116 commits to netdisco, 44 commits to home-assistant-js-websocket, 24 commits to hass-release, 12 commits to home-assistant-assets, 8 commits to example-custom-config, 7 commits to micropython-home-assistant, 5 commits to LabelBot, 4 commits to hassio, 3 commits to hassio-addons, 2 commits to python-hassbian, 2 commits to issue-bot, 2 commits to lambda-home-assistant-github, 2 commits to hassio-addons-example, 1 commit to hassio-build, 1 commit to home-assistant-notebooks, 1 commit to home-assistant-iOS")
|
||||
|
||||
### {% linkable_title Contributors %}
|
||||
|
||||
(in alphabetical order)
|
||||
|
||||
- [Aaron Bach (@bachya)](https://github.com/bachya "17 total commits to the home-assistant organization, 12 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
- [Aaron Bach (@bachya)](https://github.com/bachya "25 total commits to the home-assistant organization, 17 commits to home-assistant, 8 commits to home-assistant.github.io")
|
||||
- [Aaron Linville (@linville)](https://github.com/linville "2 total commits to the home-assistant organization, 2 commits to appdaemon")
|
||||
- [Aaron Morris (@Morrisai)](https://github.com/Morrisai "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Aaron Polley (@xarnze)](https://github.com/xarnze "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Abhishek Anand (@aa755)](https://github.com/aa755 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Abílio Costa (@abmantis)](https://github.com/abmantis "15 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Abílio Costa (@abmantis)](https://github.com/abmantis "17 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io, 1 commit to home-assistant-js-websocket, 1 commit to netdisco, 1 commit to home-assistant-polymer")
|
||||
- [Adam (@SilvrrGIT)](https://github.com/SilvrrGIT "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io")
|
||||
- [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 Cooper (@GenericStudent)](https://github.com/GenericStudent "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Adam Dullage (@Dullage)](https://github.com/Dullage "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Adam Garcia (@pancho-villa)](https://github.com/pancho-villa "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Adam Mills (@armills)](https://github.com/armills "211 total commits to the home-assistant organization, 134 commits to home-assistant, 38 commits to home-assistant.github.io, 35 commits to home-assistant-polymer, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant")
|
||||
- [Adam Mills (@armills)](https://github.com/armills "216 total commits to the home-assistant organization, 136 commits to home-assistant, 39 commits to home-assistant.github.io, 37 commits to home-assistant-polymer, 3 commits to home-assistant-js, 1 commit to homebridge-homeassistant")
|
||||
- [Adam Stone (@astone123)](https://github.com/astone123 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Adrian Popa (@mad-ady)](https://github.com/mad-ady "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Adrien Ball (@adrienball)](https://github.com/adrienball "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -38,14 +39,14 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [aetolus (@aetolus)](https://github.com/aetolus "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [AHS (@ahofelt)](https://github.com/ahofelt "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Alan Bowman (@alanbowman)](https://github.com/alanbowman "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [Alan Fischer (@alanfischer)](https://github.com/alanfischer "16 total commits to the home-assistant organization, 13 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Alan Fischer (@alanfischer)](https://github.com/alanfischer "17 total commits to the home-assistant organization, 14 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Alasdair Nicol (@alasdairnicol)](https://github.com/alasdairnicol "2 total commits to the home-assistant organization, 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")
|
||||
- [Alessandro Mogavero (@alexmogavero)](https://github.com/alexmogavero "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Alex (@asbach)](https://github.com/asbach "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Alex (@alexrockt)](https://github.com/alexrockt "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Alex (@MungoRae)](https://github.com/MungoRae "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Alex (@asbach)](https://github.com/asbach "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Alex Harvey (@infamy)](https://github.com/infamy "25 total commits to the home-assistant organization, 14 commits to home-assistant, 11 commits to home-assistant.github.io")
|
||||
- [Alex Mekkering (@AlexMekkering)](https://github.com/AlexMekkering "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Alex MF (@adsmf)](https://github.com/adsmf "1 total commits to the home-assistant organization, 1 commit to hassio-addons")
|
||||
@ -56,18 +57,19 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Alfie Day (@Azelphur)](https://github.com/Azelphur "12 total commits to the home-assistant organization, 12 commits to home-assistant")
|
||||
- [Aliaksandr (@minchik)](https://github.com/minchik "7 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to appdaemon, 2 commits to home-assistant")
|
||||
- [Allan Glen (@allanglen)](https://github.com/allanglen "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "90 total commits to the home-assistant organization, 57 commits to home-assistant.github.io, 31 commits to home-assistant, 1 commit to hassio-addons, 1 commit to pi-gen")
|
||||
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "97 total commits to the home-assistant organization, 58 commits to home-assistant.github.io, 37 commits to home-assistant, 1 commit to hassio-addons, 1 commit to pi-gen")
|
||||
- [amigian74 (@amigian74)](https://github.com/amigian74 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [amorsillo (@AndrewMorsillo)](https://github.com/AndrewMorsillo "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "102 total commits to the home-assistant organization, 74 commits to home-assistant, 26 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Andrea Falcone (@asfalcone)](https://github.com/asfalcone "5 total commits to the home-assistant organization, 5 commits to issue-bot")
|
||||
- [Andreas Cambitsis (@acambitsis)](https://github.com/acambitsis "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Andreas Jacobsen (@andreasjacobsen93)](https://github.com/andreasjacobsen93 "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 1 commit to hassio-addons, 1 commit to home-assistant")
|
||||
- [Andreas Jacobsen (@andreasjacobsen93)](https://github.com/andreasjacobsen93 "9 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to hassio-addons, 1 commit to home-assistant")
|
||||
- [Andreas Rammhold (@andir)](https://github.com/andir "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Andreas Renberg (@IQAndreas)](https://github.com/IQAndreas "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Andreea-Daniela Ene (@AndreeaEne)](https://github.com/AndreeaEne "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Andrew (@aneisch)](https://github.com/aneisch "5 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Andrej Friesen (@ajfriesen)](https://github.com/ajfriesen "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Andrew (@aoakeson)](https://github.com/aoakeson "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Andrew (@aneisch)](https://github.com/aneisch "5 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "606 total commits to the home-assistant organization, 475 commits to appdaemon, 88 commits to hadashboard, 25 commits to scenegen, 18 commits to home-assistant.github.io")
|
||||
- [Andrew LeCody (@aceat64)](https://github.com/aceat64 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Andrew Smith (@andrewmichaelsmith)](https://github.com/andrewmichaelsmith "2 total commits to the home-assistant organization, 2 commits to pi-gen")
|
||||
@ -75,7 +77,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 "177 total commits to the home-assistant organization, 88 commits to home-assistant, 61 commits to home-assistant-polymer, 28 commits to home-assistant.github.io")
|
||||
- [Andrey (@andrey-git)](https://github.com/andrey-git "182 total commits to the home-assistant organization, 89 commits to home-assistant, 63 commits to home-assistant-polymer, 30 commits to home-assistant.github.io")
|
||||
- [Andrey Kupreychik (@foxel)](https://github.com/foxel "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [Andrzej (@andriej)](https://github.com/andriej "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Andréas Lundgren (@adevade)](https://github.com/adevade "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -95,11 +97,11 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [arjenfvellinga (@arjenfvellinga)](https://github.com/arjenfvellinga "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Arno (@aetjansen)](https://github.com/aetjansen "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [ArrayLabs (@arraylabs)](https://github.com/arraylabs "7 total commits to the home-assistant organization, 5 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [arretx (@arretx)](https://github.com/arretx "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [arretx (@arretx)](https://github.com/arretx "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Arthur Leonard Andersen (@leoc)](https://github.com/leoc "9 total commits to the home-assistant organization, 9 commits to home-assistant")
|
||||
- [Arttu mahlakaarto (@amahlaka)](https://github.com/amahlaka "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [ashev (@ashev)](https://github.com/ashev "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Ashton Campbell (@AshtonCampbell)](https://github.com/AshtonCampbell "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Ashton Campbell (@AshtonCampbell)](https://github.com/AshtonCampbell "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Assaf Inbal (@shmuelzon)](https://github.com/shmuelzon "12 total commits to the home-assistant organization, 9 commits to homebridge-homeassistant, 3 commits to home-assistant")
|
||||
- [Audric Schiltknecht (@chemicalstorm)](https://github.com/chemicalstorm "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Audun Ytterdal (@auduny)](https://github.com/auduny "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -107,6 +109,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "2 total commits to the home-assistant organization, 1 commit to hadashboard, 1 commit to pi-gen")
|
||||
- [azeroth12 (@azeroth12)](https://github.com/azeroth12 "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [Bahnburner (@Bahnburner)](https://github.com/Bahnburner "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Barry Williams (@bazwilliams)](https://github.com/bazwilliams "10 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to netdisco, 2 commits to home-assistant.github.io")
|
||||
- [Bart274 (@Bart274)](https://github.com/Bart274 "26 total commits to the home-assistant organization, 17 commits to home-assistant, 8 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Bas Schipper (@basschipper)](https://github.com/basschipper "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
@ -121,15 +124,14 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Benjamin Affolter (@bliemli)](https://github.com/bliemli "31 total commits to the home-assistant organization, 31 commits to home-assistant-ansible")
|
||||
- [Benjamin Parzella (@bparzella)](https://github.com/bparzella "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Benoit BESSET (@bbesset)](https://github.com/bbesset "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [bergemalm (@bergemalm)](https://github.com/bergemalm "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [bestlibre (@bestlibre)](https://github.com/bestlibre "15 total commits to the home-assistant organization, 8 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to hassio, 1 commit to hassio-build")
|
||||
- [bestlibre (@bestlibre)](https://github.com/bestlibre "15 total commits to the home-assistant organization, 8 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to hassio-build, 1 commit to hassio")
|
||||
- [BigMoby (@bigmoby)](https://github.com/bigmoby "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Bill Nelson (@xhostplus)](https://github.com/xhostplus "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [BioSehnsucht (@BioSehnsucht)](https://github.com/BioSehnsucht "12 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 3 commits to home-assistant, 2 commits to home-assistant-polymer")
|
||||
- [Bjarni Ivarsson (@bjarniivarsson)](https://github.com/bjarniivarsson "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant-polymer")
|
||||
- [bl8rnr (@bl8rnr)](https://github.com/bl8rnr "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Blanyal D'Souza (@blanyal)](https://github.com/blanyal "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Blender3D (@Blender3D)](https://github.com/Blender3D "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Boced66 (@boced66)](https://github.com/boced66 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [boojew (@boojew)](https://github.com/boojew "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Boris K (@bokub)](https://github.com/bokub "11 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 5 commits to home-assistant")
|
||||
- [Boyi C (@fanthos)](https://github.com/fanthos "9 total commits to the home-assistant organization, 4 commits to home-assistant-polymer, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
@ -155,26 +157,27 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Bruno Adele (@badele)](https://github.com/badele "22 total commits to the home-assistant organization, 22 commits to home-assistant")
|
||||
- [Bruno Binet (@bbinet)](https://github.com/bbinet "1 total commits to the home-assistant organization, 1 commit to hassio-build")
|
||||
- [Bryce Edwards (@hoopty)](https://github.com/hoopty "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [c727 (@c727)](https://github.com/c727 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Caius Cioran (@caiuspb)](https://github.com/caiuspb "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Caleb (@finish06)](https://github.com/finish06 "7 total commits to the home-assistant organization, 7 commits to home-assistant")
|
||||
- [Cameron Bulock (@cbulock)](https://github.com/cbulock "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant")
|
||||
- [Carlo Costanzo (@CCOSTAN)](https://github.com/CCOSTAN "88 total commits to the home-assistant organization, 80 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to fabric-home-assistant, 1 commit to hassbian-scripts, 1 commit to homebridge-homeassistant")
|
||||
- [carlosmgr (@carlosmgr)](https://github.com/carlosmgr "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Carter (@BluGeni)](https://github.com/BluGeni "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [cdce8p (@cdce8p)](https://github.com/cdce8p "7 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [cdce8p (@cdce8p)](https://github.com/cdce8p "8 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Cecron (@Cecron)](https://github.com/Cecron "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [Cenk Gündoğan (@cgundogan)](https://github.com/cgundogan "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [cgtobi (@cgtobi)](https://github.com/cgtobi "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [cgtobi (@cgtobi)](https://github.com/cgtobi "10 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 5 commits to home-assistant")
|
||||
- [chanders (@chanders)](https://github.com/chanders "2 total commits to the home-assistant organization, 2 commits to hadashboard")
|
||||
- [Charles Blonde (@CharlesBlonde)](https://github.com/CharlesBlonde "19 total commits to the home-assistant organization, 12 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Charles Garwood (@cgarwood)](https://github.com/cgarwood "14 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Charles Spirakis (@srcLurker)](https://github.com/srcLurker "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Chayoung You (@yous)](https://github.com/yous "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Check your git settings! (@invalid-email-address)](https://github.com/invalid-email-address "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Chema García (@sch3m4)](https://github.com/sch3m4 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Chia-liang Kao (@clkao)](https://github.com/clkao "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Chris (@chennin)](https://github.com/chennin "15 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Chris (@firstof9)](https://github.com/firstof9 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Chris (@chennin)](https://github.com/chennin "15 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Chris 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")
|
||||
@ -186,17 +189,15 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Christian Brædstrup (@LinuxChristian)](https://github.com/LinuxChristian "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Christian Lasarczyk (@ChrisLasar)](https://github.com/ChrisLasar "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
- [ChristianKuehnel (@ChristianKuehnel)](https://github.com/ChristianKuehnel "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [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")
|
||||
- [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 "3 total commits to the home-assistant organization, 3 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")
|
||||
- [Claus F. Strasburger (@cfstras)](https://github.com/cfstras "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Clemens Wolff (@c-w)](https://github.com/c-w "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [codeavenger07 (@codeavenger07)](https://github.com/codeavenger07 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Colin Dunn (@colindunn)](https://github.com/colindunn "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Colin O'Dell (@colinodell)](https://github.com/colinodell "24 total commits to the home-assistant organization, 13 commits to home-assistant, 11 commits to home-assistant.github.io")
|
||||
- [Conrad Juhl Andersen (@cnrd)](https://github.com/cnrd "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -206,9 +207,9 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Corey Pauley (@devspacenine)](https://github.com/devspacenine "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [corneyl (@corneyl)](https://github.com/corneyl "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Craig J. Ward (@wardcraigj)](https://github.com/wardcraigj "14 total commits to the home-assistant organization, 9 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
- [cribbstechnologies (@cribbstechnologies)](https://github.com/cribbstechnologies "42 total commits to the home-assistant organization, 27 commits to home-assistant, 13 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [cribbstechnologies (@cribbstechnologies)](https://github.com/cribbstechnologies "43 total commits to the home-assistant organization, 27 commits to home-assistant, 14 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [CTLS (@CTLS)](https://github.com/CTLS "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Dale Higgs (@dale3h)](https://github.com/dale3h "32 total commits to the home-assistant organization, 20 commits to home-assistant.github.io, 10 commits to home-assistant, 1 commit to hassbot, 1 commit to homebridge-homeassistant")
|
||||
- [Dale Higgs (@dale3h)](https://github.com/dale3h "33 total commits to the home-assistant organization, 21 commits to home-assistant.github.io, 10 commits to home-assistant, 1 commit to hassbot, 1 commit to homebridge-homeassistant")
|
||||
- [Dan (@danieljkemp)](https://github.com/danieljkemp "23 total commits to the home-assistant organization, 16 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Dan Chen (@djchen)](https://github.com/djchen "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "14 total commits to the home-assistant organization, 12 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
@ -218,17 +219,17 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Dan Sarginson (@dansarginson)](https://github.com/dansarginson "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Dan Smith (@kk7ds)](https://github.com/kk7ds "84 total commits to the home-assistant organization, 68 commits to home-assistant, 14 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Dan Sullivan (@dansullivan86)](https://github.com/dansullivan86 "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Dan Van Brunt (@iDVB)](https://github.com/iDVB "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Dani (@danichispa)](https://github.com/danichispa "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
|
||||
- [Daniel Escoz (@Darkhogg)](https://github.com/Darkhogg "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "341 total commits to the home-assistant organization, 233 commits to home-assistant, 106 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "352 total commits to the home-assistant organization, 237 commits to home-assistant, 113 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Daniel Matuschek (@usul27)](https://github.com/usul27 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "63 total commits to the home-assistant organization, 34 commits to home-assistant.github.io, 27 commits to home-assistant, 2 commits to hassio-addons")
|
||||
- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "64 total commits to the home-assistant organization, 34 commits to home-assistant.github.io, 28 commits to home-assistant, 2 commits to hassio-addons")
|
||||
- [Daniel Peukert (@dpeukert)](https://github.com/dpeukert "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Daniel Schaal (@schaal)](https://github.com/schaal "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Daniel Stone (@daniel-stoneuk)](https://github.com/daniel-stoneuk "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Daniel Trnka (@trnila)](https://github.com/trnila "2 total commits to the home-assistant organization, 2 commits to appdaemon")
|
||||
- [Daniel Watkins (@OddBloke)](https://github.com/OddBloke "4 total commits to the home-assistant organization, 4 commits to home-assistant-ansible")
|
||||
- [Daniel Welch (@danielwelch)](https://github.com/danielwelch "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Danijel Stojnic (@danijelst)](https://github.com/danijelst "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Daniyar Yeralin (@yeralin)](https://github.com/yeralin "2 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant, 1 commit to home-assistant")
|
||||
- [dasos (@dasos)](https://github.com/dasos "10 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
@ -251,52 +252,45 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Dawid Wróbel (@wrobelda)](https://github.com/wrobelda "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Dean Camera (@abcminiuser)](https://github.com/abcminiuser "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Dean Galvin (@FreekingDean)](https://github.com/FreekingDean "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [deisi (@deisi)](https://github.com/deisi "12 total commits to the home-assistant organization, 10 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [demonspork (@demonspork)](https://github.com/demonspork "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [deisi (@deisi)](https://github.com/deisi "10 total commits to the home-assistant organization, 10 commits to home-assistant")
|
||||
- [Denix (@denics)](https://github.com/denics "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Dennis de Greef (@dennisdegreef)](https://github.com/dennisdegreef "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Dennis Karpienski (@TheRealLink)](https://github.com/TheRealLink "24 total commits to the home-assistant organization, 15 commits to home-assistant-polymer, 6 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Dennis Sutch (@sutch)](https://github.com/sutch "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [dersger (@dersger)](https://github.com/dersger "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Derek (@itchaboy)](https://github.com/itchaboy "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [dersger (@dersger)](https://github.com/dersger "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [devdelay (@devdelay)](https://github.com/devdelay "16 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 5 commits to home-assistant, 4 commits to homebridge-homeassistant")
|
||||
- [Diogo Gomes (@dgomes)](https://github.com/dgomes "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Diogo Soares (@diogos88)](https://github.com/diogos88 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Dougal Matthews (@d0ugal)](https://github.com/d0ugal "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [dpressle (@dpressle)](https://github.com/dpressle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [dramamoose (@dramamoose)](https://github.com/dramamoose "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [DrewSK (@dzsquared)](https://github.com/dzsquared "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [DubhAd (@DubhAd)](https://github.com/DubhAd "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io")
|
||||
- [DrewSK (@dzsquared)](https://github.com/dzsquared "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [DubhAd (@DubhAd)](https://github.com/DubhAd "15 total commits to the home-assistant organization, 15 commits to home-assistant.github.io")
|
||||
- [Duoxilian (@Duoxilian)](https://github.com/Duoxilian "11 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 5 commits to home-assistant")
|
||||
- [Dustin S (@texnofobix)](https://github.com/texnofobix "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Edward Romano (@oudeismetis)](https://github.com/oudeismetis "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Edwin Smulders (@Dutchy-)](https://github.com/Dutchy- "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Egor Tsinko (@etsinko)](https://github.com/etsinko "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Egor Tsinko (@etsinko)](https://github.com/etsinko "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Ellis Percival (@flyte)](https://github.com/flyte "31 total commits to the home-assistant organization, 25 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Emil Horpen Hetty (@emilhetty)](https://github.com/emilhetty "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [EmitKiwi (@EmitKiwi)](https://github.com/EmitKiwi "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Emil Horpen Hetty (@emilhetty)](https://github.com/emilhetty "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [emlt (@emlt)](https://github.com/emlt "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [engrbm87 (@engrbm87)](https://github.com/engrbm87 "3 total commits to the home-assistant organization, 3 commits to appdaemon")
|
||||
- [Enrique Gonzalez (@enriquegh)](https://github.com/enriquegh "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Eric Clymer (@ericwclymer)](https://github.com/ericwclymer "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Eric Hagan (@ehagan)](https://github.com/ehagan "2 total commits to the home-assistant organization, 1 commit to home-assistant-polymer, 1 commit to home-assistant")
|
||||
- [Eric Hagan (@ehagan)](https://github.com/ehagan "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Eric Oosting (@eoosting)](https://github.com/eoosting "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Eric Rolf (@xrolfex)](https://github.com/xrolfex "13 total commits to the home-assistant organization, 13 commits to home-assistant")
|
||||
- [Eric Thompson (@er0ck)](https://github.com/er0ck "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Erik Eriksson (@molobrakos)](https://github.com/molobrakos "98 total commits to the home-assistant organization, 90 commits to home-assistant, 5 commits to home-assistant.github.io, 3 commits to netdisco")
|
||||
- [Erik-jan Riemers (@riemers)](https://github.com/riemers "11 total commits to the home-assistant organization, 11 commits to home-assistant.github.io")
|
||||
- [ettisan (@ettisan)](https://github.com/ettisan "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Eugenio Panadero (@azogue)](https://github.com/azogue "68 total commits to the home-assistant organization, 39 commits to home-assistant, 23 commits to home-assistant.github.io, 3 commits to homebridge-homeassistant, 3 commits to home-assistant-polymer")
|
||||
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4168 total commits to the home-assistant organization, 2597 commits to home-assistant.github.io, 1373 commits to home-assistant, 61 commits to home-assistant-ansible, 29 commits to home-assistant-notebooks, 24 commits to home-assistant-cli, 24 commits to home-assistant-assets, 23 commits to home-assistant-dev-helper, 11 commits to hassio-build, 10 commits to home-assistant-polymer, 8 commits to netdisco, 5 commits to hassio-addons, 2 commits to hassio, 1 commit to home-assistant-js-websocket")
|
||||
- [Eugenio Panadero (@azogue)](https://github.com/azogue "73 total commits to the home-assistant organization, 44 commits to home-assistant, 23 commits to home-assistant.github.io, 3 commits to homebridge-homeassistant, 3 commits to home-assistant-polymer")
|
||||
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "4227 total commits to the home-assistant organization, 2647 commits to home-assistant.github.io, 1382 commits to home-assistant, 61 commits to home-assistant-ansible, 29 commits to home-assistant-notebooks, 24 commits to home-assistant-assets, 24 commits to home-assistant-cli, 23 commits to home-assistant-dev-helper, 11 commits to hassio-build, 10 commits to home-assistant-polymer, 8 commits to netdisco, 5 commits to hassio-addons, 2 commits to hassio, 1 commit to home-assistant-js-websocket")
|
||||
- [Fabian Heredia Montiel (@fabianhjr)](https://github.com/fabianhjr "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [fakezeta (@fakezeta)](https://github.com/fakezeta "7 total commits to the home-assistant organization, 7 commits to home-assistant")
|
||||
- [Fares Rihani (@anchepiece)](https://github.com/anchepiece "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [fedor1210 (@fedor1210)](https://github.com/fedor1210 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Felix (@xifle)](https://github.com/xifle "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Felix Krause (@KrauseFx)](https://github.com/KrauseFx "48 total commits to the home-assistant organization, 48 commits to issue-bot")
|
||||
- [felix schwenzel (@diplix)](https://github.com/diplix "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Ferry van Zeelst (@StaticCube)](https://github.com/StaticCube "6 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Finbarr Brady (@fbradyirl)](https://github.com/fbradyirl "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Florian Holzapfel (@florianholzapfel)](https://github.com/florianholzapfel "11 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 4 commits to home-assistant, 3 commits to netdisco")
|
||||
- [Florian Klien (@flowolf)](https://github.com/flowolf "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Florian Klien (@flowolf)](https://github.com/flowolf "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [florincosta (@florincosta)](https://github.com/florincosta "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [Fonta (@f0nt4)](https://github.com/f0nt4 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Franck Nijhof (@frenck)](https://github.com/frenck "13 total commits to the home-assistant organization, 12 commits to home-assistant.github.io, 1 commit to hassio")
|
||||
@ -304,17 +298,16 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Frantz (@rofrantz)](https://github.com/rofrantz "2 total commits to the home-assistant organization, 2 commits to netdisco")
|
||||
- [François Martin (@martinfrancois)](https://github.com/martinfrancois "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Frederic Hemberger (@fhemberger)](https://github.com/fhemberger "93 total commits to the home-assistant organization, 93 commits to home-assistant.github.io")
|
||||
- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "163 total commits to the home-assistant organization, 68 commits to home-assistant.github.io, 63 commits to hassbian-scripts, 27 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [Fredrik Lindqvist (@Landrash)](https://github.com/Landrash "172 total commits to the home-assistant organization, 71 commits to hassbian-scripts, 69 commits to home-assistant.github.io, 27 commits to pi-gen, 4 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [freol35241 (@freol35241)](https://github.com/freol35241 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [froz (@froz)](https://github.com/froz "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [fuga2136 (@fuga2136)](https://github.com/fuga2136 "13 total commits to the home-assistant organization, 13 commits to home-assistant.github.io")
|
||||
- [Gabor SZOLLOSI (@szogi)](https://github.com/szogi "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to appdaemon")
|
||||
- [GadgetReactor (@GadgetReactor)](https://github.com/GadgetReactor "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [garrettbeachy (@garrettbeachy)](https://github.com/garrettbeachy "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Gavin Mogan (@halkeye)](https://github.com/halkeye "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Geoff Norton (@kangaroo)](https://github.com/kangaroo "14 total commits to the home-assistant organization, 14 commits to home-assistant")
|
||||
- [George.M (@nodinosaur)](https://github.com/nodinosaur "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Georgi Kirichkov (@kirichkov)](https://github.com/kirichkov "9 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Georgi Kirichkov (@kirichkov)](https://github.com/kirichkov "12 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Georgi Yanev (@jumpalottahigh)](https://github.com/jumpalottahigh "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Georgii Staroselskii (@staroselskii)](https://github.com/staroselskii "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Gergely Imreh (@imrehg)](https://github.com/imrehg "16 total commits to the home-assistant organization, 11 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
@ -326,7 +319,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [GMFalka (@GMFalka)](https://github.com/GMFalka "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Gopal Kildoliya (@gopalkildoliya)](https://github.com/gopalkildoliya "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Graeme Smith (@Instagraeme)](https://github.com/Instagraeme "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [GreenTurtwig (@GreenTurtwig)](https://github.com/GreenTurtwig "78 total commits to the home-assistant organization, 71 commits to home-assistant.github.io, 7 commits to home-assistant")
|
||||
- [GreenTurtwig (@GreenTurtwig)](https://github.com/GreenTurtwig "80 total commits to the home-assistant organization, 73 commits to home-assistant.github.io, 7 commits to home-assistant")
|
||||
- [Greg (@theCMack)](https://github.com/theCMack "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Greg Dowling (@pavoni)](https://github.com/pavoni "249 total commits to the home-assistant organization, 222 commits to home-assistant, 25 commits to home-assistant.github.io, 2 commits to netdisco")
|
||||
- [Greg Laabs (@OverloadUT)](https://github.com/OverloadUT "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -344,7 +337,6 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Hari Menon (@floydpink)](https://github.com/floydpink "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Harris Borawski (@hborawski)](https://github.com/hborawski "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [hawk259 (@hawk259)](https://github.com/hawk259 "8 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [hcooper (@hcooper)](https://github.com/hcooper "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Heath Paddock (@heathbar)](https://github.com/heathbar "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Heiko Rothe (@mKeRix)](https://github.com/mKeRix "20 total commits to the home-assistant organization, 15 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
- [Hellowlol (@Hellowlol)](https://github.com/Hellowlol "4 total commits to the home-assistant organization, 3 commits to netdisco, 1 commit to appdaemon")
|
||||
@ -356,14 +348,15 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [hexa- (@mweinelt)](https://github.com/mweinelt "16 total commits to the home-assistant organization, 9 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [heytcass (@heytcass)](https://github.com/heytcass "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Hillary Fraley (@hillaryfraley)](https://github.com/hillaryfraley "12 total commits to the home-assistant organization, 12 commits to home-assistant.github.io")
|
||||
- [hokagegano (@hokagegano)](https://github.com/hokagegano "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Hugo Dupras (@jabesq)](https://github.com/jabesq "24 total commits to the home-assistant organization, 18 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Hugo Dupras (@jabesq)](https://github.com/jabesq "26 total commits to the home-assistant organization, 19 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Hugo Gresse (@HugoGresse)](https://github.com/HugoGresse "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Hung Le (@hungle)](https://github.com/hungle "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Huw Davies (@beardedgeek)](https://github.com/beardedgeek "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Hydreliox (@HydrelioxGitHub)](https://github.com/HydrelioxGitHub "40 total commits to the home-assistant organization, 31 commits to home-assistant, 9 commits to home-assistant.github.io")
|
||||
- [Iain Matchett (@matchett808)](https://github.com/matchett808 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Ian Copp (@icopp)](https://github.com/icopp "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [ianj001 (@ianj001)](https://github.com/ianj001 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [icovada (@icovada)](https://github.com/icovada "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [icovada (@icovada)](https://github.com/icovada "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [Igor Shults (@ishults)](https://github.com/ishults "11 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Ioan Loosley (@ioangogo)](https://github.com/ioangogo "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [IoTmessenger (@IoTmessenger)](https://github.com/IoTmessenger "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -404,7 +397,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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")
|
||||
- [Jeremy Williams (@jwillaz)](https://github.com/jwillaz "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Jeroen ter Heerdt (@jeroenterheerdt)](https://github.com/jeroenterheerdt "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Jeroen ter Heerdt (@jeroenterheerdt)](https://github.com/jeroenterheerdt "17 total commits to the home-assistant organization, 11 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Jerold Albertson (@jeroldalbertson-wf)](https://github.com/jeroldalbertson-wf "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Jesse Hills (@jesserockz)](https://github.com/jesserockz "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Jesse Newland (@jnewland)](https://github.com/jnewland "14 total commits to the home-assistant organization, 11 commits to home-assistant, 3 commits to hubot-home-assistant")
|
||||
@ -413,10 +406,10 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [jgriff2 (@jgriff2)](https://github.com/jgriff2 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Jim Rollenhagen (@jimrollenhagen)](https://github.com/jimrollenhagen "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Joakim Nohlgård (@gebart)](https://github.com/gebart "2 total commits to the home-assistant organization, 2 commits to libcoap")
|
||||
- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "23 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 10 commits to hassbian-scripts")
|
||||
- [Joakim Sørensen (@ludeeus)](https://github.com/ludeeus "25 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 12 commits to hassbian-scripts")
|
||||
- [Job (@jmvermeulen)](https://github.com/jmvermeulen "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Joe Lee (@xnoodle)](https://github.com/xnoodle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Joe Lu (@snjoetw)](https://github.com/snjoetw "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [Joe Lu (@snjoetw)](https://github.com/snjoetw "9 total commits to the home-assistant organization, 7 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [joe248 (@joe248)](https://github.com/joe248 "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Joeboyc2 (@Joeboyc2)](https://github.com/Joeboyc2 "15 total commits to the home-assistant organization, 15 commits to home-assistant.github.io")
|
||||
- [joemcmonagle (@joemcmonagle)](https://github.com/joemcmonagle "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io")
|
||||
@ -449,24 +442,24 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [JudgeDredd (@kentcalero)](https://github.com/kentcalero "10 total commits to the home-assistant organization, 10 commits to home-assistant.github.io")
|
||||
- [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 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Julius Mittenzwei (@Julius2342)](https://github.com/Julius2342 "9 total commits to the home-assistant organization, 7 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Julius Mittenzwei (@Julius2342)](https://github.com/Julius2342 "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [jumpkick (@jumpkick)](https://github.com/jumpkick "15 total commits to the home-assistant organization, 12 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Justin Dray (@justin8)](https://github.com/justin8 "9 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Justin Hayes (@GussyH)](https://github.com/GussyH "7 total commits to the home-assistant organization, 7 commits to hadashboard")
|
||||
- [Justin Weberg (@justweb1)](https://github.com/justweb1 "28 total commits to the home-assistant organization, 13 commits to home-assistant-polymer, 7 commits to hassbot, 4 commits to home-assistant, 2 commits to home-assistant.github.io, 1 commit to home-assistant-js, 1 commit to hassio")
|
||||
- [Justyn Shull (@justyns)](https://github.com/justyns "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [Kai (@luxus)](https://github.com/luxus "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Kane610 (@Kane610)](https://github.com/Kane610 "10 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant, 1 commit to netdisco")
|
||||
- [Kane610 (@Kane610)](https://github.com/Kane610 "11 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 5 commits to home-assistant, 1 commit to netdisco")
|
||||
- [Karen Goode (@kfgoode)](https://github.com/kfgoode "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [karlkar (@karlkar)](https://github.com/karlkar "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Keaton Taylor (@keatontaylor)](https://github.com/keatontaylor "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Keith (@seedzero)](https://github.com/seedzero "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Keith Lamprecht (@Nixon506E)](https://github.com/Nixon506E "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Ken Bannister (@kb2ma)](https://github.com/kb2ma "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Ken Davidson (@kwdavidson)](https://github.com/kwdavidson "10 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 2 commits to appdaemon")
|
||||
- [Ken Davidson (@kwdavidson)](https://github.com/kwdavidson "11 total commits to the home-assistant organization, 9 commits to home-assistant.github.io, 2 commits to appdaemon")
|
||||
- [Kevin (@Mister-Espria)](https://github.com/Mister-Espria "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Kevin Christensen (@nivekmai)](https://github.com/nivekmai "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "13 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Kevin Fronczak (@fronzbot)](https://github.com/fronzbot "16 total commits to the home-assistant organization, 10 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Kevin Gisi (@gisikw)](https://github.com/gisikw "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Kevin Gottsman (@gottsman)](https://github.com/gottsman "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Kevin Panaro (@kevinpanaro)](https://github.com/kevinpanaro "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -487,7 +480,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Leon99 (@Leon99)](https://github.com/Leon99 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Leonardo Saraiva (@vyper)](https://github.com/vyper "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Lev Aronsky (@aronsky)](https://github.com/aronsky "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Lewis Juggins (@lwis)](https://github.com/lwis "54 total commits to the home-assistant organization, 43 commits to home-assistant, 10 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Lewis Juggins (@lwis)](https://github.com/lwis "57 total commits to the home-assistant organization, 45 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Lindsay Ward (@lindsaymarkward)](https://github.com/lindsaymarkward "17 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [linuxlurak (@linuxlurak)](https://github.com/linuxlurak "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to hadashboard")
|
||||
- [lrmate (@lrmate)](https://github.com/lrmate "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
@ -495,7 +488,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [LucaSoldi (@LucaSoldi)](https://github.com/LucaSoldi "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Lucien Guimier (@guimier)](https://github.com/guimier "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Lukas (@lukas-hetzenecker)](https://github.com/lukas-hetzenecker "14 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Lukas Barth (@tinloaf)](https://github.com/tinloaf "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Lukas Barth (@tinloaf)](https://github.com/tinloaf "11 total commits to the home-assistant organization, 6 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
- [Luke Armstrong (@lukearmstrong)](https://github.com/lukearmstrong "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Lupin Demid (@lupin-de-mid)](https://github.com/lupin-de-mid "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Luuk (@Maharball1)](https://github.com/Maharball1 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -514,7 +507,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Marc Pabst (@mxtra)](https://github.com/mxtra "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Marc Plano-Lesay (@Kernald)](https://github.com/Kernald "12 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Marcel030nl (@Marcel030nl)](https://github.com/Marcel030nl "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "122 total commits to the home-assistant organization, 67 commits to home-assistant, 55 commits to home-assistant.github.io")
|
||||
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "126 total commits to the home-assistant organization, 70 commits to home-assistant, 56 commits to home-assistant.github.io")
|
||||
- [Marcin Jaworski (@yawor)](https://github.com/yawor "12 total commits to the home-assistant organization, 12 commits to appdaemon")
|
||||
- [Marijn Giesen (@marijngiesen)](https://github.com/marijngiesen "7 total commits to the home-assistant organization, 5 commits to hadashboard, 2 commits to home-assistant.github.io")
|
||||
- [Mark Huson (@mehuman)](https://github.com/mehuman "11 total commits to the home-assistant organization, 11 commits to home-assistant.github.io")
|
||||
@ -526,6 +519,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [marthoc (@marthoc)](https://github.com/marthoc "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Martin Berg (@mbrrg)](https://github.com/mbrrg "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Martin Donlon (@wickerwaka)](https://github.com/wickerwaka "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Martin Eberhardt (@DarkFox)](https://github.com/DarkFox "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Martin Hjelmare (@MartinHjelmare)](https://github.com/MartinHjelmare "138 total commits to the home-assistant organization, 112 commits to home-assistant, 26 commits to home-assistant.github.io")
|
||||
- [Martin Rowan (@shortbloke)](https://github.com/shortbloke "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Martin Vacula (@MatoKafkac)](https://github.com/MatoKafkac "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -543,7 +537,6 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Matthew Treinish (@mtreinish)](https://github.com/mtreinish "16 total commits to the home-assistant organization, 10 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [mattie47 (@mattie47)](https://github.com/mattie47 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [mauriciobonani (@mauriciobonani)](https://github.com/mauriciobonani "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Max Rumpf (@Maxr1998)](https://github.com/Maxr1998 "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [mboeru (@mboeru)](https://github.com/mboeru "1 total commits to the home-assistant organization, 1 commit to home-assistant-iOS")
|
||||
- [mertenats (@mertenats)](https://github.com/mertenats "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Micha LaQua (@milaq)](https://github.com/milaq "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
@ -562,6 +555,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Mikael Bergemalm (@bergemalm)](https://github.com/bergemalm "2 total commits to the home-assistant organization, 2 commits 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 Christianson (@MikeChristianson)](https://github.com/MikeChristianson "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Mike G Chambers (@mikegchambers)](https://github.com/mikegchambers "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -570,19 +564,20 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Mike Roberts (@m-roberts)](https://github.com/m-roberts "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [mikey (@pfista)](https://github.com/pfista "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Mikkel Høgh (@mikl)](https://github.com/mikl "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [milanvo (@milanvo)](https://github.com/milanvo "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [milanvo (@milanvo)](https://github.com/milanvo "8 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [MinchinWeb (@MinchinWeb)](https://github.com/MinchinWeb "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [miniconfig (@miniconfig)](https://github.com/miniconfig "27 total commits to the home-assistant organization, 20 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Minims (@Minims)](https://github.com/Minims "3 total commits to the home-assistant organization, 3 commits to homebridge-homeassistant")
|
||||
- [Mister Wil (@MisterWil)](https://github.com/MisterWil "14 total commits to the home-assistant organization, 9 commits to home-assistant, 5 commits to home-assistant.github.io")
|
||||
- [Mister Wil (@MisterWil)](https://github.com/MisterWil "16 total commits to the home-assistant organization, 10 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Mitesh Patel (@gurumitts)](https://github.com/gurumitts "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Mitko Masarliev (@masarliev)](https://github.com/masarliev "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [mje-nz (@mje-nz)](https://github.com/mje-nz "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [mjj4791 (@mjj4791)](https://github.com/mjj4791 "22 total commits to the home-assistant organization, 15 commits to home-assistant.github.io, 7 commits to home-assistant")
|
||||
- [Molodax (@Molodax)](https://github.com/Molodax "7 total commits to the home-assistant organization, 7 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")
|
||||
- [moose51789 (@moose51789)](https://github.com/moose51789 "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [morberg (@morberg)](https://github.com/morberg "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [moskovskiy82 (@moskovskiy82)](https://github.com/moskovskiy82 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [moskovskiy82 (@moskovskiy82)](https://github.com/moskovskiy82 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [motir (@motir)](https://github.com/motir "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [mtl010957 (@mtl010957)](https://github.com/mtl010957 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Mārtiņš Grunskis (@grunskis)](https://github.com/grunskis "1 total commits to the home-assistant organization, 1 commit to netdisco")
|
||||
@ -592,13 +587,12 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Nathan Henrie (@n8henrie)](https://github.com/n8henrie "18 total commits to the home-assistant organization, 8 commits to home-assistant, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant, 1 commit to appdaemon, 1 commit to home-assistant-polymer")
|
||||
- [Neil Lathwood (@laf)](https://github.com/laf "5 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Nelis Willers (@NelisW)](https://github.com/NelisW "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant")
|
||||
- [NeLLyMerC (@NeLLyMerC)](https://github.com/NeLLyMerC "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [NeLLyMerC (@NeLLyMerC)](https://github.com/NeLLyMerC "3 total commits to the home-assistant organization, 3 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 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Nicholas Sielicki (@sielicki)](https://github.com/sielicki "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Nick (@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 "38 total commits to the home-assistant organization, 25 commits to home-assistant, 13 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")
|
||||
- [Nick Waring (@nickwaring)](https://github.com/nickwaring "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Nicolas Graziano (@ngraziano)](https://github.com/ngraziano "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
@ -617,14 +611,16 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [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 "20 total commits to the home-assistant organization, 12 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Oliver (@scarface-4711)](https://github.com/scarface-4711 "22 total commits to the home-assistant organization, 13 commits to home-assistant, 8 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")
|
||||
- [olskar (@olskar)](https://github.com/olskar "1 total commits to the home-assistant organization, 1 commit to hassbian-scripts")
|
||||
- [Omar Usman (@omarusman)](https://github.com/omarusman "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Open Home Automation (@open-homeautomation)](https://github.com/open-homeautomation "41 total commits to the home-assistant organization, 29 commits to home-assistant, 12 commits to home-assistant.github.io")
|
||||
- [oznu (@oznu)](https://github.com/oznu "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
|
||||
- [Parker Moore (@parkr)](https://github.com/parkr "62 total commits to the home-assistant organization, 62 commits to home-assistant.github.io")
|
||||
- [pascal (@passie)](https://github.com/passie "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [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 "2033 total commits to the home-assistant organization, 800 commits to hassio, 390 commits to home-assistant, 291 commits to hassio-addons, 276 commits to hassio-build, 258 commits to home-assistant.github.io, 16 commits to hassio-addons-example, 1 commit to home-assistant-js-websocket, 1 commit to netdisco")
|
||||
- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "2110 total commits to the home-assistant organization, 827 commits to hassio, 397 commits to home-assistant, 300 commits to hassio-addons, 294 commits to hassio-build, 274 commits to home-assistant.github.io, 16 commits to hassio-addons-example, 1 commit to home-assistant-js-websocket, 1 commit to netdisco")
|
||||
- [patkap (@patkap)](https://github.com/patkap "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Patrick Aikens (@duckpuppy)](https://github.com/duckpuppy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Patrick Easters (@patrickeasters)](https://github.com/patrickeasters "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
@ -645,19 +641,20 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Phil (@godloth)](https://github.com/godloth "10 total commits to the home-assistant organization, 10 commits to home-assistant.github.io")
|
||||
- [Phil Cole (@filcole)](https://github.com/filcole "8 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [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 "15 total commits to the home-assistant organization, 9 commits to home-assistant.github.io, 6 commits to home-assistant")
|
||||
- [Phil Kates (@philk)](https://github.com/philk "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Phil Hawthorne (@philhawthorne)](https://github.com/philhawthorne "17 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 6 commits to home-assistant")
|
||||
- [Phil Kates (@philk)](https://github.com/philk "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [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 "32 total commits to the home-assistant organization, 20 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to hassio-build")
|
||||
- [Philipp Schmitt (@pschmitt)](https://github.com/pschmitt "33 total commits to the home-assistant organization, 21 commits to home-assistant, 11 commits to home-assistant.github.io, 1 commit to hassio-build")
|
||||
- [Phill Price (@phillprice)](https://github.com/phillprice "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [PhracturedBlue (@PhracturedBlue)](https://github.com/PhracturedBlue "15 total commits to the home-assistant organization, 7 commits to home-assistant.github.io, 7 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [Pierre Ståhl (@postlund)](https://github.com/postlund "37 total commits to the home-assistant organization, 25 commits to home-assistant, 8 commits to home-assistant.github.io, 4 commits to netdisco")
|
||||
- [Piratonym (@Piratonym)](https://github.com/Piratonym "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [PuckStar (@PuckStar)](https://github.com/PuckStar "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [R Huish (@Genestealer)](https://github.com/Genestealer "19 total commits to the home-assistant organization, 19 commits to home-assistant.github.io")
|
||||
- [R1chardTM (@R1chardTM)](https://github.com/R1chardTM "9 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [rbflurry (@rbflurry)](https://github.com/rbflurry "12 total commits to the home-assistant organization, 10 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [R1chardTM (@R1chardTM)](https://github.com/R1chardTM "10 total commits to the home-assistant organization, 5 commits to home-assistant, 4 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [rbflurry (@rbflurry)](https://github.com/rbflurry "14 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [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 "25 total commits to the home-assistant organization, 25 commits to appdaemon")
|
||||
@ -671,7 +668,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [rkabadi (@rkabadi)](https://github.com/rkabadi "17 total commits to the home-assistant organization, 17 commits to home-assistant")
|
||||
- [Rob Capellini (@capellini)](https://github.com/capellini "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Rob Slifka (@rslifka)](https://github.com/rslifka "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1198 total commits to the home-assistant organization, 531 commits to home-assistant-iOS, 255 commits to home-assistant, 247 commits to home-assistant.github.io, 87 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to scenegen, 3 commits to appdaemon, 3 commits to organization, 3 commits to hadashboard, 3 commits to home-assistant-js-websocket, 3 commits to hassbot, 3 commits to home-assistant-js, 3 commits to home-assistant-cli, 2 commits to lambda-home-assistant-github, 2 commits to home-assistant-notebooks, 2 commits to LabelBot, 2 commits to home-assistant-dev-helper, 2 commits to fabric-home-assistant, 2 commits to home-assistant-ansible, 2 commits to micropython-home-assistant, 2 commits to home-assistant-assets")
|
||||
- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1198 total commits to the home-assistant organization, 531 commits to home-assistant-iOS, 255 commits to home-assistant, 247 commits to home-assistant.github.io, 87 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to organization, 3 commits to home-assistant-js-websocket, 3 commits to appdaemon, 3 commits to scenegen, 3 commits to home-assistant-js, 3 commits to hassbot, 3 commits to home-assistant-cli, 3 commits to hadashboard, 2 commits to home-assistant-ansible, 2 commits to LabelBot, 2 commits to lambda-home-assistant-github, 2 commits to home-assistant-notebooks, 2 commits to home-assistant-dev-helper, 2 commits to micropython-home-assistant, 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 "13 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 5 commits to home-assistant")
|
||||
- [Robin Laurén (@llauren)](https://github.com/llauren "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
@ -687,13 +684,13 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [runningman84 (@runningman84)](https://github.com/runningman84 "4 total commits to the home-assistant organization, 4 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 "20 total commits to the home-assistant organization, 14 commits to home-assistant, 4 commits to homebridge-homeassistant, 2 commits to home-assistant.github.io")
|
||||
- [Russell Cloran (@rcloran)](https://github.com/rcloran "21 total commits to the home-assistant organization, 15 commits to home-assistant, 4 commits to homebridge-homeassistant, 2 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
- [Ryan Kraus (@rmkraus)](https://github.com/rmkraus "195 total commits to the home-assistant organization, 163 commits to home-assistant, 17 commits to home-assistant.github.io, 14 commits to home-assistant-polymer, 1 commit to home-assistant-notebooks")
|
||||
- [Ryan Parrish (@stickystyle)](https://github.com/stickystyle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Ryan Turner (@ryanturner)](https://github.com/ryanturner "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Ryan Turner (@turnrye)](https://github.com/turnrye "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Sabesto (@Sabesto)](https://github.com/Sabesto "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Sacha Telgenhof (@stelgenhof)](https://github.com/stelgenhof "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Sam Holmes (@sam3d)](https://github.com/sam3d "4 total commits to the home-assistant organization, 4 commits to pi-gen")
|
||||
@ -707,15 +704,16 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Scott Griffin (@scottocs11)](https://github.com/scottocs11 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [Scott O'Neil (@americanwookie)](https://github.com/americanwookie "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Scott Reston (@ih8gates)](https://github.com/ih8gates "9 total commits to the home-assistant organization, 8 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Sean Dague (@sdague)](https://github.com/sdague "60 total commits to the home-assistant organization, 41 commits to home-assistant, 10 commits to home-assistant.github.io, 5 commits to home-assistant-polymer, 3 commits to netdisco, 1 commit to home-assistant-js")
|
||||
- [Sean Gollschewsky (@gollo)](https://github.com/gollo "16 total commits to the home-assistant organization, 9 commits to home-assistant, 4 commits to home-assistant.github.io, 3 commits to hassio-build")
|
||||
- [Sean Dague (@sdague)](https://github.com/sdague "62 total commits to the home-assistant organization, 43 commits to home-assistant, 10 commits to home-assistant.github.io, 5 commits to home-assistant-polymer, 3 commits to netdisco, 1 commit to home-assistant-js")
|
||||
- [Sean Gollschewsky (@gollo)](https://github.com/gollo "17 total commits to the home-assistant organization, 10 commits to home-assistant, 4 commits to home-assistant.github.io, 3 commits to hassio-build")
|
||||
- [Sebastian (@sebk-666)](https://github.com/sebk-666 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Sebastian (@sgso)](https://github.com/sgso "3 total commits to the home-assistant organization, 3 commits to libcoap")
|
||||
- [Sebastian Muszynski (@syssi)](https://github.com/syssi "17 total commits to the home-assistant organization, 9 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Sebastian Muszynski (@syssi)](https://github.com/syssi "21 total commits to the home-assistant organization, 10 commits to home-assistant, 9 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Sebastian von Minckwitz (@teodoc)](https://github.com/teodoc "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Semir Patel (@analogue)](https://github.com/analogue "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [Sergey Isachenko (@zabuldon)](https://github.com/zabuldon "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Sergey Isachenko (@zabuldon)](https://github.com/zabuldon "7 total commits to the home-assistant organization, 5 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [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")
|
||||
- [sharukins (@sharukins)](https://github.com/sharukins "1 total commits to the home-assistant organization, 1 commit to hassio-build")
|
||||
- [Shawna O'Neal (@cherrykoda)](https://github.com/cherrykoda "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Shiny (@Br3nda)](https://github.com/Br3nda "3 total commits to the home-assistant organization, 3 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")
|
||||
@ -743,8 +741,9 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [tedstriker (@tedstriker)](https://github.com/tedstriker "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Teemu Mikkonen (@T3m3z)](https://github.com/T3m3z "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Teemu Patja (@tpatja)](https://github.com/tpatja "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Teemu R. (@rytilahti)](https://github.com/rytilahti "36 total commits to the home-assistant organization, 28 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Teemu R. (@rytilahti)](https://github.com/rytilahti "41 total commits to the home-assistant organization, 32 commits to home-assistant, 7 commits to home-assistant.github.io, 2 commits to netdisco")
|
||||
- [Teguh Sobirin (@tjstyle)](https://github.com/tjstyle "2 total commits to the home-assistant organization, 2 commits to pi-gen")
|
||||
- [Tentoe (@Tentoe)](https://github.com/Tentoe "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Terry Carlin (@terrycarlin)](https://github.com/terrycarlin "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Theb-1 (@Theb-1)](https://github.com/Theb-1 "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [thecynic (@thecynic)](https://github.com/thecynic "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
@ -779,7 +778,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Tom Matheussen (@Tommatheussen)](https://github.com/Tommatheussen "13 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant-polymer, 3 commits to home-assistant.github.io")
|
||||
- [Tom Usher (@tomusher)](https://github.com/tomusher "1 total commits to the home-assistant organization, 1 commit to netdisco")
|
||||
- [Tomi Tuhkanen (@ttu)](https://github.com/ttu "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Tony Torralba (@atorralba)](https://github.com/atorralba "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [TopdRob (@TopdRob)](https://github.com/TopdRob "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Torkild Retvedt (@torkildr)](https://github.com/torkildr "2 total commits to the home-assistant organization, 2 commits to appdaemon")
|
||||
- [Toshik (@Toshik)](https://github.com/Toshik "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
|
||||
- [tradiuz (@tradiuz)](https://github.com/tradiuz "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
@ -787,7 +786,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Trevor (@tboyce021)](https://github.com/tboyce021 "11 total commits to the home-assistant organization, 8 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 "7 total commits to the home-assistant organization, 4 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Tsvi Mostovicz (@tsvi)](https://github.com/tsvi "8 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 4 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")
|
||||
@ -806,7 +805,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 Johansson (@radhus)](https://github.com/radhus "1 total commits to the home-assistant organization, 1 commit to hassio")
|
||||
- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "86 total commits to the home-assistant organization, 59 commits to home-assistant, 25 commits to home-assistant.github.io, 2 commits to netdisco")
|
||||
- [William Scanlon (@w1ll1am23)](https://github.com/w1ll1am23 "91 total commits to the home-assistant organization, 62 commits to home-assistant, 27 commits to home-assistant.github.io, 2 commits to netdisco")
|
||||
- [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")
|
||||
@ -822,9 +821,10 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Zeb Palmer (@zebpalmer)](https://github.com/zebpalmer "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Zen Tormey (@xehn)](https://github.com/xehn "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Zhao Lu (@zlu)](https://github.com/zlu "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [ziotibia81 (@ziotibia81)](https://github.com/ziotibia81 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Zippit (@Zippit)](https://github.com/Zippit "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
|
||||
|
||||
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 Saturday, October 7th 2017, 10:31:01 pm UTC.</i>
|
||||
<i>This page was last updated Saturday, October 21st 2017, 8:19:43 pm UTC.</i>
|
||||
|
BIN
source/images/blog/2017-10-0.56/components.png
Normal file
After Width: | Height: | Size: 89 KiB |
BIN
source/images/supported_brands/clickatell.png
Normal file
After Width: | Height: | Size: 22 KiB |
BIN
source/images/supported_brands/google-assistant.png
Normal file
After Width: | Height: | Size: 6.8 KiB |
105
source/images/supported_brands/monoprice.svg
Normal file
@ -0,0 +1,105 @@
|
||||
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||||
<!-- Generator: Adobe Illustrator 19.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
|
||||
|
||||
<svg
|
||||
xmlns:dc="http://purl.org/dc/elements/1.1/"
|
||||
xmlns:cc="http://creativecommons.org/ns#"
|
||||
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
|
||||
xmlns:svg="http://www.w3.org/2000/svg"
|
||||
xmlns="http://www.w3.org/2000/svg"
|
||||
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
|
||||
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
|
||||
version="1.1"
|
||||
id="Layer_1"
|
||||
x="0px"
|
||||
y="0px"
|
||||
viewBox="0 0 420 60"
|
||||
style="enable-background:new 0 0 420 60;"
|
||||
xml:space="preserve"
|
||||
inkscape:version="0.91 r"
|
||||
sodipodi:docname="monoprice.svg"><metadata
|
||||
id="metadata3500"><rdf:RDF><cc:Work
|
||||
rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
|
||||
rdf:resource="http://purl.org/dc/dcmitype/StillImage" /></cc:Work></rdf:RDF></metadata><defs
|
||||
id="defs3498" /><sodipodi:namedview
|
||||
pagecolor="#ffffff"
|
||||
bordercolor="#666666"
|
||||
borderopacity="1"
|
||||
objecttolerance="10"
|
||||
gridtolerance="10"
|
||||
guidetolerance="10"
|
||||
inkscape:pageopacity="0"
|
||||
inkscape:pageshadow="2"
|
||||
inkscape:window-width="1920"
|
||||
inkscape:window-height="1028"
|
||||
id="namedview3496"
|
||||
showgrid="false"
|
||||
inkscape:zoom="4.1404762"
|
||||
inkscape:cx="210"
|
||||
inkscape:cy="1.0178263"
|
||||
inkscape:window-x="0"
|
||||
inkscape:window-y="0"
|
||||
inkscape:window-maximized="1"
|
||||
inkscape:current-layer="g3457" /><style
|
||||
type="text/css"
|
||||
id="style3455">
|
||||
.st0{fill:#FFFFFF;}
|
||||
</style><g
|
||||
id="g3457"><path
|
||||
class="st0"
|
||||
d="M51.3,4.4C57.2,4.4,62,9.2,62,15.1v29.9c0,5.9-4.8,10.7-10.7,10.7H21.4c-5.9,0-10.7-4.8-10.7-10.7V15.1 c0-5.9,4.8-10.7,10.7-10.7H51.3 M53.3,25.2c0-2-0.7-3.7-2.1-5.1c-1.4-1.4-3.1-2.1-5.1-2.1c-2,0-3.7,0.7-5.1,2.1 c-1.4,1.4-2.1,3.1-2.1,5.1v7.3c0,1.6-0.8,2.4-2.4,2.4c-1.6,0-2.4-0.8-2.4-2.4v-6.8v-0.4c0-2-0.7-3.7-2.1-5.1 c-1.4-1.4-3.1-2.1-5.1-2.1c-2,0-3.7,0.7-5.1,2.1c-1.4,1.4-2.1,3.1-2.1,5.1v14.5c0,1.6,0.8,2.4,2.4,2.4s2.4-0.8,2.4-2.4V25.2h0 c0-1.6,0.8-2.4,2.4-2.4c1.6,0,2.4,0.8,2.4,2.4v7.3c0,2,0.7,3.7,2.1,5.1c1.4,1.4,3.1,2.1,5.1,2.1c2,0,3.7-0.7,5.1-2.1 c1.4-1.4,2.1-3.1,2.1-5.1V32v-6.8c0-1.6,0.8-2.4,2.4-2.4c1.6,0,2.4,0.8,2.4,2.4h0l0,14.5c0,1.6,0.8,2.4,2.4,2.4 c1.6,0,2.4-0.8,2.4-2.4V25.2z"
|
||||
id="path3459"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M146,12c5.4,0,9.9,1.7,13.5,5.1c3.6,3.4,5.4,7.7,5.4,12.9c0,5.2-1.8,9.5-5.5,12.8c-3.6,3.4-8.2,5.1-13.8,5.1 c-5.3,0-9.7-1.7-13.2-5.1c-3.5-3.4-5.3-7.6-5.3-12.7c0-5.2,1.8-9.6,5.3-13C136.1,13.7,140.6,12,146,12z M146.2,16.8 c-4,0-7.3,1.3-9.9,3.8c-2.6,2.5-3.9,5.7-3.9,9.6c0,3.8,1.3,6.9,3.9,9.4c2.6,2.5,5.8,3.8,9.7,3.8c3.9,0,7.2-1.3,9.8-3.8 c2.6-2.6,3.9-5.8,3.9-9.6c0-3.7-1.3-6.8-3.9-9.4C153.2,18,150,16.8,146.2,16.8z"
|
||||
id="path3461"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M202.8,12.3h4.8v35.4h-4.4l-23.7-27.3v27.3h-4.8V12.3h4.1l23.9,27.5V12.3z"
|
||||
id="path3463"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M236.2,12c5.4,0,9.9,1.7,13.5,5.1c3.6,3.4,5.4,7.7,5.4,12.9c0,5.2-1.8,9.4-5.4,12.8c-3.6,3.4-8.2,5.1-13.7,5.1 c-5.3,0-9.7-1.7-13.2-5.1c-3.5-3.4-5.3-7.6-5.3-12.7c0-5.2,1.8-9.6,5.3-13C226.3,13.8,230.7,12,236.2,12z M236.4,16.8 c-4,0-7.3,1.3-9.9,3.8c-2.6,2.5-3.9,5.7-3.9,9.6c0,3.8,1.3,6.9,3.9,9.4c2.6,2.5,5.8,3.8,9.7,3.8c3.9,0,7.2-1.3,9.8-3.8 c2.6-2.6,3.9-5.7,3.9-9.5c0-3.7-1.3-6.8-3.9-9.4C243.4,18.1,240.2,16.8,236.4,16.8z"
|
||||
id="path3465"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M265.1,47.7V12.3h11.2c3.4,0,6.1,0.9,8.1,2.7s3,4.3,3,7.3c0,2.1-0.5,3.9-1.5,5.5c-1,1.6-2.4,2.7-4.2,3.5 c-1.8,0.7-4.4,1.1-7.7,1.1h-3.7v15.3H265.1z M275.4,16.8h-5.2v11.1h5.5c2.1,0,3.6-0.5,4.8-1.5c1.1-1,1.7-2.4,1.7-4.2 C282.2,18.6,279.9,16.8,275.4,16.8z"
|
||||
id="path3467"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M322.6,45.2c-0.7-1-1.7-2.5-3-4.5c-2-3.2-3.5-5.4-4.6-6.7c-0.8-0.9-1.5-1.6-2.3-2.3c0.4-0.1,0.8-0.2,1.1-0.4 c1.8-0.7,3.2-1.9,4.2-3.5c1-1.6,1.5-3.4,1.5-5.5c0-3.1-1-5.5-3-7.3c-2-1.8-4.7-2.7-8.1-2.7h-11.2v35.4h5.1V32.4h2.4 c1,0.1,1.7,0.2,2.2,0.5c0.7,0.4,1.5,1,2.4,1.9c0.9,0.9,1.8,2,2.9,3.5l1.7,2.8l1.6,2.6l1,1.4c0.2,0.2,0.3,0.3,0.3,0.4l1.5,2.3h6 L322.6,45.2z M302.5,16.8h5.2c4.5,0,6.7,1.8,6.7,5.4c0,1.8-0.6,3.2-1.7,4.2c-1.1,1-2.7,1.5-4.8,1.5h-5.5V16.8z"
|
||||
id="path3469"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M332.6,12.3h5.1v35.4h-5.1V12.3z"
|
||||
id="path3471"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M379,39.4V45c-3.7,2-7.9,3-12.8,3c-3.9,0-7.3-0.8-10-2.4s-4.9-3.7-6.5-6.5c-1.6-2.8-2.4-5.8-2.4-9 c0-5.1,1.8-9.4,5.5-12.9c3.6-3.5,8.1-5.2,13.5-5.2c3.7,0,7.8,1,12.3,2.9v5.4c-4.1-2.3-8.1-3.5-12-3.5c-4,0-7.4,1.3-10,3.8 c-2.7,2.5-4,5.7-4,9.5c0,3.9,1.3,7,3.9,9.5c2.6,2.5,6,3.7,10,3.7C370.8,43.4,374.9,42.1,379,39.4z"
|
||||
id="path3473"
|
||||
style="fill:#000000" /><path
|
||||
class="st0"
|
||||
d="M388.6,12.3h20.1v4.5h-15v10.8h14.5v4.5h-14.5v11h15.5v4.5h-20.6V12.3z"
|
||||
id="path3475"
|
||||
style="fill:#000000" /><g
|
||||
id="g3477"
|
||||
style="fill:#000000"><path
|
||||
class="st0"
|
||||
d="M98.9,39.5L98.9,39.5l10.6-27.2h7.7v35.4h-5V18.1h-0.1l-11.8,29.6h-3.2L85.5,18.1h-0.1v29.6h-4.8V12.3h7.7 L98.9,39.5z"
|
||||
id="path3479"
|
||||
style="fill:#000000" /></g></g><g
|
||||
id="XMLID_235_" /><g
|
||||
id="XMLID_236_" /><g
|
||||
id="XMLID_237_" /><g
|
||||
id="XMLID_238_" /><g
|
||||
id="XMLID_239_" /><g
|
||||
id="XMLID_240_" /><g
|
||||
id="XMLID_241_" /><g
|
||||
id="XMLID_242_" /><g
|
||||
id="XMLID_243_" /><g
|
||||
id="XMLID_244_" /><g
|
||||
id="XMLID_245_" /><g
|
||||
id="XMLID_246_" /><g
|
||||
id="XMLID_247_" /><g
|
||||
id="XMLID_248_" /><g
|
||||
id="XMLID_249_" /></svg>
|
After Width: | Height: | Size: 5.7 KiB |
BIN
source/images/supported_brands/namecheap.png
Normal file
After Width: | Height: | Size: 1.4 KiB |
BIN
source/images/supported_brands/rocketchat.png
Normal file
After Width: | Height: | Size: 2.9 KiB |
BIN
source/images/supported_brands/skybell.png
Normal file
After Width: | Height: | Size: 22 KiB |
BIN
source/images/supported_brands/toon.png
Normal file
After Width: | Height: | Size: 37 KiB |
309
source/images/supported_brands/travisci.svg
Normal file
@ -0,0 +1,309 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!-- Generator: Adobe Illustrator 19.2.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
|
||||
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
|
||||
viewBox="0 0 200 200" style="enable-background:new 0 0 200 200;" xml:space="preserve">
|
||||
<style type="text/css">
|
||||
.st0{fill:#CB3349;}
|
||||
.st1{fill:#F4EDAE;}
|
||||
.st2{fill:#E6CCAD;}
|
||||
.st3{fill:#656C67;}
|
||||
.st4{fill:#E5CAA3;}
|
||||
.st5{fill:#C7B39A;}
|
||||
.st6{fill:#EBD599;}
|
||||
.st7{fill:#2D3136;}
|
||||
.st8{fill:#EDF6FA;}
|
||||
.st9{opacity:0.8;}
|
||||
.st10{opacity:0.75;fill:#EBD599;}
|
||||
</style>
|
||||
<g>
|
||||
<g>
|
||||
<path class="st0" d="M47.781,86.572c0,0-31.118,21.903-32.335,30.247l2.335-0.48c0,0,37.264-24.699,66.803-27.711l0.669-3.749
|
||||
L47.781,86.572z"/>
|
||||
<path class="st0" d="M96.629,83.442l-24.511,17.385l1.325,1.063c0.999-0.806,43.539-13.798,43.539-13.798l8.969-5.623
|
||||
C119.933,83.218,96.629,83.442,96.629,83.442z"/>
|
||||
<path class="st0" d="M117.932,104.469c17.405,0,43.495-17.046,43.495-17.046l-8.434-1.605c-0.417,0.417-13.6-0.462-13.6-0.462
|
||||
l-6.258-1.738l-14.951,17.036l-1.217,2.956C118.042,103.173,117.932,104.469,117.932,104.469z"/>
|
||||
</g>
|
||||
<path class="st0" d="M174.728,158.832l-5.377,1.514l-24.843-0.537l-15.541-12.085l-18.784,4.7l-21.726-1.88l-12.166,13.294
|
||||
l-22.828,6.819l-11.398-3.534c-0.363-0.313-0.574-0.494-0.574-0.494l5.116,12.527c0,0,11.588,12.424,18.061,13.885
|
||||
c6.472,1.461,18.165-0.105,26.935-1.463c8.769-1.357,15.764-4.489,18.582-9.603c2.818-5.117,3.236-6.578,3.236-6.578
|
||||
s8.353,11.797,15.556,13.155c7.203,1.357,28.605-5.952,28.605-5.952s13.051-3.549,15.346-8.038
|
||||
c2.297-4.489,8.353-19.209,8.353-19.209L174.728,158.832z M44.456,169.038c-0.12-0.055-0.241-0.111-0.361-0.166
|
||||
c-0.856-0.739-1.556-1.343-2.013-1.736L44.456,169.038z"/>
|
||||
<g>
|
||||
<path class="st1" d="M195.832,70.085c-0.054-0.671-0.128-1.342-0.21-2.009c-0.058-0.473-0.133-0.967-0.215-1.424
|
||||
c-1.793-1.509-3.831-2.851-5.952-4.071c-2.299-1.343-4.704-2.546-7.159-3.663c-2.438-1.15-4.942-2.191-7.461-3.207
|
||||
c-1.257-0.51-2.525-1.005-3.798-1.477c-1.269-0.495-2.55-0.956-3.835-1.424c2.697,0.447,5.366,1.059,8.015,1.741
|
||||
c1.723,0.446,3.437,0.945,5.14,1.477c-12.112-31.655-41.07-52.27-72.687-52.27c-31.622,0-60.577,20.615-72.686,52.27
|
||||
c1.703-0.532,3.417-1.031,5.137-1.477c2.653-0.682,5.323-1.294,8.018-1.741c-1.289,0.468-2.567,0.929-3.84,1.424
|
||||
c-1.267,0.472-2.536,0.967-3.798,1.477c-2.519,1.016-5.016,2.057-7.46,3.207c-2.45,1.117-4.857,2.32-7.156,3.663
|
||||
c-2.121,1.219-4.157,2.562-5.957,4.071c-0.075,0.457-0.151,0.951-0.21,1.424c-0.081,0.667-0.155,1.338-0.21,2.009
|
||||
c-0.118,1.349-0.166,2.703-0.177,4.061c-0.027,2.713,0.156,5.426,0.5,8.11c0.37,2.692,0.864,5.366,1.595,7.951
|
||||
c0.36,1.295,0.768,2.572,1.24,3.808c0.237,0.617,0.495,1.225,0.764,1.816c0.134,0.294,0.274,0.585,0.413,0.864l0.172,0.328
|
||||
c0.199,0.101,0.408,0.204,0.607,0.3l1.204,0.575c0.671,0.305,1.6,0.746,2.368,1.09c0.043-0.037,0.086-0.075,0.123-0.114
|
||||
l-2.235-8.513c0.474-0.13,4.718-1.225,12.032-2.617c-0.59-0.112-1.186-0.241-1.772-0.381c-1.665-0.414-3.309-0.919-4.899-1.564
|
||||
c-0.79-0.333-1.568-0.697-2.309-1.115c-0.742-0.426-1.472-0.908-2.037-1.548c8.036,2.622,24.64,1.434,39.399-0.091
|
||||
c13.499-1.391,27.029-2.293,40.63-2.32c13.602,0.027,27.137,0.929,40.63,2.32c14.766,1.525,31.37,2.713,39.405,0.091
|
||||
c-0.564,0.64-1.293,1.123-2.035,1.548c-0.741,0.418-1.519,0.782-2.308,1.115c-1.592,0.645-3.234,1.15-4.899,1.564
|
||||
c-0.247,0.059-0.496,0.113-0.743,0.166c8.02,1.488,12.689,2.697,13.188,2.831l-2.138,8.11c0.43-0.194,0.864-0.381,1.29-0.574
|
||||
l1.202-0.575c0.2-0.097,0.403-0.199,0.607-0.3l0.166-0.328c0.146-0.279,0.286-0.57,0.419-0.864
|
||||
c0.27-0.591,0.528-1.199,0.764-1.816c0.473-1.236,0.882-2.513,1.241-3.808c0.731-2.585,1.225-5.259,1.595-7.951
|
||||
c0.345-2.685,0.526-5.398,0.501-8.11C196,72.788,195.951,71.434,195.832,70.085z"/>
|
||||
<path class="st2" d="M116.787,182.661c-1.064,0.16-2.128,0.295-3.186,0.375c-0.682,0.033-1.404,0.102-2.059,0.102l-0.242,0.005
|
||||
c0.822-1.837,1.446-3.26,1.919-4.339C114.182,179.884,115.407,181.221,116.787,182.661z"/>
|
||||
<path class="st2" d="M119.101,185.018c3.304,3.272,7.398,5.146,11.904,5.479c-7.569,3.074-14.702,4.26-20.197,4.63
|
||||
c-5.478,0.367-11.032-0.279-16.474-1.771c0.456-0.082,0.79-0.14,1.193-0.189c0.447-0.054,10.206-1.327,14.605-7.868l0.413,0.009
|
||||
l1.08-0.009c0.731,0,1.395-0.06,2.094-0.087c1.66-0.144,3.283-0.381,4.878-0.703C118.764,184.68,118.93,184.847,119.101,185.018z"
|
||||
/>
|
||||
<path class="st3" d="M128.464,87.071c-0.317,0.413-0.671,0.869-1.048,1.343c-1.933,2.444-4.614,5.57-7.794,8.627
|
||||
c-3.696-0.114-7.494-0.177-11.404-0.177c-6.46,0-12.655,0.171-18.537,0.457c8.311-3.449,18.296-6.818,29.109-8.842
|
||||
C121.948,87.881,125.181,87.403,128.464,87.071z"/>
|
||||
<path class="st3" d="M79.821,90.792c-2.966,2.084-6.317,4.744-9.566,7.971c-8.321,0.833-15.578,1.842-21.567,2.81
|
||||
C57.895,97.341,68.401,93.446,79.821,90.792z"/>
|
||||
<path class="st3" d="M181.48,107.969l-3.384,23.679l-16.212,11.355l-42.283-4.807l-6.365-20.961
|
||||
c-0.151-0.51-0.581-0.885-1.108-0.971c-1.567-0.253-2.953-0.382-4.108-0.382c-1.16,0-2.541,0.129-4.115,0.382
|
||||
c-0.522,0.086-0.95,0.461-1.106,0.971l-6.209,20.45l-42.047,9.357L37.881,135.37l-3.283-26.572
|
||||
c0.715-0.404,1.441-0.806,2.176-1.209c1.031-0.222,2.191-0.457,3.475-0.704l3.094,25.073c0.048,0.392,0.264,0.741,0.586,0.967
|
||||
l11.462,8.032c0.236,0.16,0.516,0.246,0.795,0.246c0.101,0,0.199-0.01,0.306-0.033l34.57-7.692
|
||||
c0.119-0.027,0.237-0.069,0.344-0.124c0.322-0.171,0.575-0.466,0.682-0.827l6.225-20.498c1.67-0.43,5.947-1.429,9.706-1.429
|
||||
c3.749,0,8.03,0.999,9.701,1.429l6.225,20.498c0.161,0.532,0.624,0.912,1.176,0.977l34.57,3.927
|
||||
c0.335,0.037,0.677-0.05,0.952-0.242l11.469-8.025c0.31-0.22,0.52-0.566,0.573-0.946l3.062-21.421
|
||||
C178.048,107.241,179.971,107.643,181.48,107.969z"/>
|
||||
<path class="st3" d="M185.751,93.119l-2.976,11.29c-6.086-1.342-19.456-3.975-37.654-5.747c5.946-2.535,12-5.715,17.531-9.69
|
||||
C173.481,90.502,181.432,92.141,185.751,93.119z"/>
|
||||
<g>
|
||||
<path class="st4" d="M63.841,128.441c2.357-1.274,5.021-1.085,9.19-1.079c0.447,0.011,0.908,0.005,1.39-0.005
|
||||
c0.41-0.005,0.822-0.011,1.258-0.022c4.296-0.042,7.869,0.366,7.806-6.381c-0.065-6.746-3.062-12.198-7.354-12.155
|
||||
c-4.297,0.037-8.454,5.564-8.197,12.306c0.07,1.756,0.328,3.023,0.742,3.937C64.931,125.98,63.899,128.296,63.841,128.441z
|
||||
M115.498,100.692c-1.665,1.349-3.421,2.61-5.249,3.712l-6.097,3.68c-3.824,0.466-7.143,1.412-7.331,1.467
|
||||
c-0.112,0.031-0.219,0.079-0.317,0.14c-0.296,0.171-0.521,0.455-0.629,0.794l-6.209,20.46l-33.185,7.38l-10.452-7.321
|
||||
l-3.041-24.634c5.936-1.09,13.874-2.352,23.41-3.42c-1.022,1.225-2.014,2.508-2.955,3.855l-5.677,8.149l8.266-5.511
|
||||
c0.123-0.086,5.387-3.549,13.998-7.761c8.582-0.644,18.053-1.059,28.188-1.059C110.689,100.622,113.113,100.65,115.498,100.692z"
|
||||
/>
|
||||
<path class="st4" d="M151.835,125.675c-0.042-0.16-0.945-2.873-4.942-2.397c0.461-1.003,0.666-2.356,0.521-4.21
|
||||
c-0.528-6.731-4.443-12.08-8.735-11.931c-4.292,0.152-7.042,5.731-6.805,12.478c0.236,6.741,3.84,6.694,8.132,6.543
|
||||
C145.776,126.051,148.945,124.278,151.835,125.675z M173.015,106.29l-2.992,20.944l-10.539,7.379l-33.141-3.766l-6.183-20.363
|
||||
c-0.14-0.451-0.494-0.799-0.945-0.934c-0.205-0.06-4.308-1.23-8.659-1.607l0.795-0.053c0.687-0.049,12.118-1.451,25.767-6.157
|
||||
C152.233,102.894,164.576,104.753,173.015,106.29z"/>
|
||||
</g>
|
||||
<g>
|
||||
<path class="st5" d="M63.841,128.441c2.357-1.274,5.021-1.085,9.19-1.079c0.447,0.011,0.908,0.005,1.39-0.005
|
||||
c0.41-0.005,0.822-0.011,1.258-0.022c4.296-0.042,7.869,0.366,7.806-6.381c-0.065-6.746-3.062-12.198-7.354-12.155
|
||||
c-4.297,0.037-8.454,5.564-8.197,12.306c0.07,1.756,0.328,3.023,0.742,3.937C64.931,125.98,63.899,128.296,63.841,128.441z
|
||||
M115.498,100.692c-1.665,1.349-3.421,2.61-5.249,3.712l-6.097,3.68c-3.824,0.466-7.143,1.412-7.331,1.467
|
||||
c-0.112,0.031-0.219,0.079-0.317,0.14c-0.296,0.171-0.521,0.455-0.629,0.794l-6.209,20.46l-33.185,7.38l-10.452-7.321
|
||||
l-3.041-24.634c5.936-1.09,13.874-2.352,23.41-3.42c-1.022,1.225-2.014,2.508-2.955,3.855l-5.677,8.149l8.266-5.511
|
||||
c0.123-0.086,5.387-3.549,13.998-7.761c8.582-0.644,18.053-1.059,28.188-1.059C110.689,100.622,113.113,100.65,115.498,100.692z"
|
||||
/>
|
||||
<path class="st5" d="M151.835,125.675c-0.042-0.16-0.945-2.873-4.942-2.397c0.461-1.003,0.666-2.356,0.521-4.21
|
||||
c-0.528-6.731-4.443-12.08-8.735-11.931c-4.292,0.152-7.042,5.731-6.805,12.478c0.236,6.741,3.84,6.694,8.132,6.543
|
||||
C145.776,126.051,148.945,124.278,151.835,125.675z M173.015,106.29l-2.992,20.944l-10.539,7.379l-33.141-3.766l-6.183-20.363
|
||||
c-0.14-0.451-0.494-0.799-0.945-0.934c-0.205-0.06-4.308-1.23-8.659-1.607l0.795-0.053c0.687-0.049,12.118-1.451,25.767-6.157
|
||||
C152.233,102.894,164.576,104.753,173.015,106.29z"/>
|
||||
</g>
|
||||
<path class="st2" d="M187.481,115.502c0.508,0.419,0.911,1.504,0.456,6.558c-0.559,6.188-3.16,17.049-4.771,18.8
|
||||
c-1.778,0.344-5.505-0.064-7.778-0.595c0.393-1.559,0.505-2.306,0.822-3.9l3.975-2.781c0.317-0.22,0.526-0.566,0.58-0.941
|
||||
l2.778-19.466C185.229,114.089,186.964,115.076,187.481,115.502z"/>
|
||||
<path class="st2" d="M40.937,140.908c0.199,0.704,0.408,1.407,0.624,2.1c-2.139,0.628-6.495,1.23-8.465,0.886
|
||||
c-1.633-1.645-4.679-12.966-5.345-18.978c-0.543-4.871-0.162-5.924,0.333-6.334c0.575-0.483,2.728-1.708,4.593-2.707l2.519,20.449
|
||||
c0.048,0.393,0.257,0.741,0.586,0.967L40.937,140.908z"/>
|
||||
<path class="st2" d="M121.347,141.194l-0.151,1.305c0,0-4.581,4.248-11.956,5.199c-7.375,0.95-13.171-3.582-13.171-3.582
|
||||
c0.242,0.788,0.586,2.567,2.256,4.086c-1.965-0.235-4.087-0.393-6.313-0.393c-0.804,0-1.616,0.023-2.401,0.061
|
||||
c-4.539,0.237-10.924,7.1-15.414,14.014c-2.203,0.697-9.089,2.883-17.06,5.237c-7.44-10.309-11.098-20.842-11.469-21.932
|
||||
l0.005-0.006c-0.15-0.419-0.301-0.839-0.441-1.268l1.913,1.338v0.005l4.726,3.309l1.58,1.101c0.236,0.167,0.515,0.253,0.794,0.253
|
||||
c0.102,0,0.204-0.011,0.305-0.031l43.435-9.67c0.487-0.107,0.881-0.473,1.025-0.95l6.194-20.39c1.069-0.145,2.008-0.22,2.814-0.22
|
||||
c0.801,0,1.746,0.075,2.815,0.22l6.374,20.997c0.162,0.532,0.624,0.919,1.171,0.977L121.347,141.194z"/>
|
||||
<path class="st2" d="M170.926,140.066l1.402-0.984c-0.232,0.973-0.484,1.94-0.747,2.896c-1.949,6.248-4.25,11.774-6.805,16.656
|
||||
c-0.565,0.039-1.161,0.061-1.8,0.061c-1.972,0-3.986-0.167-6.215-0.371c-3.868-0.355-10.007-1.058-11.946-1.283
|
||||
c-1.67-1.332-7.385-5.873-12.14-9.615c-0.187-0.151-0.348-0.291-0.505-0.42c-0.837-0.708-1.789-1.513-3.717-1.513
|
||||
c-1.751,0-4.308,0.638-10.489,2.508c3.212-2.401,3.233-5.5,3.233-5.5l0.151-1.305l40.748,4.629
|
||||
c0.332,0.038,0.676-0.048,0.955-0.241l4.094-2.868L170.926,140.066z"/>
|
||||
<path class="st6" d="M140.937,54.337c0.124,3.625,0.033,10.194-1.655,16.345c-0.068,0.237-0.058,0.479,0,0.704
|
||||
c-2.148-0.226-4.297-0.419-6.446-0.591c2.412-5.054,2.938-10.436,3.052-12.332C137.74,57.146,139.584,55.567,140.937,54.337z"/>
|
||||
<path class="st6" d="M79.456,58.462c0.112,1.896,0.638,7.267,3.046,12.317c-2.149,0.171-4.297,0.37-6.441,0.596
|
||||
c0.058-0.221,0.065-0.457,0-0.694c-1.686-6.139-1.772-12.714-1.654-16.345C75.76,55.567,77.597,57.146,79.456,58.462z"/>
|
||||
<path class="st7" d="M151.835,125.675c-2.89-1.396-6.059,0.377-11.828,0.484c-4.292,0.151-7.896,0.198-8.132-6.543
|
||||
c-0.237-6.747,2.513-12.326,6.805-12.478c4.292-0.15,8.207,5.2,8.735,11.931c0.145,1.854-0.06,3.207-0.521,4.21
|
||||
C150.89,122.802,151.793,125.514,151.835,125.675z M138.347,115.797c1.209-0.027,2.175-1.026,2.154-2.235
|
||||
c-0.021-1.214-1.02-2.181-2.235-2.153c-1.213,0.02-2.175,1.02-2.152,2.234C136.135,114.851,137.134,115.819,138.347,115.797z"/>
|
||||
|
||||
<ellipse transform="matrix(0.9998 -0.0183 0.0183 0.9998 -2.0526 2.5461)" class="st8" cx="138.307" cy="113.602" rx="2.194" ry="2.194"/>
|
||||
<path class="st7" d="M83.484,120.953c0.063,6.747-3.509,6.339-7.806,6.381c-0.435,0.011-0.848,0.016-1.258,0.022
|
||||
c-0.482,0.011-0.944,0.016-1.39,0.005c-4.168-0.005-6.833-0.194-9.19,1.079c0.058-0.145,1.09-2.461,4.835-3.4
|
||||
c-0.414-0.914-0.673-2.181-0.742-3.937c-0.257-6.741,3.9-12.269,8.197-12.306C80.422,108.755,83.419,114.208,83.484,120.953z
|
||||
M76.85,117.424c1.209-0.031,2.165-1.043,2.133-2.251c-0.033-1.214-1.041-2.17-2.25-2.137c-1.215,0.031-2.172,1.041-2.139,2.25
|
||||
C74.626,116.501,75.636,117.457,76.85,117.424z"/>
|
||||
|
||||
<ellipse transform="matrix(0.9997 -0.0257 0.0257 0.9997 -2.9357 2.0113)" class="st8" cx="76.79" cy="115.23" rx="2.195" ry="2.195"/>
|
||||
<g class="st9">
|
||||
<path class="st6" d="M50.691,75.155c0,0,0.667-8.692,2.03-12.023c0.702-1.717,4.996-2.81,8.276-3.591
|
||||
c3.278-0.78,8.508-2.342,9.524,2.264c1.015,4.606,2.653,7.963,3.746,9.446l-1.404-18.97l-22.562,5.464l-1.484,16.786l0.703,1.327
|
||||
L50.691,75.155"/>
|
||||
<path class="st6" d="M164.855,75.155c0,0-0.666-8.692-2.029-12.023c-0.703-1.717-4.997-2.81-8.275-3.591
|
||||
c-3.28-0.78-8.51-2.342-9.526,2.264c-1.013,4.606-2.654,7.963-3.748,9.446l1.407-18.97l22.562,5.464l1.483,16.786l-0.703,1.327
|
||||
L164.855,75.155"/>
|
||||
</g>
|
||||
<path class="st10" d="M132.965,18.378c0,0-0.598,45.49-11.224,45.49c-10.626,0-12.75,0-12.75,0h-2.125c0,0-2.126,0-12.752,0
|
||||
S82.63,18.398,82.63,18.398l-5.22,15.438l0.085,21.183l3.707,2.947l1.685,9.096l2.357,5.307l45.482,0.084l2.105-3.791l1.769-6.4
|
||||
l0.254-4.043l5.023-14.341L132.965,18.378z"/>
|
||||
<path class="st10" d="M166.429,60.794c0,0,2.187,15.692,7.974,18.522c5.788,2.829,0,0,0,0l-8.103-2.444L166.429,60.794z"/>
|
||||
<path class="st10" d="M48.908,60.794c0,0-2.187,15.692-7.975,18.522c-5.788,2.829,0,0,0,0l8.104-2.444L48.908,60.794z"/>
|
||||
<path class="st7" d="M167.987,76.8c2.755,0.902,5.526,1.858,8.036,3.325c-1.343-0.532-2.729-0.913-4.126-1.257
|
||||
c-1.391-0.355-2.793-0.655-4.201-0.924c-2.82-0.531-5.65-0.982-8.498-1.327c-2.841-0.37-5.687-0.682-8.546-0.924
|
||||
c-2.858-0.241-5.709-0.483-8.573-0.65c-11.446-0.704-22.924-0.88-34.41-0.892c-11.483,0.006-22.962,0.221-34.409,0.897
|
||||
c-2.862,0.166-5.715,0.409-8.572,0.651c-2.857,0.241-5.71,0.548-8.546,0.923c-2.847,0.345-5.678,0.796-8.498,1.327
|
||||
c-1.407,0.264-2.81,0.57-4.206,0.919c-1.391,0.344-2.783,0.725-4.126,1.257c2.509-1.466,5.28-2.427,8.041-3.331
|
||||
c0.232-0.075,0.467-0.139,0.703-0.214c-0.015-0.059-0.032-0.113-0.043-0.177c-0.048-0.317-1.069-7.859,0.709-18.645
|
||||
c0.086-0.516,0.456-0.935,0.962-1.075l2.917-0.831c0.634-22.625,9.952-33.266,10.243-33.594
|
||||
c-8.326,13.397-8.25,29.286-8.106,32.986l18.128-5.152c0.016-0.005,0.026-0.005,0.042-0.01c0.076-0.016,0.151-0.027,0.226-0.032
|
||||
c0.021,0,0.049-0.006,0.075-0.006c0.092-0.005,0.195,0.006,0.297,0.027c0.015,0,0.031,0.011,0.053,0.016
|
||||
c0.075,0.016,0.145,0.042,0.224,0.075c0.033,0.016,0.054,0.033,0.086,0.049c0.058,0.033,0.119,0.07,0.177,0.112
|
||||
c0.016,0.011,0.034,0.016,0.049,0.033c0.011,0.011,0.021,0.022,0.032,0.032c0.016,0.016,0.037,0.027,0.054,0.044
|
||||
c0.012,0.016,0.494,0.493,1.262,1.209c-0.182-5.973,0.102-23.108,8.262-37.31c-0.172,0.498-6.646,19.428-4.415,40.645
|
||||
c0.724,0.58,1.486,1.149,2.229,1.649c0.359,0.247,0.58,0.655,0.585,1.09c0.006,0.07,0.161,6.833,3.148,12.586
|
||||
c0.042,0.086,0.074,0.177,0.102,0.268c7.429-0.505,14.878-0.709,22.312-0.714c7.436,0.005,14.88,0.22,22.307,0.731
|
||||
c0.027-0.097,0.06-0.193,0.109-0.285c2.986-5.753,3.142-12.516,3.142-12.586c0.01-0.436,0.231-0.843,0.591-1.09
|
||||
c0.741-0.5,1.493-1.069,2.224-1.649c2.234-21.217-4.24-40.147-4.411-40.645c8.153,14.201,8.444,31.336,8.262,37.31
|
||||
c0.762-0.715,1.246-1.192,1.261-1.209c0.016-0.016,0.039-0.027,0.053-0.044c0.012-0.01,0.018-0.021,0.033-0.032
|
||||
c0.016-0.016,0.033-0.022,0.049-0.033c0.06-0.042,0.119-0.079,0.177-0.118c0.028-0.01,0.054-0.027,0.081-0.043
|
||||
c0.081-0.033,0.155-0.059,0.236-0.08c0.016,0,0.033-0.011,0.049-0.011c0.096-0.021,0.2-0.032,0.296-0.027
|
||||
c0.027,0,0.049,0.006,0.07,0.006c0.075,0.005,0.156,0.016,0.231,0.032c0.012,0.006,0.028,0.006,0.042,0.01l18.129,5.152
|
||||
c0.146-3.7,0.221-19.59-8.104-32.986c0.289,0.328,9.609,10.969,10.237,33.594l2.922,0.831c0.499,0.14,0.875,0.559,0.962,1.075
|
||||
c1.777,10.786,0.752,18.328,0.708,18.645c-0.01,0.065-0.026,0.124-0.042,0.182C167.519,76.655,167.75,76.724,167.987,76.8z
|
||||
M164.69,75.832c0.14-1.207,0.789-7.809-0.591-16.801l-20.52-5.833c0.184,3.475,0.265,11.012-1.707,18.199
|
||||
c-0.026,0.086-0.058,0.172-0.101,0.258c0.203,0.021,0.408,0.037,0.606,0.064c5.769,0.661,11.511,1.584,17.189,2.83
|
||||
C161.278,74.947,162.992,75.372,164.69,75.832z M139.281,70.681c1.688-6.15,1.779-12.72,1.655-16.345
|
||||
c-1.353,1.23-3.197,2.809-5.049,4.125c-0.114,1.896-0.64,7.278-3.052,12.332c2.149,0.173,4.298,0.366,6.446,0.591
|
||||
C139.223,71.16,139.213,70.919,139.281,70.681z M82.501,70.779c-2.408-5.05-2.934-10.422-3.046-12.317
|
||||
c-1.858-1.316-3.696-2.895-5.049-4.125c-0.119,3.631-0.032,10.206,1.654,16.345c0.065,0.237,0.058,0.473,0,0.694
|
||||
C78.205,71.149,80.352,70.951,82.501,70.779z M73.568,71.643c-0.039-0.075-0.07-0.161-0.098-0.247
|
||||
c-1.975-7.187-1.889-14.723-1.712-18.199l-20.514,5.833c-1.38,8.982-0.736,15.583-0.597,16.797
|
||||
c1.703-0.462,3.411-0.887,5.131-1.284c2.835-0.628,5.693-1.154,8.556-1.638c2.869-0.478,5.747-0.843,8.626-1.192
|
||||
C73.165,71.686,73.364,71.671,73.568,71.643z"/>
|
||||
<g id="XMLID_1_">
|
||||
<g>
|
||||
<path class="st7" d="M129.293,18.973v17.025h-12.068v-4.974h-2.72v22.981h4.109v12.85H97.505v-12.85h4.092V31.025h-2.711v4.974
|
||||
h-12.06V18.973H129.293z M125.667,32.381v-9.789h-5.257h-9.523H90.443v9.789h4.816v-4.974h9.964v30.225h-4.1v5.606h13.865
|
||||
v-5.606h-4.1V27.407h9.964v4.974H125.667z"/>
|
||||
<polygon class="st0" points="125.667,22.591 125.667,32.381 120.851,32.381 120.851,27.407 110.887,27.407 110.887,57.632
|
||||
114.987,57.632 114.987,63.238 101.123,63.238 101.123,57.632 105.223,57.632 105.223,27.407 95.259,27.407 95.259,32.381
|
||||
90.443,32.381 90.443,22.591 110.887,22.591 120.41,22.591 "/>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
</g>
|
||||
<path class="st3" d="M30.694,93.119c1.759-0.399,4.136-0.907,7.051-1.47c-1.791,1.221-3.909,2.754-6.222,4.597L30.694,93.119z"/>
|
||||
<path class="st5" d="M95.111,139.78c0,0,0.492,3.165-3.938,4.519c-4.428,1.355-32.482,9.716-35.682,9.263
|
||||
c-3.199-0.451-11.319-5.874-11.319-5.874l-1.969-7.004l12.016,7.492L95.111,139.78z"/>
|
||||
<path class="st5" d="M120.242,139.167c0,0-0.354,3.182,4.131,4.345c4.484,1.161,32.875,8.295,36.05,7.704
|
||||
c3.176-0.591,11.053-6.361,11.053-6.361l1.663-7.084l-11.045,6.588L120.242,139.167z"/>
|
||||
<path class="st5" d="M28.412,133.956c0,0,3.887,7.775,10.166,5.083l4.485,1.645l-0.448,3.29l-9.419,1.195l-2.541-1.494
|
||||
L28.412,133.956z"/>
|
||||
<path class="st5" d="M187.551,131.822c0,0-6.353,8.115-12.632,5.424l-2.019,1.302l0.448,3.289l9.419,1.196l2.54-1.495
|
||||
L187.551,131.822z"/>
|
||||
<path class="st5" d="M89.279,192.904c0,0,23.03,11.611,49.106-4.188l-8.374-0.571c0,0-18.272,7.232-32.738,3.235L89.279,192.904z"
|
||||
/>
|
||||
<path class="st7" d="M112.626,171.509l1.594,1.899c0.036,0.046,3.577,4.26,7.906,8.552c2.879,2.853,6.357,4.297,10.343,4.297
|
||||
c1.361,0,2.791-0.175,4.235-0.523c1.34-0.326,2.796-0.673,4.287-1.03c5.384-1.287,11.482-2.749,14.438-3.577
|
||||
c0.585-0.166,1.238-0.315,1.925-0.472c3.935-0.909,9.329-2.163,12.187-7.889c2.149-4.297,5.047-9.874,7.197-13.961
|
||||
c-1.863,0.859-3.816,1.79-5.203,2.52c-2.138,1.123-4.938,1.667-8.558,1.667c-2.152,0-4.266-0.181-6.605-0.389
|
||||
c-4.675-0.43-12.586-1.361-12.667-1.372l-0.606-0.067l-0.478-0.383c-0.071-0.052-7.003-5.575-12.606-9.981
|
||||
c-0.227-0.186-0.434-0.358-0.621-0.513c-0.59-0.503-0.59-0.503-0.942-0.503c-1.797,0-7.02,1.62-18.462,5.167l-0.703,0.223
|
||||
l-0.689-0.26c-0.078-0.026-7.585-2.81-16.581-2.81c-0.736,0-1.47,0.019-2.185,0.056c-0.901,0.046-5.958,2.448-12.425,12.68
|
||||
l-0.419,0.657l-0.741,0.238c-0.107,0.037-11.238,3.63-23.042,7.005l-0.766,0.218l-0.725-0.337
|
||||
c-0.077-0.031-4.696-2.174-9.091-4.194c2.397,3.541,5.462,7.958,8.159,11.422c4.711,6.067,10.649,11.674,22.034,11.674
|
||||
c1.428,0,2.945-0.088,4.503-0.265c11.581-1.309,14.563-1.837,16.168-2.117c0.543-0.092,0.973-0.171,1.522-0.238
|
||||
c0.088-0.011,9.571-1.237,12.232-7.206c2.744-6.134,3.298-7.595,3.319-7.651l0.968-2.583c0,0,0.12-0.669,0.317-0.877
|
||||
c0,0.005,0,0.005,0.005,0.005l0.019,0.016C112.174,170.826,112.626,171.509,112.626,171.509z M40.499,55.71
|
||||
c-2.516,1.014-5.016,2.06-7.46,3.209c-2.449,1.119-4.856,2.32-7.155,3.66c-2.121,1.222-4.157,2.563-5.954,4.076
|
||||
c-0.077,0.455-0.149,0.952-0.211,1.423c-0.078,0.667-0.156,1.336-0.208,2.009c-0.119,1.346-0.166,2.703-0.18,4.059
|
||||
c-0.026,2.713,0.16,5.426,0.502,8.112c0.372,2.692,0.864,5.369,1.594,7.952c0.363,1.295,0.767,2.573,1.243,3.804
|
||||
c0.233,0.623,0.492,1.228,0.762,1.818c0.134,0.294,0.274,0.585,0.413,0.864l0.172,0.326c0.201,0.104,0.409,0.207,0.605,0.3
|
||||
l1.206,0.574c0.673,0.311,1.6,0.751,2.366,1.093c0.046-0.037,0.088-0.078,0.124-0.114l-2.231-8.511
|
||||
c0.471-0.129,4.717-1.227,12.032-2.619c-0.59-0.109-1.191-0.238-1.775-0.379c-1.662-0.413-3.309-0.921-4.898-1.563
|
||||
c-0.787-0.336-1.569-0.699-2.309-1.119c-0.741-0.425-1.471-0.905-2.035-1.547c8.035,2.624,24.637,1.433,39.398-0.088
|
||||
c13.501-1.393,27.028-2.293,40.628-2.325c13.6,0.031,27.138,0.931,40.63,2.325c14.77,1.522,31.374,2.713,39.406,0.088
|
||||
c-0.564,0.642-1.293,1.122-2.034,1.547c-0.739,0.42-1.522,0.782-2.309,1.119c-1.595,0.642-3.236,1.149-4.903,1.563
|
||||
c-0.244,0.056-0.492,0.114-0.741,0.166c8.02,1.486,12.689,2.697,13.186,2.832l-2.138,8.107c0.43-0.192,0.864-0.377,1.288-0.574
|
||||
l1.207-0.574c0.196-0.094,0.404-0.196,0.606-0.3l0.166-0.326c0.144-0.279,0.284-0.57,0.419-0.864
|
||||
c0.27-0.591,0.528-1.196,0.767-1.818c0.471-1.231,0.879-2.51,1.236-3.804c0.731-2.583,1.228-5.26,1.595-7.952
|
||||
c0.346-2.686,0.528-5.4,0.502-8.112c-0.01-1.356-0.062-2.713-0.176-4.059c-0.057-0.673-0.13-1.341-0.213-2.009
|
||||
c-0.057-0.471-0.135-0.968-0.213-1.423c-1.797-1.513-3.831-2.853-5.954-4.076c-2.299-1.34-4.704-2.541-7.159-3.66
|
||||
c-2.438-1.149-4.943-2.195-7.46-3.209c-1.259-0.508-2.528-1.005-3.801-1.476c-1.267-0.491-2.552-0.956-3.835-1.423
|
||||
c2.696,0.445,5.369,1.06,8.013,1.739c1.724,0.446,3.444,0.948,5.141,1.481c-12.11-31.658-41.07-52.272-72.685-52.272
|
||||
c-31.622,0-60.576,20.614-72.684,52.272c1.702-0.533,3.416-1.035,5.135-1.481c2.651-0.678,5.322-1.294,8.02-1.739
|
||||
c-1.29,0.466-2.568,0.931-3.842,1.423C43.03,54.705,41.763,55.202,40.499,55.71z M199.929,74.026
|
||||
c0.146,2.914,0.068,5.833-0.258,8.733c-0.305,2.894-0.854,5.762-1.619,8.605c-0.4,1.414-0.86,2.811-1.404,4.198
|
||||
c-0.275,0.693-0.569,1.383-0.89,2.071c-0.161,0.341-0.331,0.678-0.523,1.025l-0.284,0.512c-0.104,0.186-0.187,0.326-0.348,0.574
|
||||
l-0.294,0.457l-0.461,0.237c-0.492,0.254-0.895,0.445-1.342,0.653l-1.298,0.585c-0.871,0.372-1.745,0.724-2.62,1.065
|
||||
c-0.611,0.239-1.15,0.457-1.662,0.674l-1.444,5.487c-0.036-0.009-0.471-0.12-1.283-0.315l-0.078,0.574
|
||||
c1.594,0.833,4.726,2.522,5.793,3.403c2.148,1.775,2.299,4.587,1.823,9.841c-0.244,2.697-1.139,7.946-2.381,12.767
|
||||
c-2.144,8.298-3.283,9.273-4.753,9.649c-0.746,0.192-1.894,0.383-3.008,0.383c-2.266,0-5.353,0.063-7.429-0.439
|
||||
c-0.533,1.888-2.055,6.812-5.068,12.962c0.151-0.073,0.3-0.135,0.435-0.207c3.717-1.952,10.861-5.064,11.162-5.199l5.643-2.452
|
||||
l-2.89,5.435c-0.067,0.118-6.264,11.773-10.059,19.383c-3.769,7.538-10.835,9.179-15.065,10.151
|
||||
c-0.637,0.151-1.241,0.291-1.733,0.425c-3.035,0.854-9.18,2.319-14.599,3.623c-0.064,0.016-0.13,0.033-0.197,0.042
|
||||
c-3.335,2.061-6.974,3.899-10.955,5.411c-14.568,5.518-29.923,5.208-43.844,0.092c-2.261,0.291-5.234,0.647-9.193,1.097
|
||||
c-1.72,0.192-3.392,0.291-4.985,0.291c-13.264,0-20.294-6.736-25.425-13.331c-5.493-7.062-12.212-17.546-12.497-17.985L31,158.426
|
||||
l6.585,2.961c3.152,1.419,12.524,5.757,15.205,7c0.217-0.061,0.43-0.124,0.642-0.186c-4.457-6.357-8.112-13.605-10.695-21.634
|
||||
c-2.195,0.662-5.576,1.175-8.206,1.175c-0.961,0-1.822-0.072-2.484-0.228c-1.471-0.336-3.148-1.754-5.431-9.795
|
||||
c-1.325-4.668-2.314-9.764-2.603-12.387c-0.57-5.121-0.466-7.864,1.662-9.636c1.283-1.071,5.611-3.344,6.507-3.809l-0.192-1.58
|
||||
c-13.75,8.08-21.991,15.22-22.157,15.366L0,134.302l7.005-11.047c5.544-8.755,11.948-15.832,17.84-21.284
|
||||
c-0.244-0.098-0.471-0.196-0.71-0.294l-1.299-0.585c-0.445-0.208-0.849-0.399-1.34-0.653l-0.461-0.237l-0.295-0.457
|
||||
c-0.166-0.249-0.238-0.388-0.347-0.574l-0.29-0.512c-0.181-0.347-0.358-0.684-0.518-1.025c-0.327-0.689-0.621-1.378-0.89-2.071
|
||||
c-0.544-1.387-1.005-2.784-1.404-4.198c-0.771-2.843-1.315-5.71-1.62-8.605c-0.321-2.9-0.404-5.819-0.259-8.733
|
||||
c0.078-1.455,0.218-2.909,0.419-4.354c0.104-0.725,0.213-1.45,0.358-2.17c0.15-0.734,0.296-1.418,0.518-2.221l0.155-0.564
|
||||
l0.404-0.317c2.294-1.802,4.768-3.163,7.284-4.369c2.071-0.973,4.183-1.833,6.311-2.616c5.943-16.493,16.162-31.118,29.591-41.311
|
||||
C74.337,5.57,90.664,0,107.671,0c17.007,0,33.334,5.57,47.218,16.106c13.43,10.193,23.649,24.819,29.588,41.307
|
||||
c2.133,0.787,4.24,1.641,6.316,2.62c2.515,1.206,4.99,2.567,7.283,4.369l0.404,0.317l0.156,0.564
|
||||
c0.227,0.803,0.372,1.487,0.517,2.221c0.146,0.72,0.26,1.445,0.357,2.17C199.713,71.117,199.858,72.571,199.929,74.026z
|
||||
M187.934,122.057c0.456-5.052,0.058-6.139-0.455-6.554c-0.513-0.43-2.247-1.412-3.935-2.329l-2.779,19.464
|
||||
c-0.052,0.378-0.265,0.721-0.58,0.942l-3.977,2.781c-0.315,1.593-0.429,2.345-0.817,3.903c2.273,0.528,5.999,0.938,7.775,0.595
|
||||
C184.778,139.111,187.38,128.249,187.934,122.057z M182.773,104.409l2.977-11.29c-4.318-0.978-12.27-2.615-23.1-4.148
|
||||
c-5.53,3.976-11.582,7.155-17.53,9.691C163.319,100.433,176.69,103.068,182.773,104.409z M178.093,131.646l3.385-23.676
|
||||
c-1.506-0.326-3.431-0.729-5.731-1.169l-3.059,21.422c-0.057,0.378-0.265,0.725-0.575,0.943l-11.472,8.023
|
||||
c-0.27,0.192-0.616,0.28-0.947,0.243l-34.572-3.929c-0.554-0.063-1.015-0.446-1.176-0.973l-6.227-20.5
|
||||
c-1.668-0.431-5.949-1.43-9.696-1.43c-3.764,0-8.041,0.999-9.708,1.43l-6.228,20.5c-0.109,0.356-0.358,0.653-0.682,0.822
|
||||
c-0.104,0.057-0.223,0.098-0.343,0.125l-34.572,7.692c-0.109,0.022-0.202,0.033-0.306,0.033c-0.279,0-0.559-0.083-0.792-0.25
|
||||
l-11.467-8.029c-0.321-0.223-0.534-0.575-0.585-0.968l-3.091-25.072c-1.284,0.249-2.443,0.487-3.479,0.703
|
||||
c-0.734,0.405-1.46,0.809-2.174,1.213l3.281,26.568l16.666,11.675l42.047-9.354l6.207-20.449c0.156-0.514,0.585-0.892,1.108-0.975
|
||||
c1.574-0.253,2.95-0.382,4.116-0.382c1.153,0,2.536,0.129,4.105,0.382c0.528,0.083,0.957,0.461,1.108,0.975l6.366,20.956
|
||||
l42.282,4.808L178.093,131.646z M170.023,127.235l2.992-20.948c-8.439-1.536-20.78-3.394-35.897-4.554
|
||||
c-13.647,4.707-25.077,6.108-25.766,6.155l-0.797,0.057c4.353,0.374,8.454,1.544,8.66,1.605c0.452,0.135,0.804,0.481,0.944,0.933
|
||||
l6.186,20.366l33.138,3.764L170.023,127.235z M172.326,139.08l-1.404,0.983l-3.779,2.651l-4.095,2.868
|
||||
c-0.279,0.192-0.621,0.28-0.954,0.243l-40.746-4.633l-2.966-0.337c-0.549-0.063-1.01-0.446-1.171-0.977l-6.377-20.998
|
||||
c-1.066-0.145-2.014-0.219-2.81-0.219c-0.809,0-1.751,0.073-2.817,0.219l-6.192,20.392c-0.145,0.476-0.538,0.839-1.025,0.946
|
||||
l-43.435,9.672c-0.103,0.02-0.206,0.03-0.305,0.03c-0.279,0-0.559-0.083-0.798-0.253l-1.578-1.098l-4.726-3.307v-0.011
|
||||
l-1.91-1.335c0.135,0.43,0.289,0.85,0.441,1.268l-0.006,0.006c0.368,1.092,4.028,11.622,11.467,21.929
|
||||
c7.967-2.35,14.858-4.535,17.057-5.234c4.488-6.917,10.877-13.777,15.418-14.014c0.781-0.037,1.595-0.061,2.402-0.061
|
||||
c2.221,0,4.344,0.16,6.31,0.393c-1.671-1.517-2.013-3.298-2.256-4.085c0,0,5.793,4.53,13.17,3.584
|
||||
c7.378-0.953,11.959-5.204,11.959-5.204s-0.021,3.102-3.236,5.503c6.182-1.869,8.739-2.511,10.489-2.511
|
||||
c1.931,0,2.883,0.808,3.717,1.519c0.161,0.129,0.322,0.268,0.507,0.419c4.753,3.742,10.468,8.283,12.141,9.614
|
||||
c1.936,0.227,8.075,0.926,11.943,1.283c2.23,0.201,4.245,0.372,6.217,0.372c0.637,0,1.233-0.026,1.797-0.063
|
||||
c2.558-4.88,4.857-10.411,6.808-16.653C171.844,141.021,172.099,140.053,172.326,139.08z M157.292,87.487
|
||||
c-0.01-0.006-0.02-0.012-0.031-0.012c-3.272-0.243-6.543-0.466-9.826-0.651c-4.555-0.26-9.112-0.477-13.667-0.668
|
||||
c-0.265,0.394-0.802,1.17-1.574,2.225c-2.479,3.355-7.398,9.51-13.704,14.729c8.926-1.6,24.409-5.56,37.803-14.905
|
||||
C156.629,87.967,156.961,87.719,157.292,87.487z M127.416,88.413c0.377-0.471,0.729-0.926,1.044-1.34
|
||||
c-3.281,0.331-6.512,0.808-9.67,1.408c-10.814,2.024-20.801,5.389-29.11,8.837c5.887-0.285,12.078-0.455,18.54-0.455
|
||||
c3.908,0,7.708,0.067,11.404,0.176C122.803,93.983,125.485,90.857,127.416,88.413z M131.003,190.498
|
||||
c-4.503-0.332-8.598-2.205-11.903-5.477c-0.171-0.175-0.336-0.343-0.502-0.512c-1.598,0.321-3.219,0.559-4.881,0.704
|
||||
c-0.698,0.026-1.361,0.087-2.091,0.087l-1.083,0.011l-0.413-0.011c-4.396,6.539-14.159,7.813-14.605,7.87
|
||||
c-0.403,0.046-0.734,0.103-1.191,0.186c5.442,1.491,10.996,2.138,16.474,1.77C116.3,194.759,123.435,193.568,131.003,190.498z
|
||||
M113.603,183.037c1.056-0.083,2.117-0.218,3.184-0.378c-1.383-1.438-2.604-2.775-3.568-3.857
|
||||
c-0.471,1.082-1.096,2.505-1.92,4.339h0.243C112.2,183.142,112.92,183.07,113.603,183.037z M110.249,104.405
|
||||
c1.827-1.103,3.582-2.366,5.249-3.712c-2.387-0.041-4.809-0.072-7.278-0.072c-10.137,0-19.606,0.415-28.189,1.061
|
||||
c-8.61,4.209-13.875,7.672-13.998,7.76l-8.268,5.514l5.679-8.149c0.937-1.353,1.931-2.636,2.956-3.857
|
||||
c-9.536,1.066-17.477,2.329-23.41,3.422l3.038,24.632l10.453,7.321l33.184-7.378l6.212-20.464
|
||||
c0.104-0.337,0.331-0.621,0.627-0.793c0.098-0.063,0.202-0.109,0.315-0.14c0.192-0.052,3.51-0.999,7.336-1.465L110.249,104.405z
|
||||
M114.065,85.617c-2.31-0.036-4.623-0.057-6.933-0.062h-0.005c-3.39,0.005-6.787,0.041-10.189,0.109l-6.269,2.971
|
||||
c-0.005,0.005-0.041,0.021-0.088,0.048c-0.942,0.46-9.174,4.613-16.919,12.021c6.943-3.65,17.146-8.418,29.153-12.115
|
||||
C106.412,87.487,110.181,86.471,114.065,85.617z M70.251,98.761c3.251-3.225,6.605-5.886,9.567-7.967
|
||||
c-11.415,2.651-21.923,6.543-31.128,10.778C54.679,100.604,61.932,99.595,70.251,98.761z M72.41,88.812
|
||||
c3.825-1.072,7.771-2.009,11.813-2.796c-5.798,0.212-11.6,0.481-17.393,0.808c-3.366,0.186-6.715,0.414-10.065,0.667
|
||||
c-1.678,0.129-3.345,0.263-5.007,0.445c-0.476,0.046-0.942,0.098-1.418,0.16c-4.369,2.614-21.127,13.134-32.631,26.889
|
||||
C28.888,107.216,48.363,95.542,72.41,88.812z M41.56,143.009c-0.218-0.693-0.424-1.398-0.621-2.102l-5.162-3.612
|
||||
c-0.327-0.228-0.534-0.575-0.586-0.969l-2.516-20.449c-1.864,0.999-4.017,2.225-4.592,2.707c-0.497,0.409-0.875,1.46-0.336,6.332
|
||||
c0.668,6.01,3.712,17.333,5.348,18.979C35.063,144.242,39.422,143.637,41.56,143.009z M37.745,91.649
|
||||
c-2.915,0.564-5.292,1.071-7.051,1.47l0.829,3.127C33.836,94.402,35.954,92.87,37.745,91.649z"/>
|
||||
</g>
|
||||
</g>
|
||||
</svg>
|
After Width: | Height: | Size: 29 KiB |
BIN
source/images/supported_brands/yi.png
Normal file
After Width: | Height: | Size: 14 KiB |