mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 21:36:52 +00:00
Merge branch 'current' into next
This commit is contained in:
Paulus Schoutsen
commit
0ac6fd0f3f
@ -75,6 +75,8 @@ collections:
|
||||
output: true
|
||||
docs:
|
||||
output: true
|
||||
addons:
|
||||
output: true
|
||||
|
||||
# ----------------------- #
|
||||
# 3rd Party Settings #
|
||||
@ -139,9 +141,10 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 43
|
||||
current_patch_version: 0
|
||||
date_released: 2017-04-22
|
||||
current_patch_version: 2
|
||||
date_released: 2017-04-27
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
patch_version_notes: ""
|
||||
# Example #release-0431---april-25
|
||||
patch_version_notes: "#release-0432---april-27"
|
||||
|
||||
24
source/_addons/lets_encrypt.markdown
Normal file
24
source/_addons/lets_encrypt.markdown
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Let's Encrypt"
|
||||
description: "Automatically manage your SSL certificate using Let's Encrypt."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and renew it if the certificate is expiring in the next 30 days.
|
||||
|
||||
```json
|
||||
{
|
||||
"email": "example@example.com",
|
||||
"domains": ["example.com", "mqtt.example.com", "hass.example.com"]
|
||||
}
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **email** (*Required*): Your email address for registration on Let's Encrypt.
|
||||
- **domains** (*Required*): A list of domains to create/renew the certificate.
|
||||
30
source/_addons/mosquitto.markdown
Normal file
30
source/_addons/mosquitto.markdown
Normal file
@ -0,0 +1,30 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Mosquitto MQTT broker"
|
||||
description: "Fast and reliable MQTT broker."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Set up a [mosquitto](https://mosquitto.org/) MQTT broker.
|
||||
|
||||
```json
|
||||
{
|
||||
"plain": true,
|
||||
"ssl": false,
|
||||
"anonymous": true,
|
||||
"logins": [
|
||||
{"username": "testuser", "password": "mypw"}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **plain** (*Optional*): Listen to broker on port 1883 without SSL/TLS. Defaults to `true`.
|
||||
- **ssl** (*Optional*): Listen to broker on port 8883 with SSL/TLS. This requires certificates. Defaults to `false`.
|
||||
- **anonymous** (*Optional*): Allow anonymous connection. If *logins* is set, anonymous user can only read data. Defaults to `true`.
|
||||
- **logins** (*Optional*): A list of user that will be created with *username* and *password*.
|
||||
34
source/_addons/samba.markdown
Normal file
34
source/_addons/samba.markdown
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Samba"
|
||||
description: "Manage your Home Assistant and custom addons over Samba."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
This allows you to set up a [Samba](https://samba.org/) server to access hass.io folders using Windows network shares.
|
||||
|
||||
```json
|
||||
{
|
||||
"workgroup": "WORKGROUP",
|
||||
"guest": true,
|
||||
"map_config": true,
|
||||
"map_addons": true,
|
||||
"map_ssl": false,
|
||||
"username": "",
|
||||
"password": ""
|
||||
}
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **workgroup** (*Optional*): default `WORKGROUP`. Set network workgroup.
|
||||
- **guest** (*Optional*): Allow login without a username or password. Defaults to `true`.
|
||||
- **map_config** (*Optional*): Expose Home Assistant configuration folder. Defaults to `true`.
|
||||
- **map_addons** (*Optional*): Expose local custom addons folder. Defaults to `true`.
|
||||
- **map_ssl** (*Optional*): Expose SSL folder. Be careful with this option! Defaults to `false`.
|
||||
- **username** (*Optional*): The username for logging in if guest login is not used.
|
||||
- **password** (*Optional*): Password for `username`. An empty password is not supported.
|
||||
24
source/_addons/ssh.markdown
Normal file
24
source/_addons/ssh.markdown
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: page
|
||||
title: "SSH Server"
|
||||
description: "Allow logging in remotely to your server using SSH."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Setting up a [SSH](https://openssh.org/) server allows access to hass.io folders with SSH client. It also allows tunneling for access from an external network. Please note that you only need to do this on a ResinOS platform as most Linux flavors have their own SSH server.
|
||||
|
||||
```json
|
||||
{
|
||||
"authorized_keys": [
|
||||
"ssh-rsa AKDJD3839...== my-key"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **authorized_keys** (*Required*): Your public-keys for authorized keyfile. Every element will be a line inside that file.
|
||||
@ -14,6 +14,8 @@ ha_release: 0.42
|
||||
|
||||
The `totalconnect` platform provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies.
|
||||
|
||||
If you have issues running this component, you may require "libxml2-dev" and "libxmlsec1-dev". To install these on Hassbian, run the command `apt install libxml2-dev libxmlsec1-dev` with sudo
|
||||
|
||||
To enable this, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -306,6 +306,34 @@ text: !include alexa_confirm.yaml
|
||||
|
||||
Alexa will now respond with a random phrase each time. You can use the include for as many different intents as you like so you only need to create the list once.
|
||||
|
||||
<p class='note'>
|
||||
As of April 2017, the random filter has been somewhat broken. You'll get a random response the first time this runs, but subsequent commands will reply with the same randomly-chosen phrase. On reboot, Home Assistant will pick a new random choice, but you're stuck with that choice till you reboot. To get around that, use the following code in alexa_confirm.yaml:
|
||||
</p>
|
||||
|
||||
```text
|
||||
{% raw %} >
|
||||
{% set responses = [
|
||||
"OK",
|
||||
"Sure",
|
||||
"If you insist",
|
||||
"Done",
|
||||
"No worries",
|
||||
"I can do that",
|
||||
"Leave it to me",
|
||||
"Consider it done",
|
||||
"As you wish",
|
||||
"By your command",
|
||||
"Affirmative",
|
||||
"Yes oh revered one",
|
||||
"I will",
|
||||
"As you decree, so shall it be",
|
||||
"No Problem"
|
||||
] %}
|
||||
{% set rindex = (range(0, (responses | length - 1) )|random) -%}
|
||||
{{responses[rindex]}}
|
||||
{% endraw %}
|
||||
```
|
||||
|
||||
|
||||
## {% linkable_title Flash Briefing Skills %}
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: nasa.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.36
|
||||
redirect_from: /components/sensor.iss/
|
||||
---
|
||||
|
||||
The `iss` platform uses the [Open Notify API](http://open-notify.org/Open-Notify-API/ISS-Location-Now/) to let you know if the station is above your home location. This means that ISS is 10° above the horizon of your home.
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Binary sensor
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.43
|
||||
---
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Tado"
|
||||
title: "Tado Thermostat"
|
||||
description: "Instructions on how to integrate Tado thermostats with Home Assistant."
|
||||
date: 2017-03-20 12:00
|
||||
sidebar: true
|
||||
@ -13,20 +13,8 @@ ha_release: 0.41
|
||||
---
|
||||
|
||||
|
||||
The `tado` component platform is used as an interface to the my.tado.com website. It adds climate devices for every tado zone and sensors for some additional information of the zones.
|
||||
The `tado` climate platform is interact with your climate devices.
|
||||
|
||||
To use your tado thermostats in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
tado:
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
```
|
||||
The requirement is that you have set up the [tado](/components/tado/) component.
|
||||
|
||||
- **username** (*Required*): Username for my.tado.com.
|
||||
- **password** (*Required*): Password for my.tado.com.
|
||||
|
||||
The tado thermostats are internet connected thermostats. There exists an unofficial api at my.tado.com, which is used by theire website and now by this component.
|
||||
|
||||
It currently supports presenting the current temperature, the setting temperature and the current operation mode. Switching the mode is also supported. If no user is at home anymore, the devices are showing the away-state. Switching to away-mode is not supported.
|
||||
@ -20,12 +20,12 @@ To enable a command line cover in your installation, add the following to your `
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
- platform: command_line
|
||||
covers:
|
||||
garage_door:
|
||||
command_open: move_command up garage
|
||||
command_close: move_command down garage
|
||||
command_stop: move_command stop garage
|
||||
- platform: command_line
|
||||
covers:
|
||||
garage_door:
|
||||
command_open: move_command up garage
|
||||
command_close: move_command down garage
|
||||
command_stop: move_command stop garage
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -48,18 +48,18 @@ In this section you find some real life examples of how to use this sensor.
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
- platform: command_line
|
||||
covers:
|
||||
garage_door:
|
||||
command_open: move_command up garage
|
||||
command_close: move_command down garage
|
||||
command_stop: move_command stop garage
|
||||
command_state: state_command garage
|
||||
value_template: {% raw %}>
|
||||
{% if value == 'open' %}
|
||||
100
|
||||
{% elif value == 'closed' %}
|
||||
0
|
||||
{% endif %}
|
||||
{% endraw %}
|
||||
- platform: command_line
|
||||
covers:
|
||||
garage_door:
|
||||
command_open: move_command up garage
|
||||
command_close: move_command down garage
|
||||
command_stop: move_command stop garage
|
||||
command_state: state_command garage
|
||||
value_template: {% raw %}>
|
||||
{% if value == 'open' %}
|
||||
100
|
||||
{% elif value == 'closed' %}
|
||||
0
|
||||
{% endif %}
|
||||
{% endraw %}
|
||||
```
|
||||
|
||||
@ -20,12 +20,11 @@ To enable Garadget Covers in your installation, add the following to your `confi
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
platform: garadget
|
||||
covers:
|
||||
190028001947343412342341:
|
||||
username: UseYourLogin@garadget.com
|
||||
password: abc123
|
||||
name: Left Garage Door
|
||||
- platform: garadget
|
||||
covers:
|
||||
190028001947343412342341:
|
||||
username: UseYourLogin@garadget.com
|
||||
password: abc123
|
||||
4c003f001151353432134214:
|
||||
access_token: df4cc785ff818f2b01396c44142342fccdef
|
||||
```
|
||||
@ -33,13 +32,13 @@ cover:
|
||||
Configuration variables:
|
||||
|
||||
- **covers** array (*Required*): List of your doors.
|
||||
- **device** (*Required*): This is the device id from your Garadget portal.
|
||||
- **device** (*Required*): This is the device id from your Garadget portal.
|
||||
- Either:
|
||||
- **username** (*Required*): Your Garadget account username.
|
||||
- **password** (*Required*): Your Garadget account password.
|
||||
- Or:
|
||||
- **access_token** (*Required*): A generated access_token from your garadget account
|
||||
- **name** (*Optional*): Name to use in the Frontend, will use name configured in Garadget otherwise.
|
||||
- **access_token** (*Required*): A generated `access_token` from your Garadget account.
|
||||
- **name** (*Optional*): Name to use in the frontend, will use name configured in Garadget otherwise.
|
||||
|
||||
|
||||
If provided, the **access_token** will be used, otherwise the **username** and **password** will be used to automatically generate an access token at start time.
|
||||
@ -53,25 +52,25 @@ If provided, the **access_token** will be used, otherwise the **username** and *
|
||||
```yaml
|
||||
# Related configuration.yaml entry
|
||||
cover:
|
||||
platform: garadget
|
||||
covers:
|
||||
190028001947343412342341:
|
||||
access_token: !secret garadget_access_token
|
||||
name: Garage door
|
||||
- platform: garadget
|
||||
covers:
|
||||
190028001947343412342341:
|
||||
access_token: !secret garadget_access_token
|
||||
name: Garage door
|
||||
|
||||
sensor:
|
||||
platform: template
|
||||
sensors:
|
||||
garage_door_status:
|
||||
friendly_name: 'State of the door'
|
||||
value_template: {% raw %}'{{ states.cover.garage_door.state }}'{% endraw %}
|
||||
garage_door_time_in_state:
|
||||
friendly_name: 'Since'
|
||||
value_template: {% raw %}'{{ states.cover.garage_door.attributes["time in state"] }}'{% endraw %}
|
||||
garage_door_wifi_signal_strength:
|
||||
friendly_name: 'WiFi strength'
|
||||
value_template: {% raw %}'{{ states.cover.garage_door.attributes["wifi signal strength (dB)"] }}'{% endraw %}
|
||||
unit_of_measurement: 'dB'
|
||||
- platform: template
|
||||
sensors:
|
||||
garage_door_status:
|
||||
friendly_name: 'State of the door'
|
||||
value_template: {% raw %}'{{ states.cover.garage_door.state }}'{% endraw %}
|
||||
garage_door_time_in_state:
|
||||
friendly_name: 'Since'
|
||||
value_template: {% raw %}'{{ states.cover.garage_door.attributes["time in state"] }}'{% endraw %}
|
||||
garage_door_wifi_signal_strength:
|
||||
friendly_name: 'WiFi strength'
|
||||
value_template: {% raw %}'{{ states.cover.garage_door.attributes["wifi signal strength (dB)"] }}'{% endraw %}
|
||||
unit_of_measurement: 'dB'
|
||||
|
||||
group:
|
||||
garage_door:
|
||||
|
||||
@ -24,8 +24,8 @@ The easiest way to find your roller shutters is to add this to your `configurati
|
||||
|
||||
```yaml
|
||||
cover:
|
||||
platform: rfxtrx
|
||||
automatic_add: True
|
||||
- platform: rfxtrx
|
||||
automatic_add: True
|
||||
```
|
||||
|
||||
Launch your homeassistant and go the website (e.g http://localhost:8123). Push your remote and your device should be added.
|
||||
@ -34,10 +34,10 @@ Once added it will show an ID (e.g `0b11000102ef9f210010f70`) and you can verify
|
||||
|
||||
```yaml
|
||||
cover:
|
||||
platform: rfxtrx
|
||||
devices:
|
||||
0b11000102ef9f210010f70:
|
||||
name: device_name
|
||||
- platform: rfxtrx
|
||||
devices:
|
||||
0b11000102ef9f210010f70:
|
||||
name: device_name
|
||||
```
|
||||
|
||||
##### {% linkable_title RFY %}
|
||||
@ -51,14 +51,14 @@ Example configuration:
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
platform: rfxtrx
|
||||
automatic_add: False
|
||||
signal_repetitions: 2
|
||||
devices:
|
||||
0b1100ce3213c7f210010f70: # Siemens/LightwaveRF
|
||||
name: Bedroom Shutter
|
||||
070a00000a000101: # RFY
|
||||
name: Bathroom Shutter
|
||||
- platform: rfxtrx
|
||||
automatic_add: False
|
||||
signal_repetitions: 2
|
||||
devices:
|
||||
0b1100ce3213c7f210010f70: # Siemens/LightwaveRF
|
||||
name: Bedroom Shutter
|
||||
070a00000a000101: # RFY
|
||||
name: Bathroom Shutter
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -34,7 +34,7 @@ cover:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **relay_time** (*Optional*): The time that the relay will be on for in seconds. Default is .2 seconds.
|
||||
- **relay_time** (*Optional*): The time that the relay will be on for in seconds. Default is 0.2 seconds.
|
||||
- **state_pull_mode** (*Optional*): The direction the State pin is pulling. It can be UP or DOWN. Default is UP.
|
||||
- **covers** array (*Required*): List of your doors.
|
||||
- **relay_pin** (*Required*): The pin of your Raspberry Pi where the relay is connected.
|
||||
@ -57,3 +57,7 @@ cover:
|
||||
name: 'Right door'
|
||||
```
|
||||
|
||||
## {% linkable_title Remote Raspberry Pi Cover %}
|
||||
|
||||
If you don't have Home Assistant running on your Raspberry Pi and you want to use it as a remote cover instead, there is a project called [GarageQTPi](https://github.com/Jerrkawz/GarageQTPi) that will work remotely with the [MQTT Cover Component](/components/cover.mqtt/). Follow the Github instructions to install and configure GarageQTPi and once configured follow the Home Assistant instructions to configure the MQTT Cover.
|
||||
|
||||
|
||||
@ -18,11 +18,11 @@ To enable SCSGate covers in your installation, add the following to your `config
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
platform: scsgate
|
||||
devices:
|
||||
living_room:
|
||||
name: Living Room
|
||||
scs_id: XXXXX
|
||||
- platform: scsgate
|
||||
devices:
|
||||
living_room:
|
||||
name: Living Room
|
||||
scs_id: XXXXX
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -14,7 +14,7 @@ ha_release: 0.7.6
|
||||
|
||||
_This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci/)._
|
||||
|
||||
This is a presence detection scanner for [OpenWRT](https://openwrt.org/) using [ubus](http://wiki.openwrt.org/doc/techref/ubus).
|
||||
This is a presence detection scanner for [OpenWRT](https://openwrt.org/) using [ubus](http://wiki.openwrt.org/doc/techref/ubus). It scans for changes in `hostapd.*`, which will detect and report changes in devices connected to the access point on the router.
|
||||
|
||||
Before this scanner can be used you have to install the ubus RPC package on OpenWRT:
|
||||
|
||||
@ -70,3 +70,101 @@ Configuration variables:
|
||||
- **password** (*Required*): The password for your given account.
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
If you find that this never creates `known_devices.yaml`, or if you need more information on the communication chain between Home Assistant and OpenWRT, follow these steps to grab the packet stream and gain insight into what's happening.
|
||||
|
||||
### Increase Log Level
|
||||
|
||||
1. On your Home Assistant device, stop Home Assistant
|
||||
2. Adjust `configuration.yaml` to log more detail for the `device_tracker` component
|
||||
```yaml
|
||||
logger:
|
||||
default: warn
|
||||
logs:
|
||||
homeassistant.components.device_tracker: debug
|
||||
```
|
||||
3. In another window, tail the logfile in the configuration directory:
|
||||
```
|
||||
$ tail -f home-assistant.log | grep device_tracker
|
||||
```
|
||||
4. If you see a python stack trace like the following, check your configuration for correct username/password.
|
||||
```
|
||||
17-04-28 10:43:30 INFO (MainThread) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
|
||||
17-04-28 10:43:30 INFO (MainThread) [homeassistant.loader] Loaded device_tracker.ubus from homeassistant.components.device_tracker.ubus
|
||||
17-04-28 10:43:30 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
|
||||
17-04-28 10:43:31 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.ubus
|
||||
17-04-28 10:43:31 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform ubus
|
||||
File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/__init__.py", line 152, in async_setup_platform
|
||||
File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 36, in get_scanner
|
||||
File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 58, in __init__
|
||||
File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 156, in _get_session_id
|
||||
File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/ubus.py", line 147, in _req_json_rpc
|
||||
17-04-28 10:43:31 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=device_tracker, service=see>
|
||||
17-04-28 10:43:31 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=device_tracker>
|
||||
```
|
||||
5. If you see lines like the following repeated at intervals that correspond to the check interval from the config (12 seconds by default), then Home Assistant is correctly polling the router, and you'll need to look at what the router is sending back.
|
||||
```
|
||||
17-04-28 10:50:34 INFO (Thread-7) [homeassistant.components.device_tracker.ubus] Checking ARP
|
||||
```
|
||||
|
||||
### Inspect Packets With TCPDump
|
||||
_These steps require that `tcpdump` is installed on your Home Assistant device, and that you have a utility such as [Wireshark](https://www.wireshark.org) for viewing the packets. It also assumes that Home Assistant is communicating with your router over HTTP and not HTTPS._
|
||||
|
||||
1. On your Home Assistant device, stop Home Assistant
|
||||
2. In another shell on your Home Assistant device, start tcpdump
|
||||
```bash
|
||||
$ sudo tcpdump -nnvXSs 0 -w /var/tmp/dt.out 'host <router_ip> and port 80'
|
||||
```
|
||||
* In this example we are only looking for traffic to or from port 80, and we are writing the packet stream out to `/var/tmp/dt.out`
|
||||
3. Start Home Assistant
|
||||
4. After a few seconds you should see a line like `Got xx` where `xx` is an incrementing number. This indicates that it has captured packets that match our filter. After you see this number increment a few times (>20), you can hit `Ctrl-C` to cancel the capture.
|
||||
6. Transfer `/var/tmp/dt.out` to the machine where you're running Wireshark and either drag/drop it onto the Wireshark window or use File/Open to open the capture file.
|
||||
7. In the window that opens, look for the first line that reads `POST /ubus`. Right click on this line, choose Follow and then HTTP Stream to view just the HTTP stream for this connection.
|
||||
8. The first `POST` will show Home Assistant logging into ubus and receiving a session identifier back. It will look something like this:
|
||||
```
|
||||
POST /ubus HTTP/1.1
|
||||
Host: 10.68.0.1
|
||||
Accept: */*
|
||||
User-Agent: python-requests/2.13.0
|
||||
Connection: keep-alive
|
||||
Accept-Encoding: gzip, deflate
|
||||
Content-Length: 161
|
||||
|
||||
{"jsonrpc": "2.0", "params": ["00000000000000000000000000000000", "session", "login", {"password": "<password>", "username": "root"}], "method": "call", "id": 1}
|
||||
|
||||
HTTP/1.1 200 OK
|
||||
Date: Fri, 28 Apr 2017 12:04:46 GMT
|
||||
Content-Type: application/json
|
||||
Transfer-Encoding: chunked
|
||||
Connection: keep-alive
|
||||
|
||||
{"jsonrpc":"2.0","id":1,"result":[0,{"ubus_rpc_session":"8b4e1632389fcfd09e96a792e01c332c","timeout":300,"expires":300,"acls":{"access-group":{"unauthenticated":["read"],"user":["read"]},"ubus":{"*":["*"],"session":["access","login"]},"uci":{"*":["read"]}},"data":{"username":"root"}}]}
|
||||
```
|
||||
9. In the response above, the portion that reads `"result":[0,` indicates that ubus accepted the login without issue. If this is not `0`, search online for what ubus status corresponds to the number you're receiving and address any issues that it brings to light.
|
||||
10. Otherwise, back in the main Wireshark window click the `x` in the right side of the filter bar where it reads `tcp.stream eq 0`. Scroll down until you find the next `POST /ubus` line and view the HTTP stream again. This request is Home Assistant actually requesting information and will look something like the following:
|
||||
```
|
||||
POST /ubus HTTP/1.1
|
||||
Host: 10.68.0.1
|
||||
Accept: */*
|
||||
User-Agent: python-requests/2.13.0
|
||||
Connection: keep-alive
|
||||
Accept-Encoding: gzip, deflate
|
||||
Content-Length: 114
|
||||
|
||||
{"jsonrpc": "2.0", "params": ["8b4e1632389fcfd09e96a792e01c332c", "hostapd.*", "", {}], "method": "list", "id": 1}
|
||||
|
||||
HTTP/1.1 200 OK
|
||||
Date: Fri, 28 Apr 2017 12:04:46 GMT
|
||||
Content-Type: application/json
|
||||
Transfer-Encoding: chunked
|
||||
Connection: keep-alive
|
||||
|
||||
{"jsonrpc":"2.0","id":1,"result":{}}
|
||||
```
|
||||
11. In this case we are actually receiving a valid response with no data. The request says that we are looking for ARP information from `hostapd.*`, which is the access point on the router. In my environment I don't use the AP on the router, and so it was correctly returning no data. Armed with this information, I know that I cannot use this component for device tracking or presence.
|
||||
|
||||
### Cleanup
|
||||
|
||||
When you're done troubleshooting, remember to reset your logging configuration and delete any capture files that contain sensitive information.
|
||||
|
||||
@ -41,10 +41,10 @@ Configuration variables (global):
|
||||
|
||||
Configuration variables (host):
|
||||
|
||||
- **ip** (*Required*): IP of CCU/Homegear
|
||||
- **port** (*Optional*): Port of CCU/Homegear XML-RPC Server (default is 2001, use 2000 for wired and 2010 for IP)
|
||||
- **callback_ip** (*Optional*): Set this, if HASS is reachable under a different IP from the CCU (NAT, Docker etc.)
|
||||
- **callback_port** (*Optional*): Set this, if HASS is reachable under a different port from the CCU (NAT, Docker etc.)
|
||||
- **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.
|
||||
- **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.
|
||||
- **username** (*Optional*): When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.
|
||||
- **password** (*Optional*): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.
|
||||
@ -87,8 +87,8 @@ Resolving names can take some time. So when you start Home Assistant you won't s
|
||||
|
||||
### {% linkable_title Multiple hosts %}
|
||||
|
||||
In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
|
||||
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
|
||||
In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
|
||||
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
|
||||
This does *not* affect the entites in Home Assistant. They all use their own connection and work as expected.
|
||||
|
||||
### {% linkable_title Reading attributes of entities %}
|
||||
@ -107,7 +107,7 @@ sensor:
|
||||
|
||||
### {% linkable_title Variables %}
|
||||
|
||||
It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables.
|
||||
It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables.
|
||||
The states of the variables are available through the attributes of your hub entity (e.g. `homematic.rf`). Use templates (as mentioned above) to make your variables available to automations or as entities.
|
||||
The values of variables are polled from the CCU/Homegear in an interval of 30 seconds. Setting the value of a variable happens instantly and is directly pushed.
|
||||
|
||||
@ -184,10 +184,9 @@ action:
|
||||
value: true
|
||||
```
|
||||
|
||||
|
||||
#### {% linkable_title Advanced examples %}
|
||||
|
||||
If you are familiar with the internals of HomeMatic devices, you can manually set values on the devices. This can serve as a workaround if support for a device is currently not available, or only limited functionality has been implemented.
|
||||
If you are familiar with the internals of HomeMatic devices, you can manually set values on the devices. This can serve as a workaround if support for a device is currently not available, or only limited functionality has been implemented.
|
||||
Using this service provides you direct access to the setValue-method of the primary connection. If you have multiple hosts, you may select the one hosting a specific device by providing the proxy-parameter with a value equivalent to the name you have chosen. In the example configuration from above `rf`, `wired` and `ip` would be valid values.
|
||||
|
||||
Manually turn on a switch actor
|
||||
|
||||
@ -28,7 +28,7 @@ Configuration variables:
|
||||
- **api_password** (*Optional*): Protect Home Assistant with a password.
|
||||
- **server_host** (*Optional*): Only listen to incoming requests on specific ip/host (default: accept all)
|
||||
- **server_port** (*Optional*): Let you set a port to use. Defaults to 8123.
|
||||
- **base_url** (*Optional*): The url that Home Assistant is available on the internet. For example: `hass-example.duckdns.org:8123`. Defaults to local IP address.
|
||||
- **base_url** (*Optional*): The url that Home Assistant is available on the internet. For example: `hass-example.duckdns.org:8123`. Defaults to local IP address. The IOS app finds local installations, if you have a outside url use this so that you can auto fill when discovered in the app.
|
||||
- **development** (*Optional*): Disable caching and load unvulcanized assets. Useful for Frontend development.
|
||||
- **ssl_certificate** (*Optional*): Path to your TLS/SSL certificate to serve Home Assistant over a secure connection.
|
||||
- **ssl_key** (*Optional*): Path to your TLS/SSL key to serve Home Assistant over a secure connection.
|
||||
|
||||
@ -11,6 +11,7 @@ logo: openalpr.png
|
||||
ha_category: Image Processing
|
||||
featured: false
|
||||
ha_release: 0.36
|
||||
redirect_from: /components/openalpr/
|
||||
---
|
||||
|
||||
[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](https://home-assistant.io/components/automation/).
|
||||
|
||||
@ -11,7 +11,7 @@ logo: home-assistant.png
|
||||
ha_category: Other
|
||||
---
|
||||
|
||||
The introduction component will show a card in the UI with steps on how to get started. It will also print the same message to the console when starting up.
|
||||
The introduction component will show a card in the UI with 'Welcome Home!' and steps on how to get started. It will also print the same message to the console when starting up.
|
||||
|
||||
The introduction component is loaded by default on a new Home Assistant instance.
|
||||
|
||||
|
||||
@ -100,18 +100,22 @@ automation:
|
||||
```
|
||||
|
||||
## {% linkable_title Permissions %}
|
||||
There might be permissions problems with the event input device file. If this is the case, the user that hass runs as must be allowed read and write permissions with:
|
||||
There might be permissions problems with the event input device file. If this is the case, the user that Home Assistant runs as must be allowed read and write permissions with:
|
||||
|
||||
```bash
|
||||
$ sudo setfacl -m u:HASS_USER:rw /dev/input/event*
|
||||
```
|
||||
sudo setfacl -m u:HASS_USER:rw /dev/input/event*
|
||||
```
|
||||
where `HASS_USER` is the user hass runs as.
|
||||
|
||||
where `HASS_USER` is the user who runs Home Assistant.
|
||||
|
||||
If you want to make this permanent, you can use a udev rule that sets it for all event input devices. Add a file `/etc/udev/rules.d/99-userdev-input.rules` containing:
|
||||
```
|
||||
|
||||
```bash
|
||||
KERNEL=="event*", SUBSYSTEM=="input", RUN+="/usr/bin/setfacl -m u:HASS_USER:rw $env{DEVNAME}"
|
||||
```
|
||||
|
||||
You can check ACLs permissions with
|
||||
```
|
||||
getfacl /dev/input/event*
|
||||
|
||||
```bash
|
||||
$ getfacl /dev/input/event*
|
||||
```
|
||||
|
||||
@ -20,7 +20,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Binary Sensor](/components/binary_sensor.knx)
|
||||
- [Sensor](/components/sensor.knx)
|
||||
- [Switch](/components/switch.knx)
|
||||
- [Thermostat](/components/thermostat.knx)
|
||||
- [Thermostat](/components/climate.knx)
|
||||
|
||||
A `knx` section must be present in the `configuration.yaml` file and contain the following options as required:
|
||||
|
||||
|
||||
33
source/_components/light.knx.markdown
Normal file
33
source/_components/light.knx.markdown
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
layout: page
|
||||
title: "KNX Light"
|
||||
description: "Instructions on how to integrate KXN lights with Home Assistant."
|
||||
date: 2016-06-24 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: knx.png
|
||||
ha_category: DIY
|
||||
ha_release: 0.44
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
The `knx` light component is used as in interface to switching/light actuators.
|
||||
|
||||
To use your KNX light in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
light:
|
||||
- platform: knx
|
||||
name: KNX light
|
||||
address: 0/0/1
|
||||
```
|
||||
|
||||
- **name** (*Optional*): A name for this devices used within Home assistant
|
||||
- **address** (*Required*): The KNX group address that is used to turn on/off this actuator channel
|
||||
- **state_address** (*Optional*): Some KNX devices can change their state internally without any messages on the KXN bus, e.g. if you configure a timer on a channel. The optional `state_address` can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
|
||||
For switching/light actuators that are only controlled by a single group address and can't change their state internally, you don't have to configure the state address.
|
||||
|
||||
@ -26,3 +26,85 @@ light:
|
||||
Configuration variables:
|
||||
|
||||
- **server** (*Optional*): Your server address. Only needed if using more than one network interface. Omit if you are unsure.
|
||||
|
||||
|
||||
## {% linkable_title Light effects %}
|
||||
|
||||
The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`]({{site_root}}/components/light/#service-lightturn_on) service, for example like this:
|
||||
```yaml
|
||||
automation:
|
||||
- alias: ...
|
||||
trigger:
|
||||
# ...
|
||||
action:
|
||||
- service: light.turn_on
|
||||
data:
|
||||
entity_id: light.office, light.kitchen
|
||||
effect: lifx_effect_breathe
|
||||
```
|
||||
|
||||
However, if you want to fully control a light effect, you have to use its dedicated service call, like this:
|
||||
```yaml
|
||||
script:
|
||||
colorloop_start:
|
||||
alias: 'Start colorloop'
|
||||
sequence:
|
||||
- service: light.lifx_effect_colorloop
|
||||
data:
|
||||
entity_id: group.livingroom
|
||||
brightness: 255
|
||||
period: 10
|
||||
spread: 30
|
||||
change: 35
|
||||
```
|
||||
|
||||
The available light effects and their options are listed below.
|
||||
|
||||
### {% linkable_title Service `light.lifx_effect_breathe` %}
|
||||
|
||||
Run a breathe effect by fading to a color and back.
|
||||
|
||||
| Service data attribute | Description |
|
||||
| ---------------------- | ----------- |
|
||||
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Else targets all.
|
||||
| `color_name` | A color name such as `red` or `green`.
|
||||
| `rgb_color` | A list containing three integers representing the RGB color you want the light to be.
|
||||
| `brightness` | Integer between 0 and 255 for how bright the color should be.
|
||||
| `period` | The duration of a single breathe.
|
||||
| `cycles` | The total number of breathes.
|
||||
| `power_on` | Set this to False to skip the effect on lights that are turned off (defaults to True).
|
||||
|
||||
### {% linkable_title Service `light.lifx_effect_pulse` %}
|
||||
|
||||
Run a flash effect by quickly changing to a color and then back.
|
||||
|
||||
| Service data attribute | Description |
|
||||
| ---------------------- | ----------- |
|
||||
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Else targets all.
|
||||
| `color_name` | A color name such as `red` or `green`.
|
||||
| `rgb_color` | A list containing three integers representing the RGB color you want the light to be.
|
||||
| `brightness` | Integer between 0 and 255 for how bright the color should be.
|
||||
| `period` | The duration of a single pulse.
|
||||
| `cycles` | The total number of pulses.
|
||||
| `power_on` | Set this to False to skip the effect on lights that are turned off (defaults to True).
|
||||
|
||||
### {% linkable_title Service `light.lifx_effect_colorloop` %}
|
||||
|
||||
Run an effect with colors looping around the color wheel. All participating lights will coordinate to keep similar (but not identical) colors.
|
||||
|
||||
| Service data attribute | Description |
|
||||
| ---------------------- | ----------- |
|
||||
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Else targets all.
|
||||
| `brightness` | Number between 0 and 255 indicating brightness of the effect. Leave this out to maintain the current brightness of each participating light.
|
||||
| `period` | Duration (in seconds) between the start of a new color change.
|
||||
| `change` | Hue movement per period, in degrees on a color wheel (ranges from 0 to 359).
|
||||
| `spread` | Total hue covered by participating lights, in degrees on a color wheel (ranges from 0 to 359).
|
||||
| `power_on` | Set this to False to skip the effect on lights that are turned off (defaults to True).
|
||||
|
||||
### {% linkable_title Service `light.lifx_effect_stop` %}
|
||||
|
||||
Run an effect that does nothing, thereby stopping any other effect that might be running.
|
||||
|
||||
| Service data attribute | Description |
|
||||
| ---------------------- | ----------- |
|
||||
| `entity_id` | String or list of strings that point at `entity_id`s of lights. Else targets all.
|
||||
|
||||
14
source/_components/light.lutron.markdown
Normal file
14
source/_components/light.lutron.markdown
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Lutron Light"
|
||||
description: "Instructions how to setup the Lutron lights within Home Assistant."
|
||||
date: 2017-04-30 09:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: lutron.png
|
||||
ha_category: Light
|
||||
---
|
||||
|
||||
To get your Lutron lights working with Home Assistant, follow the instructions for the general [Lutron component](/components/lutron/).
|
||||
14
source/_components/light.lutron_caseta.markdown
Normal file
14
source/_components/light.lutron_caseta.markdown
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Lutron Caseta Light"
|
||||
description: "Instructions how to setup the Lutron Caseta lights within Home Assistant."
|
||||
date: 2017-04-30 09:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: lutron.png
|
||||
ha_category: Light
|
||||
---
|
||||
|
||||
To get your Lutron Caseta lights working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/).
|
||||
@ -33,7 +33,7 @@ Configuration variables:
|
||||
- **brightness_scale** (*Optional*): Defines the maximum brightness value (i.e. 100%) of the MQTT device (defaults to 255).
|
||||
- **brightness_state_topic** (*Optional*): The MQTT topic subscribed to receive brightness state updates.
|
||||
- **brightness_value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the brightness value.
|
||||
- **color_temp_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's color temperature state.
|
||||
- **color_temp_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's color temperature state. The color temperature command slider has a range of 157 to 500 mireds (micro reciprocal degrees).
|
||||
- **color_temp_state_topic** (*Optional*): The MQTT topic subscribed to receive color temperature state updates.
|
||||
- **color_temp_value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the color temperature value.
|
||||
- **effect_command_topic** (*Optional*): The MQTT topic to publish commands to change the light's effect state.
|
||||
|
||||
@ -13,5 +13,4 @@ ha_iot_class: "Local Polling"
|
||||
ha_release: 0.43
|
||||
---
|
||||
|
||||
For installation instructions, see [the Trådfri component][/components/tradfri/].
|
||||
|
||||
For installation instructions, see [the Trådfri component](/components/tradfri/).
|
||||
|
||||
@ -19,11 +19,12 @@ Presently, there's only support for communicating with the [RadioRA 2](http://ww
|
||||
|
||||
When configured, the `lutron` component will automatically discover the rooms and their associated switches/dimmers as configured by the RadioRA 2 software from Lutron. Each room will be treated as a separate group.
|
||||
|
||||
To use Lutron RadioRA 2 devices in your installation, add the following to your configuration.yaml file using the IP of your RadioRA 2 Main Repeater:
|
||||
To use Lutron RadioRA 2 devices in your installation, add the following to your `configuration.yaml` file using the IP of your RadioRA 2 Main Repeater:
|
||||
|
||||
``` yaml
|
||||
# Example configuration.yaml entry
|
||||
lutron:
|
||||
lutron_host: <ip>
|
||||
lutron_host:IP_ADDRESS
|
||||
lutron_user: lutron
|
||||
lutron_password: integration
|
||||
```
|
||||
@ -35,5 +36,5 @@ Configuration variables:
|
||||
- **lutron_password** (*Required*): The password for the user specified above. `integration` is the password for the always-present `lutron` user.
|
||||
|
||||
<p class='note'>
|
||||
It is recommended to assign a static IP address to your Main Repeater. This ensures that it won't change IP addresses, so you won't have to change the `lutron_ip` if it reboots and comes up with a different IP address.
|
||||
It is recommended to assign a static IP address to your Main Repeater. This ensures that it won't change IP addresses, so you won't have to change the `lutron_ip` if it reboots and comes up with a different IP address.
|
||||
</p>
|
||||
|
||||
@ -13,17 +13,18 @@ featured: False
|
||||
ha_release: 0.41
|
||||
---
|
||||
|
||||
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems.
|
||||
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems.
|
||||
|
||||
This component only supports the Caseta line of products. Current only supports Caseta dimmers as Home Assistant lights and caseta wall switches as Home Assistant switches.
|
||||
This component only supports the Caseta line of products. Current only supports Caseta dimmers as Home Assistant lights and caseta wall switches as Home Assistant switches.
|
||||
|
||||
When configured, the `lutron_caseta` component will automatically discover dimmers and switches as setup in the Lutron SmartBridge.
|
||||
|
||||
To use Lutron Caseta devices in your installation, add the following to your configuration.yaml file using the IP of your lutron Smartbridge:
|
||||
To use Lutron Caseta devices in your installation, add the following to your `configuration.yaml` file using the IP of your lutron Smartbridge:
|
||||
|
||||
``` yaml
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
lutron_caseta:
|
||||
host: <ip_address>
|
||||
host: IP_ADDRESS
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -31,5 +32,5 @@ Configuration variables:
|
||||
- **host** (*Required*): The IP address of the Lutron SmartBridge.
|
||||
|
||||
<p class='note'>
|
||||
It is recommended to assign a static IP address to your Lutron SmartBridge. This ensures that it won't change IP address, so you won't have to change the `host` if it reboots and comes up with a different IP address.
|
||||
It is recommended to assign a static IP address to your Lutron SmartBridge. This ensures that it won't change IP address, so you won't have to change the `host` if it reboots and comes up with a different IP address.
|
||||
</p>
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: maxcube.png
|
||||
ha_category: DIY
|
||||
ha_category: Climate
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
@ -16,8 +16,8 @@ ha_iot_class: "Local Polling"
|
||||
[eQ-3 MAX!](http://www.eq-3.com/products/max.html) integration for Home Assistant allows you to connect eQ-3 MAX! components via the eQ-3 MAX! Cube. The components connects to the eQ-3 MAX! Cube via TCP and automatically makes all supported components available in Home Assistant. The name for each device is created by concatenating the MAX! room and device names.
|
||||
|
||||
Limitations:
|
||||
- Configuring weekly schedules is not possible
|
||||
- Implementation is based on the reverse engineered [MAX! protocol](https://github.com/Bouni/max-cube-protocol)
|
||||
- Configuring weekly schedules is not possible.
|
||||
- Implementation is based on the reverse engineered [MAX! protocol](https://github.com/Bouni/max-cube-protocol).
|
||||
|
||||
Supported Devices:
|
||||
- MAX! Radiator Thermostat (tested)
|
||||
@ -32,6 +32,6 @@ A `maxcube` section must be present in the `configuration.yaml` file and contain
|
||||
maxcube:
|
||||
host: 192.168.0.20
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
- **host** (*Required*): The IP address of the eQ-3 MAX! Cube to use.
|
||||
- **port** (*Optional*): The UDP port number. Defaults to `62910`.
|
||||
|
||||
@ -52,10 +52,12 @@ Currently known supported models:
|
||||
- U6000 (port must be set to 8001)
|
||||
- K6500AF (port must be set to 8001)
|
||||
- KS8005 (port must be set to 8001, and `pip3 install websocket-client` must be executed)
|
||||
- K5600AK (partially supported, turn on works but state is not updated)
|
||||
|
||||
Currently tested but not working models:
|
||||
|
||||
- J5200 - Unable to see state and unable to control
|
||||
- JU7500 - Unable to see state and unable to control
|
||||
|
||||
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.samsungtv.markdown).
|
||||
The first letter (U, P, L, H & K) represent the screen type, e.g. LED or Plasma. The second letter represents the region, E is Europe, N is North America and A is Asia & Australia. The two numbers following that represent the screen size.
|
||||
@ -63,4 +65,4 @@ If you add your model remember to remove these before adding them to the list.
|
||||
|
||||
Currently the ability to select a source is not implemented.
|
||||
|
||||
There's currently a [known issue](https://github.com/home-assistant/home-assistant/issues/2098) with some TV's receiving a *Key press UP* that can interrupt certain applications.
|
||||
There's currently a [known issue](https://github.com/home-assistant/home-assistant/issues/2098) with some TVs receiving a *Key press UP* that can interrupt certain applications.
|
||||
|
||||
@ -25,7 +25,13 @@ To create the required Spotify Application, login to [Spotify Developer](https:/
|
||||
|
||||
`http://<your_home_assistant_url_or_local_ip>/api/spotify`
|
||||
|
||||
Remember to select **Save** after adding the URI.
|
||||
If you've set up Home Assistant to use SSL encryption, use:
|
||||
|
||||
`https://<your_home_assistant_url_or_local_ip>/api/spotify`
|
||||
|
||||
The first part of the URL will be whatever you use to access Home Assistant from outside your network (including port if applicable).
|
||||
|
||||
Remember to select **Save** after adding the URI. You may also need to set the `base_url` attribute of the [HTTP Component](https://home-assistant.io/components/http/).
|
||||
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
@ -48,4 +54,14 @@ Configuration variables:
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
After the prerequisites and configuration are complete, restart Home Assistant. A **Spotify** configurator element will be available. Follow the instructions to authorize Home Assistant to access your Spotify account. A Spotify media player will then appear.
|
||||
After the prerequisites and configuration are complete, restart Home Assistant. A **Spotify** configurator element will be available. Follow the instructions to authorize Home Assistant to access your Spotify account. A Spotify media player will then appear. If Spotify prompts you to download a file after completing authorization, discard the download. It is not needed.
|
||||
|
||||
## {% linkable_title Sources %}
|
||||
The sources are based on if you have streamed to these devices before in Spotify. If you don't have any sources, then simply stream from your phone to another device in your house, bluetooth, echo, etc. Once you do the sources will show up in the developer console as a device to cast/stream to. Also know that the devices won't show up in the dev-console as sources unless they are powered on as well.
|
||||
|
||||
## {% linkable_title URI Links For Playlists/Etc %}
|
||||
You can send playlists to spotify via the "media_content_type": "playlist" and "media_content_id": "spotify:user:spotify:playlist:37i9dQZF1DWSkkUxEhrBdF" which are a part of the media_player.play_media service, you can test this from the services control panel in the Home Assistant frontend.
|
||||
|
||||
In this example this is a URI link to the Reggae Infusions playlist, the link below from Spotify explains how to get this URI value to use for playlists in the Spotify component.
|
||||
|
||||
https://support.spotify.com/us/using_spotify/share_music/why-do-you-have-two-different-link-formats/
|
||||
|
||||
@ -52,4 +52,5 @@ media_player:
|
||||
- livetv
|
||||
- youtube
|
||||
- makotv
|
||||
- netflix
|
||||
```
|
||||
|
||||
@ -239,7 +239,7 @@ You will receive an event named `html5_notification.closed` when the notificatio
|
||||
|
||||
### {% linkable_title Making notifications work with NGINX proxy %}
|
||||
|
||||
If you use [NGINX](/ecosystem/nginx/) as an proxy with authentication in front of HASS, you may have trouble with receiving events back to HASS. It's because of authentication token that cannot be passed through the proxy.
|
||||
If you use [NGINX](/ecosystem/nginx/) as an proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It's because of authentication token that cannot be passed through the proxy.
|
||||
|
||||
To solve the issue put additional location into your nginx site's configuration:
|
||||
|
||||
|
||||
@ -55,3 +55,32 @@ kodi_notification:
|
||||
- **displaytime** (*Optional*): Length in milliseconds the message stays on screen. *Defaults to `10000` ms*
|
||||
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
|
||||
## {% linkable_title Services %}
|
||||
|
||||
### {% linkable_title Media control services %}
|
||||
Available services: `kodi_add_to_playlist`, `kodi_set_shuffle`
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ------------------------------------------------ |
|
||||
| `entity_id` | yes | Target a specific media player. Defaults to all. |
|
||||
|
||||
#### {% linkable_title Service `media_player/kodi_set_shuffle` %}
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|------------------------|----------|----------------------------------------------------------|
|
||||
| `entity_id` | yes | Target a specific media player. It must be of type kodi. |
|
||||
| `shuffle_on ` | no | True/false for shuffle on/off |
|
||||
|
||||
#### {% linkable_title Service `media_player/kodi_add_to_playlist` %}
|
||||
|
||||
Add a song or an entire album to the default playlist (i.e. playlist id 0).
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|------------------------|----------|----------------------------------------------------------------------------|
|
||||
| `entity_id` | yes | Target a specific media player. It must be of type kodi. |
|
||||
| `media_type ` | no | either SONG or ALBUM |
|
||||
| media_id | yes | id of the media as defined in kodi |
|
||||
| media_name | yes | name of the media, HA will search for the media with name closer to this. If ALL add all albums, if artist_name is provided adds all albums of that artist. |
|
||||
| artist_name | yes | name of the artist, HA will search for the artist with name closer to this.|
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ha_release: 0.32
|
||||
|
||||
Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google&hl=de) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google).
|
||||
The notifications are in the global scope of your Android TV device. They will be displayed regardless of which application is running.
|
||||
The In-App purchases only apply to the client for Android smartphones, so there isn't any limit when pushing notifications from HASS.
|
||||
The In-App purchases only apply to the client for Android smartphones, so there isn't any limit when pushing notifications from Home Assistant.
|
||||
|
||||
To enable the notification platform, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -1,132 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "OpenALPR"
|
||||
description: "Instructions how to integrate licences plates with OpenALPR into Home Assistant."
|
||||
date: 2016-09-22 00:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: openalpr.png
|
||||
ha_category: Deprecated
|
||||
featured: false
|
||||
ha_release: 0.29
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
**This platform has been deprecated in favor of the "[OpenALPR image processing](/components/image_processing.openalpr_local/)" platform and will be removed in the future. Please use the "OpenALPR image processing" platform.**
|
||||
</p>
|
||||
|
||||
[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates recorded with a camera. You can use them to open a garage door or trigger any other [automation](https://home-assistant.io/components/automation/).
|
||||
|
||||
<p class='note'>
|
||||
If you want use a video stream. You need setup the [ffmpeg](/components/ffmpeg) component. See also there for troubleshooting local ffmpeg installation.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Local installation %}
|
||||
|
||||
If you want process all data locally, you need version 2.3.1 or higher of the `alpr` commandline tool.
|
||||
|
||||
If you don't find binaries for your distribution you can compile from source. Documention of how to build OpenALPR is found [here](https://github.com/openalpr/openalpr/wiki).
|
||||
|
||||
On a Debian system you can use this `cmake` command to build only the command line tool:
|
||||
|
||||
```bash
|
||||
$ cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr ..
|
||||
```
|
||||
|
||||
Verify your `alpr` installation with:
|
||||
|
||||
```
|
||||
$ wget -O- -q http://plates.openalpr.com/h786poj.jpg | alpr -
|
||||
```
|
||||
|
||||
### {% linkable_title Configuration Home Assistant %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
openalpr:
|
||||
engine: local
|
||||
region: eu
|
||||
confidence: 80.0
|
||||
entities:
|
||||
- name: Camera garage 1
|
||||
interval: 5
|
||||
render: ffmpeg
|
||||
input: INPUT_STREAM
|
||||
extra_arguments: SOME OTHER FFMPEG STUFF
|
||||
- name: Camera garage 2
|
||||
interval: 5
|
||||
render: image
|
||||
input: https://camera_ip/still_image.jpg
|
||||
username: admin
|
||||
password: bla
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **engine** (*Required*): `local` or `cloud` for processing
|
||||
- **region** (*Required*): Country or region. List of supported [values](https://github.com/openalpr/openalpr/tree/master/runtime_data/config).
|
||||
- **confidence** (*Optional*): The minimum of confidence in percent to process with Home Assistant. Defaults to 80.
|
||||
- **entities** (*Required*): A list of device to add in Home Assistant.
|
||||
- **name** (*Optional*): This parameter allows you to override the name of your OpenALPR entity.
|
||||
- **interval** (*Optional*): Time in seconds to poll a picture. If the interval is 0 It don't poll and it only process data with `openalpr.scan` service. Default is 2 seconds.
|
||||
- **render** (*Optional*): How is Home Assistant to get a picture from. It support `ffmpeg` for video streams and `image` for a still image. Default is with `ffmpeg`.
|
||||
- **input** (*Required*): The source from getting pictures. With `ffmpeg` it could by all supported input. Image only support an URL.
|
||||
- **extra_arguments** (*Optional*): Only available with `ffmpeg`.
|
||||
- **username** (*Optional*): Only available with image for HTTP authentification.
|
||||
- **password** (*Optional*): Only available with image for HTTP authentification.
|
||||
|
||||
### {% linkable_title Configuration Home Assistant local processing %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
openalpr:
|
||||
engine: local
|
||||
region: eu
|
||||
alpr_binary: /usr/bin/alpr
|
||||
entities:
|
||||
...
|
||||
```
|
||||
Configuration variables:
|
||||
|
||||
- **alpr_binary** (*Optional*): Default `alpr`. The command line tool `alpr` from OpenALPR software for local processing.
|
||||
|
||||
### {% linkable_title Configuration Home Assistant cloud processing %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
openalpr:
|
||||
engine: cloud
|
||||
region: eu
|
||||
api_key: SK_AAABBBBCCCEEEE
|
||||
entities:
|
||||
...
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): You need an API key from [OpenALPR Cloud](https://cloud.openalpr.com/).
|
||||
|
||||
#### {% linkable_title Service %}
|
||||
|
||||
- `openalpr.scan`: Scan immediately a picture from input.
|
||||
- `openalpr.restart`: Restart a ffmpeg process
|
||||
|
||||
#### {% linkable_title Events %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml automation entry
|
||||
automation:
|
||||
- alias: Open garage door
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: openalpr.found
|
||||
event_data:
|
||||
entity_id: openalpr.camera_garage_1
|
||||
plate: BE2183423
|
||||
...
|
||||
```
|
||||
|
||||
This event is trigger after OpenALPR found a new licence plate.
|
||||
@ -36,9 +36,9 @@ remote:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **name** (*Required*): The hub's name to display in the front end.
|
||||
- **name** (*Required*): The hub's name to display in the frontend.
|
||||
- **host** (*Required*): The Harmony device's IP address.
|
||||
- **port** (*Optional*): The Harmony device's port. 5222 is default.
|
||||
- **port** (*Optional*): The Harmony device's port. Defaults to 5222.
|
||||
- **activity** (*Optional*): Activity to use when turnon service is called without any data.
|
||||
- **scan_interval** (*Optional*): Amount in seconds in between polling for device's current activity. Defaults to 30 seconds.
|
||||
|
||||
@ -52,10 +52,10 @@ Upon startup one file will be written to your Home Assistant configuration direc
|
||||
|
||||
Supported services:
|
||||
|
||||
- **Turn Off**: Turn off all devices that were switched on from the start of the current activity
|
||||
- **Turn On**: Start an activity, will start the default activity from configuration.yaml if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your HASS config directory. The service will respond faster if the activity ID is passed instead of the name
|
||||
- **Send Command**: Send a command to one device, device ID and available commands are written to the configuration file at startup
|
||||
- **Sync**: Synchronizes the Harmony device with the Harmony web service if any changes are made from the web portal or app
|
||||
- **Turn Off**: Turn off all devices that were switched on from the start of the current activity.
|
||||
- **Turn On**: Start an activity, will start the default activity from configuration.yaml if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your [Home Assistant configuration directory](/docs/configuration/). The service will respond faster if the activity ID is passed instead of the name.
|
||||
- **Send Command**: Send a command to one device, device ID and available commands are written to the configuration file at startup.
|
||||
- **Sync**: Synchronizes the Harmony device with the Harmony web service if any changes are made from the web portal or app.
|
||||
|
||||
|
||||
### {% linkable_title Examples %}
|
||||
@ -91,7 +91,7 @@ sensor:
|
||||
```
|
||||
|
||||
|
||||
The example below shows how to control an `input_boolean` switch using the Harmony remote's current activity. The switch will turn on when the remote's state changes and the Kodi activity is started and off when the remote's state changes and the current activity is PowerOff.
|
||||
The example below shows how to control an `input_boolean` switch using the Harmony remote's current activity. The switch will turn on when the remote's state changes and the Kodi activity is started and off when the remote's state changes and the current activity is PowerOff.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
@ -117,7 +117,8 @@ automation:
|
||||
entity_id: input_boolean.notify
|
||||
````
|
||||
|
||||
The automation example below shows how to send a command via the harmony remote using the `send_command` service to send the 'Pause' command to the hub, which is already defined as an IR code for each device to be used via the Harmony app. It is checking for the activity name as exposed through the sensor in the harmony remote component using Jinga if statements to set the device_id, sending the correct Pause command for the given activity. This requires checking your activity list and device_id from the `harmony_REMOTENAME.conf` file created when you start the component. In this example, the harmony hub is named bedroom.
|
||||
The automation example below shows how to send a command via the harmony remote using the `send_command` service to send the 'Pause' command to the hub, which is already defined as an IR code for each device to be used via the Harmony app. It is checking for the activity name as exposed through the sensor in the harmony remote component using Jinja if statements to set the device_id, sending the correct Pause command for the given activity. This requires checking your activity list and device_id from the `harmony_REMOTENAME.conf` file created when you start the component. In this example, the harmony hub is named bedroom.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Harmony Pause contextual for activity
|
||||
|
||||
@ -117,7 +117,7 @@ If you find a device is recognized differently, with different protocols or the
|
||||
### {% linkable_title Technical overview %}
|
||||
|
||||
- The`rflink` Python module a asyncio transport/protocol is setup that fires an callback for every (valid/supported) packet received by the RFLink gateway.
|
||||
- This component uses this callback to distribute 'rflink packet events' over the HASS bus which can be subscribed to by entities/platform implementations.
|
||||
- This component uses this callback to distribute 'rflink packet events' over Home Assistant's bus which can be subscribed to by entities/platform implementations.
|
||||
- The platform implementions take care of creating new devices (if enabled) for unsees incoming packet id's.
|
||||
- Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entitiy logic is maintained in this main component.
|
||||
|
||||
@ -135,7 +135,7 @@ logger:
|
||||
|
||||
This will give you output looking like this:
|
||||
|
||||
```
|
||||
```bash
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nod
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: o RadioFrequencyLink - R
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: FLink Gateway V1.1 - R45
|
||||
|
||||
@ -11,6 +11,7 @@ logo: dark_sky.png
|
||||
ha_category: Weather
|
||||
featured: true
|
||||
ha_release: 0.30
|
||||
redirect_from: /components/sensor.forecast/
|
||||
---
|
||||
|
||||
The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as a source for meteorological data for your location. The location is based on the `longitude` and `latitude` coordinates configured in your `configuration.yaml` file. The coordinates are auto-detected but to take advantage of the hyper-local weather reported by Dark Sky, you can refine them down to your exact home address. GPS coordinates can be found by using [Google Maps](https://www.google.com/maps) and clicking on your home or [Openstreetmap](http://www.openstreetmap.org/).
|
||||
@ -80,7 +81,7 @@ Configuration variables:
|
||||
</pre>
|
||||
|
||||
<p class='note warning'>
|
||||
Note: While the platform is called "darksky" the sensors will show up in Home Assistant as "dark_sky" (eg: sensor.dark_sky_summary).
|
||||
While the platform is called "darksky" the sensors will show up in Home Assistant as "dark_sky" (eg: sensor.dark_sky_summary).
|
||||
</p>
|
||||
|
||||
Details about the API are available in the [Dark Sky documentation](https://darksky.net/dev/docs).
|
||||
|
||||
@ -15,7 +15,7 @@ ha_release: "0.40"
|
||||
|
||||
The `dnsip` sensor will expose an IP address, fetched via DNS resolution, as its value. There are two operational modes:
|
||||
|
||||
1. When you enable the sensor with minimal configuration, it will query [OpenDNS](https://www.opendns.com/)' nameserver with the hostname `myip.opendns.com`, which will resolve to your external/public IP address.
|
||||
1. When you enable the sensor with minimal configuration, it will query the [OpenDNS](https://www.opendns.com/) nameservers with the hostname `myip.opendns.com`, which will resolve to your external/public IP address.
|
||||
2. If you specify a `hostname`, a regular DNS lookup will be performed, providing you the IP the hostname resolves to.
|
||||
|
||||
You may also override the nameserver that is being used by setting the `resolver` parameter to any nameserver you like.
|
||||
@ -32,7 +32,7 @@ Configuration variables:
|
||||
|
||||
- **hostname** (*Optional*): The hostname for which to perform the DNS query. Default: `myip.opendns.com` (special hostname that resolves to your public IP)
|
||||
- **resolver** (*Optional*): The DNS server to target the query at. Default: `208.67.222.222` (OpenDNS)
|
||||
- **ipv6** (*Optional*): Set this to `true` or `false` if IPv6 should be used. When resolving the public IP, this will be the IP of the machine HASS is running on.
|
||||
- **ipv6** (*Optional*): Set this to `true` or `false` if IPv6 should be used. When resolving the public IP, this will be the IP of the machine where Home Assistant is running on.
|
||||
- **resolver_ipv6** (*Optional*): The IPv6 DNS server to target the query at. Default: `2620:0:ccc::2` (OpenDNS)
|
||||
- **scan_interval** (*Optional*): Defines number of seconds for polling interval. Default: `120` seconds.
|
||||
|
||||
|
||||
@ -1,104 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Forecast.io"
|
||||
description: "How to integrate Forecast.io within Home Assistant."
|
||||
date: 2015-04-25 9:06
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: forecast.png
|
||||
ha_category: Deprecated
|
||||
featured: False
|
||||
ha_release: pre 0.7
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
**This platform has been deprecated in favor of the "[darksky](/components/sensor.darksky/)" platform and will be removed in the future. Please use the "darksky" platform.**
|
||||
</p>
|
||||
|
||||
The `forecast` platform uses the [Forecast.io](https://forecast.io/) web service as a source of meteorological data for your location. The location is based on the `longitude` and `latitude` coordinates configured in your `configuration.yaml` file. The coordinates are auto-detected but to take advantage of the hyper-local weather reported by forecast.io, you can refine them down to your exact home address. GPS coordinates can be found by using [Google Maps](https://www.google.com/maps) and clicking on your home or [Openstreetmap](http://www.openstreetmap.org/).
|
||||
|
||||
You need an API key which is free but requires [registration](https://developer.forecast.io/register). You can make up to 1000 calls per day for free which means that you could make one approximately every 86 seconds.
|
||||
|
||||
<p class='note warning'>
|
||||
[Forecast.io](https://forecast.io/) will charge you $0.0001 per API call if you enter your credit card details and create more than 1000 calls per day.
|
||||
</p>
|
||||
|
||||
To add Forecast.io to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: forecast
|
||||
api_key: YOUR_APP_KEY
|
||||
monitored_conditions:
|
||||
- summary
|
||||
- icon
|
||||
- nearest_storm_distance
|
||||
- nearest_storm_bearing
|
||||
- precip_type
|
||||
- precip_intensity
|
||||
- precip_probability
|
||||
- temperature
|
||||
- apparent_temperature
|
||||
- dew_point
|
||||
- wind_speed
|
||||
- wind_bearing
|
||||
- cloud_cover
|
||||
- humidity
|
||||
- pressure
|
||||
- visibility
|
||||
- ozone
|
||||
- minutely_summary
|
||||
- hourly_summary
|
||||
- daily_summary
|
||||
- temperature_max
|
||||
- temperature_min
|
||||
- apparent_temperature_max
|
||||
- apparent_temperature_min
|
||||
- precip_intensity_max
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): Your API key for http://forecast.io/.
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend.
|
||||
- **summary**: A human-readable text summary of the current conditions.
|
||||
- **precip_type**: The type of precipitation occurring.
|
||||
- **precip_intensity**: The average expected intensity of precipitation occurring.
|
||||
- **precip_probability**: A value between 0 and 1 which is representing the probability of precipitation.
|
||||
- **temperature**: The current temperature.
|
||||
- **apparent_temperature**: A numerical value representing the apparent (or "feels like") temperature.
|
||||
- **dew_point**: The dew point.
|
||||
- **wind_speed**: The wind speed.
|
||||
- **wind_bearing**: Where the wind is coming from in degrees, with true north at 0° and progressing clockwise.
|
||||
- **cloud_cover**: The percentage of sky occluded by clouds.
|
||||
- **humidity**: The relative humidity.
|
||||
- **pressure**: The sea-level air pressure in millibars.
|
||||
- **visibility**: The average visibility.
|
||||
- **ozone**: The columnar density of total atmospheric ozone in Dobson.
|
||||
- **minutely_summary**: A human-readable text summary for the next hour.
|
||||
- **hourly_summary**: A human-readable text summary for the next 24 hours.
|
||||
- **daily_summary**: A human-readable text summary for the next 7 days.
|
||||
- **temperature_max**: Today's expected high temperature.
|
||||
- **temperature_min**: Today's expected low temperature.
|
||||
- **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.
|
||||
- **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 forecast.io decide the unit system based on location.
|
||||
- **update_inverval** (*Optional*): Minimum time interval between updates. Default is 2 minutes. Supported formats:
|
||||
- `update_interval: 'HH:MM:SS'`
|
||||
- `update_interval: 'HH:MM'`
|
||||
- Time period dictionary, e.g.:
|
||||
<pre>update_interval:
|
||||
# At least one of these must be specified:
|
||||
days: 0
|
||||
hours: 0
|
||||
minutes: 3
|
||||
seconds: 30
|
||||
milliseconds: 0
|
||||
</pre>
|
||||
|
||||
Details about the API are available in the [Forecast.io documentation](https://developer.forecast.io/docs/v2).
|
||||
@ -16,14 +16,17 @@ ha_release: 0.7.3
|
||||
|
||||
The `glances` sensor platform is consuming the system information provided by the [Glances](https://github.com/nicolargo/glances) API. This enables one to track remote host and display their stats in Home Assistant.
|
||||
|
||||
This sensors needs a running instance of `glances` on the host. The minimal supported version of `glances` is 2.3:
|
||||
This sensors needs a running instance of `glances` on the host. The minimal supported version of `glances` is 2.3.
|
||||
To start a Glances RESTful API server on its default port 61208, the a test the following command can be used:
|
||||
|
||||
```bash
|
||||
$ sudo glances -w
|
||||
Glances web server started on http://0.0.0.0:61208/
|
||||
```
|
||||
|
||||
Check if you are able to access the API located at `http://IP_ADRRESS:61208/api/2`. The details about your memory usage is provided as a JSON response. If so, you are good to proceed.
|
||||
Check if you are able to access the API located at `http://IP_ADRRESS:61208/api/2`. Don't use `-s` as this will start the XMLRPC server on port 61209. Home Assistant only supports the REST API of GLANCES.
|
||||
|
||||
The details about your memory usage is provided as a JSON response. If so, you are good to proceed.
|
||||
|
||||
```bash
|
||||
$ curl -X GET http://IP_ADDRESS:61208/api/2/mem/free
|
||||
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "International Space Station Sensor"
|
||||
description: "Know if or when ISS will be above your home location"
|
||||
date: 2016-12-18 10:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: nasa.png
|
||||
ha_category: Deprecated
|
||||
ha_release: 0.36
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
**This platform has been deprecated in favor of the "[ISS](/components/binary_sensor.iss/)" platform and will be removed in the future. Please use the "iss" binary sensor platform.**
|
||||
</p>
|
||||
|
||||
The `iss` platform uses the [Open Notify API](http://open-notify.org/Open-Notify-API/ISS-Location-Now/) to let you know if the station is above your home location. This means that ISS is 10° above the horizon of your home.
|
||||
You can check in the attributes of the sensor how many minutes you have to wait until the next rise of the station and the number of people in space.
|
||||
|
||||
To add ISS sensor to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: iss
|
||||
```
|
||||
@ -13,7 +13,7 @@ ha_release: 0.29
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The [Mi Flora plant sensor](https://www.open-homeautomation.com/2016/08/23/reverse-engineering-the-mi-plant-sensor/) is a small Bluetooth Low Energy device that monitors not only the moisture, but also light, temperature and conductivity. As only a single BLE device can be polled at the same time, the library implements locking to make sure this is the case.
|
||||
The `miflora` sensor platform allows one to monitor to plants. The [Mi Flora plant sensor](https://www.aliexpress.com/item/Newest-Original-Xiaomi-Flora-Monitor-Digital-Plants-Flowers-Soil-Water-Light-Tester-Sensor-Monitor-for-Aquarium/32685750372.html) is a small Bluetooth Low Energy device that monitors not only the moisture, but also light, temperature and conductivity. As only a single BLE device can be polled at the same time, the library implements locking to make sure this is the case.
|
||||
|
||||
To use your Mi Flora plant sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -38,7 +38,7 @@ sensor:
|
||||
- **median** (*Optional*): Sometimes the sensor measurements show spikes. Using this parameter, the poller will report the median of the last 3 (you can also use larger values) measurements. This filters out single spikes. Median: 5 will also filter double spikes. If you never have problems with spikes, `median: 1` will work fine.
|
||||
- **timeout** (*Optional*): Define the timeout value in seconds when polling (defaults to 10 if not defined)
|
||||
- **retries** (*Optional*): Define the number of retries when polling (defaults to 2 if not defined)
|
||||
- **cache** (*Optional*): Define cache expiration value in seconds (defaults to 1200 if not defined)
|
||||
- **cache_value** (*Optional*): Define cache expiration value in seconds (defaults to 1200 if not defined)
|
||||
- **adapter** (*Optional*): Define the bluetooth adapter to use (defaults to hci0). Run `hciconfig` to get a list of available adapters.
|
||||
|
||||
Note that by default the sensor is only polled once every 15 minutes. This means with the `median: 3` setting will take as least 30 minutes before the sensor will report a value after a Home Assistant restart. As the values usually change very slowly, this isn't a big problem.
|
||||
@ -62,6 +62,3 @@ sensor:
|
||||
- battery
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ha_category: Sensor
|
||||
ha_release: "0.40"
|
||||
---
|
||||
|
||||
The `modem_callerid` sensor platform uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1).
|
||||
The `modem_callerid` sensor platform uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1).
|
||||
|
||||
To enable the sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
@ -19,7 +19,6 @@ To enable the sensor, add the following lines to your `configuration.yaml`:
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: modem_callerid
|
||||
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -31,7 +30,7 @@ To find the path of your USB modem, run:
|
||||
|
||||
`$ ls /dev/ttyACM*`
|
||||
|
||||
If `hass` runs with another user (e.g. *homeassistant* on Hassbian) give access to the stick with:
|
||||
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`
|
||||
|
||||
@ -46,7 +45,7 @@ Some example automations:
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: sensor.modem_callerid
|
||||
state: "callerid"
|
||||
state: "callerid"
|
||||
action:
|
||||
service: notify.notify
|
||||
data:
|
||||
|
||||
19
source/_components/sensor.tado.markdown
Normal file
19
source/_components/sensor.tado.markdown
Normal file
@ -0,0 +1,19 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Tado Sensor"
|
||||
description: "Instructions on how to integrate Tado thermostats with Home Assistant."
|
||||
date: 2017-03-20 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: tado.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.41
|
||||
---
|
||||
|
||||
The `tado` sensor platform allow you to monitor your tado climate devices.
|
||||
|
||||
|
||||
The requirement is that you have set up the [tado](/components/tado/) component.
|
||||
|
||||
@ -28,7 +28,7 @@ Configuration variables:
|
||||
- Alias for the command
|
||||
- Command itself.
|
||||
|
||||
The commands can be dynamic, using templates to insert values of other entities. When using templates you are limited to only template the arguments. You are also no longer allowed to use pipe symbols when using templates.
|
||||
The commands can be dynamic, using templates to insert values for arguments. When using templates, shell_command runs in a more secure environment which doesn't allow any shell helpers like automatically expanding the home dir `~` or using pipe symbols to run multiple commands.
|
||||
|
||||
Any service data passed into the service call to activate the shell command will be available as a variable within the template.
|
||||
|
||||
|
||||
14
source/_components/switch.lutron_caseta.markdown
Normal file
14
source/_components/switch.lutron_caseta.markdown
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Lutron Caseta Switch"
|
||||
description: "Instructions how to setup the Lutron Caseta switches within Home Assistant."
|
||||
date: 2017-04-30 09:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: lutron.png
|
||||
ha_category: Switch
|
||||
---
|
||||
|
||||
To get your Lutron Caseta switches working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/).
|
||||
34
source/_components/tado.markdown
Normal file
34
source/_components/tado.markdown
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Tado"
|
||||
description: "Instructions on how to integrate Tado devices with Home Assistant."
|
||||
date: 2017-03-20 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: tado.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.41
|
||||
---
|
||||
|
||||
|
||||
The `tado` component platform is used as an interface to the [my.tado.com](https://my.tado.com/webapp/#/account/sign-in) website. It adds climate devices for every tado zone and sensors for some additional information of the zones.
|
||||
|
||||
To use your tado thermostats in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
tado:
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **username** (*Required*): Username for my.tado.com.
|
||||
- **password** (*Required*): Password for my.tado.com.
|
||||
|
||||
The tado thermostats are internet connected thermostats. There exists an unofficial API at [my.tado.com](https://my.tado.com/webapp/#/account/sign-in), which is used by their website and now by this component.
|
||||
|
||||
It currently supports presenting the current temperature, the setting temperature and the current operation mode. Switching the mode is also supported. If no user is at home anymore, the devices are showing the away-state. Switching to away-mode is not supported.
|
||||
@ -16,7 +16,7 @@ Use Telegram on your mobile device to send messages or commands to your Home Ass
|
||||
|
||||
A command looks like `/thecommand`
|
||||
|
||||
When received by hass it will fire a `telegram.command` event on the event bus with the following `event_data`:
|
||||
When received by hass it will fire a `telegram_command` event on the event bus with the following `event_data`:
|
||||
|
||||
```yaml
|
||||
command: "/thecommand"
|
||||
@ -36,7 +36,7 @@ alias: 'telegram bot that reply pong to ping'
|
||||
hide_entity: true
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: telegram.command
|
||||
event_type: telegram_command
|
||||
event_data:
|
||||
command: '/ping'
|
||||
action:
|
||||
@ -50,7 +50,7 @@ Example that show keyboard interaction with `notify.telegram`
|
||||
```yaml
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: telegram.command
|
||||
event_type: telegram_command
|
||||
event_data:
|
||||
command: '/start'
|
||||
action:
|
||||
@ -68,7 +68,7 @@ and an automation to trigger a related command "/siren".
|
||||
```yaml
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: telegram.command
|
||||
event_type: telegram_command
|
||||
event_data:
|
||||
command: '/siren'
|
||||
action:
|
||||
|
||||
@ -12,9 +12,9 @@ ha_category: Telegram chatbot
|
||||
ha_release: 0.42
|
||||
---
|
||||
|
||||
Telegram chatbot webhooks implementation as described in [docs](https://core.telegram.org/bots/webhooks).
|
||||
Telegram chatbot webhooks implementation as described in the Telegram [documentation](https://core.telegram.org/bots/webhooks).
|
||||
|
||||
One of two bot implementations supported by Telegram. Described by Telegram as the preferred implementation but requires your hass instance to be exposed to the internet.
|
||||
This is one of two bot implementations supported by Telegram. Described by Telegram as the preferred implementation but requires your Home Assistant instance to be exposed to the internet.
|
||||
|
||||
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
@ -46,7 +46,8 @@ Full configuration sample:
|
||||
http:
|
||||
base_url: <public_url>
|
||||
|
||||
telegram_webhooks:
|
||||
telegram_bot:
|
||||
platform: webhooks
|
||||
api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
trusted_networks:
|
||||
- 149.154.167.197/32
|
||||
@ -58,4 +59,4 @@ telegram_webhooks:
|
||||
allowed_chat_ids:
|
||||
- 12345
|
||||
- 67890
|
||||
```
|
||||
```
|
||||
|
||||
@ -1,125 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Telegram webhooks"
|
||||
description: "Telegram webhooks support"
|
||||
date: 2017-02-13 18:50
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: telegram.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.39
|
||||
---
|
||||
|
||||
Telegram webhooks support as described in [docs](https://core.telegram.org/bots/webhooks).
|
||||
|
||||
With new component `telegram_webhooks` it is possible to send commands to Home Assistant via a Telegram bot. It works well with Telegram notification: webhooks receive commands from user and notify send messages to user.
|
||||
|
||||
Webhook responds only to:
|
||||
|
||||
- users listed in configuration, in telegram user_id format.
|
||||
- telegram servers (listed in webhooks [docs](https://core.telegram.org/bots/webhooks)) specified in trusted_networks
|
||||
|
||||
|
||||
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
http:
|
||||
base_url: <public_url>
|
||||
|
||||
telegram_webhooks:
|
||||
user_id:
|
||||
user1: USER_ID
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **user_id** (*Required*): A list of user in the `user_id` Telegram format enabled to interact to webhook
|
||||
- **api_key** (*Optional*): The API token of your bot. If present, the webhook of bot is automatically registered to `public_url/api/telegram_webhooks`. If not present, manual registration is required.
|
||||
- **trusted_networks** (*Optional*): Telegram server access ACL as list. Defaults to `149.154.167.197-233`.
|
||||
|
||||
Full configuration sample:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
http:
|
||||
base_url: <public_url>
|
||||
|
||||
telegram_webhooks:
|
||||
api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
trusted_networks:
|
||||
- 149.154.167.197/32
|
||||
- 149.154.167.198/31
|
||||
- 149.154.167.200/29
|
||||
- 149.154.167.208/28
|
||||
- 149.154.167.224/29
|
||||
- 149.154.167.232/31
|
||||
user_id:
|
||||
user1: USER_ID
|
||||
user2: USER_ID
|
||||
```
|
||||
|
||||
### {% linkable_title Configuration samples %}
|
||||
|
||||
Telegram webhooks raise an event `telegram_command` with a payload.
|
||||
|
||||
```json
|
||||
{
|
||||
"command": "/thecommand",
|
||||
"args": "strings after command",
|
||||
"user_id": "12345"
|
||||
}
|
||||
```
|
||||
|
||||
Automation example that realize simple test to command/notify interaction.
|
||||
|
||||
```yaml
|
||||
alias: 'telegram bot that reply pong to ping'
|
||||
hide_entity: true
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: telegram_command
|
||||
event_data:
|
||||
command: '/ping'
|
||||
action:
|
||||
- service: notify.telegram
|
||||
data:
|
||||
message: 'pong'
|
||||
```
|
||||
|
||||
Example that show keyboard interaction with `notify.telegram`
|
||||
|
||||
```yaml
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: telegram_command
|
||||
event_data:
|
||||
command: '/start'
|
||||
action:
|
||||
- service: notify.telegram
|
||||
data:
|
||||
message: 'commands'
|
||||
data:
|
||||
keyboard:
|
||||
- '/ping, /alarm'
|
||||
- '/siren'
|
||||
```
|
||||
|
||||
and an automation to trigger a related command "/siren".
|
||||
|
||||
```yaml
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: telegram_command
|
||||
event_data:
|
||||
command: '/siren'
|
||||
action:
|
||||
- service: homeassistant.turn_on
|
||||
entity_id: switch.vision_zm1601eu5_battery_operated_siren_switch_9_0
|
||||
- delay:
|
||||
seconds: 10
|
||||
- service: homeassistant.turn_off
|
||||
entity_id: switch.vision_zm1601eu5_battery_operated_siren_switch_9_0
|
||||
```
|
||||
@ -14,22 +14,44 @@ 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.
|
||||
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:
|
||||
For this to work, you need to install a modified lib-coap library.
|
||||
|
||||
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
|
||||
$ make install
|
||||
$ sudo make install
|
||||
```
|
||||
|
||||
To enable these lights, add the following lines to your `configuration.yaml` file:
|
||||
macOS:
|
||||
|
||||
```bash
|
||||
$ sudo brew install libtool
|
||||
$ sudo brew install autoconf
|
||||
$ sudo 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
|
||||
$ sudo 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'>
|
||||
If you see an "Unable to connect" message, restart the gateway and try again.
|
||||
</p>
|
||||
|
||||
The gateway can also be manually configured by adding the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -41,4 +63,4 @@ tradfri:
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The IP address or hostname of your Trådfri gateway.
|
||||
- **api_key** (*Required*): Can be found on the back of the Trådfri gateway.
|
||||
- **api_key** (*Required*): Can be found listed as Security Key on the back of the Trådfri gateway.
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category: Other
|
||||
|
||||
The `updater` component will check daily for new releases. It will show a badge in the frontend if a new version was found.
|
||||
|
||||
The updater component will also collect basic information about Home Assistant and its environment. The information includes the current Home Assistant version, the timezone, Python version and operating system information. No identifiable information (i.e. IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python [source code](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/updater.py#L91).
|
||||
The updater component will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the timezone, Python version and operating system information. No identifiable information (i.e. IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python [source code](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/updater.py#L91). For further information about the Updater's data please check the [detailed overview](/docs/backend/updater/).
|
||||
|
||||
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ DEFAULT_NAME = 'World'
|
||||
|
||||
|
||||
def setup(hass, config):
|
||||
"""Setup is called when Home Assistant is loading our component."""
|
||||
"""Set up is called when Home Assistant is loading our component."""
|
||||
|
||||
def handle_hello(call):
|
||||
name = call.data.get(ATTR_NAME, DEFAULT_NAME)
|
||||
|
||||
@ -82,7 +82,7 @@ CONF_TEXT = 'text'
|
||||
DEFAULT_TEXT = 'No text!'
|
||||
|
||||
def setup(hass, config):
|
||||
"""Setup the Hello State component. """
|
||||
"""Set up the Hello State component. """
|
||||
# Get the text from the configuration. Use DEFAULT_TEXT if no name is provided.
|
||||
text = config[DOMAIN].get(CONF_TEXT, DEFAULT_TEXT)
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ This example follows a topic on MQTT and updates the state of an entity to the l
|
||||
import homeassistant.loader as loader
|
||||
|
||||
# The domain of your component. Should be equal to the name of your component.
|
||||
DOMAIN = "hello_mqtt"
|
||||
DOMAIN = 'hello_mqtt'
|
||||
|
||||
# List of component names (string) your component depends upon.
|
||||
DEPENDENCIES = ['mqtt']
|
||||
@ -33,14 +33,14 @@ DEFAULT_TOPIC = 'home-assistant/hello_mqtt'
|
||||
|
||||
|
||||
def setup(hass, config):
|
||||
"""Setup the Hello MQTT component."""
|
||||
"""Set up the Hello MQTT component."""
|
||||
mqtt = loader.get_component('mqtt')
|
||||
topic = config[DOMAIN].get('topic', DEFAULT_TOPIC)
|
||||
entity_id = 'hello_mqtt.last_message'
|
||||
|
||||
# Listener to be called when we receive a message.
|
||||
def message_received(topic, payload, qos):
|
||||
"""A new MQTT message has been received."""
|
||||
"""Handle new MQTT messages."""
|
||||
hass.states.set(entity_id, payload)
|
||||
|
||||
# Subscribe our listener to a topic.
|
||||
|
||||
@ -39,35 +39,35 @@ from homeassistant.components import device_tracker, light, notify
|
||||
from homeassistant.helpers.event import track_state_change
|
||||
from homeassistant.const import STATE_ON, STATE_OFF, STATE_HOME, STATE_NOT_HOME
|
||||
|
||||
DOMAIN = "simple_alarm"
|
||||
_LOGGER = logging.getLogger(__name__)
|
||||
|
||||
DOMAIN = 'simple_alarm"'
|
||||
|
||||
DEPENDENCIES = ['group', 'device_tracker', 'light']
|
||||
|
||||
# Attribute to tell which light has to flash when a known person comes home
|
||||
# If omitted will flash all.
|
||||
CONF_KNOWN_LIGHT = "known_light"
|
||||
CONF_KNOWN_LIGHT = 'known_light'
|
||||
|
||||
# Attribute to tell which light has to flash when an unknown person comes home
|
||||
# If omitted will flash all.
|
||||
CONF_UNKNOWN_LIGHT = "unknown_light"
|
||||
CONF_UNKNOWN_LIGHT = 'unknown_light'
|
||||
|
||||
# Services to test the alarms
|
||||
SERVICE_TEST_KNOWN_ALARM = "test_known"
|
||||
SERVICE_TEST_UNKNOWN_ALARM = "test_unknown"
|
||||
SERVICE_TEST_KNOWN_ALARM = 'test_known'
|
||||
SERVICE_TEST_UNKNOWN_ALARM = 'test_unknown'
|
||||
|
||||
|
||||
def setup(hass, config):
|
||||
""" Sets up the simple alarms. """
|
||||
logger = logging.getLogger(__name__)
|
||||
|
||||
"""Set up the simple alarms."""
|
||||
light_ids = []
|
||||
|
||||
for conf_key in (CONF_KNOWN_LIGHT, CONF_UNKNOWN_LIGHT):
|
||||
light_id = config[DOMAIN].get(conf_key, light.ENTITY_ID_ALL_LIGHTS)
|
||||
|
||||
if hass.states.get(light_id) is None:
|
||||
logger.error(
|
||||
'Light id %s could not be found in state machine', light_id)
|
||||
_LOGGER.error(
|
||||
"Light id %s could not be found in state machine", light_id)
|
||||
|
||||
return False
|
||||
|
||||
@ -77,7 +77,7 @@ def setup(hass, config):
|
||||
known_light_id, unknown_light_id = light_ids
|
||||
|
||||
if hass.states.get(device_tracker.ENTITY_ID_ALL_DEVICES) is None:
|
||||
logger.error('No devices are being tracked, cannot setup alarm')
|
||||
_LOGGER.error("No devices are being tracked, cannot setup alarm")
|
||||
|
||||
return False
|
||||
|
||||
@ -102,7 +102,7 @@ def setup(hass, config):
|
||||
DOMAIN, SERVICE_TEST_UNKNOWN_ALARM, lambda call: unknown_alarm())
|
||||
|
||||
def unknown_alarm_if_lights_on(entity_id, old_state, new_state):
|
||||
""" Called when a light has been turned on. """
|
||||
"""Called when a light has been turned on."""
|
||||
if not device_tracker.is_on(hass):
|
||||
unknown_alarm()
|
||||
|
||||
@ -111,7 +111,7 @@ def setup(hass, config):
|
||||
unknown_alarm_if_lights_on, STATE_OFF, STATE_ON)
|
||||
|
||||
def ring_known_alarm(entity_id, old_state, new_state):
|
||||
""" Called when a known person comes home. """
|
||||
"""Called when a known person comes home."""
|
||||
if light.is_on(hass, known_light_id):
|
||||
known_alarm()
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ automation:
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: sensor.motion_sensor
|
||||
to: 'on'
|
||||
state: 'on'
|
||||
action:
|
||||
service: homeassistant.turn_on
|
||||
entity_id: light.kitchen
|
||||
@ -29,7 +29,7 @@ automation:
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: sensor.motion_sensor
|
||||
to: 'off'
|
||||
state: 'off'
|
||||
for:
|
||||
minutes: 10
|
||||
action:
|
||||
|
||||
@ -103,6 +103,10 @@ sensor:
|
||||
name: Occasion
|
||||
command: "python3 occasion.py"
|
||||
```
|
||||
<p class='note'>
|
||||
If you are using docker to run home assistant then the occasion.py script will be placed under /config. Your command should instead be: command: "python3 /command/occasion.py"
|
||||
</p>
|
||||
|
||||
|
||||
To simplify things, we create a Home Assistant script that changes the visibility of a group, but also verifies that an entity is in a specific state:
|
||||
|
||||
@ -124,8 +128,8 @@ automation:
|
||||
trigger:
|
||||
- platform: state
|
||||
entity_id: sensor.occasion
|
||||
- platform: event
|
||||
event_type: homeassistant_start
|
||||
- platform: homeassistant
|
||||
event: start
|
||||
action:
|
||||
service: script.group_visibility
|
||||
data:
|
||||
@ -169,8 +173,8 @@ automation:
|
||||
trigger:
|
||||
- platform: state
|
||||
entity_id: sensor.occasion
|
||||
- platform: event
|
||||
event_type: homeassistant_start
|
||||
- platform: homeassistant
|
||||
event: start
|
||||
action:
|
||||
service: script.group_visibility
|
||||
data:
|
||||
|
||||
@ -89,6 +89,11 @@ Home Assistant adds extensions to allow templates to access all of the current s
|
||||
|
||||
[strp-format]: https://docs.python.org/3.4/library/datetime.html#strftime-and-strptime-behavior
|
||||
|
||||
<p class='note warning'>
|
||||
If your template uses an `entity_id` that begins with a number (example: `states.device_tracker.2008_gmc`) you must use a bracket syntax to avoid errors caused by rendering the `entity_id` improperly. In the example given, the correct syntax for the device tracker would be: `states.device_tracker['2008_gmc']`
|
||||
</p>
|
||||
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
### {% linkable_title States %}
|
||||
|
||||
53
source/_docs/ecosystem/backup/backup_dropbox.markdown
Normal file
53
source/_docs/ecosystem/backup/backup_dropbox.markdown
Normal file
@ -0,0 +1,53 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Configuration Backup to Dropbox"
|
||||
description: "Instructions how backup your Home Assistant configuration to Dropbox"
|
||||
date: 2017-04-24 18:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /cookbook/dropboxbackup/
|
||||
---
|
||||
|
||||
Backing up and regularly syncing your Home Assistant configuration to [Dropbox](http://dropbox.com) similar to [Github Backup](https://home-assistant.io/docs/ecosystem/backup/backup_github/)
|
||||
|
||||
### {% linkable_title Requirements %}
|
||||
|
||||
You need 2 parts in order to get it working correctly.
|
||||
|
||||
Become the user you run homeassistant from.
|
||||
|
||||
- A seperate python script that syncs a specific folder. Which can be found [here](https://gist.github.com/riemers/31e3350041fd3e47e489cbc811209d6f)
|
||||
- The excellent [dropbox uploader script](https://github.com/andreafabrizi/Dropbox-Uploader/blob/master/dropbox_uploader.sh) you can grab the .sh file only.
|
||||
|
||||
Download those files to a folder of your liking, after that edit both files and change paths accordingly.
|
||||
### {% linkable_title Step 1: Linking your dropbox account %}
|
||||
|
||||
```bash
|
||||
$ chmod +x dropbox_uploader.sh
|
||||
$ ./dropbox_uploader.sh
|
||||
```
|
||||
Follow the instructions you see on your screen.
|
||||
|
||||
### {% linkable_title Step 2: Running the dropbox uploader %}
|
||||
|
||||
Go to the folder you have placed dropbox.py.
|
||||
|
||||
```bash
|
||||
$ python dropbox.py
|
||||
```
|
||||
|
||||
The first time can take a lot of time since it will upload all your files!
|
||||
Do note, this will **backup your passwords to dropbox too**
|
||||
|
||||
### {% linkable_title Automate the backup %}
|
||||
|
||||
So you just made a full backup, next time you want it to be done automaticly. Since your database can change and so do other files over time.
|
||||
Add it to your crontab, edit the **path/to** part.
|
||||
|
||||
```bash
|
||||
$ (crontab -l 2>/dev/null; echo "0 3 * * * python /path/to/dropbox.py") | crontab -
|
||||
```
|
||||
|
||||
_The python script is very crude, there is room for improvement with regards to not backing up certain files like cache or files that will be installed by HA again after reinstall. But it gets the job done._
|
||||
116
source/_docs/ecosystem/backup/backup_usb.markdown
Normal file
116
source/_docs/ecosystem/backup/backup_usb.markdown
Normal file
@ -0,0 +1,116 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Configuration Backup to USB drive"
|
||||
description: "Instructions how backup your Home Assistant configuration to USB drive"
|
||||
date: 2017-04-29 08:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Backing up your Home Assistant configuration to USB drive. A good plus side is that you don't need to mask all your passwords since the backup is locally at your home/residence.
|
||||
|
||||
### {% linkable_title Requirements %}
|
||||
First you need a USB drive. Once you have one you need to prepare it to be used on your device.
|
||||
Once connected you want to format/work with the drive. To know what path it is in, you can check with `dmesg`.
|
||||
|
||||
```bash
|
||||
# dmesg | grep sd
|
||||
[ 0.909712] sdhci: Secure Digital Host Controller Interface driver
|
||||
[ 0.916414] sdhci: Copyright(c) Pierre Ossman
|
||||
[ 0.923366] sdhost: log_buf @ bac07000 (fac07000)
|
||||
[ 0.989001] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
|
||||
[ 1.049095] sdhci-pltfm: SDHCI platform and OF driver helper
|
||||
[726257.743301] sd 0:0:0:0: Attached scsi generic sg0 type 0
|
||||
[726259.184810] sd 0:0:0:0: [sda] 124846080 512-byte logical blocks: (63.9 GB/59.5 GiB)
|
||||
[726259.185603] sd 0:0:0:0: [sda] Write Protect is off
|
||||
[726259.185613] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
|
||||
[726259.186432] sd 0:0:0:0: [sda] No Caching mode page found
|
||||
[726259.186445] sd 0:0:0:0: [sda] Assuming drive cache: write through
|
||||
[726259.206085] sda: sda1
|
||||
[726259.209004] sd 0:0:0:0: [sda] Attached SCSI removable disk
|
||||
```
|
||||
|
||||
Here we see we have a drive on `/dev/sda1`. We assume you created a partition on the drive to start with. This can be any type of partition. Preferred is a Linux filesystem type so you can set permissions!
|
||||
|
||||
Mount the drive (as root) to `/media`
|
||||
|
||||
```bash
|
||||
# mount /dev/sda1 /media/
|
||||
```
|
||||
|
||||
### {% linkable_title Prepare USB Stick %}
|
||||
Change into it and create a folder called `hassbackup` and change the ownership to the user that runs Home Assistant. In my case group and user are both `homeassistant`.
|
||||
|
||||
```bash
|
||||
# cd /media/
|
||||
/media# mkdir hassbackup
|
||||
/media# chown homeassistant:homeassistant hassbackup/
|
||||
/media# ls -al
|
||||
total 28
|
||||
drwxr-xr-x 4 root root 4096 Apr 29 10:36 .
|
||||
drwxr-xr-x 22 root root 4096 Mar 22 18:37 ..
|
||||
drwxr-xr-x 2 homeassistant homeassistant 4096 Apr 29 10:36 hassbackup
|
||||
drwx------ 2 root root 16384 Apr 29 10:18 lost+found
|
||||
```
|
||||
You can ignore 'lost+found'.
|
||||
|
||||
### {% linkable_title Install Dependency %}
|
||||
|
||||
In order to preserve space on your drive we use zip. Install that too.
|
||||
|
||||
```bash
|
||||
/media# apt-get install zip
|
||||
Reading package lists... Done
|
||||
Building dependency tree
|
||||
[...]
|
||||
Setting up zip (3.0-8) ...
|
||||
```
|
||||
|
||||
### {% linkable_title Install and run script %}
|
||||
|
||||
Become the `homeassistant` user and place the following [script](https://gist.github.com/riemers/041c6a386a2eab95c55ba3ccaa10e7b0) to a place of your liking.
|
||||
|
||||
```bash
|
||||
# wget https://gist.githubusercontent.com/riemers/041c6a386a2eab95c55ba3ccaa10e7b0/raw/86727d4e72e9757da4f68f1c9d784720e72d0e99/usb_backup.sh
|
||||
```
|
||||
|
||||
Make the downloaded script executable.
|
||||
|
||||
```bash
|
||||
# chmod +x usb_backup.sh
|
||||
```
|
||||
|
||||
Open up the file and change the paths you want to use, then simply run the `./usb_backup.sh`.
|
||||
|
||||
```bash
|
||||
$ .homeassistant/extraconfig/shell_code/usb_backup.sh
|
||||
[i] Creating backup
|
||||
[i] Backup complete: /media/hassbackup/hass-config_20170429_112728.zip
|
||||
[i] Keeping all files no prunning set
|
||||
```
|
||||
|
||||
### {% linkable_title Crontab %}
|
||||
In order for this to automatically make a backup every night at 3 am, you can add a crontab for it as the `homeassistant` user.
|
||||
Change below path to where you placed the `usb_backup.sh` and run the following line.
|
||||
|
||||
```bash
|
||||
(crontab -l 2>/dev/null; echo "0 3 * * * /home/homeassistant/.homeassistant/extraconfig/shell_code/usb_backup.sh") | crontab -
|
||||
```
|
||||
|
||||
### {% linkable_title Auto mount %}
|
||||
|
||||
This does not automaticly mount your USB drive at boot. You need to do that manually or add a line to your `/etc/fstab` file.
|
||||
|
||||
If your drive is on `/dev/sda1`, you could add a entry to your `/etc/fstab` like so:
|
||||
|
||||
```text
|
||||
/dev/sda1 /media ext4 defaults,noatime 0 1
|
||||
```
|
||||
|
||||
Manual step to mount the USB drive:
|
||||
|
||||
```bash
|
||||
# mount /dev/sda1 /media
|
||||
```
|
||||
@ -34,7 +34,21 @@ At launch, Home Assistant for iOS sets up geofences for all zones in your Home A
|
||||
|
||||
### Configuration
|
||||
|
||||
To disable location tracking add `track_ios: false` to each zones settings or under customize.
|
||||
Add `track_ios: false` to your zone configurations to disable zone location tracking for all connected iOS apps.
|
||||
|
||||
### iBeacons
|
||||
|
||||
As of 1.0.3 the app has basic support for using iBeacons to trigger enter/exit updates. To configure them, add your iBeacon details to your zone like this:
|
||||
|
||||
```yaml
|
||||
zone.home:
|
||||
beacon:
|
||||
uuid: B9407F30-F5F8-466E-AFF9-25556B57FE6D
|
||||
major: 60042
|
||||
minor: 43814
|
||||
```
|
||||
|
||||
Restart Home Assistant and then the iOS app. It will begin then begin using iBeacons _instead of your location_ for enter and exit triggers around your zones. To add an iBeacon to `zone.home` add the above under your `customize`.
|
||||
|
||||
[apple-energy-guide]: https://developer.apple.com/library/content/documentation/Performance/Conceptual/EnergyGuide-iOS/LocationBestPractices.html#//apple_ref/doc/uid/TP40015243-CH24-SW4
|
||||
[apple-location-programming-guide]: https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html#//apple_ref/doc/uid/TP40009497-CH2-SW9
|
||||
|
||||
@ -57,3 +57,28 @@ automation
|
||||
data:
|
||||
subtitle: "Subtitle goes here"
|
||||
```
|
||||
|
||||
### {% linkable_title Sending notifications to multiple phones %}
|
||||
To send notifications to multiple phones, create a [notification group](https://home-assistant.io/components/notify.group/):
|
||||
```yaml
|
||||
notify:
|
||||
- name: NOTIFIER_NAME
|
||||
platform: group
|
||||
services:
|
||||
- service: ios_iphone_one
|
||||
- service: ios_iphone_two
|
||||
```
|
||||
Now, you can send notifications to everyone in the group using:
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Notify iOS app
|
||||
trigger:
|
||||
...
|
||||
action:
|
||||
service: notify.NOTIFIER_NAME
|
||||
data:
|
||||
message: "Something happened at home!"
|
||||
data:
|
||||
push:
|
||||
badge: 5
|
||||
```
|
||||
|
||||
@ -24,10 +24,28 @@ data:
|
||||
push:
|
||||
category: map
|
||||
action_data:
|
||||
latitude: 40.785091
|
||||
longitude: -73.968285
|
||||
latitude: "40.785091"
|
||||
longitude: "-73.968285"
|
||||
```
|
||||
|
||||
## Showing a second pin
|
||||
|
||||
You can use the following properties under `action_data` to display a second pin. If used, the first pin will be red and the second green.
|
||||
|
||||
- **second_latitude**: The latitude of the second pin. **Must be a string!**
|
||||
- **second_longitude**: The longitude of the second pin. **Must be a string!**
|
||||
- **shows_line_between_points**: A Boolean value indicating whether a line should be drawn between the first and second pin.
|
||||
|
||||
## Extra configuration
|
||||
|
||||
You can also pass the following properties under `action_data` to modify the map in various ways. All are expected to be boolean values unless otherwise noted:
|
||||
|
||||
- **shows_compass**: A Boolean indicating whether the map displays a compass control.
|
||||
- **shows_points_of_interest**: A Boolean indicating whether the map displays point-of-interest information.
|
||||
- **shows_scale**: A Boolean indicating whether the map shows scale information.
|
||||
- **shows_traffic**: A Boolean value indicating whether the map displays traffic information.
|
||||
- **shows_user_location**: A Boolean value indicating whether the map should try to display the user’s location.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/ios/map.png' />
|
||||
An example of the map dynamic content.
|
||||
@ -60,3 +78,7 @@ data:
|
||||
# Combining with actionable notifications
|
||||
|
||||
As you can see the `category` key is used to tell the device what kind of content extension to use. You can use the same category identifiers in your own custom [actions](/ecosystem/ios/notifications/actions/) to add actions to the content extension.
|
||||
|
||||
# Troubleshooting
|
||||
|
||||
If you are having problems with receiving these special notifications try restarting your phone first. The extensions somewhat often fail to register properly until a restart.
|
||||
|
||||
@ -89,8 +89,7 @@ http {
|
||||
server_name example.com;
|
||||
|
||||
# These shouldn't need to be changed
|
||||
listen 80 default_server;
|
||||
listen [::]:80 default_server ipv6only=on;
|
||||
listen [::]:80 default_server ipv6only=off;
|
||||
return 301 https://$host$request_uri;
|
||||
}
|
||||
|
||||
@ -110,7 +109,7 @@ http {
|
||||
|
||||
|
||||
# These shouldn't need to be changed
|
||||
listen 443 default_server;
|
||||
listen [::]:443 default_server ipv6only=off; # if your nginx version is >= 1.9.5 you can also add the "http2" flag here
|
||||
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
|
||||
ssl on;
|
||||
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
|
||||
|
||||
@ -10,4 +10,4 @@ footer: true
|
||||
redirect_from: /ecosystem/notebooks/graph/
|
||||
---
|
||||
|
||||
For graphing this [Jupyter notebook](ha_external_link: http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/graph-single-sensor.ipynb) should get you started.
|
||||
For graphing this [Jupyter notebook](http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/graph-single-sensor.ipynb) should get you started.
|
||||
|
||||
@ -10,14 +10,17 @@ footer: true
|
||||
redirect_from: /getting-started/hassbian-customization/
|
||||
---
|
||||
|
||||
To allow you to customize your installation further, we have included a set of Hassbian scripts.
|
||||
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation.
|
||||
|
||||
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it's usage is not recommended if you share your network with others.
|
||||
- Install Libcec. Adds local [HDMI CEC support][cec].
|
||||
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects offical repository. Now includes websocket support.
|
||||
- Install Open Z-Wave. Installs Open Z-Wave and prepares for using a USB or GPIO ZWave controller.
|
||||
- Install Hue. hue: Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
|
||||
- Install Tellstick. Installs the Tellstick package for controling and using a connected Tellstick.
|
||||
|
||||
All of these scripts are available in the directory `/home/pi/hassbian-scripts/`. For more information about these scripts have a look at the [hassbian-scripts repository][hassbian-repo].
|
||||
The tool is available by running `hassbian-config`. To view the available packages run `hassbian-config show` and `sudo hassbian-config install PACKAGENAME`.
|
||||
For more information about this tool have a look at the [hassbian-scripts repository][hassbian-repo].
|
||||
|
||||
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts#the-included-scripts
|
||||
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts
|
||||
[cec]: /components/hdmi_cec/
|
||||
|
||||
@ -12,9 +12,9 @@ redirect_from: /getting-started/installation-raspberry-pi-image/
|
||||
|
||||
The easiest way to install Home Assistant on your Raspberry Pi is by using HASSbian: a Raspberry Pi image with Home Assistant built-in. The image will install the latest version of Home Assistant on initial boot (~10 minutes).
|
||||
|
||||
1. [Download the Hassbian 1.1 image][image-download] (359 MB)
|
||||
1. [Download the Hassbian image][image-download] (364 MB)
|
||||
2. Use [Etcher][etcher] to flash the image to your SD card
|
||||
3. Ensure your Raspberry Pi has access to the internet.
|
||||
3. Ensure your Raspberry Pi has wired access to the internet.
|
||||
4. Insert SD card to Raspberry Pi and turn it on. Initial installation of Home Assistant will take about 5 minutes.
|
||||
|
||||
These instructions are also available as a [video](https://www.youtube.com/watch?v=iIz6XqDwHEk). Additional information is available in this [video](https://www.youtube.com/watch?v=tCGlQSsQ-Mc).
|
||||
@ -25,6 +25,8 @@ The following extras are included on the image:
|
||||
|
||||
- GPIO pins are ready to use.
|
||||
- Bluetooth is ready to use (supported models only, no Bluetooth LE).
|
||||
- SSH server is enabled.
|
||||
- A tool called `hassbian_config`.
|
||||
|
||||
### {% linkable_title Technical Details %}
|
||||
|
||||
@ -32,6 +34,6 @@ The following extras are included on the image:
|
||||
- Home Assistant will be started as a service run by the user `homeassistant`
|
||||
- The configuration is located at `/home/homeassistant/.homeassistant`
|
||||
|
||||
[image-download]: https://github.com/home-assistant/pi-gen/releases/download/v1.1/image_2017-02-03-HASSbian.zip
|
||||
[image-download]: https://github.com/home-assistant/pi-gen/releases/latest
|
||||
[etcher]: https://etcher.io/
|
||||
[http://hassbian.local:8123]: http://hassbian.local:8123
|
||||
|
||||
@ -16,11 +16,21 @@ Some components that are specific for the Raspberry Pi can require some further
|
||||
|
||||
The Bluetooth tracker will work on a Raspberry Pi 3 with the built-in Bluetooth module or with a USB Bluetooth device on any of the other Raspberry Pi's.
|
||||
|
||||
Install the following external dependencies.
|
||||
```bash
|
||||
$ sudo apt-get install bluetooth libbluetooth-dev
|
||||
```
|
||||
After this follow the [Bluetooth Tracker component](/components/device_tracker.bluetooth_tracker/) and [Device Tracker page](/components/device_tracker/) pages.
|
||||
Software needed for the tracker is pre-installed so just follow the [Bluetooth Tracker component](/components/device_tracker.bluetooth_tracker/) and [Device Tracker page](/components/device_tracker/) pages.
|
||||
|
||||
### {% linkable_title Raspberry Pi GPIO %}
|
||||
|
||||
Each of the following devices are connected to the GPIO pins on the Raspberry Pi.
|
||||
For more details about the GPIO layout, visit the [documentation](https://www.raspberrypi.org/documentation/usage/gpio/) from the Raspberry Pi foundation.
|
||||
|
||||
Permission have been given to the `homeassistant` user to use the GPIO pins and all of the following components should require no underlying changes to work.
|
||||
Just follow the component pages for each on how to add them to your Home Assistant installation.
|
||||
|
||||
- [DHT Sensor](/components/sensor.dht/).
|
||||
- [Raspberry Pi Cover](/components/cover.rpi_gpio/).
|
||||
- [Raspberry PI GPIO Binary Sensor](/components/binary_sensor.rpi_gpio/).
|
||||
- [Raspberry PI GPIO Switch](/components/switch.rpi_gpio/).
|
||||
- [Raspberry Pi RF Switch](/components/switch.rpi_rf/).
|
||||
|
||||
### {% linkable_title Raspberry Pi Camera %}
|
||||
|
||||
@ -34,63 +44,8 @@ $ sudo raspi-config
|
||||
|
||||
Select `Enable camera` choose `<Yes>` and hit `Enter`, then go to `Finish` and you'll be prompted to reboot.
|
||||
|
||||
After reboot add your `homeassistant` account to the `video` group.
|
||||
|
||||
```bash
|
||||
$ sudo adduser homeassistant video
|
||||
```
|
||||
|
||||
After this follow the [Raspberry Pi Camera component](/components/camera.rpi_camera/) page.
|
||||
|
||||
### {% linkable_title Raspberry Pi GPIO %}
|
||||
|
||||
Each of the following devices are connected to the GPIO pins on the Raspberry Pi.
|
||||
For more details about the GPIO layout, visit the [documentation](https://www.raspberrypi.org/documentation/usage/gpio/) from the Raspberry Pi foundation.
|
||||
|
||||
Since these are not normally used some extra permission will need to be added.
|
||||
In general the permission that is needed is granted by adding the `homeassistant` account to the `gpio` group.
|
||||
|
||||
### {% linkable_title Raspberry Pi Cover %}
|
||||
|
||||
Add your `homeassistant` account to the `gpio` group
|
||||
```bash
|
||||
$ sudo adduser homeassistant gpio
|
||||
```
|
||||
After this follow the [Raspberry Pi Cover component](/components/cover.rpi_gpio/) page.
|
||||
|
||||
### {% linkable_title DHT Sensor %}
|
||||
|
||||
Add your `homeassistant` account to the `gpio` group
|
||||
```bash
|
||||
$ sudo adduser homeassistant gpio
|
||||
```
|
||||
After this follow the [DHT Sensor component](/components/sensor.dht/) page.
|
||||
|
||||
|
||||
### {% linkable_title Raspberry PI GPIO Binary Sensor %}
|
||||
|
||||
Add your `homeassistant` account to the `gpio` group
|
||||
```bash
|
||||
$ sudo adduser homeassistant gpio
|
||||
```
|
||||
After this follow the [Raspberry PI GPIO Binary Sensor component](/components/binary_sensor.rpi_gpio/) page.
|
||||
|
||||
### {% linkable_title Raspberry PI GPIO Switch %}
|
||||
|
||||
Add your `homeassistant` account to the `gpio` group.
|
||||
```bash
|
||||
$ sudo adduser homeassistant gpio
|
||||
```
|
||||
After this follow the [Raspberry PI GPIO Switch component](/components/switch.rpi_gpio/) page.
|
||||
|
||||
### {% linkable_title Raspberry Pi RF Switch %}
|
||||
|
||||
Add your `homeassistant` account to the `gpio` group
|
||||
```bash
|
||||
$ sudo adduser homeassistant gpio
|
||||
```
|
||||
After this follow the [Raspberry Pi RF Switch component](/components/switch.rpi_rf/) page.
|
||||
|
||||
### {% linkable_title One wire Sensor %}
|
||||
|
||||
The One wire sensor requires that support for it is enabled on the Raspberry Pi and that the One Wire device is connected to GPIO pin 4.
|
||||
|
||||
@ -31,12 +31,3 @@ $ pip3 install --upgrade homeassistant
|
||||
$ exit
|
||||
$ sudo systemctl start home-assistant@homeassistant.service
|
||||
```
|
||||
|
||||
#### {% linkable_title Upgrading the hassbian-scripts %}
|
||||
|
||||
To update the hassbian-scripts directory execute the following command as the `pi` user.
|
||||
|
||||
```bash
|
||||
$ cd /home/pi/hassbian-scripts
|
||||
$ git pull
|
||||
```
|
||||
|
||||
@ -24,8 +24,8 @@ and Home Assistant itself.
|
||||
$ pip3 install homeassistant
|
||||
```
|
||||
|
||||
Home Assistant is part of the [AUR](https://aur.archlinux.org/packages/home-assistant/). This means that it can be installed directly with `pacman`:
|
||||
Home Assistant is part of the [AUR](https://aur.archlinux.org/packages/home-assistant/). This means that it can be installed with `pacaur`:
|
||||
|
||||
```bash
|
||||
$ sudo pacman -S home-assistant
|
||||
$ sudo pacaur -S home-assistant
|
||||
```
|
||||
|
||||
@ -20,10 +20,10 @@ The default way to update Home Assistant to the latest release, when available,
|
||||
$ pip3 install --upgrade homeassistant
|
||||
```
|
||||
|
||||
After updating, you must restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable)
|
||||
After updating, you must restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e. minutes) depending on your device. This is because all requirements are updated as well.
|
||||
|
||||
<p class='note'>
|
||||
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [HASSbian](/docs/hassbian/installation/), [Raspberry Pi All-In-One Installer](/docs/installation/raspberry-pi-all-in-one/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
|
||||
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [HASSbian](/docs/hassbian/installation/), [Raspberry Pi All-In-One Installer](/docs/installation/raspberry-pi-all-in-one/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
|
||||
</p>
|
||||
|
||||
[BRUH automation](http://www.bruhautomation.com) has created [a tutorial video](https://www.youtube.com/watch?v=tuG2rs1Cl2Y) explaining how to upgrade Home Assistant.
|
||||
|
||||
@ -63,7 +63,7 @@ The `su` command means 'switch' user. We use the '-s' flag because the `homeassi
|
||||
|
||||
All this step does is stick a Python environment in the directory we're using. That's it. It's just a directory. There's nothing special about it, and it is entirely self-contained.
|
||||
|
||||
It will include a `bin` directory, which will contain all the executables used in the virtualenv (including hass itself). It also includes a script called `activate` which we will use to activate the virtualenv.
|
||||
It will include a `bin` directory, which will contain all the executables used in the virtualenv (including Home Assistant itself). It also includes a script called `activate` which we will use to activate the virtualenv.
|
||||
|
||||
```bash
|
||||
$ virtualenv -p python3 /srv/homeassistant
|
||||
@ -128,7 +128,6 @@ Finally, get and install `python-openzwave`.
|
||||
(homeassistant)$ cd /srv/homeassistant/src
|
||||
(homeassistant)$ git clone https://github.com/OpenZWave/python-openzwave.git
|
||||
(homeassistant)$ cd python-openzwave
|
||||
(homeassistant)$ git checkout python3
|
||||
(homeassistant)$ PYTHON_EXEC=`which python3` make build
|
||||
(homeassistant)$ PYTHON_EXEC=`which python3` make install
|
||||
```
|
||||
|
||||
@ -34,14 +34,13 @@ Make sure you have at least version 0.23 and at the most 0.24.1 of cython.
|
||||
$ sudo pip3 install --upgrade cython==0.24.1
|
||||
```
|
||||
|
||||
Then get the OpenZWave files and switch to the `python3` branch:
|
||||
Then get the OpenZWave files:
|
||||
|
||||
<p class='note warning'>Do not use root to build python-openzwave as it will surely fail.</p>
|
||||
|
||||
```bash
|
||||
$ git clone https://github.com/OpenZWave/python-openzwave.git
|
||||
$ cd python-openzwave
|
||||
$ git checkout python3
|
||||
$ PYTHON_EXEC=$(which python3) make build
|
||||
$ sudo PYTHON_EXEC=$(which python3) make install
|
||||
```
|
||||
@ -62,6 +61,7 @@ With this installation, your `config_path` needed below will resemble:
|
||||
```
|
||||
|
||||
If you followed along with setting up a virtual environment, your path will be:
|
||||
|
||||
```bash
|
||||
/srv/homeassistant/python-openzwave/openzwave/config
|
||||
```
|
||||
@ -85,8 +85,8 @@ Configuration variables:
|
||||
- **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.
|
||||
- **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`.
|
||||
|
||||
To find the path of your Z-Wave USB stick or module, run:
|
||||
|
||||
@ -99,7 +99,7 @@ Or, on some other systems (such as Raspberry Pi), use:
|
||||
```bash
|
||||
$ ls /dev/ttyACM*
|
||||
|
||||
# If `hass` runs with another user (e.g. *homeassistant* on Hassbian) give access to the stick with:
|
||||
# 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
|
||||
```
|
||||
|
||||
|
||||
@ -17,6 +17,7 @@
|
||||
<li>{% active_link /developers/development_environment/ Setting up Environment %}</li>
|
||||
<li>{% active_link /developers/development_submitting/ Submit your Work %}</li>
|
||||
<li>{% active_link /developers/development_checklist/ Checklist %}</li>
|
||||
<li>{% active_link /developers/development_guidelines/ Style guidelines %}</li>
|
||||
<li>{% active_link /developers/development_testing/ Testing %}</li>
|
||||
<li>{% active_link /developers/development_catching_up/ Catching up with Reality %}</li>
|
||||
<li>{% active_link /developers/development_validation/ Validation %}</li>
|
||||
|
||||
@ -198,9 +198,16 @@
|
||||
<li>{% active_link /docs/ecosystem/certificates/lets_encrypt/ Let's Encrypt (detailed) %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Backup
|
||||
<ul>
|
||||
<li>{% active_link /docs/ecosystem/backup/backup_github/ Backup to GitHub %}</li>
|
||||
<li>{% active_link /docs/ecosystem/backup/backup_dropbox/ Backup to Dropbox %}</li>
|
||||
<li>{% active_link /docs/ecosystem/backup/backup_usb/ Backup to USB device %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>{% active_link /docs/ecosystem/scenegen/ scenegen %}</li>
|
||||
<li>{% active_link /docs/ecosystem/synology/ Synology %}</li>
|
||||
<li>{% active_link /docs/ecosystem/backup/backup_github/ Backup to GitHub %}</li>
|
||||
<li>{% active_link /docs/ecosystem/hass-configurator/ HASS Configurator %}</li>
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
24
source/_includes/asides/hassio_navigation.html
Normal file
24
source/_includes/asides/hassio_navigation.html
Normal file
@ -0,0 +1,24 @@
|
||||
<section class="aside-module grid__item one-whole lap-one-half">
|
||||
<div class='section'>
|
||||
<h1 class="title delta">Topics</h1>
|
||||
<ul class='divided sidebar-menu'>
|
||||
<li>
|
||||
{% active_link /hassio/ Hass.io %}
|
||||
<ul>
|
||||
<li>{% active_link /hassio/installation/ Installation %}</li>
|
||||
<li>{% active_link /addons/ Available add-ons %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<ul class='divided sidebar-menu'>
|
||||
<li>
|
||||
{% active_link /hassio/development/ Development %}
|
||||
<ul>
|
||||
<li>{% active_link /hassio/architecture/ Architecture %}</li>
|
||||
<li>{% active_link /hassio/create_hassio_addon/ Creating add-ons %}</li>
|
||||
<li>{% active_link /hassio/create_hassio_addon_repository/ Creating add-on repositories %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</section>
|
||||
@ -10,6 +10,8 @@
|
||||
{% include asides/getting_started_navigation.html | compact_newlines %}
|
||||
{% elsif url_parts[1] == 'docs' %}
|
||||
{% include asides/docs_navigation.html | compact_newlines %}
|
||||
{% elsif url_parts[1] == 'hassio' or url_parts[1] == 'addons' %}
|
||||
{% include asides/hassio_navigation.html | compact_newlines %}
|
||||
{% else %}
|
||||
{% include asides/about.html %}
|
||||
|
||||
|
||||
@ -48,6 +48,7 @@ Also note that you have till the end of the weekend to [submit an application][a
|
||||
- Ping binary sensor ([@fabaff] - [#7052]) ([binary_sensor.ping docs]) (new-platform)
|
||||
- myStrom Wifi Bulbs ([@fabaff] - [#7161]) ([light.mystrom docs]) (new-platform)
|
||||
|
||||
<!--more-->
|
||||
## {% linkable_title Breaking changes %}
|
||||
|
||||
- Remove deprecated classes from `homeassistant.remote` ([@balloob] - [#7011])
|
||||
@ -82,7 +83,32 @@ sensor:
|
||||
directions: '1'
|
||||
```
|
||||
|
||||
<!--more-->
|
||||
## If you need help...
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
|
||||
## Reporting Issues
|
||||
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
|
||||
|
||||
## {% linkable_title Release 0.43.1 - April 25 %}
|
||||
|
||||
- Zwave cover workaround for graber shades. ([@turbokongen] - [#7204]) ([cover.zwave docs]) ([zwave.workaround docs])
|
||||
- Upgrade paho-mqtt to 1.2.3 ([@fabaff] - [#7214])
|
||||
- Workround for wemo subscription bug. ([@pavoni] - [#7245]) ([wemo docs]) ([switch.wemo docs])
|
||||
- Fix telegram webhooks ([@MartinHjelmare] - [#7236]) ([telegram_bot docs]) ([telegram_bot.webhooks docs])
|
||||
- Work around bad content-type in Hook api response ([@KlaasH] - [#7267]) ([switch.hook docs])
|
||||
- Recorder: Check for ENTITY_ID key that contains None value ([@balloob] - [#7287]) ([recorder docs])
|
||||
|
||||
## {% linkable_title Release 0.43.2 - April 27 %}
|
||||
|
||||
- Frontend: Fix default date on history/logbook (@amelchio)
|
||||
- Frontend: Fix logbook ui (@balloob)
|
||||
- Upgrade pytradfri to 1.1 ([@balloob] - [#7290])
|
||||
- Upgrade python-telegram-bot to 5.3.1 ([@fabaff] - [#7311]) ([notify.telegram docs]) ([telegram_bot.polling docs]) ([telegram_bot.webhooks docs])
|
||||
- Version bump of aioautomatic ([@armills] - [#7300]) ([device_tracker.automatic docs])
|
||||
- Version bump for automatic ([@armills] - [#7329]) ([device_tracker.automatic docs])
|
||||
- Fix breaking SSL in test HTML5 ([@balloob] - [#7310]) ([notify.html5 docs])
|
||||
- Fix for building Python Open Z-Wave in Docker ([@balloob] - [#7337])
|
||||
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- Update kodi for aiohttp2 ([@armills] - [#6967]) ([media_player.kodi docs]) ([notify.kodi docs])
|
||||
@ -460,3 +486,39 @@ sensor:
|
||||
[wemo docs]: /components/wemo/
|
||||
[zwave docs]: /components/zwave/
|
||||
[zwave.node_entity docs]: /components/zwave.node_entity/
|
||||
<<<<<<< HEAD
|
||||
=======
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[#7204]: https://github.com/home-assistant/home-assistant/pull/7204
|
||||
[#7214]: https://github.com/home-assistant/home-assistant/pull/7214
|
||||
[#7236]: https://github.com/home-assistant/home-assistant/pull/7236
|
||||
[#7245]: https://github.com/home-assistant/home-assistant/pull/7245
|
||||
[#7267]: https://github.com/home-assistant/home-assistant/pull/7267
|
||||
[#7287]: https://github.com/home-assistant/home-assistant/pull/7287
|
||||
[@KlaasH]: https://github.com/KlaasH
|
||||
[cover.zwave docs]: https://home-assistant.io/components/cover.zwave/
|
||||
[recorder docs]: https://home-assistant.io/components/recorder/
|
||||
[switch.hook docs]: https://home-assistant.io/components/switch.hook/
|
||||
[switch.wemo docs]: https://home-assistant.io/components/switch.wemo/
|
||||
[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/
|
||||
[telegram_bot.webhooks docs]: https://home-assistant.io/components/telegram_bot.webhooks/
|
||||
[wemo docs]: https://home-assistant.io/components/wemo/
|
||||
[zwave.workaround docs]: https://home-assistant.io/components/zwave.workaround/
|
||||
[#7271]: https://github.com/home-assistant/home-assistant/pull/7271
|
||||
[#7282]: https://github.com/home-assistant/home-assistant/pull/7282
|
||||
[#7290]: https://github.com/home-assistant/home-assistant/pull/7290
|
||||
[#7300]: https://github.com/home-assistant/home-assistant/pull/7300
|
||||
[#7310]: https://github.com/home-assistant/home-assistant/pull/7310
|
||||
[#7311]: https://github.com/home-assistant/home-assistant/pull/7311
|
||||
[#7323]: https://github.com/home-assistant/home-assistant/pull/7323
|
||||
[#7324]: https://github.com/home-assistant/home-assistant/pull/7324
|
||||
[#7329]: https://github.com/home-assistant/home-assistant/pull/7329
|
||||
[#7337]: https://github.com/home-assistant/home-assistant/pull/7337
|
||||
[device_tracker.automatic docs]: https://home-assistant.io/components/device_tracker.automatic/
|
||||
[hassio docs]: https://home-assistant.io/components/hassio/
|
||||
[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
|
||||
[notify.telegram docs]: https://home-assistant.io/components/notify.telegram/
|
||||
[telegram_bot.polling docs]: https://home-assistant.io/components/telegram_bot.polling/
|
||||
>>>>>>> current
|
||||
|
||||
29
source/_posts/2017-04-24-hardware-contest-2017.markdown
Normal file
29
source/_posts/2017-04-24-hardware-contest-2017.markdown
Normal file
@ -0,0 +1,29 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Hardware Contest 2017"
|
||||
description: "Voting period for Hardware Contest 2017 started"
|
||||
date: 2017-04-24 06:00:00 +0000
|
||||
date_formatted: "April 24, 2017"
|
||||
author: Fabian Affolter
|
||||
author_twitter: fabaff
|
||||
comments: true
|
||||
categories: Community
|
||||
og_image: /images/default-social.png
|
||||
---
|
||||
|
||||
We have four submissions for our [Hardware Contest 2017][hardware].
|
||||
|
||||
- [Part of IoT-course](https://community.home-assistant.io/t/entry-for-hardware-contest-part-of-iot-course/14827)
|
||||
- [Automating a nursing home!](https://community.home-assistant.io/t/entry-automating-a-nursing-home/14872)
|
||||
- [Dedicated hardware for coding, testing, building, and contributing to Home Assistant](https://community.home-assistant.io/t/entry-dedicated-hardware-for-coding-testing-building-and-contributing-to-home-assistant/15515)
|
||||
- [HassIO - Home Assistant hub for dummies](https://community.home-assistant.io/t/entry-hassio-home-assistant-hub-for-dummies/16037)
|
||||
|
||||
The voting is now open. To keep things simple are we using the voting feature of the [forum]. Vote for your choices.
|
||||
|
||||
End of the voting period: April, 30 2017 - 23.59 UTC
|
||||
|
||||
[hardware]: https://home-assistant.io/blog/2017/04/01/thomas-krenn-award/
|
||||
[award]: https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/
|
||||
[forum]: https://community.home-assistant.io/c/contest-2017
|
||||
[twitter]: https://twitter.com/home_assistant
|
||||
|
||||
@ -1,23 +1,23 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Setting up InfluxDB and Grafana using Docker"
|
||||
description: "Use this tutorial to setup InfluxDB and Grafana on a Docker container and use it with Home Assistant."
|
||||
description: "Use this tutorial to setup InfluxDB and Grafana in a Docker container and use it with Home Assistant."
|
||||
date: 2017-04-25 08:04:05 +0000
|
||||
date_formatted: "April 25, 2017"
|
||||
author: Alok Saboo
|
||||
author_twitter: alokrsaboo
|
||||
comments: true
|
||||
categories: tutorial
|
||||
categories: How-To
|
||||
og_image: /images/blog/2017-04-influxdb-grafana/influxdb-grafana-ha.png
|
||||
---
|
||||
|
||||
Home Assistant collects volumes of (time series) data that are well suited for some fancy graphs. Although the [History](https://home-assistant.io/components/history/) component provides some nice plots, I am sure you have always wanted those fancy [Grafana](https://grafana.com/) plots. The problem, however, is that low-powered device such as Raspberry Pi that most of us use for our Home Assistant setup are not well suited for such operation.
|
||||
|
||||
Instead of running InfluxDB and Grafana on a Raspberry Pi, you can run them in a Docker container on another machine. For this tutorial, I am using a Synology NAS, but the instructions should apply to other devices that can run Docker. Just follow the steps below:
|
||||
Instead of running [InfluxDB](https://www.influxdata.com/) and Grafana on a Raspberry Pi or a different system and go through the [classic approach of installing both tools separately](/blog/2015/12/07/influxdb-and-grafana/), you can run them in a Docker container on another machine. For this tutorial, I am using a Synology NAS, but the instructions should apply to other devices that can run Docker. Just follow the steps below:
|
||||
|
||||
1. SSH into your NAS. You may have to run `sudo su` if you are getting permission errors.
|
||||
2. Download the [docker-statsd-influxdb-grafana]( https://hub.docker.com/r/samuelebistoletti/docker-statsd-influxdb-grafana/) image using the command:
|
||||
` docker pull samuelebistoletti/docker-statsd-influxdb-grafana`
|
||||
`docker pull samuelebistoletti/docker-statsd-influxdb-grafana`
|
||||
3. To start the container for the first-time launch:
|
||||
```
|
||||
docker run -d \
|
||||
|
||||
@ -0,0 +1,50 @@
|
||||
---
|
||||
layout: post
|
||||
title: "HASSbian 1.21 - It's about time isn't it"
|
||||
description: "New release of the HASSbian Raspberry Pi Image for Home Assistant"
|
||||
date: 2017-04-30 16:00:00 +0100
|
||||
date_formatted: "April 30, 2017"
|
||||
author: Fredrik Lindqvist
|
||||
comments: true
|
||||
categories: Technology
|
||||
---
|
||||
|
||||
### Hassbian 1.21 - It's about time isn't it
|
||||
Since I, the developer of HASSbian, have been moving, started a new job and so on I've had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I'll do my best to release more often. There's no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the [hassbian-config][hassbian-config-release] package. For more information have a look at the [hassbian-config][hassbian-repo] page.
|
||||
|
||||
### Hassbian 1.22 - Sins of last night
|
||||
Development is sometimes fast and joyful but mistakes are made at times.
|
||||
|
||||
With the release of 1.21 a small problem with the OpenZWave build script wasn't corrected even tough it was a known bug. Problem is simple as it's only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.
|
||||
|
||||
### {% linkable_title Hassbian-config %}
|
||||
|
||||
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the `hassbian-scripts` functionality from 1.1.
|
||||
|
||||
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it's usage is not recommended if you share your network with others.
|
||||
- Install Libcec. Adds local [HDMI CEC support][cec].
|
||||
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
|
||||
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.
|
||||
- Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git.
|
||||
- Install Tradfri. Installs dependencies for using IKEA Trådfri.
|
||||
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
|
||||
- Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick.
|
||||
|
||||
### {% linkable_title Spring cleaning %}
|
||||
|
||||
With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.
|
||||
|
||||
- Replaced the `hassbian-scripts` folder with `hassbian-config`.
|
||||
- Update `pi-gen`. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.
|
||||
- Added libtool and autoconf package. Dependencies for some of the pip packages.
|
||||
- Pi ZeroW should now work with the image.
|
||||
|
||||
To follow discussions about the development of the HASSbian image or to contribute join the [HASSbian gitter chat][hassbian-gitter].
|
||||
|
||||
To get started with the new image, check out the installation instructions in the [getting started section][gs-image].
|
||||
|
||||
[cec]: /components/hdmi_cec/
|
||||
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts/
|
||||
[hassbian-config-release]: https://github.com/home-assistant/hassbian-scripts/releases/latest
|
||||
[hassbian-gitter]: https://gitter.im/home-assistant/hassbian
|
||||
[gs-image]: /getting-started/installation-raspberry-pi-image/
|
||||
@ -0,0 +1,71 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant on a Pi Zero W in 30 minutes"
|
||||
description: "Installing Home Assistant (Hassbian) on a Pi Zero W"
|
||||
date: 2017-05-01 09:00:00
|
||||
date_formatted: "May 1, 2017"
|
||||
author: Avraham David Gelbfish
|
||||
author_twitter: adgelbfish
|
||||
comments: true
|
||||
categories: How-To
|
||||
og_image: /images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png
|
||||
---
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png" />
|
||||
</p>
|
||||
|
||||
Saw the [announcement](/blog/2017/04/30/hassbian-1.21-its-about-time/) yesterday for HASSbian 1.21 and got super excited?
|
||||
|
||||
Today we'll flash the latest HASSbian to a [Raspbery Pi Zero W](https://www.raspberrypi.org/products/pi-zero/).
|
||||
**With an added bonus** that besides for an USB cable for power, there's no need for any cables!
|
||||
|
||||
What you'll need:
|
||||
- a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi)
|
||||
- a microSD card
|
||||
- some source of USB power
|
||||
- Wifi
|
||||
- a desktop or laptop
|
||||
|
||||
Let's get to it!
|
||||
|
||||
First, download the HASSbian 1.21 image from [here](https://github.com/home-assistant/pi-gen/releases/tag/v1.21).
|
||||
|
||||
Unzip it.
|
||||
|
||||
Flash it to the microSD card. If you need a flash tool, try [Etcher](https://etcher.io/)
|
||||
|
||||
When the flashing finishes, remove it and plug it back in. You should see a drive called "boot".
|
||||
|
||||
Right in there, not in any folders, create a file called `wpa_supplicant.conf`.
|
||||
|
||||
The contents of the configuration file should be something like this:
|
||||
(You may have to adjust for your configuration, hints [here](https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md) )
|
||||
|
||||
```
|
||||
network={
|
||||
ssid="YOUR_WIFI_NETWORK_NAME_HERE"
|
||||
psk="YOUR_WIFI_PASSWORD_HERE"
|
||||
key_mgmt=WPA-PSK
|
||||
}
|
||||
```
|
||||
|
||||
Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
|
||||
|
||||
After about a minute, use your SSH client to connect to HASSbian (or `hassbian.local` from a Mac), with the username `pi`. The default password is `raspberry`.
|
||||
|
||||
It's a good idea to change the password. To do so, use the `passwd` command.
|
||||
|
||||
Next, type the following two commands into the SSH console:
|
||||
|
||||
```
|
||||
$ sudo systemctl enable install_homeassistant.service
|
||||
$ sudo systemctl start install_homeassistant.service
|
||||
```
|
||||
|
||||
Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
|
||||
|
||||
To try it out, go to [http://hassbian:8123](http://hassbian:8123) or [http://hassbian.local:8123](http://hassbian.local:8123) if you're using Mac.
|
||||
|
||||
For further details about HASSbian, take a look at the [documentation](https://home-assistant.io/docs/hassbian/).
|
||||
|
||||
21
source/addons/index.html
Normal file
21
source/addons/index.html
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Hass.io Add-ons"
|
||||
description: "List of the built-in add-ons of Hass.io."
|
||||
date: 2017-04-30 13:35
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
regenerate: true
|
||||
---
|
||||
|
||||
<p>Add-ons are extensions for your Home Assistant installation.</p>
|
||||
|
||||
{% assign addons = site.addons | sort: 'title' %}
|
||||
|
||||
<ul>
|
||||
{% for addon in addons %}
|
||||
<li><a href='{{ addon.url }}'>{{ addon.title }}</a></li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
@ -2,7 +2,7 @@
|
||||
layout: page
|
||||
title: "Credits"
|
||||
description: "Credits for the developers who contributed to Home Assistant."
|
||||
date: 2017-04-18 21:17:50 +0000
|
||||
date: 2017-04-24 07:59:09 +0000
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
@ -13,7 +13,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
|
||||
### {% linkable_title Author %}
|
||||
|
||||
- [Paulus Schoutsen (@balloob)](https://github.com/balloob "5150 total commits to the home-assistant organization, 3190 commits to home-assistant, 1039 commits to home-assistant.github.io, 497 commits to home-assistant-polymer, 244 commits to home-assistant-js, 103 commits to netdisco, 39 commits to home-assistant-js-websocket, 12 commits to home-assistant-assets, 8 commits to hass-release, 7 commits to micropython-home-assistant, 4 commits to example-custom-config, 2 commits to python-hassbian, 2 commits to lambda-home-assistant-github, 1 commit to issue-bot, 1 commit to home-assistant-notebooks, 1 commit to home-assistant-iOS")
|
||||
- [Paulus Schoutsen (@balloob)](https://github.com/balloob "5191 total commits to the home-assistant organization, 3215 commits to home-assistant, 1045 commits to home-assistant.github.io, 501 commits to home-assistant-polymer, 244 commits to home-assistant-js, 106 commits to netdisco, 39 commits to home-assistant-js-websocket, 12 commits to home-assistant-assets, 11 commits to hass-release, 7 commits to micropython-home-assistant, 4 commits to example-custom-config, 2 commits to lambda-home-assistant-github, 2 commits to python-hassbian, 1 commit to home-assistant-notebooks, 1 commit to issue-bot, 1 commit to home-assistant-iOS")
|
||||
|
||||
### {% linkable_title Contributors %}
|
||||
|
||||
@ -28,7 +28,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Abhishek Anand (@aa755)](https://github.com/aa755 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [abmantis (@abmantis)](https://github.com/abmantis "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Adam Garcia (@pancho-villa)](https://github.com/pancho-villa "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Adam Mills (@armills)](https://github.com/armills "126 total commits to the home-assistant organization, 82 commits to home-assistant, 22 commits to home-assistant-polymer, 19 commits to home-assistant.github.io, 3 commits to home-assistant-js")
|
||||
- [Adam Mills (@armills)](https://github.com/armills "129 total commits to the home-assistant organization, 85 commits to home-assistant, 22 commits to home-assistant-polymer, 19 commits to home-assistant.github.io, 3 commits to home-assistant-js")
|
||||
- [ADeeds (@ADeeds)](https://github.com/ADeeds "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [AdithyanI (@AdithyanI)](https://github.com/AdithyanI "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Aditya Shevade (@adibis)](https://github.com/adibis "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -39,7 +39,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Albert Lee (@trisk)](https://github.com/trisk "10 total commits to the home-assistant organization, 6 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Alberto Arias Maestro (@albertoarias)](https://github.com/albertoarias "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Aleksey Gureiev (@alg)](https://github.com/alg "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Alessandro Mogavero (@alexmogavero)](https://github.com/alexmogavero "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 Harvey (@infamy)](https://github.com/infamy "21 total commits to the home-assistant organization, 11 commits to home-assistant, 10 commits to home-assistant.github.io")
|
||||
- [Alex Mekkering (@AlexMekkering)](https://github.com/AlexMekkering "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -54,20 +54,20 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Alexandre Perrin (@kAworu)](https://github.com/kAworu "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Alfie Day (@Azelphur)](https://github.com/Azelphur "12 total commits to the home-assistant organization, 12 commits to home-assistant")
|
||||
- [Allan Glen (@allanglen)](https://github.com/allanglen "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "49 total commits to the home-assistant organization, 31 commits to home-assistant.github.io, 16 commits to home-assistant, 1 commit to pi-gen, 1 commit to hassbian-scripts")
|
||||
- [Alok Saboo (@arsaboo)](https://github.com/arsaboo "51 total commits to the home-assistant organization, 32 commits to home-assistant.github.io, 17 commits to home-assistant, 1 commit to pi-gen, 1 commit to hassbian-scripts")
|
||||
- [amahlaka (@amahlaka)](https://github.com/amahlaka "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [amorsillo (@fignuts)](https://github.com/fignuts "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Anastasia A. (@Sacret)](https://github.com/Sacret "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Anders Gjendem (@agjendem)](https://github.com/agjendem "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "19 total commits to the home-assistant organization, 13 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Anders Melchiorsen (@amelchio)](https://github.com/amelchio "23 total commits to the home-assistant organization, 17 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [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 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [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 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Andrew (@aoakeson)](https://github.com/aoakeson "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Andrew (@aneisch)](https://github.com/aneisch "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Andrew Cockburn (@acockburn)](https://github.com/acockburn "240 total commits to the home-assistant organization, 122 commits to appdaemon, 85 commits to hadashboard, 25 commits to scenegen, 8 commits to home-assistant.github.io")
|
||||
- [Andrew LeCody (@aceat64)](https://github.com/aceat64 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Andrew McClure (@nzfarmer1)](https://github.com/nzfarmer1 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -77,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 "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Andrey (@andrey-git)](https://github.com/andrey-git "101 total commits to the home-assistant organization, 53 commits to home-assistant, 26 commits to home-assistant-polymer, 22 commits to home-assistant.github.io")
|
||||
- [Andrey (@andrey-git)](https://github.com/andrey-git "103 total commits to the home-assistant organization, 54 commits to home-assistant, 27 commits to home-assistant-polymer, 22 commits to home-assistant.github.io")
|
||||
- [Andrey Petrov (@anpetrov)](https://github.com/anpetrov "2 total commits to the home-assistant organization, 1 commit to home-assistant.github.io, 1 commit 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")
|
||||
- [Andy Lindeman (@alindeman)](https://github.com/alindeman "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -101,7 +101,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Assaf Inbal (@shmuelzon)](https://github.com/shmuelzon "11 total commits to the home-assistant organization, 8 commits to homebridge-homeassistant, 3 commits to home-assistant")
|
||||
- [atorralba (@atorralba)](https://github.com/atorralba "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Audun Ytterdal (@auduny)](https://github.com/auduny "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [aufano (@aufano)](https://github.com/aufano "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [aufano (@aufano)](https://github.com/aufano "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Austin (@trainman419)](https://github.com/trainman419 "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Avraham David Gelbfish (@adgelbfish)](https://github.com/adgelbfish "2 total commits to the home-assistant organization, 1 commit to hadashboard, 1 commit to pi-gen")
|
||||
- [Barry Williams (@bazwilliams)](https://github.com/bazwilliams "5 total commits to the home-assistant organization, 2 commits to netdisco, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
@ -139,7 +139,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Brendan Berg (@captainnapalm)](https://github.com/captainnapalm "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Brent Hughes (@bah2830)](https://github.com/bah2830 "25 total commits to the home-assistant organization, 16 commits to home-assistant, 8 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Brent Saltzman (@brent20)](https://github.com/brent20 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Brian J King (@brianjking)](https://github.com/brianjking "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io")
|
||||
- [Brian J King (@brianjking)](https://github.com/brianjking "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
|
||||
- [Brian Karani Ndwiga (@rayrayndwiga)](https://github.com/rayrayndwiga "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Brian Torres-Gil (@btorresgil)](https://github.com/btorresgil "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Brigham Brown (@brigham)](https://github.com/brigham "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -156,12 +156,12 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [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 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Charles Blonde (@CharlesBlonde)](https://github.com/CharlesBlonde "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Charles Spirakis (@srcLurker)](https://github.com/srcLurker "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Chayoung You (@yous)](https://github.com/yous "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Check your git settings! (@invalid-email-address)](https://github.com/invalid-email-address "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Chema García (@sch3m4)](https://github.com/sch3m4 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Chris (@AlucardZero)](https://github.com/AlucardZero "15 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 4 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 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")
|
||||
@ -182,7 +182,6 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Chun-wei Kuo (@Domon)](https://github.com/Domon "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [chz^3 (@chzchzchz)](https://github.com/chzchzchz "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Ciquattro (@CiquattroFPV)](https://github.com/CiquattroFPV "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [citruz (@citruz)](https://github.com/citruz "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [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")
|
||||
- [Claudiu Farcas (@farcasclaudiu)](https://github.com/farcasclaudiu "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Claus F. Strasburger (@cfstras)](https://github.com/cfstras "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
@ -194,14 +193,13 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Cooper Dale (@Cooper-Dale)](https://github.com/Cooper-Dale "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Corban Mailloux (@corbanmailloux)](https://github.com/corbanmailloux "17 total commits to the home-assistant organization, 16 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Craig J. Ward (@wardcraigj)](https://github.com/wardcraigj "11 total commits to the home-assistant organization, 7 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [dainok (@dainok)](https://github.com/dainok "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Dale Higgs (@dale3h)](https://github.com/dale3h "24 total commits to the home-assistant organization, 13 commits to home-assistant.github.io, 9 commits to home-assistant, 1 commit to homebridge-homeassistant, 1 commit to hassbot")
|
||||
- [Dan (@danieljkemp)](https://github.com/danieljkemp "22 total commits to the home-assistant organization, 15 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Dan Cinnamon (@Cinntax)](https://github.com/Cinntax "13 total commits to the home-assistant organization, 10 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Dan Ford (@dpford)](https://github.com/dpford "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Dan Lowe (@tangledhelix)](https://github.com/tangledhelix "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Dan Olson (@danielolson13)](https://github.com/danielolson13 "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Dan Ports (@drkp)](https://github.com/drkp "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Dan Ports (@drkp)](https://github.com/drkp "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [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")
|
||||
@ -210,7 +208,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Daniel Høyer Iversen (@Danielhiversen)](https://github.com/Danielhiversen "291 total commits to the home-assistant organization, 197 commits to home-assistant, 92 commits to home-assistant.github.io, 2 commits to home-assistant-polymer")
|
||||
- [Daniel Matuschek (@usul27)](https://github.com/usul27 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Daniel Perna (@danielperna84)](https://github.com/danielperna84 "47 total commits to the home-assistant organization, 32 commits to home-assistant.github.io, 15 commits to home-assistant")
|
||||
- [Daniel Peukert (@dpeukert)](https://github.com/dpeukert "1 total commits to the home-assistant organization, 1 commit to home-assistant-polymer")
|
||||
- [Daniel Peukert (@dpeukert)](https://github.com/dpeukert "2 total commits to the home-assistant organization, 1 commit to home-assistant-polymer, 1 commit to home-assistant.github.io")
|
||||
- [Daniel Watkins (@OddBloke)](https://github.com/OddBloke "4 total commits to the home-assistant organization, 4 commits to home-assistant-ansible")
|
||||
- [Daniel Wiberg (@dannew)](https://github.com/dannew "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Danijel Stojnic (@danijelst)](https://github.com/danijelst "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -220,8 +218,8 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Dave (@d4v3d)](https://github.com/d4v3d "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Dave Banks (@djbanks)](https://github.com/djbanks "3 total commits to the home-assistant organization, 2 commits to appdaemon, 1 commit to home-assistant")
|
||||
- [DaveSergeant (@dethpickle)](https://github.com/dethpickle "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [David (@fanaticDavid)](https://github.com/fanaticDavid "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
|
||||
- [David (@dschoorisse)](https://github.com/dschoorisse "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [David (@fanaticDavid)](https://github.com/fanaticDavid "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
|
||||
- [David Baumann (@daBONDi)](https://github.com/daBONDi "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [David De Sloovere (@DavidDeSloovere)](https://github.com/DavidDeSloovere "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [David McNett (@nugget)](https://github.com/nugget "9 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
@ -231,7 +229,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [David Thomas (@synth3tk)](https://github.com/synth3tk "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [David-Leon Pohl (@DavidLP)](https://github.com/DavidLP "14 total commits to the home-assistant organization, 12 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [davidedmundson (@davidedmundson)](https://github.com/davidedmundson "7 total commits to the home-assistant organization, 4 commits to home-assistant, 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 Camera (@abcminiuser)](https://github.com/abcminiuser "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [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 "9 total commits to the home-assistant organization, 9 commits to home-assistant")
|
||||
- [Delper (@Delper)](https://github.com/Delper "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -242,7 +240,6 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 Soares (@diogos88)](https://github.com/diogos88 "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Dmytro Kytsmen (@Kietzmann)](https://github.com/Kietzmann "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [doudz (@doudz)](https://github.com/doudz "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [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")
|
||||
- [Drew Wells (@drewwells)](https://github.com/drewwells "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
@ -250,10 +247,8 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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")
|
||||
- [Dylan Barlett (@dbarlett)](https://github.com/dbarlett "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [ecksun (@ecksun)](https://github.com/ecksun "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.github.io, 2 commits to home-assistant")
|
||||
- [eieste (@eieste)](https://github.com/eieste "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [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")
|
||||
- [Emanuele Palombo (@elbowz)](https://github.com/elbowz "1 total commits to the home-assistant organization, 1 commit 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")
|
||||
@ -264,9 +259,9 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Eric Jansen (@ej81)](https://github.com/ej81 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Eric Rolf (@xrolfex)](https://github.com/xrolfex "13 total commits to the home-assistant organization, 13 commits to home-assistant")
|
||||
- [Eric Thompson (@er0ck)](https://github.com/er0ck "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Erik Eriksson (@molobrakos)](https://github.com/molobrakos "89 total commits to the home-assistant organization, 81 commits to home-assistant, 5 commits to home-assistant.github.io, 3 commits to netdisco")
|
||||
- [Erik Eriksson (@molobrakos)](https://github.com/molobrakos "90 total commits to the home-assistant organization, 82 commits to home-assistant, 5 commits to home-assistant.github.io, 3 commits to netdisco")
|
||||
- [ettisan (@ettisan)](https://github.com/ettisan "8 total commits to the home-assistant organization, 8 commits to home-assistant")
|
||||
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "3520 total commits to the home-assistant organization, 2214 commits to home-assistant.github.io, 1152 commits to home-assistant, 59 commits to home-assistant-ansible, 23 commits to home-assistant-dev-helper, 21 commits to home-assistant-cli, 20 commits to home-assistant-notebooks, 12 commits to home-assistant-assets, 10 commits to home-assistant-polymer, 8 commits to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [Fabian Affolter (@fabaff)](https://github.com/fabaff "3549 total commits to the home-assistant organization, 2225 commits to home-assistant.github.io, 1170 commits to home-assistant, 59 commits to home-assistant-ansible, 23 commits to home-assistant-dev-helper, 21 commits to home-assistant-cli, 20 commits to home-assistant-notebooks, 12 commits to home-assistant-assets, 10 commits to home-assistant-polymer, 8 commits to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [Fabian Heredia Montiel (@fabianhjr)](https://github.com/fabianhjr "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [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")
|
||||
@ -302,7 +297,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Gergely Imreh (@imrehg)](https://github.com/imrehg "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Gert (@Gerto)](https://github.com/Gerto "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Gert-Jan van de Streek (@keerts)](https://github.com/keerts "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Gianluca Barbaro (@MrMep)](https://github.com/MrMep "20 total commits to the home-assistant organization, 14 commits to home-assistant, 6 commits to home-assistant.github.io")
|
||||
- [Gianluca Barbaro (@MrMep)](https://github.com/MrMep "24 total commits to the home-assistant organization, 16 commits to home-assistant, 8 commits to home-assistant.github.io")
|
||||
- [Giannie (@Giannie)](https://github.com/Giannie "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Gianpaolo Macario (@gmacario)](https://github.com/gmacario "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Giel Janssens (@gieljnssns)](https://github.com/gieljnssns "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
@ -314,7 +309,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Graeme Smith (@Instagraeme)](https://github.com/Instagraeme "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Graham Christensen (@grahamc)](https://github.com/grahamc "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [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 "238 total commits to the home-assistant organization, 211 commits to home-assistant, 25 commits to home-assistant.github.io, 2 commits to netdisco")
|
||||
- [Greg Dowling (@pavoni)](https://github.com/pavoni "239 total commits to the home-assistant organization, 212 commits to home-assistant, 25 commits to home-assistant.github.io, 2 commits to netdisco")
|
||||
- [Greg MacLellan (@gregmac)](https://github.com/gregmac "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Greg Stevenson (@gstevenson)](https://github.com/gstevenson "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Gregor Gruener (@ggruner)](https://github.com/ggruner "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
@ -324,12 +319,12 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [gwendalg (@gwendalg)](https://github.com/gwendalg "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Hajime Morrita (@omo)](https://github.com/omo "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Hao Hu (@howiehu)](https://github.com/howiehu "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [happyleavesaoc (@happyleavesaoc)](https://github.com/happyleavesaoc "83 total commits to the home-assistant organization, 65 commits to home-assistant, 17 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [happyleavesaoc (@happyleavesaoc)](https://github.com/happyleavesaoc "88 total commits to the home-assistant organization, 68 commits to home-assistant, 19 commits to home-assistant.github.io, 1 commit to home-assistant-polymer")
|
||||
- [Harald Nagel (@haraldnagel)](https://github.com/haraldnagel "8 total commits to the home-assistant organization, 6 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Hari Menon (@floydpink)](https://github.com/floydpink "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Harris Borawski (@hborawski)](https://github.com/hborawski "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Harry Kantas (@harrykantas)](https://github.com/harrykantas "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [hawk259 (@hawk259)](https://github.com/hawk259 "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [hawk259 (@hawk259)](https://github.com/hawk259 "6 total commits to the home-assistant organization, 3 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [HBDK (@HBDK)](https://github.com/HBDK "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [hcooper (@hcooper)](https://github.com/hcooper "2 total commits to the home-assistant organization, 2 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")
|
||||
@ -337,6 +332,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Hellowlol (@Hellowlol)](https://github.com/Hellowlol "3 total commits to the home-assistant organization, 3 commits to netdisco")
|
||||
- [Helmut Januschka (@hjanuschka)](https://github.com/hjanuschka "3 total commits to the home-assistant organization, 3 commits to issue-bot")
|
||||
- [Henning Dickten (@hensing)](https://github.com/hensing "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Henrik Nicolaisen (@hmn)](https://github.com/hmn "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Hermann Kraus (@herm)](https://github.com/herm "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Hernán R (@hmronline)](https://github.com/hmronline "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [hexa- (@mweinelt)](https://github.com/mweinelt "17 total commits to the home-assistant organization, 10 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
@ -378,14 +374,11 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Jared J. (@jjensn)](https://github.com/jjensn "2 total commits to the home-assistant organization, 1 commit to netdisco, 1 commit to home-assistant")
|
||||
- [Jason Carter (@JasonCarter80)](https://github.com/JasonCarter80 "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [Jason Hite (@jasonmhite)](https://github.com/jasonmhite "6 total commits to the home-assistant organization, 6 commits to appdaemon")
|
||||
- [Jason Schollenberger (@jschollenberger)](https://github.com/jschollenberger "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Jason Woodward (@woodwardjd)](https://github.com/woodwardjd "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Javier González Calleja (@gonzalezcalleja)](https://github.com/gonzalezcalleja "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Jay Love (@jslove)](https://github.com/jslove "2 total commits to the home-assistant organization, 1 commit to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Javier González Calleja (@gonzalezcalleja)](https://github.com/gonzalezcalleja "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Jay Love (@jslove)](https://github.com/jslove "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Jean Regisser (@jeanregisser)](https://github.com/jeanregisser "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Jean-Michel Julien (@KurdyMalloy)](https://github.com/KurdyMalloy "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Jean-Philippe Bouillot (@Jypy)](https://github.com/Jypy "3 total commits to the home-assistant organization, 2 commits to home-assistant, 1 commit to home-assistant.github.io")
|
||||
- [Jed Lippold (@jlippold)](https://github.com/jlippold "1 total commits to the home-assistant organization, 1 commit to home-assistant.github.io")
|
||||
- [Jean-Philippe Bouillot (@Jypy)](https://github.com/Jypy "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Jeff Schroeder (@SEJeff)](https://github.com/SEJeff "17 total commits to the home-assistant organization, 17 commits to home-assistant")
|
||||
- [Jeff Wilson (@jawilson)](https://github.com/jawilson "15 total commits to the home-assistant organization, 13 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Jeffrey Lin (@linjef)](https://github.com/linjef "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -400,6 +393,7 @@ 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")
|
||||
- [jnimmo (@jnimmo)](https://github.com/jnimmo "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Joakim af Sandeberg (@jotunacorn)](https://github.com/jotunacorn "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Joakim Nohlgård (@gebart)](https://github.com/gebart "2 total commits to the home-assistant organization, 2 commits to libcoap")
|
||||
- [Job Vermeulen (@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")
|
||||
@ -408,15 +402,16 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Joeboyc2 (@Joeboyc2)](https://github.com/Joeboyc2 "12 total commits to the home-assistant organization, 11 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Joel Asher Friedman (@joelash)](https://github.com/joelash "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [joemcmonagle (@joemcmonagle)](https://github.com/joemcmonagle "8 total commits to the home-assistant organization, 8 commits to home-assistant.github.io")
|
||||
- [Johan Bloemberg (@aequitas)](https://github.com/aequitas "31 total commits to the home-assistant organization, 25 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Johan Bloemberg (@aequitas)](https://github.com/aequitas "32 total commits to the home-assistant organization, 26 commits to home-assistant, 5 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Johan Carlquist (@theseal)](https://github.com/theseal "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Johan Klintberg (@moogblob)](https://github.com/moogblob "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Johann Kellerman (@kellerza)](https://github.com/kellerza "144 total commits to the home-assistant organization, 114 commits to home-assistant, 30 commits to home-assistant.github.io")
|
||||
- [Johannes K. (@roadrash2108)](https://github.com/roadrash2108 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [John Arild Berentsen (@turbokongen)](https://github.com/turbokongen "164 total commits to the home-assistant organization, 132 commits to home-assistant, 26 commits to home-assistant.github.io, 6 commits to home-assistant-polymer")
|
||||
- [John Arild Berentsen (@turbokongen)](https://github.com/turbokongen "166 total commits to the home-assistant organization, 133 commits to home-assistant, 27 commits to home-assistant.github.io, 6 commits to home-assistant-polymer")
|
||||
- [John Coggeshall (@coogle)](https://github.com/coogle "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [John Lindley (@jwl17330536)](https://github.com/jwl17330536 "18 total commits to the home-assistant organization, 11 commits to hadashboard, 6 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [John McLaughlin (@loghound)](https://github.com/loghound "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [John Mihalic (@mezz64)](https://github.com/mezz64 "28 total commits to the home-assistant organization, 18 commits to home-assistant, 9 commits to home-assistant.github.io, 1 commit to hadashboard")
|
||||
- [John Mihalic (@mezz64)](https://github.com/mezz64 "29 total commits to the home-assistant organization, 19 commits to home-assistant, 9 commits to home-assistant.github.io, 1 commit to hadashboard")
|
||||
- [John Williams (@Jaidan)](https://github.com/Jaidan "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [johnappletree (@johnappletree)](https://github.com/johnappletree "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Jon (@JonMurphy)](https://github.com/JonMurphy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
@ -424,7 +419,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Jon Evans (@craftyjon)](https://github.com/craftyjon "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Jon Maddox (@maddox)](https://github.com/maddox "102 total commits to the home-assistant organization, 78 commits to home-assistant, 16 commits to homebridge-homeassistant, 8 commits to home-assistant.github.io")
|
||||
- [Jonatan Castro (@jcastro)](https://github.com/jcastro "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Jonathan Baginski (@patchedsoul)](https://github.com/patchedsoul "113 total commits to the home-assistant organization, 86 commits to fabric-home-assistant, 27 commits to home-assistant.github.io")
|
||||
- [Jonathan Baginski (@patchedsoul)](https://github.com/patchedsoul "114 total commits to the home-assistant organization, 86 commits to fabric-home-assistant, 28 commits to home-assistant.github.io")
|
||||
- [joopert (@joopert)](https://github.com/joopert "4 total commits to the home-assistant organization, 4 commits to home-assistant")
|
||||
- [Jordan Keith (@zeddD1abl0)](https://github.com/zeddD1abl0 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Jose Juan Montes (@jjmontesl)](https://github.com/jjmontesl "7 total commits to the home-assistant organization, 5 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
@ -462,7 +457,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Keyasha Brothern (@KMBrothern)](https://github.com/KMBrothern "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [kireyeu (@kireyeu)](https://github.com/kireyeu "4 total commits to the home-assistant organization, 4 commits to home-assistant-notebooks")
|
||||
- [KiXaM 刻む (@kixam)](https://github.com/kixam "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Klaas Hoekema (@KlaasH)](https://github.com/KlaasH "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Klaas Hoekema (@KlaasH)](https://github.com/KlaasH "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Krasimir Chariyski (@Chariyski)](https://github.com/Chariyski "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [Krasimir Zhelev (@zhelev)](https://github.com/zhelev "2 total commits to the home-assistant organization, 1 commit to netdisco, 1 commit to home-assistant")
|
||||
- [Kyle Gordon (@kylegordon)](https://github.com/kylegordon "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -483,6 +478,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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")
|
||||
- [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 "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [LvivEchoes (@LvivEchoes)](https://github.com/LvivEchoes "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [m4tek (@m4tek)](https://github.com/m4tek "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Maciej Wasilak (@mwasilak)](https://github.com/mwasilak "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Magas (@magas0)](https://github.com/magas0 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -498,7 +494,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Marc Pabst (@mxtra)](https://github.com/mxtra "2 total commits to the home-assistant organization, 1 commit to home-assistant-polymer, 1 commit to home-assistant")
|
||||
- [Marc Plano-Lesay (@Kernald)](https://github.com/Kernald "9 total commits to the home-assistant organization, 9 commits to home-assistant.github.io")
|
||||
- [Marcel030nl (@Marcel030nl)](https://github.com/Marcel030nl "6 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "92 total commits to the home-assistant organization, 49 commits to home-assistant, 43 commits to home-assistant.github.io")
|
||||
- [Marcelo Moreira de Mello (@tchellomello)](https://github.com/tchellomello "93 total commits to the home-assistant organization, 50 commits to home-assistant, 43 commits to home-assistant.github.io")
|
||||
- [Marcin Jaworski (@yawor)](https://github.com/yawor "10 total commits to the home-assistant organization, 10 commits to appdaemon")
|
||||
- [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 (@scmmmh)](https://github.com/scmmmh "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -510,18 +506,19 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Markus Peter (@bimbar)](https://github.com/bimbar "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Markus Stenberg (@fingon)](https://github.com/fingon "6 total commits to the home-assistant organization, 6 commits to home-assistant")
|
||||
- [Martin Bernstorff (@ryqiem)](https://github.com/ryqiem "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Martin Hjelmare (@MartinHjelmare)](https://github.com/MartinHjelmare "115 total commits to the home-assistant organization, 90 commits to home-assistant, 25 commits to home-assistant.github.io")
|
||||
- [Martin Hjelmare (@MartinHjelmare)](https://github.com/MartinHjelmare "118 total commits to the home-assistant organization, 93 commits to home-assistant, 25 commits to home-assistant.github.io")
|
||||
- [Martin J. Laubach (@mjl)](https://github.com/mjl "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Martin Nöhrer (@matrixx567)](https://github.com/matrixx567 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Martin Rowan (@shortbloke)](https://github.com/shortbloke "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Martin Vacula (@MatoKafkac)](https://github.com/MatoKafkac "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [martinfrancois (@martinfrancois)](https://github.com/martinfrancois "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Martokk (@martokk)](https://github.com/martokk "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Mathew Peterson (@mathewpeterson)](https://github.com/mathewpeterson "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Matt N. (@mnoorenberghe)](https://github.com/mnoorenberghe "22 total commits to the home-assistant organization, 15 commits to home-assistant.github.io, 6 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [Matt Rogers (@rogersmj)](https://github.com/rogersmj "20 total commits to the home-assistant organization, 20 commits to hadashboard")
|
||||
- [Matteo Lampugnani (@t30)](https://github.com/t30 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [Matthew Bowen (@mgbowen)](https://github.com/mgbowen "4 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Matthew Garrett (@mjg59)](https://github.com/mjg59 "8 total commits to the home-assistant organization, 5 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Matthew Garrett (@mjg59)](https://github.com/mjg59 "9 total commits to the home-assistant organization, 6 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Matthew Treinish (@mtreinish)](https://github.com/mtreinish "12 total commits to the home-assistant organization, 8 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [Matthias Grawinkel (@meatz)](https://github.com/meatz "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Max Rumpf (@Maxr1998)](https://github.com/Maxr1998 "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
@ -536,7 +533,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Michael Luggen (@l00mi)](https://github.com/l00mi "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Michael Requeny (@requenym)](https://github.com/requenym "14 total commits to the home-assistant organization, 14 commits to home-assistant.github.io")
|
||||
- [Michael Shim (@shimeez)](https://github.com/shimeez "1 total commits to the home-assistant organization, 1 commit to fabric-home-assistant")
|
||||
- [Michaël Arnauts (@michaelarnauts)](https://github.com/michaelarnauts "48 total commits to the home-assistant organization, 24 commits to home-assistant, 20 commits to home-assistant.github.io, 3 commits to home-assistant-polymer, 1 commit to netdisco")
|
||||
- [Michaël Arnauts (@michaelarnauts)](https://github.com/michaelarnauts "49 total commits to the home-assistant organization, 24 commits to home-assistant, 21 commits to home-assistant.github.io, 3 commits to home-assistant-polymer, 1 commit to netdisco")
|
||||
- [Michel Settembrino (@MS-Informatique)](https://github.com/MS-Informatique "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [micw (@micw)](https://github.com/micw "6 total commits to the home-assistant organization, 4 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Mikayla Hutchinson (@mhutch)](https://github.com/mhutch "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -548,10 +545,10 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [MinchinWeb (@MinchinWeb)](https://github.com/MinchinWeb "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [miniconfig (@miniconfig)](https://github.com/miniconfig "27 total commits to the home-assistant organization, 20 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Minims (@Minims)](https://github.com/Minims "3 total commits to the home-assistant organization, 3 commits to homebridge-homeassistant")
|
||||
- [Mitesh Patel (@gurumitts)](https://github.com/gurumitts "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Mitko Masarliev (@masarliev)](https://github.com/masarliev "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Mitesh Patel (@gurumitts)](https://github.com/gurumitts "5 total commits to the home-assistant organization, 3 commits to home-assistant, 2 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")
|
||||
- [mnestor (@mnestor)](https://github.com/mnestor "6 total commits to the home-assistant organization, 5 commits to home-assistant, 1 commit to home-assistant-polymer")
|
||||
- [Molodax (@Molodax)](https://github.com/Molodax "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Molodax (@Molodax)](https://github.com/Molodax "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
- [Moon Shot (@moonshot)](https://github.com/moonshot "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [moskovskiy82 (@moskovskiy82)](https://github.com/moskovskiy82 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [mtl010957 (@mtl010957)](https://github.com/mtl010957 "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
@ -572,7 +569,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Nicolas Graziano (@ngraziano)](https://github.com/ngraziano "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Nicolas Martignoni (@martignoni)](https://github.com/martignoni "1 total commits to the home-assistant organization, 1 commit to pi-gen")
|
||||
- [Niklas (@niklaswa)](https://github.com/niklaswa "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Nikolas Beutler (@biacz)](https://github.com/biacz "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Nikolas Beutler (@biacz)](https://github.com/biacz "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Nils Uliczka (@darookee)](https://github.com/darookee "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [NMA (@nma83)](https://github.com/nma83 "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [nodomain (@nodomain)](https://github.com/nodomain "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to homebridge-homeassistant")
|
||||
@ -583,17 +580,17 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [obgm (@obgm)](https://github.com/obgm "480 total commits to the home-assistant organization, 480 commits to libcoap")
|
||||
- [OLD PROFILE! Go to /dennisreimann (@dbloete)](https://github.com/dbloete "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Ole-Kenneth (@olekenneth)](https://github.com/olekenneth "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
|
||||
- [Oleksii Serdiuk (@leppa)](https://github.com/leppa "4 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 2 commits to home-assistant")
|
||||
- [Oleksii Serdiuk (@leppa)](https://github.com/leppa "4 total commits to the home-assistant organization, 2 commits to home-assistant, 2 commits to home-assistant.github.io")
|
||||
- [Olimpiu Rob (@olimpiurob)](https://github.com/olimpiurob "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Oliv3rDog (@Oliv3rDog)](https://github.com/Oliv3rDog "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Oliver (@scarface-4711)](https://github.com/scarface-4711 "7 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant, 1 commit to netdisco")
|
||||
- [Oliver (@scarface-4711)](https://github.com/scarface-4711 "8 total commits to the home-assistant organization, 4 commits to home-assistant, 3 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")
|
||||
- [Open Home Automation (@open-homeautomation)](https://github.com/open-homeautomation "22 total commits to the home-assistant organization, 18 commits to home-assistant, 4 commits to home-assistant.github.io")
|
||||
- [OpenDave15 (@OpenDave15)](https://github.com/OpenDave15 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Otto Winter (@OttoWinter)](https://github.com/OttoWinter "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Parker Moore (@parkr)](https://github.com/parkr "62 total commits to the home-assistant organization, 62 commits to home-assistant.github.io")
|
||||
- [Pascal Bach (@bachp)](https://github.com/bachp "9 total commits to the home-assistant organization, 9 commits to home-assistant")
|
||||
- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "439 total commits to the home-assistant organization, 345 commits to home-assistant, 92 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [Pascal Vizeli (@pvizeli)](https://github.com/pvizeli "445 total commits to the home-assistant organization, 351 commits to home-assistant, 92 commits to home-assistant.github.io, 1 commit to netdisco, 1 commit to home-assistant-js-websocket")
|
||||
- [patkap (@patkap)](https://github.com/patkap "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Patrick Aikens (@duckpuppy)](https://github.com/duckpuppy "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Patrick White (@pw)](https://github.com/pw "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
@ -616,7 +613,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [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 "18 total commits to the home-assistant organization, 11 commits to home-assistant, 7 commits to home-assistant.github.io")
|
||||
- [Pierre Ståhl (@postlund)](https://github.com/postlund "22 total commits to the home-assistant organization, 15 commits to home-assistant, 4 commits to home-assistant.github.io, 3 commits to netdisco")
|
||||
- [Pierre Ståhl (@postlund)](https://github.com/postlund "26 total commits to the home-assistant organization, 18 commits to home-assistant, 4 commits to netdisco, 4 commits to home-assistant.github.io")
|
||||
- [pinksocks (@pinksocks)](https://github.com/pinksocks "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Piratonym (@Piratonym)](https://github.com/Piratonym "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [PuckStar (@PuckStar)](https://github.com/PuckStar "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
@ -637,7 +634,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Rob Capellini (@capellini)](https://github.com/capellini "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Rob Johnson (@robjohnson189)](https://github.com/robjohnson189 "1 total commits to the home-assistant organization, 1 commit 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 "1083 total commits to the home-assistant organization, 455 commits to home-assistant-iOS, 242 commits to home-assistant, 238 commits to home-assistant.github.io, 71 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 hassbot, 3 commits to scenegen, 3 commits to home-assistant-js-websocket, 3 commits to home-assistant-js, 3 commits to hadashboard, 3 commits to home-assistant-cli, 3 commits to appdaemon, 2 commits to home-assistant-ansible, 2 commits to home-assistant-dev-helper, 2 commits to micropython-home-assistant, 2 commits to home-assistant-assets, 2 commits to fabric-home-assistant, 2 commits to home-assistant-notebooks, 2 commits to lambda-home-assistant-github, 1 commit to LabelBot")
|
||||
- [Robbie Trencheny (@robbiet480)](https://github.com/robbiet480 "1161 total commits to the home-assistant organization, 530 commits to home-assistant-iOS, 243 commits to home-assistant, 240 commits to home-assistant.github.io, 71 commits to homebridge-homeassistant, 15 commits to home-assistant-polymer, 9 commits to hubot-home-assistant, 8 commits to Analytics-Receiver, 6 commits to netdisco, 3 commits to home-assistant-js, 3 commits to appdaemon, 3 commits to home-assistant-js-websocket, 3 commits to hadashboard, 3 commits to organization, 3 commits to hassbot, 3 commits to scenegen, 3 commits to home-assistant-cli, 2 commits to home-assistant-assets, 2 commits to home-assistant-notebooks, 2 commits to home-assistant-dev-helper, 2 commits to fabric-home-assistant, 2 commits to home-assistant-ansible, 2 commits to lambda-home-assistant-github, 2 commits to micropython-home-assistant, 1 commit to LabelBot")
|
||||
- [Robby Grossman (@freerobby)](https://github.com/freerobby "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Robin Laurén (@llauren)](https://github.com/llauren "1 total commits to the home-assistant organization, 1 commit to appdaemon")
|
||||
- [Roddie Hasan (@eiddor)](https://github.com/eiddor "6 total commits to the home-assistant organization, 6 commits to home-assistant.github.io")
|
||||
@ -672,9 +669,9 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Scott Bradshaw (@swbradshaw)](https://github.com/swbradshaw "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Scott Henning (@shenning00)](https://github.com/shenning00 "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [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 "7 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 1 commit to home-assistant-polymer, 1 commit to home-assistant")
|
||||
- [Scott Reston (@ih8gates)](https://github.com/ih8gates "8 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 1 commit to home-assistant-polymer, 1 commit to home-assistant")
|
||||
- [scottocs11 (@scottocs11)](https://github.com/scottocs11 "7 total commits to the home-assistant organization, 7 commits to home-assistant.github.io")
|
||||
- [Sean Dague (@sdague)](https://github.com/sdague "50 total commits to the home-assistant organization, 34 commits to home-assistant, 7 commits to home-assistant.github.io, 5 commits to home-assistant-polymer, 3 commits to netdisco, 1 commit to home-assistant-js")
|
||||
- [Sean Dague (@sdague)](https://github.com/sdague "51 total commits to the home-assistant organization, 35 commits to home-assistant, 7 commits to home-assistant.github.io, 5 commits to home-assistant-polymer, 3 commits to netdisco, 1 commit to home-assistant-js")
|
||||
- [Sebastian (@sebk-666)](https://github.com/sebk-666 "4 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [Sebastian (@sgso)](https://github.com/sgso "3 total commits to the home-assistant organization, 3 commits to libcoap")
|
||||
- [Sebastian Hartnick (@goir)](https://github.com/goir "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -699,13 +696,13 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Stuart Mumford (@Cadair)](https://github.com/Cadair "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Stéphane Bidoul (ACSONE) (@sbidoul)](https://github.com/sbidoul "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [System Tester (@systemtester)](https://github.com/systemtester "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
- [Sytone (@sytone)](https://github.com/sytone "9 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant-cli, 1 commit to home-assistant")
|
||||
- [Sören Oldag (@soldag)](https://github.com/soldag "7 total commits to the home-assistant organization, 4 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [Sytone (@sytone)](https://github.com/sytone "10 total commits to the home-assistant organization, 6 commits to home-assistant.github.io, 2 commits to home-assistant-cli, 2 commits to home-assistant")
|
||||
- [Sören Oldag (@soldag)](https://github.com/soldag "9 total commits to the home-assistant organization, 5 commits to home-assistant.github.io, 4 commits to home-assistant")
|
||||
- [Teagan Glenn (@Teagan42)](https://github.com/Teagan42 "49 total commits to the home-assistant organization, 45 commits to home-assistant, 3 commits to home-assistant.github.io, 1 commit to home-assistant-js")
|
||||
- [techtrails (@techtrails)](https://github.com/techtrails "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [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 "26 total commits to the home-assistant organization, 18 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Teemu R. (@rytilahti)](https://github.com/rytilahti "28 total commits to the home-assistant organization, 20 commits to home-assistant, 7 commits to home-assistant.github.io, 1 commit to netdisco")
|
||||
- [Teguh Sobirin (@tjstyle)](https://github.com/tjstyle "2 total commits to the home-assistant organization, 2 commits to pi-gen")
|
||||
- [Terry Carlin (@terrycarlin)](https://github.com/terrycarlin "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
- [The Gitter Badger (@gitter-badger)](https://github.com/gitter-badger "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
@ -720,6 +717,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Thomas Friedel (@tfriedel)](https://github.com/tfriedel "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Thomas Petazzoni (@tpetazzoni)](https://github.com/tpetazzoni "1 total commits to the home-assistant organization, 1 commit to libcoap")
|
||||
- [Thomas Pötsch (@thp-comnets)](https://github.com/thp-comnets "7 total commits to the home-assistant organization, 7 commits to libcoap")
|
||||
- [thrawnarn (@thrawnarn)](https://github.com/thrawnarn "1 total commits to the home-assistant organization, 1 commit to netdisco")
|
||||
- [ThUnD3r|Gr33n (@thundergreen)](https://github.com/thundergreen "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
- [tijuca (@tijuca)](https://github.com/tijuca "106 total commits to the home-assistant organization, 106 commits to libcoap")
|
||||
- [Tim (@tinglis1)](https://github.com/tinglis1 "3 total commits to the home-assistant organization, 3 commits to home-assistant.github.io")
|
||||
@ -738,7 +736,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Tomi Tuhkanen (@ttu)](https://github.com/ttu "3 total commits to the home-assistant organization, 3 commits to home-assistant")
|
||||
- [Touliloup (@RiRomain)](https://github.com/RiRomain "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [tradiuz (@tradiuz)](https://github.com/tradiuz "5 total commits to the home-assistant organization, 5 commits to home-assistant.github.io")
|
||||
- [Trevor (@tboyce1)](https://github.com/tboyce1 "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [Trevor (@tboyce021)](https://github.com/tboyce021 "5 total commits to the home-assistant organization, 5 commits to home-assistant")
|
||||
- [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")
|
||||
- [Tyler Crumpton (@tylercrumpton)](https://github.com/tylercrumpton "3 total commits to the home-assistant organization, 2 commits to home-assistant.github.io, 1 commit to home-assistant")
|
||||
@ -746,6 +744,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Tõnis Tobre (@tobre6)](https://github.com/tobre6 "1 total commits to the home-assistant organization, 1 commit to homebridge-homeassistant")
|
||||
- [Valentin Alexeev (@valentinalexeev)](https://github.com/valentinalexeev "11 total commits to the home-assistant organization, 8 commits to home-assistant, 3 commits to home-assistant.github.io")
|
||||
- [Valentin VĂLCIU (@axiac)](https://github.com/axiac "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [viswa-swami (@viswa-swami)](https://github.com/viswa-swami "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [Vittorio Monaco (@vittoriom)](https://github.com/vittoriom "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Vlad Korniev (@vkorn)](https://github.com/vkorn "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [vllungu (@vllungu)](https://github.com/vllungu "3 total commits to the home-assistant organization, 3 commits to libcoap")
|
||||
@ -764,7 +763,7 @@ This page contains a list of people who have contributed in one way or another t
|
||||
- [Wolf-Bastian Pöttner (@BastianPoe)](https://github.com/BastianPoe "6 total commits to the home-assistant organization, 3 commits to home-assistant.github.io, 3 commits to home-assistant")
|
||||
- [Wolfgang Malgadey (@wmalgadey)](https://github.com/wmalgadey "2 total commits to the home-assistant organization, 2 commits to home-assistant")
|
||||
- [XECDesign (@XECDesign)](https://github.com/XECDesign "56 total commits to the home-assistant organization, 56 commits to pi-gen")
|
||||
- [Xorso (@Xorso)](https://github.com/Xorso "20 total commits to the home-assistant organization, 20 commits to home-assistant")
|
||||
- [Xorso (@Xorso)](https://github.com/Xorso "21 total commits to the home-assistant organization, 21 commits to home-assistant")
|
||||
- [Yannic-HAW (@Yannic-HAW)](https://github.com/Yannic-HAW "1 total commits to the home-assistant organization, 1 commit to home-assistant")
|
||||
- [Yannick Simard (@TheRaven)](https://github.com/TheRaven "2 total commits to the home-assistant organization, 2 commits to home-assistant.github.io")
|
||||
- [Yasin Soliman (@yasinS)](https://github.com/yasinS "4 total commits to the home-assistant organization, 4 commits to home-assistant.github.io")
|
||||
@ -773,8 +772,9 @@ 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")
|
||||
- [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 Tuesday, April 18th 2017, 9:17:50 pm UTC.</i>
|
||||
<i>This page was last updated Monday, April 24th 2017, 7:59:09 am UTC.</i>
|
||||
|
||||
81
source/developers/development_guidelines.markdown
Normal file
81
source/developers/development_guidelines.markdown
Normal file
@ -0,0 +1,81 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Style guidelines"
|
||||
description: "Details about styling your code."
|
||||
date: 2017-04-28 20:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Home Assistant enforces strict [PEP8 style](https://www.python.org/dev/peps/pep-0008/) and [PEP 257 (Docstring Conventions)](https://www.python.org/dev/peps/pep-0257/) compliance on all code submitted. We automatically test every pull request as part of the linting process with [Coveralls](https://coveralls.io/github/home-assistant/home-assistant) and [Travis CI](https://travis-ci.org/home-assistant/home-assistant).
|
||||
|
||||
Summary of the most relevant points:
|
||||
|
||||
- Line length is limited to 79 characters (see below).
|
||||
- Use 4 spaces per indentation level. We don't use tabs.
|
||||
- Comments should be full sentences and end with a period.
|
||||
- [Imports](https://www.python.org/dev/peps/pep-0008/#imports) should be ordered.
|
||||
- Constants and the content of lists and directories should be in alphabetical order.
|
||||
- Avoid trailing whitespace but surround binary operators with a single space.
|
||||
- Line separator should be set to `LF`.
|
||||
|
||||
The maximum line length comes directly from the [PEP8 style guide](https://www.python.org/dev/peps/pep-0008/#maximum-line-length), and is also used by the Python standard library. All code must pass these linting checks, and no exceptions will be made. There have already been numerous requests to increase the maximum line length, but after evaluating the options, the Home Assistant maintainers have decided to stay at 79 characters. This decision is final.
|
||||
|
||||
Those points may require that you adjust your IDE or editor settings.
|
||||
|
||||
## {% linkable_title Our recommandations %}
|
||||
|
||||
For some cases [PEPs](https://www.python.org/dev/peps/) don't make a statement. This section covers our recommandations about the code style. Those points were collected from the exisiting code and based on what contributors and developers were using the most. This is basically a majority decision, thus you may not agree with it. But we would like to encourage you follow those recommandations to keep the code unified.
|
||||
|
||||
### {% linkable_title Quotes %}
|
||||
|
||||
Use single quotes `'` for single word and `"` for multiple words or sentences.
|
||||
|
||||
```python
|
||||
ATTR_WATERLEVEL = 'level'
|
||||
CONF_ATTRIBUTION = "Data provided by the WUnderground weather service"
|
||||
SENSOR_TYPES = {
|
||||
'alerts': ['Alerts', None],
|
||||
}
|
||||
```
|
||||
|
||||
### {% linkable_title File headers %}
|
||||
|
||||
The docstring in the file header should contain a link to the documentation to make it easy to find further information, especially about the configuration or details which are not mentioned in the code.
|
||||
|
||||
```python
|
||||
"""
|
||||
Support for MQTT lights.
|
||||
|
||||
For more details about this platform, please refer to the documentation at
|
||||
https://home-assistant.io/components/light.mqtt/
|
||||
"""
|
||||
```
|
||||
|
||||
### {% linkable_title Requirements %}
|
||||
|
||||
Please place [Platform requirements](/developers/code_review_platform/#1-requirements) right after the imports.
|
||||
|
||||
```python
|
||||
[...]
|
||||
from homeassistant.helpers.entity import Entity
|
||||
|
||||
REQUIREMENTS = ['xmltodict==0.11.0']
|
||||
```
|
||||
|
||||
### {% linkable_title Log messages %}
|
||||
|
||||
There is no need to add the platform or component name to the log messages. This will be added automatically. Like `syslog` messages there shouldn't be no period at the end. Try to avoid brackets and additional quotes around the output to make it easier for users to parse the log. A widely style is shown below but you are free to compose the messages as you like.
|
||||
|
||||
```python
|
||||
_LOGGER.error("No route to device: %s", self._resource)
|
||||
```
|
||||
|
||||
```bash
|
||||
2017-05-01 14:28:07 ERROR [homeassistant.components.sensor.arest] No route to device: 192.168.0.18
|
||||
```
|
||||
|
||||
Don't print out wrong API keys, tokens, usernames, or passwords.
|
||||
|
||||
@ -9,11 +9,11 @@ sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Home Assistant enforces strict [PEP8 style](https://www.python.org/dev/peps/pep-0008/) compliance on all code submitted. We automatically test every pull request with [Coveralls](https://coveralls.io/github/home-assistant/home-assistant) and [Travis CI](https://travis-ci.org/home-assistant/home-assistant).
|
||||
As states in the [Style guidelines section](/developers/development_guidelines/) all code is checked as part of the linting process and unit test were run.
|
||||
|
||||
### {% linkable_title Local testing %}
|
||||
|
||||
**Important:** Run tox before you create your pull request to avoid annoying fixes. Local testing requires installing tox.
|
||||
**Important:** Run `tox` before you create your pull request to avoid annoying fixes. Local testing requires installing `tox`.
|
||||
|
||||
```bash
|
||||
$ pip3 install tox
|
||||
@ -63,6 +63,3 @@ The `flake8-docstrings` extension will check docstrings according to [PEP257](ht
|
||||
|
||||
If you can't avoid a PyLint warning, add a comment to disable the PyLint check for that line with `# pylint: disable=YOUR-ERROR-NAME`. An example of an unavoidable PyLint warning is not using the passed-in datetime if you're listening for a time change.
|
||||
|
||||
### {% linkable_title Maximum Line Length %}
|
||||
|
||||
As part of the linting process, all code is checked for a maximum line length of 79 characters. This comes directly from the [PEP8 style guide](https://www.python.org/dev/peps/pep-0008/#maximum-line-length), and is also used by the Python standard library. All code must pass these linting checks, and no exceptions will be made. There have already been numerous requests to increase the maximum line length, but after evaluating the options, the Home Assistant maintainers have decided to stay at 79 characters. This decision is final.
|
||||
|
||||
@ -63,13 +63,14 @@ def setup_platform(hass, config, add_devices, discovery_info=None):
|
||||
|
||||
# Verify that passed in configuration works
|
||||
if not hub.is_valid_login():
|
||||
_LOGGER.error('Could not connect to AwesomeLight hub')
|
||||
_LOGGER.error("Could not connect to AwesomeLight hub")
|
||||
return False
|
||||
|
||||
# Add devices
|
||||
add_devices(AwesomeLight(light) for light in hub.lights())
|
||||
|
||||
|
||||
|
||||
class AwesomeLight(Light):
|
||||
"""Representation of an Awesome Light."""
|
||||
|
||||
@ -87,7 +88,7 @@ class AwesomeLight(Light):
|
||||
|
||||
@property
|
||||
def brightness(self):
|
||||
"""Brightness of the light (an integer in the range 1-255).
|
||||
"""Return the brightness of the light.
|
||||
|
||||
This method is optional. Removing it indicates to Home Assistant
|
||||
that brightness is not supported for this light.
|
||||
|
||||
@ -15,7 +15,7 @@ This is a minimum implementation of a platform for the sensor component.
|
||||
|
||||
Copy the code below and create it as a file in `<config_dir>/custom_components/sensor/example.py`.
|
||||
|
||||
Add the following to your configuration.yaml:
|
||||
Add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
38
source/hassio/architecture.markdown
Normal file
38
source/hassio/architecture.markdown
Normal file
@ -0,0 +1,38 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Hass.io Architecture"
|
||||
description: "The architecture of Hass.io."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
<p class='img'>
|
||||
<a href='/images/hassio/architecture.png'><img src='/images/hassio/architecture.png' alt='Architecture overview of Hass.io'></a>
|
||||
Architecture overview of Hass.io
|
||||
</p>
|
||||
|
||||
### {% linkable_title Host Control (HC) %}
|
||||
|
||||
This is a daemon running on the host machine that allows the supervisor to control certain aspects of the host OS:
|
||||
|
||||
- Power cycle (restart, turn off)
|
||||
- Manage network settings
|
||||
- Local updates
|
||||
|
||||
### {% linkable_title Host %}
|
||||
|
||||
Our pre-build images are based on [ResinOS]. Any Linux machine can be turned into a Hass.io host by running [the installer][linux].
|
||||
|
||||
### {% linkable_title Supervisor %}
|
||||
|
||||
The supervisor offers an API to manage the host and running the Docker containers.
|
||||
|
||||
### {% linkable_title Configuration panel %}
|
||||
|
||||
The configuration panel lives inside the supervisor but is accessible via the Home Assistant user interface. The configuration panel allows the user to manage the installation.
|
||||
|
||||
[ResinOS]: https://resinos.io/
|
||||
[linux]: /hassio/installation/#alternative-install-on-generic-linux-server
|
||||
94
source/hassio/create_hassio_addon.markdown
Normal file
94
source/hassio/create_hassio_addon.markdown
Normal file
@ -0,0 +1,94 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Create an add-on for Hass.io"
|
||||
description: "Steps on how-to create an add-on for Hass.io."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Add-ons are docker container they run a script and do some things. User are able to set a add-on specific options.
|
||||
|
||||
### {% linkable_title Add-on folder %}
|
||||
|
||||
```
|
||||
addon_name:
|
||||
Dockerfile
|
||||
config.json
|
||||
run.sh
|
||||
```
|
||||
|
||||
All add-ons are based on Alpine Linux 3.5. You can use `FROM %%BASE_IMAGE%%` inside your docker file to build the right arch or for automatic build with our scripts.
|
||||
|
||||
Your Docker need also a env variable `VERSION` with the version of the add-on. With our build system include this line:
|
||||
```
|
||||
ENV VERSION %%VERSION%%
|
||||
```
|
||||
|
||||
As a user might run many add-ons, it is encouraged to try to stick to Bash scripts if you're doing simple things.
|
||||
|
||||
### {% linkable_title Add-on config %}
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "xy",
|
||||
"version": "1.2",
|
||||
"slug": "folder",
|
||||
"description": "long descripton",
|
||||
"startup": "before|after|once",
|
||||
"boot": "auto|manual",
|
||||
"ports": {
|
||||
"123/tcp": 123
|
||||
},
|
||||
"map": ["config", "ssl", "addons", "backup"],
|
||||
"options": {},
|
||||
"schema": {},
|
||||
"image": "repo/{arch}-my-custom-addon"
|
||||
}
|
||||
```
|
||||
|
||||
### {% linkable_title Options / Schema %}
|
||||
|
||||
The `options` dict have all available options with default value. If you want to set a value to requered and need to be set from user before it start the addon, set it to null. We support arrays for single deeps.
|
||||
|
||||
```json
|
||||
{
|
||||
"message": "custom things",
|
||||
"logins": [
|
||||
{ "username": "beer", "password": "123456" },
|
||||
{ "username": "cheep", "password": "654321" }
|
||||
],
|
||||
"random": ["haha", "hihi", "huhu", "hghg"],
|
||||
"link": "http://blebla.com/"
|
||||
}
|
||||
```
|
||||
|
||||
The `schmema` look like the `options` but describe how we should validate the user input. For example above:
|
||||
|
||||
```json
|
||||
{
|
||||
"message": "str",
|
||||
"logins": [
|
||||
{ "username": "str", "password": "str" }
|
||||
],
|
||||
"random": ["str"],
|
||||
"link": "url"
|
||||
}
|
||||
```
|
||||
|
||||
We support:
|
||||
- str
|
||||
- bool
|
||||
- int
|
||||
- float
|
||||
- email
|
||||
- url
|
||||
|
||||
### {% linkable_title SSL %}
|
||||
|
||||
Default you can use `fullchain.pem` and `privkey.pem` from `/ssl` for you stuff. Your SSL addon should also create default this files.
|
||||
|
||||
### {% linkable_title Need to know %}
|
||||
`/data` is a volume with a persistant store. `/data/options.json` have the user config inside. You can use `jq` inside shell script to parse this data.
|
||||
24
source/hassio/create_hassio_addon_repository.markdown
Normal file
24
source/hassio/create_hassio_addon_repository.markdown
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Create an add-on repository for Hass.io"
|
||||
description: "Add-ons repositories."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Look to our example [repository](https://github.com/home-assistant/hassio-addons-example).
|
||||
|
||||
Add-ons repository can have multible add-ons with diferents folders or it can be a single add-on. It is importent that you add the json file to root.
|
||||
|
||||
Add a `repository.json` to the root of your git repository with:
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "Needed, Name of repository",
|
||||
"url": "http://www.example/addons",
|
||||
"maintainer": "HomeAssistant Team <info@home-assistant.io>"
|
||||
}
|
||||
```
|
||||
18
source/hassio/development.markdown
Normal file
18
source/hassio/development.markdown
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Hass.io development"
|
||||
description: "How to get started with Hass.io development."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Seen all the Hass.io stuff and want to built on top of it? That's awesome.
|
||||
|
||||
Before you get started with development, get familiar with [the architecture][arch].
|
||||
|
||||
[Placeholder]
|
||||
|
||||
[arch]: /hassio/architecture/
|
||||
12
source/hassio/index.markdown
Normal file
12
source/hassio/index.markdown
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Hass.io"
|
||||
description: "Manage your Home Assistant and custom addons over Samba."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Hass.io turns your Raspberry Pi (or other device) into the ultimate Home Automation hub. It takes away all the hassle of installing Home Assistant and related applications and keeping them up to date. Updates to the operating system, Home Assistant, and any add-ons can be done via the Home Assistant UI with a single click.
|
||||
31
source/hassio/installation.markdown
Normal file
31
source/hassio/installation.markdown
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Installing Hass.io"
|
||||
description: "Instructions on how-to install Hass.io."
|
||||
date: 2017-04-30 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
Hass.io images are available for all available Raspberry Pi platforms. Download the appropriate image for your Raspberry Pi:
|
||||
|
||||
- [Raspberry Pi / Zero][pi1]
|
||||
- [Raspberry Pi 2][pi2]
|
||||
- [Raspberry Pi 3][pi3]
|
||||
|
||||
Flash the downloaded image to an SD card using [Etcher]. Insert SD card to Raspberry Pi and turn it on. You will be able to reach your installation on [http://hassio.local][local].
|
||||
|
||||
On first boot, it downloads the Home Assistant container and that can take some time.
|
||||
|
||||
### {% linkable_title Alternative: install on generic Linux server %}
|
||||
|
||||
For advanced users, it is also possible to try Hass.io on your Linux server or inside a VM. To do so, [follow these instructions][linux].
|
||||
|
||||
[Etcher]: https://etcher.io/
|
||||
[pi1]: https://github.com/home-assistant/hassio-build/releases/download/0.7/resinos-hassio-0.7-raspberrypi.img.bz2
|
||||
[pi2]: https://github.com/home-assistant/hassio-build/releases/download/0.7/resinos-hassio-0.7-raspberrypi2.img.bz2
|
||||
[pi3]: https://github.com/home-assistant/hassio-build/releases/download/0.7/resinos-hassio-0.7-raspberrypi3.img.bz2
|
||||
[linux]: https://github.com/home-assistant/hassio-build/tree/master/install
|
||||
[local]: http://hassio.local:8123
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user