From 33bff220449611674c495235d46895b4a354dc05 Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Tue, 10 Oct 2017 08:57:20 +0200
Subject: [PATCH 01/88] Fix host entry
---
source/_components/device_tracker.owntracks_http.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/device_tracker.owntracks_http.markdown b/source/_components/device_tracker.owntracks_http.markdown
index 830883a8800..0895af69c1d 100644
--- a/source/_components/device_tracker.owntracks_http.markdown
+++ b/source/_components/device_tracker.owntracks_http.markdown
@@ -30,7 +30,7 @@ For configuration options and usage instructions, read the documentation for the
Open OwnTracks and go to Connection preferences:
- Mode: Private HTTP
- - Host: /api/owntracks//
+ - Host: [Home Assistant URL]:[port]/api/owntracks/[your name]/[device name]
- Identification: turn authentication on, username `homeassistant` and password is your API password that you use to login to Home Assistant.
Host example: If I host my Home Assistant at `https://example.duckdns.org`, my name is Paulus and my phone is a Pixel I would set the host to be `https://example.duckdns.org/api/owntracks/paulus/pixel`. This will result in an entity with an ID of `device_tracker.paulus_pixel`. You can pick any name for the user and the device.
From 56b81dc6fbac71f756d107b1fc4a44b4a8a0c6fe Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Tue, 10 Oct 2017 09:07:35 +0200
Subject: [PATCH 02/88] UPdate formatting
---
source/_components/device_tracker.owntracks_http.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_components/device_tracker.owntracks_http.markdown b/source/_components/device_tracker.owntracks_http.markdown
index 0895af69c1d..7e91746e55a 100644
--- a/source/_components/device_tracker.owntracks_http.markdown
+++ b/source/_components/device_tracker.owntracks_http.markdown
@@ -29,8 +29,8 @@ For configuration options and usage instructions, read the documentation for the
Open OwnTracks and go to Connection preferences:
- - Mode: Private HTTP
+ - Mode: Select **Private HTTP**
- Host: [Home Assistant URL]:[port]/api/owntracks/[your name]/[device name]
- - Identification: turn authentication on, username `homeassistant` and password is your API password that you use to login to Home Assistant.
+ - Identification: Turn **Authentication** on, username `homeassistant` and password is your API password that you use to login to Home Assistant.
Host example: If I host my Home Assistant at `https://example.duckdns.org`, my name is Paulus and my phone is a Pixel I would set the host to be `https://example.duckdns.org/api/owntracks/paulus/pixel`. This will result in an entity with an ID of `device_tracker.paulus_pixel`. You can pick any name for the user and the device.
From c9be934028ae9c0386ad733b32c57c6db9148608 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Tue, 10 Oct 2017 10:12:56 +0200
Subject: [PATCH 03/88] Update configurator.markdown
---
source/_addons/configurator.markdown | 4 ----
1 file changed, 4 deletions(-)
diff --git a/source/_addons/configurator.markdown b/source/_addons/configurator.markdown
index f15c9b197ae..f2b2d3df19f 100644
--- a/source/_addons/configurator.markdown
+++ b/source/_addons/configurator.markdown
@@ -39,8 +39,6 @@ Screenshot of the HASS Configurator.
```json
{
- "homeassistant_api": "http://homeassistant:8123/api",
- "homeassistant_password": "",
"username": "admin",
"password": "secret",
"certfile": "fullchain.pem",
@@ -52,8 +50,6 @@ Screenshot of the HASS Configurator.
}
```
-- **homeassistant_api** (*Optional*): The configurator fetches some data from your running Home Assistant instance. If the API is not available through the default URL, modify this variable to fix this.
-- **homeassistant_password** (*Optional*): If you plan on using API functions, you have to set your API password. Calling services of Home Assistant is prohibited without authentication.
- **username** (*Optional*): Set a username to access your configuration is protected.
- **password** (*Required*): Set a password for access.
- **ssl** (*Optional*): Enable or Disable SSL for the editor.
From 38cce60544e25c98184c2185fba17b54e33dfd34 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Tue, 10 Oct 2017 11:32:59 +0200
Subject: [PATCH 04/88] Update duckdns.markdown
---
source/_addons/duckdns.markdown | 3 +++
1 file changed, 3 insertions(+)
diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown
index 07a262fad63..8e89ad9eb59 100644
--- a/source/_addons/duckdns.markdown
+++ b/source/_addons/duckdns.markdown
@@ -37,6 +37,9 @@ Use the following configuration in Home Assistant to use the generated certifica
```yaml
http:
+ base_url: https://my-domain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
```
+
+If you use a other port as `8123` or a SSL proxy, change the port number.
From 5985eeeea982f01a6d149f124d098ae1fab6de5f Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Tue, 10 Oct 2017 11:36:06 +0200
Subject: [PATCH 05/88] Update lets_encrypt.markdown
---
source/_addons/lets_encrypt.markdown | 3 +++
1 file changed, 3 insertions(+)
diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown
index 976fbf43325..98d33c86e03 100644
--- a/source/_addons/lets_encrypt.markdown
+++ b/source/_addons/lets_encrypt.markdown
@@ -36,6 +36,9 @@ Use the following configuration in Home Assistant to use the generated certifica
```yaml
http:
+ base_url: https://my-domain.tld:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
```
+
+If you use a other port as `8123` or a SSL proxy, change the port number.
From 263db7b6e9fa3f50f835f9588f675038d5e367e1 Mon Sep 17 00:00:00 2001
From: DubhAd
Date: Wed, 11 Oct 2017 07:22:47 +0100
Subject: [PATCH 06/88] Update MQTT broker docs for clarity (#3573)
* Update MQTT broker docs for clarity
Adding words to note that the reason a "run your own" broker is the most private is because the embedded broker doesn't support TLS/SSL.
Also updating to use the new configuration tags.
* Update to reference hbmqtt supporting TLS
---
source/_docs/mqtt/broker.markdown | 68 +++++++++++++++++++++++--------
1 file changed, 50 insertions(+), 18 deletions(-)
diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown
index f2a2a90eec1..375639661da 100644
--- a/source/_docs/mqtt/broker.markdown
+++ b/source/_docs/mqtt/broker.markdown
@@ -17,13 +17,13 @@ The MQTT component needs you to run an MQTT broker for Home Assistant to connect
Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the [HBMQTT broker](https://pypi.python.org/pypi/hbmqtt) is started and Home Assistant connects to it. Embedded broker default configuration:
-| Setting | Value |
-| ------- | ----- |
-| Host | localhost
-| Port | 1883
-| Protocol | 3.1.1
-| User | homeassistant
-| Password | Your API [password](/components/http/)
+| Setting | Value |
+| -------------- | ----- |
+| Host | localhost
+| Port | 1883
+| Protocol | 3.1.1
+| User | homeassistant
+| Password | Your API [password](/components/http/)
| Websocket port | 8080
```yaml
@@ -51,7 +51,7 @@ mqtt:
### {% linkable_title Run your own %}
-This is the most private option but requires a bit more work. There are multiple free and open-source brokers to pick from: eg. [Mosquitto](http://mosquitto.org/), [EMQ](http://emqtt.io/), or [Mosca](http://www.mosca.io/).
+Along with the embedded broker this is the most private option, but it requires a bit more work. There are multiple free and open-source brokers to pick from: eg. [Mosquitto](http://mosquitto.org/), [EMQ](http://emqtt.io/), or [Mosca](http://www.mosca.io/).
```yaml
# Example configuration.yaml entry
@@ -61,16 +61,48 @@ mqtt:
Configuration variables:
-- **broker** (*Optional*): The IP address or hostname of your MQTT broker, e.g. 192.168.1.32.
-- **port** (*Optional*): The network port to connect to. Default is 1883.
-- **client_id** (*Optional*): The client ID that Home Assistant will use. Has to be unique on the server. Default is a randomly generated one.
-- **keepalive** (*Optional*): The time in seconds between sending keep alive messages for this client. Default is 60.
-- **username** (*Optional*): The username to use with your MQTT broker.
-- **password** (*Optional*): The corresponding password for the username to use with your MQTT broker.
-- **protocol** (*Optional*): Protocol to use: 3.1 or 3.1.1. By default it connects with 3.1.1 and falls back to 3.1 if server does not support 3.1.1.
-- **certificate** (*Optional*): Path to the certificate file, eg. `/home/user/.homeassistant/server.crt`.
-- **tls_insecure** (*Optional*): Set the verification of the server hostname in the server certificate.
-- **tls_version** (*Optional*): TLS/SSL protocol version to use. Available options are: `auto`, `1.0`, `1.1`, `1.2`. Defaults to `auto`.
+{% configuration %}
+broker:
+ required: false
+ description: The IP address or hostname of your MQTT broker, e.g. 192.168.1.32.
+ type: string
+port:
+ required: false
+ description: The network port to connect to. Default is 1883.
+ type: int
+client_id:
+ required: false
+ description: The client ID that Home Assistant will use. Has to be unique on the server. Default is a randomly generated one.
+ type: string
+keepalive:
+ required: false
+ description: The time in seconds between sending keep alive messages for this client. Default is 60.
+ type: int
+username:
+ required: false
+ description: The username to use with your MQTT broker.
+ type: string
+password:
+ required: false
+ description: The corresponding password for the username to use with your MQTT broker.
+ type: string
+protocol:
+ required: false
+ description: Protocol to use: 3.1 or 3.1.1. By default it connects with 3.1.1 and falls back to 3.1 if server does not support 3.1.1.
+ type: string
+certificate:
+ required: false
+ description: Path to the certificate file, eg. `/home/user/.homeassistant/server.crt`.
+ type: string
+tls_insecure:
+ required: false
+ description: Set the verification of the server hostname in the server certificate.
+ type: boolean
+tls_version:
+ required: false
+ description: TLS/SSL protocol version to use. Available options are: `auto`, `1.0`, `1.1`, `1.2`. Defaults to `auto`.
+ type: string
+{% endconfiguration %}
There is an issue with the Mosquitto package included in Ubuntu 14.04 LTS. Specify `protocol: 3.1` in your MQTT configuration to work around this issue.
From d116c65d9eacaf6ca852247fc18c3b946a7ea4f0 Mon Sep 17 00:00:00 2001
From: jodur
Date: Wed, 11 Oct 2017 08:30:32 +0200
Subject: [PATCH 07/88] Update fail2ban.markdown (#3503)
Please update this reference according to the last additions made in the original topic :https://community.home-assistant.io/t/is-there-a-log-file-for-invalid-logins-blocking-hackers/2892/16
---
source/_cookbook/fail2ban.markdown | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/source/_cookbook/fail2ban.markdown b/source/_cookbook/fail2ban.markdown
index 8eed73efb0c..505fad6272d 100644
--- a/source/_cookbook/fail2ban.markdown
+++ b/source/_cookbook/fail2ban.markdown
@@ -20,7 +20,7 @@ Then make sure logging is enabled in your `configuration.yaml` file for your Hom
logger:
default: critical
logs:
- homeassistant.components.http: warning
+ homeassistant.components.http.ban: warning
```
Next we will be creating these three files :
@@ -43,12 +43,9 @@ Contents of `/etc/fail2ban/filter.d/hass.local`:
before = common.conf
[Definition]
-failregex = ^%(__prefix_line)s.*Login attempt or request with an invalid password from .*$
+failregex = ^%(__prefix_line)s.*Login attempt or request with invalid authentication from .*$
ignoreregex =
-
-[Init]
-datepattern = ^%%y-%%m-%%d %%H:%%M:%%S
```
Contents of `/etc/fail2ban/jail.local` (Note that you'll need to change the `logpath` to match your logfile which will be different from the path listed.):
@@ -58,7 +55,7 @@ Contents of `/etc/fail2ban/jail.local` (Note that you'll need to change the `log
enabled = true
filter = hass
action = iptables-allports[name=HASS]
-logpath = /opt/hass-prod-cfg/home-assistant.log
+logpath = /home/homeassistant/.homeassistant/home-assistant.log
maxretry = 5
```
From c12a98692def95d128d13f0ed59634475dc12ce4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20H=C3=B8yer=20Iversen?=
Date: Wed, 11 Oct 2017 09:06:44 +0200
Subject: [PATCH 08/88] Update xiaomi_aqara.markdown
---
source/_components/xiaomi_aqara.markdown | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/source/_components/xiaomi_aqara.markdown b/source/_components/xiaomi_aqara.markdown
index 37919505bb2..b9c9392b79d 100644
--- a/source/_components/xiaomi_aqara.markdown
+++ b/source/_components/xiaomi_aqara.markdown
@@ -88,12 +88,12 @@ xiaomi_aqara:
{% configuration %}
mac:
- description: The MAC of your gateway. *Optional if only using one gateway.*
- required: true
+ description: The MAC address of your gateway. *Optional if only using one gateway.*
+ required: false
type: string
key:
description: The key of your gateway. *Optional if only using sensors and/or binary sensors.*
- required: true
+ required: false
type: string
discovery_retry:
description: Number of times that Home Assistant should try to reconnect to the gateway.
@@ -105,6 +105,10 @@ xiaomi_aqara:
required: false
type: string
default: any
+ host:
+ description: The host / ip address of the gateway. If this parameter is used the multicast discovery of the gateway is skipped.
+ required: false
+ type: string
{% endconfiguration %}
### {% linkable_title Services %}
From 9c25564272dff1ce45aa1df9870a24ff54607c12 Mon Sep 17 00:00:00 2001
From: Tsvi Mostovicz
Date: Wed, 11 Oct 2017 13:03:36 +0300
Subject: [PATCH 09/88] device_tracker.mqtt configuration.yaml is wrong (#3583)
The topic to be looked up must be in quotes for the example to work.
---
source/_components/device_tracker.mqtt.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_components/device_tracker.mqtt.markdown b/source/_components/device_tracker.mqtt.markdown
index 2b1bd0d519a..d60b895c50e 100644
--- a/source/_components/device_tracker.mqtt.markdown
+++ b/source/_components/device_tracker.mqtt.markdown
@@ -22,8 +22,8 @@ To use this device tracker in your installation, add the following to your `conf
device_tracker:
- platform: mqtt
devices:
- paulus_oneplus: /location/paulus
- annetherese_n4: /location/annetherese
+ paulus_oneplus: 'location/paulus'
+ annetherese_n4: 'location/annetherese'
```
Configuration variables:
From 82abe839deed97665f4db2694e59c906f1a61dde Mon Sep 17 00:00:00 2001
From: Albatross
Date: Wed, 11 Oct 2017 06:52:45 -0400
Subject: [PATCH 10/88] Typo Fix: Alexa Documentation (#3582)
---
source/_components/alexa.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/alexa.markdown b/source/_components/alexa.markdown
index d97bf68ae1b..179fb4076c1 100644
--- a/source/_components/alexa.markdown
+++ b/source/_components/alexa.markdown
@@ -101,7 +101,7 @@ This means that we can now ask Alexa things like:
When activated, the Alexa component will have Home Assistant's native intent support handle the incoming intents. If you want to run actions based on intents, use the [`intent_script`](/components/intent_script) component.
-To enable Alex add the following entry to your `configuration.yaml` file:
+To enable Alexa add the following entry to your `configuration.yaml` file:
```yaml
alexa:
From e958de8474c7294afdf625b091d66289d2c55bc5 Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Wed, 11 Oct 2017 12:52:01 +0200
Subject: [PATCH 11/88] Fix Liquid error introduced with #3573
---
source/_docs/mqtt/broker.markdown | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown
index 375639661da..a5f9e9ba70c 100644
--- a/source/_docs/mqtt/broker.markdown
+++ b/source/_docs/mqtt/broker.markdown
@@ -19,12 +19,13 @@ Home Assistant contains an embedded MQTT broker. If no broker configuration is g
| Setting | Value |
| -------------- | ----- |
-| Host | localhost
-| Port | 1883
-| Protocol | 3.1.1
-| User | homeassistant
-| Password | Your API [password](/components/http/)
-| Websocket port | 8080
+| Host | localhost |
+| Port | 1883 |
+| Protocol | 3.1.1 |
+| User | homeassistant |
+| Password | Your API [password](/components/http/) |
+| Websocket port | 8080 |
+
```yaml
# Example configuration.yaml entry
@@ -59,8 +60,6 @@ mqtt:
broker: 192.168.1.100
```
-Configuration variables:
-
{% configuration %}
broker:
required: false
@@ -88,7 +87,7 @@ password:
type: string
protocol:
required: false
- description: Protocol to use: 3.1 or 3.1.1. By default it connects with 3.1.1 and falls back to 3.1 if server does not support 3.1.1.
+ description: "Protocol to use: 3.1 or 3.1.1. By default it connects with 3.1.1 and falls back to 3.1 if server does not support 3.1.1."
type: string
certificate:
required: false
@@ -100,7 +99,7 @@ tls_insecure:
type: boolean
tls_version:
required: false
- description: TLS/SSL protocol version to use. Available options are: `auto`, `1.0`, `1.1`, `1.2`. Defaults to `auto`.
+ description: "TLS/SSL protocol version to use. Available options are: `auto`, `1.0`, `1.1`, `1.2`. Defaults to `auto`."
type: string
{% endconfiguration %}
From 259bdf81a5bb172e4a9d75ad17cf255d90afbc19 Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Thu, 12 Oct 2017 10:59:22 +0200
Subject: [PATCH 12/88] Update file name
---
source/_docs/ecosystem/tor.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/ecosystem/tor.markdown b/source/_docs/ecosystem/tor.markdown
index c5fd98dc0eb..6d87b5f08b4 100644
--- a/source/_docs/ecosystem/tor.markdown
+++ b/source/_docs/ecosystem/tor.markdown
@@ -88,7 +88,7 @@ Add the authentication cookie to your `torrc` client configuration on your lapto
HidServAuth abcdef1234567890.onion ABCDEF1122334455667789
```
-For Tor Browser on Windows, Mac or Linux, you can find the torrc file here: `/Browser/TorBrowser/Data/Tor/torrc-defaults`
+For Tor Browser on Windows, Mac or Linux, you can find the torrc file here: `/Browser/TorBrowser/Data/Tor/torrc`
Once you have added the entry, restart the browser, and then browse to the "dot onion" site address to connect to your Home Assistant instance.
From 77cd72f8c3b1eef58cbddcb3b999d4b1e01368e8 Mon Sep 17 00:00:00 2001
From: dnaphreak
Date: Thu, 12 Oct 2017 11:23:21 -0400
Subject: [PATCH 13/88] minor change to make instructions clear (#3590)
* minor change to make instructions clear
change to make it clear there are two ways to install pyvizio rather than two steps.
* Add blank lines before code
---
source/_components/media_player.vizio.markdown | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/source/_components/media_player.vizio.markdown b/source/_components/media_player.vizio.markdown
index 989d37113d7..ae68385e13a 100644
--- a/source/_components/media_player.vizio.markdown
+++ b/source/_components/media_player.vizio.markdown
@@ -20,10 +20,15 @@ The `vizio` component will allow you to control [SmartCast](https://www.vizio.co
Before adding your TV to Home Assistant you'll need to pair it manually. To do so follow these steps:
-Install the command-line tool using pip (or you can choose to download it manually):
+Install the command-line tool using `pip` (or you can choose to download it manually):
```bash
$ pip3 install git+https://github.com/vkorn/pyvizio.git@master
+```
+
+or
+
+```bash
$ pip3 install -I .
```
From 3b54d869ba45391be8f37dc8b7fdaa9803fd81bb Mon Sep 17 00:00:00 2001
From: Phil Hawthorne
Date: Fri, 13 Oct 2017 02:24:33 +1100
Subject: [PATCH 14/88] Update 055 breaking changes for recorder (#3591)
The recorder component introduces some breaking changes. Expanding those
in the breaking changes section so people don't get caught out
---
source/_posts/2017-10-07-release-55.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_posts/2017-10-07-release-55.markdown b/source/_posts/2017-10-07-release-55.markdown
index d571aa158fc..125d88345b6 100644
--- a/source/_posts/2017-10-07-release-55.markdown
+++ b/source/_posts/2017-10-07-release-55.markdown
@@ -58,7 +58,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by "_" and no longer " ". ([@w1ll1am23] - [#9303]) ([wink docs]) ([binary_sensor.wink docs]) ([lock.wink docs]) (breaking change)
- TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. ([@djchen] - [#9607]) ([switch.tplink docs]) (breaking change)
- Renamed `input_slider` to `input_number` which has now a numeric text box option. ([@BioSehnsucht] - [#9494]) ([demo docs]) ([input_number docs]) (breaking change)
-- Recorder: Add new purge service and interval. ([@milanvo] - [#9523]) ([recorder docs]) (breaking change)
+- Recorder: Add new purge service and interval. The recorder component no longer accepts a `purge_days` parameter. If you are using `purge_days` you must use `purge_interval` and `purge_keep_days`. ([@milanvo] - [#9523]) ([recorder docs]) (breaking change)
- OpenCV image processing: Typo in classifier was fixed. ([@arsaboo] - [#9697]) ([image_processing.opencv docs]) (breaking change)
- Tradfri Lights: Async support with resource observation. ([@lwis] - [#7815]) ([tradfri docs]) ([light.tradfri docs]) (breaking change)
From 37a7104d7d4e604b4c3f0c5724e1baf2a2989a2f Mon Sep 17 00:00:00 2001
From: c727
Date: Thu, 12 Oct 2017 17:25:09 +0200
Subject: [PATCH 15/88] fix example for custom state cards (#3592)
* change to state-card-my-custom-light
* .html
---
.../developers/frontend_creating_custom_ui.markdown | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/source/developers/frontend_creating_custom_ui.markdown b/source/developers/frontend_creating_custom_ui.markdown
index 8303acbbb1b..51678f01cbb 100644
--- a/source/developers/frontend_creating_custom_ui.markdown
+++ b/source/developers/frontend_creating_custom_ui.markdown
@@ -13,15 +13,15 @@ If you would like to use your own [State card](/developers/frontend_add_card/) w
Put the element source file and its dependencies in `www/custom_ui/` directory under your Home Assistant [configuration](/docs/configuration/) directory.
-For example if creating a state card for the `light` domain named `my_custom_light_card` put `my_custom_light_card.html` in `www/custom_ui/`.
+For example if creating a state card for the `light` domain named `state-card-my-custom-light` put `state-card-my-custom-light.html` in `www/custom_ui/`.
-That file should implement `` tag with Polymer.
+That file should implement `` tag with Polymer.
-In `my_custom_light_card.html` you should use `` to import all the dependencies **not** used by Home Assistant's UI.
+In `state-card-my-custom-light.html` you should use `` to import all the dependencies **not** used by Home Assistant's UI.
Do not import any dependencies used by the Home Assistant UI.
Importing those will work in `development: 1` mode, but will fail in production mode.
-1) In the `customize:` section of the `configuration.yaml` file put `custom_ui_state_card: `.
+1) In the `customize:` section of the `configuration.yaml` file put `custom_ui_state_card: state-card-my-custom-light`.
2) In the `frontend` section use `extra_html_url` to specify the URL to load.
For example:
@@ -29,11 +29,11 @@ For example:
homeassistant:
customize:
light.bedroom:
- custom_ui_state_card: my_custom_light_card
+ custom_ui_state_card: state-card-my-custom-light
frontend:
extra_html_url:
- - /local/custom_ui/my_custom_light_card.html
+ - /local/custom_ui/state-card-my-custom-light.html
```
For more possibilities, see the [Custom UI section](/cookbook/#user-interface) on our Examples page.
From 1841de73055b42e255420dbf7f38f5b8d3a9fa48 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Thu, 12 Oct 2017 22:50:42 +0200
Subject: [PATCH 16/88] Create cec_scan.markdown
---
source/_addons/cec_scan.markdown | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100644 source/_addons/cec_scan.markdown
diff --git a/source/_addons/cec_scan.markdown b/source/_addons/cec_scan.markdown
new file mode 100644
index 00000000000..4c048eff157
--- /dev/null
+++ b/source/_addons/cec_scan.markdown
@@ -0,0 +1,12 @@
+---
+layout: page
+title: "CEC Scanner"
+description: "Scan HDMI CEC devices."
+date: 2017-04-30 13:28
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+Help you to discover the HDMI CEC address. Start the add-on and look into log to see all connected device on HDMI.
From d504c806abe6e67b77e126c53417fd38e0b10688 Mon Sep 17 00:00:00 2001
From: Andrey
Date: Fri, 13 Oct 2017 08:42:12 +0300
Subject: [PATCH 17/88] Update custom_ui_by_andrey-git.markdown
---
source/_cookbook/custom_ui_by_andrey-git.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_cookbook/custom_ui_by_andrey-git.markdown b/source/_cookbook/custom_ui_by_andrey-git.markdown
index cea9eeae1a2..5b593d3250c 100644
--- a/source/_cookbook/custom_ui_by_andrey-git.markdown
+++ b/source/_cookbook/custom_ui_by_andrey-git.markdown
@@ -1,6 +1,6 @@
---
layout: page
-title: "Custom UI light state-card by andrey-git"
+title: "Custom UI state-card by andrey-git"
description: ""
date: 2017-02-04 10:45
sidebar: true
From 76846e0869567363059ad245cf835fc179928356 Mon Sep 17 00:00:00 2001
From: james-fry
Date: Fri, 13 Oct 2017 09:46:46 +0100
Subject: [PATCH 18/88] Update xiaomi_aqara.markdown
Added mention of multicast requirement
---
source/_components/xiaomi_aqara.markdown | 1 +
1 file changed, 1 insertion(+)
diff --git a/source/_components/xiaomi_aqara.markdown b/source/_components/xiaomi_aqara.markdown
index b9c9392b79d..dcfad4c8041 100644
--- a/source/_components/xiaomi_aqara.markdown
+++ b/source/_components/xiaomi_aqara.markdown
@@ -168,6 +168,7 @@ and stops the sound when the button is pressed once.
That means that Home Assistant is not getting any response from your Xiaomi gateway. Might be a local network problem or your firewall.
- Make sure you have [enabled LAN access](https://community.home-assistant.io/t/beta-xiaomi-gateway-integration/8213/1832).
- Turn off the firewall on the system where Home Assistant is running.
+- Ensure your router supports multicast as this is a requirement of the Xiaomi GW
- Try to leave the MAC address `mac:` blank.
- Try to set `discovery_retry: 10`.
- Try to disable and then enable LAN access.
From 319d6623e625a0d9474a667dd6346914159c03a1 Mon Sep 17 00:00:00 2001
From: Eleftherios Chamakiotis
Date: Fri, 13 Oct 2017 13:12:32 +0300
Subject: [PATCH 19/88] Update alarmdecoder.markdown (#3603)
Corrected configuration variable baud, as the schema expects 'baudrate' instead of 'baud'
---
source/_components/alarmdecoder.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/alarmdecoder.markdown b/source/_components/alarmdecoder.markdown
index b3b54f2959f..82beb4b5e62 100644
--- a/source/_components/alarmdecoder.markdown
+++ b/source/_components/alarmdecoder.markdown
@@ -50,6 +50,6 @@ Configuration variables:
- **host** (*Optional*): The IP address of the AlarmDecoder device on your home network, if using socket type. Default: `localhost`
- **port** (*Optional*): The port of the AlarmDecoder device on your home network, if using socket type. Default: `10000`
- **path** (*Optional*): The path of the AlarmDecoder device, if using socket type. Default: `/dev/ttyUSB0`
-- **baud** (*Optional*): The baud rate of the AlarmDecoder device, if using serial type. Default: `115200`
+- **baudrate** (*Optional*): The baud rate of the AlarmDecoder device, if using serial type. Default: `115200`
- **panel_display** (*Optional*): Create a sensor called sensor.alarm_display to match the Alarm Keypad display. Default: `off`
- **zones** (*Optional*): AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*
From 989c5b5e06c2ea3001ba292f0b8c1a3813d5dec9 Mon Sep 17 00:00:00 2001
From: Johan van der Kuijl
Date: Fri, 13 Oct 2017 12:13:16 +0200
Subject: [PATCH 20/88] Small typo fix (#3602)
callack => callback
---
source/_docs/ecosystem/appdaemon.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown
index 1ee29133933..f8f86bdff42 100755
--- a/source/_docs/ecosystem/appdaemon.markdown
+++ b/source/_docs/ecosystem/appdaemon.markdown
@@ -55,7 +55,7 @@ This is also fairly easy to achieve with Home Assistant automations, but we are
## Motion Light
-Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changes where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callack function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
+Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changes where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callback function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
```python
import homeassistant.appapi as appapi
From 4f7dd6b40020c53565c38c7455844873ca776eb8 Mon Sep 17 00:00:00 2001
From: Charles Garwood
Date: Fri, 13 Oct 2017 06:18:23 -0400
Subject: [PATCH 21/88] Update config panel docs (#3493)
Removed information on groups panel as it's disabled. Added information on new panels that have been added.
---
source/_components/config.markdown | 27 ++++++++++++++++-----------
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/source/_components/config.markdown b/source/_components/config.markdown
index 7490d3e4064..514840e7f73 100644
--- a/source/_components/config.markdown
+++ b/source/_components/config.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Config"
-description: "Instructions how to setup the configuration panel Home Assistant."
+description: "Instructions how to setup the configuration panel for Home Assistant."
date: 2017-02-24 20:00
sidebar: true
comments: false
@@ -21,16 +21,7 @@ To enable the configuration panel, add the following to your `configuration.yaml
config:
```
-### {% linkable_title Group & Views %}
-
-The **Groups & Views** sections allows you to re-arrange your [groups](/components/group/). Also, you can edit the group's setting and switch between "view" and "group".
-
-
-
-
-
-
-### {% linkable_title Server Management %}
+### {% linkable_title General %}
This section enables you to control Home Assistant from within Home Assistant. Check your configuration, reload the core, groups, and automation, and the Home Assistant process itself. With a single mouse click.
@@ -38,4 +29,18 @@ This section enables you to control Home Assistant from within Home Assistant. C
+### {% linkable_title Customization %}
+This section enables you to customize entities within Home Assistant. Use this to set friendly names, change icons, hide entities, and modify other attributes.
+
+### {% linkable_title Automation %}
+
+This section enables you to create and modify automations from within Home Assistant, without needing to write out the yaml code.
+
+### {% linkable_title Script %}
+
+Similar to the automation editor, this section enables you to create and modify scripts from within Home Assistant, without needing to write out the yaml code.
+
+### {% linkable_title Z-Wave %}
+
+This section enables you to control your Z-Wave network and devices from within Home Assistant. You can add and remove devices, as well as change device specific configuration variables.
From 7f5be9a0b296f6c677e98927d85cc64331e99790 Mon Sep 17 00:00:00 2001
From: Phill Price
Date: Fri, 13 Oct 2017 11:19:57 +0100
Subject: [PATCH 22/88] Add Hass.io log location (#3599)
To aid debugging Hass.io logs
---
source/_components/logger.markdown | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/source/_components/logger.markdown b/source/_components/logger.markdown
index e04e44511b0..70168cf440b 100644
--- a/source/_components/logger.markdown
+++ b/source/_components/logger.markdown
@@ -68,8 +68,16 @@ data:
homeassistant.components.media_player.yamaha: debug
```
-The log information are stored in the [configuration directory](/docs/configuration/) as `home-assistant.log` and you can read it with the command-line tool `cat` or follow it dynamically with `tail -f`. If you are a Hassbian user you can use the example below:
+The log information are stored in the [configuration directory](/docs/configuration/) as `home-assistant.log` and you can read it with the command-line tool `cat` or follow it dynamically with `tail -f`.
+
+If you are a Hassbian user you can use the example below:
```bash
$ tail -f /home/homeassistant/.homeassistant/home-assistant.log
```
+
+If you are a Hass.io user you can use the example below, whenlogged in through the ssh addon:
+
+```bash
+$ tail -f /config/home-assistant.log
+```
From 718d3ffce5302f3c47744c3c4f0a072c24fc1f91 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Fri, 13 Oct 2017 14:16:52 +0200
Subject: [PATCH 23/88] Update mosquitto.markdown
---
source/_addons/mosquitto.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown
index ad2fef0f620..7db04f10c51 100644
--- a/source/_addons/mosquitto.markdown
+++ b/source/_addons/mosquitto.markdown
@@ -46,5 +46,5 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own) add the follow
```yaml
# Example configuration.yaml entry
mqtt:
- broker: 172.17.0.1
+ broker: core-mqtt
```
From c86f7cb361f7ac8761a4cdd7f75045cb6425474b Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Fri, 13 Oct 2017 22:08:44 +0200
Subject: [PATCH 24/88] Update mosquitto.markdown
---
source/_addons/mosquitto.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown
index 7db04f10c51..f944dc7989c 100644
--- a/source/_addons/mosquitto.markdown
+++ b/source/_addons/mosquitto.markdown
@@ -46,5 +46,5 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own) add the follow
```yaml
# Example configuration.yaml entry
mqtt:
- broker: core-mqtt
+ broker: core-mosquitto
```
From b5716c5afab7a9d8be48b6f465bcc5f4811939e5 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Sat, 14 Oct 2017 00:39:39 +0200
Subject: [PATCH 25/88] Update addon_config.markdown
---
source/developers/hassio/addon_config.markdown | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/source/developers/hassio/addon_config.markdown b/source/developers/hassio/addon_config.markdown
index 2ba863e77b6..13909e7bbd6 100644
--- a/source/developers/hassio/addon_config.markdown
+++ b/source/developers/hassio/addon_config.markdown
@@ -131,7 +131,7 @@ The config for an add-on is stored in `config.json`.
### {% linkable_title Options / Schema %}
-The `options` dictionary contains all available options and their default value. Set the default value to `null` if the value is required to be given by the user before the add-on can start. Only non-nested arrays and dictionaries are supported.
+The `options` dictionary contains all available options and their default value. Set the default value to `null` if the value is required to be given by the user before the add-on can start. Only nested arrays and dictionaries are supported with a deep of two size. If you want make a option optional, put `?` to the end of data type.
```json
{
@@ -158,7 +158,8 @@ The `schema` looks like `options` but describes how we should validate the user
"random": ["match(^\w*$)"],
"link": "url",
"size": "int(5,20)",
- "count": "float"
+ "count": "float",
+ "not_need": "str?"
}
```
From 4160e39ac49e2f29c19fb566c68e83f77b852b70 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Sat, 14 Oct 2017 00:40:56 +0200
Subject: [PATCH 26/88] Update addon_config.markdown
---
source/developers/hassio/addon_config.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/developers/hassio/addon_config.markdown b/source/developers/hassio/addon_config.markdown
index 13909e7bbd6..7ce40cd18bd 100644
--- a/source/developers/hassio/addon_config.markdown
+++ b/source/developers/hassio/addon_config.markdown
@@ -131,7 +131,7 @@ The config for an add-on is stored in `config.json`.
### {% linkable_title Options / Schema %}
-The `options` dictionary contains all available options and their default value. Set the default value to `null` if the value is required to be given by the user before the add-on can start. Only nested arrays and dictionaries are supported with a deep of two size. If you want make a option optional, put `?` to the end of data type.
+The `options` dictionary contains all available options and their default value. Set the default value to `null` if the value is required to be given by the user before the add-on can start, and it show it inside default values. Only nested arrays and dictionaries are supported with a deep of two size. If you want make a option optional, put `?` to the end of data type, otherwise it will be a required value.
```json
{
From a01c713fd4c16388061ec0206d13e143065e19db Mon Sep 17 00:00:00 2001
From: Mitchell Cash
Date: Sat, 14 Oct 2017 14:49:16 +1000
Subject: [PATCH 27/88] Add Groups definition to glossary (#3616)
---
source/_data/glossary.yml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml
index a0edf13014e..39245d7ef25 100644
--- a/source/_data/glossary.yml
+++ b/source/_data/glossary.yml
@@ -14,4 +14,5 @@
description: "Often used abbreviation for Home Assistant."
- topic: Discovery
description: The automatic setup of zeroconf/mDNS and uPnP devices after they are discovered.
-
+- topic: Groups
+ description: "Groups are a way to organize your entities into a group."
From 5605937729243b5f64a0bde124f9fb20f590d837 Mon Sep 17 00:00:00 2001
From: Sebastian Muszynski
Date: Sat, 14 Oct 2017 06:50:51 +0200
Subject: [PATCH 28/88] Xiaomi light description updated. (#3607)
---
source/_components/light.xiaomi_aqara.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/light.xiaomi_aqara.markdown b/source/_components/light.xiaomi_aqara.markdown
index 561cf132c29..25e01ba22c7 100644
--- a/source/_components/light.xiaomi_aqara.markdown
+++ b/source/_components/light.xiaomi_aqara.markdown
@@ -14,7 +14,7 @@ ha_iot_class: "Local Push"
---
-The `xiaomi aqara` light platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) lights.
+The `xiaomi aqara` light platform allows you to control the internal light of the xiaomi gateway. The component will be loaded automatically and provides a device called `light.gateway_light_28ffffffffff`.
The requirement is that you have setup [Xiaomi aqara](/components/xiaomi_aqara/).
From 16d109f9d2ca8a71b9729b1b86e3a34453d05a55 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Fri, 13 Oct 2017 23:40:08 -0700
Subject: [PATCH 29/88] Update lets_encrypt.markdown
---
source/_addons/lets_encrypt.markdown | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown
index 98d33c86e03..31fdd13f3b8 100644
--- a/source/_addons/lets_encrypt.markdown
+++ b/source/_addons/lets_encrypt.markdown
@@ -7,13 +7,17 @@ sidebar: true
comments: false
sharing: true
footer: true
-featured: true
+featured: false
---
+
+You should not use this if you are also using the [DuckDNS add-on]. The DuckDNS add-on has integrated Let's Encrypt support.
+
+
Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration.
-This add-on need port 80/443 to verify the certificate request, please stop all add-ons that also use these ports, or you may not be able to start this add-on.
+This add-on uses ports 80/443 to verify the certificate request. You will need to stop all other add-ons that also use these ports.
```json
@@ -42,3 +46,5 @@ http:
```
If you use a other port as `8123` or a SSL proxy, change the port number.
+
+[DuckDNS add-on]: /addons/duckdns/
From 7a8bbdc99a406074dfd84b9fafabdc32b95fd9e0 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Fri, 13 Oct 2017 23:41:13 -0700
Subject: [PATCH 30/88] Update duckdns.markdown
---
source/_addons/duckdns.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown
index 8e89ad9eb59..9667c91e725 100644
--- a/source/_addons/duckdns.markdown
+++ b/source/_addons/duckdns.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "DuckDNS"
-description: "Automatically update your Duck DNS IP address."
+description: "Automatically update your Duck DNS IP address with integrated HTTPS support via Let's Encrypt."
date: 2017-04-30 13:28
sidebar: true
comments: false
From e9bfa54ee285279a9e5cb438c31213c6171daaff Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen
Date: Sat, 14 Oct 2017 00:18:27 -0700
Subject: [PATCH 31/88] Update lets_encrypt.markdown
---
source/_docs/ecosystem/certificates/lets_encrypt.markdown | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
index c248bec61d7..ad7963fae69 100644
--- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown
+++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
@@ -9,6 +9,10 @@ sharing: true
footer: true
---
+
+If you are using Hass.io, do not use this guide. Instead, use the [DuckDNS add-on](/addons/duckdns/) to automatically maintain a subdomain including HTTPS certificates via Let's Encrypt.
+
+
Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](https://home-assistant.io/docs/configuration/basic/) page.
From 5137e06f3d885538ddcf583fb39bf2482f5289c0 Mon Sep 17 00:00:00 2001
From: Fredrik Fjeld
Date: Sat, 14 Oct 2017 14:54:22 +0200
Subject: [PATCH 32/88] Added quote marks around target phone number. (#3618)
The notification will not work if the target phone number is not quoted.
---
source/_components/notify.facebook.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_components/notify.facebook.markdown b/source/_components/notify.facebook.markdown
index 1d76436a13e..209fe6c827d 100644
--- a/source/_components/notify.facebook.markdown
+++ b/source/_components/notify.facebook.markdown
@@ -46,8 +46,8 @@ automation:
data:
message: 'Good Evening'
target:
- - +919413017584
- - +919784516314
+ - '+919413017584'
+ - '+919784516314'
```
You can also send messages to users that do not have stored their phone number with Facebook, but this requires a bit more work. The Messenger platform uses page specific user IDs instead of a global user ID. You will need to enable a webhook for the "messages" event in Facebook's developer console. Once a user writes a message to a page, that webhook will then receive the user's page specifc ID as part of the webhook's payload. Below is a simple PHP script that reacts to the message "get my id" and sends a reply containing the user's ID:
From 30c4700c301d4fa6a4c8c0ad990ab9b741d8dfb6 Mon Sep 17 00:00:00 2001
From: Max Rumpf
Date: Sat, 14 Oct 2017 17:28:42 +0200
Subject: [PATCH 33/88] Decrease size of search bar and remove outline (#3611)
This ensures that the close button stays in the first line, and doesn't get pushed below the search icon.
---
sass/custom/_paulus.scss | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss
index 9e7e2c3cac7..d1345929eea 100644
--- a/sass/custom/_paulus.scss
+++ b/sass/custom/_paulus.scss
@@ -23,13 +23,14 @@ $primary-color: #049cdb;
float: right;
.algolia-autocomplete {
- width: calc(100% - 58px);
+ width: calc(100% - 64px);
margin: 0 10px;
}
input {
border: 0;
width: 100%;
+ outline: none;
}
}
}
From b4a92c15ec59054d722dd8c075ce623b487f7e7e Mon Sep 17 00:00:00 2001
From: Boced66
Date: Sat, 14 Oct 2017 17:42:40 +0200
Subject: [PATCH 34/88] Device tracker GpsLogger : Change the device name
(#3606)
Explain how to change the device name in the URL
---
source/_components/device_tracker.gpslogger.markdown | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/source/_components/device_tracker.gpslogger.markdown b/source/_components/device_tracker.gpslogger.markdown
index d0f92db962b..9259d8f702c 100644
--- a/source/_components/device_tracker.gpslogger.markdown
+++ b/source/_components/device_tracker.gpslogger.markdown
@@ -29,7 +29,9 @@ To configure GPSLogger, you must set up the app to send a `GET` request to your
```yaml
http:///api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT
```
-. Make sure to include the API password if you have configured a password in Home Assistant (add `&api_password=` to the end of the URL). Configure that options under "General Options":
+Make sure to include the API password if you have configured a password in Home Assistant (add `&api_password=` to the end of the URL).
+You can change your device name by editing "%SER" in this URL (e.g.: &device=user_devicename)
+Configure that options under "General Options":
- Start on boot: yes
- Start on app launch: yes
@@ -43,6 +45,7 @@ Set the URL under "General Options -> Logging details":
http:///api/gpslogger?latitude=%LAT&longitude=%LON&device=%SER&accuracy=%ACC&battery=%BATT&speed=%SPD&direction=%DIR&altitude=%ALT&provider=%PROV&activity=%ACT
```
(be sure you include API password (`&api_password=`) if needed, or you can also use HTTP Basic authentication `http://:@/api/gpslogger...`)
+(You can change your device name by editing "%SER" in this URL (e.g.: &device=user_devicename))
- Log to OpenGTS Server: no
- Log to Plain Text: no
- Log to NMEA: no
From a330ff8b33ff46fe98d32a64c36e219b4a8c1e82 Mon Sep 17 00:00:00 2001
From: jurafxp
Date: Sat, 14 Oct 2017 22:35:35 +0200
Subject: [PATCH 35/88] Working Apache config for websockets (#3623)
---
source/_docs/ecosystem/apache.markdown | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/source/_docs/ecosystem/apache.markdown b/source/_docs/ecosystem/apache.markdown
index d8ec1aac020..ae0c1925114 100644
--- a/source/_docs/ecosystem/apache.markdown
+++ b/source/_docs/ecosystem/apache.markdown
@@ -32,13 +32,19 @@ To be able to access to your Home Assistant instance by using https://home.examp
```text
- ProxyPreserveHost On
- ProxyRequests Off
ServerName home.example.org
- ProxyPass /api/websocket ws://localhost:8123/api/websocket
- ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket
+ ProxyPreserveHost On
+ ProxyRequests off
ProxyPass / http://localhost:8123/
ProxyPassReverse / http://localhost:8123/
+ ProxyPass /api/websocket ws://localhost:8123/api/websocket
+ ProxyPassReverse /api/websocket ws://localhost:8123/api/websocket
+
+ RewriteEngine on
+ RewriteCond %{HTTP:Upgrade} =websocket [NC]
+ RewriteRule /(.*) ws://localhost:8123/$1 [P,L]
+ RewriteCond %{HTTP:Upgrade} !=websocket [NC]
+ RewriteRule /(.*) http://localhost:8123/$1 [P,L]
```
From 8f5f2f2e52386119081bebca0ce3c20405063bd1 Mon Sep 17 00:00:00 2001
From: Phill Price
Date: Sat, 14 Oct 2017 22:43:06 +0100
Subject: [PATCH 36/88] Remove flux_led option from discovery (#3624)
fails to load configuration with this option in.
---
source/_components/discovery.markdown | 2 --
1 file changed, 2 deletions(-)
diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown
index c133e9a7125..726da20c46c 100644
--- a/source/_components/discovery.markdown
+++ b/source/_components/discovery.markdown
@@ -27,7 +27,6 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
* DirecTV
* Apple TV
* Yeelight Sunflower Bulb
- * Flux Led/MagicLight
* Linn / Openhome
* Denon Network Receivers
* Bose Soundtouch speakers
@@ -59,7 +58,6 @@ Valid values for ignore are:
* `bose_soundtouch`: Bose Soundtouch speakers
* `denonavr`: Denon Network Receivers
* `directv`: DirecTV
- * `flux_led`: Flux Led/MagicLight
* `frontier_silicon`
* `google_cast`: Google Chromecast
* `harmony`: Harmony Hub
From c48fda8081612cdb94a2e9fd43aac24edc4c7661 Mon Sep 17 00:00:00 2001
From: moskovskiy82
Date: Sun, 15 Oct 2017 10:34:07 +0300
Subject: [PATCH 37/88] Update input_datetime.markdown (#3629)
* Update input_datetime.markdown
As the frontend is not merged the documentation is very misleading
* Make it a note
---
source/_components/input_datetime.markdown | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/_components/input_datetime.markdown b/source/_components/input_datetime.markdown
index f9351f09848..0ae8cae833c 100644
--- a/source/_components/input_datetime.markdown
+++ b/source/_components/input_datetime.markdown
@@ -12,6 +12,10 @@ ha_category: Automation
ha_release: 0.55
---
+
+This component is a work in progress. The frontend is not yet implemented.
+
+
The `input_datetime` component allows the user to define date and time values that can be controlled via the frontend and can be used within automations and templates.
To add three datetime inputs to your installation, one with both date and time, and one with date or time each, add the following lines to your `configuration.yaml`:
From 498cbf746030b634b5ec52a261c817c46cfdac5c Mon Sep 17 00:00:00 2001
From: DanielXYZ2000
Date: Sun, 15 Oct 2017 09:39:11 +0200
Subject: [PATCH 38/88] Add Link and fix config (#3628)
Add the example html and fix the config (who instead of hello)
---
source/_components/panel_custom.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_components/panel_custom.markdown b/source/_components/panel_custom.markdown
index 1ed44576e58..49775f28557 100644
--- a/source/_components/panel_custom.markdown
+++ b/source/_components/panel_custom.markdown
@@ -18,7 +18,7 @@ The `panel_custom` support allows you to add additional panels to your Home Assi
To enable customized panels in your installation, add the following to your `configuration.yaml` file:
```yaml
-# Example configuration.yaml entry
+# Example configuration.yaml entry for https://github.com/home-assistant/example-custom-config/blob/master/panels/hello_world.html
panel_custom:
- name: todomvc
sidebar_title: TodoMVC
@@ -26,7 +26,7 @@ panel_custom:
url_path: my-todomvc
webcomponent_path: /home/hass/hello.html
config:
- hello: world
+ who: world
```
Configuration variables:
From c80025347043c57144e0f63e524901471f08735d Mon Sep 17 00:00:00 2001
From: DrewSK
Date: Sun, 15 Oct 2017 02:40:37 -0500
Subject: [PATCH 39/88] Update glossary.yml (#3627)
* Update glossary.yml
Added automation, trigger, and template. Adjusted the groups entry to not utilize the term in the definition.
* Remove white space
---
source/_data/glossary.yml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml
index 39245d7ef25..e18d05c02e5 100644
--- a/source/_data/glossary.yml
+++ b/source/_data/glossary.yml
@@ -15,4 +15,10 @@
- topic: Discovery
description: The automatic setup of zeroconf/mDNS and uPnP devices after they are discovered.
- topic: Groups
- description: "Groups are a way to organize your entities into a group."
+ description: "Groups are a way to organize your entities into a single unit."
+- topic: Automation
+ description: "Capability to call a service based on a simple or complex trigger. Automation allows a condition such as sunset to cause an event, such as a light turning on."
+- topic: Trigger
+ description: "Values or conditions of a platform that are defined to cause an automation to run."
+- topic: Template
+ description: "An automation definition can include variables for the service or data from the trigger values. This allows automations to generate dynamic actions."
From 7cf3d727552475f2d72f2c5b9c06140cd80be151 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Sun, 15 Oct 2017 15:49:34 +0200
Subject: [PATCH 40/88] Update addon_communication.markdown
---
source/developers/hassio/addon_communication.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/developers/hassio/addon_communication.markdown b/source/developers/hassio/addon_communication.markdown
index 7dd40ca0091..d7bee9d5162 100644
--- a/source/developers/hassio/addon_communication.markdown
+++ b/source/developers/hassio/addon_communication.markdown
@@ -14,7 +14,7 @@ It exists diferent ways to communication between add-ons or home-assistant insid
## {% linkable_title Network %}
-We use a internal network. That allow to speak with every add-on or from Home-Assistant to add-on by name or alias. Only the a add-on they run on Host network are a bit limited. They can speak with all internal add-ons over there name but all other add-on can't speak with the add-on name to this add-on, but alias work wheel. So use the name/alias to communicate inside Hass.io
+We use a internal network. That allow to speak with every add-on or from Home-Assistant to add-on by name or alias. Only the a add-on they run on Host network are a bit limited. They can speak with all internal add-ons over there name but all other add-on can't speak with the add-on name to this add-on, but alias work wheel. So use the name/alias to communicate inside Hass.io. The name have format `{REPO}-{SLUG}` i.e. `local-xy` or `3283fh-myaddon`.
i.e. use `hassio` to speak with internal API.
From f762f779a2dee9171dab3beb2bb11029c800ae9e Mon Sep 17 00:00:00 2001
From: Pascal Vizeli
Date: Sun, 15 Oct 2017 15:56:01 +0200
Subject: [PATCH 41/88] Update lets_encrypt.markdown
---
source/_addons/lets_encrypt.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown
index 31fdd13f3b8..8917e007bf4 100644
--- a/source/_addons/lets_encrypt.markdown
+++ b/source/_addons/lets_encrypt.markdown
@@ -17,7 +17,7 @@ You should not use this if you are also using the [DuckDNS add-on]. The DuckDNS
Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration.
-This add-on uses ports 80/443 to verify the certificate request. You will need to stop all other add-ons that also use these ports.
+This add-on uses ports 80/443 to verify the certificate request. You will need to stop all other add-ons that also use these ports. If you don't need a port (like with https you don't need port 80) you can remove this from network config.
```json
From b5119b9d57638ca3490278975178ab3591150f77 Mon Sep 17 00:00:00 2001
From: mortenmathiasen
Date: Sun, 15 Oct 2017 21:33:06 +0200
Subject: [PATCH 42/88] Make the example work as is (#3630)
The HVAC component will not appear without valid initial values sent from the sketch. Initial default values added to avoid the problem.
---
source/_components/climate.mysensors.markdown | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/source/_components/climate.mysensors.markdown b/source/_components/climate.mysensors.markdown
index c629b0083fc..a61fae33f90 100644
--- a/source/_components/climate.mysensors.markdown
+++ b/source/_components/climate.mysensors.markdown
@@ -98,6 +98,8 @@ MyMessage msgHVACSetPointC(CHILD_ID_HVAC, V_HVAC_SETPOINT_COOL);
MyMessage msgHVACSpeed(CHILD_ID_HVAC, V_HVAC_SPEED);
MyMessage msgHVACFlowState(CHILD_ID_HVAC, V_HVAC_FLOW_STATE);
+bool initialValueSent = false;
+
void presentation() {
sendSketchInfo("Heatpump", "2.1");
present(CHILD_ID_HVAC, S_HVAC, "Thermostat");
@@ -108,6 +110,13 @@ void setup() {
void loop() {
// put your main code here, to run repeatedly:
+ if (!initialValueSent) {
+ send(msgHVACSetPointC.set(20));
+ send(msgHVACSpeed.set("Auto"));
+ send(msgHVACFlowState.set("Off"));
+
+ initialValueSent = true;
+ }
}
void receive(const MyMessage &message) {
From 84224dff346f2238d9a0d76ac5b9c54381b6bf7e Mon Sep 17 00:00:00 2001
From: Florian Klien
Date: Sun, 15 Oct 2017 21:34:07 +0200
Subject: [PATCH 43/88] xiaomi gateway setup tip (#3636)
Initializing the Xiaomi Home app with the OnePlus 3 failed. Trying the Nexus 5 helped.
---
source/_components/xiaomi_aqara.markdown | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/_components/xiaomi_aqara.markdown b/source/_components/xiaomi_aqara.markdown
index dcfad4c8041..cb138708016 100644
--- a/source/_components/xiaomi_aqara.markdown
+++ b/source/_components/xiaomi_aqara.markdown
@@ -158,6 +158,10 @@ and stops the sound when the button is pressed once.
## {% linkable_title Troubleshooting %}
+### {% linkable_title Initial setup problem %}
+
+If you run into trouble initializing the gateway with your app, try another smartphone. I had trouble with the OnePlus 3, but it worked with a Nexus 5.
+
### {% linkable_title Connection problem %}
```bash
From 74a6e9c4fb0c1c227dfca172c65280bf0b4e0097 Mon Sep 17 00:00:00 2001
From: DubhAd
Date: Sun, 15 Oct 2017 20:38:42 +0100
Subject: [PATCH 44/88] Added reference to previous name (#3637)
---
source/_components/input_number.markdown | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/_components/input_number.markdown b/source/_components/input_number.markdown
index 3a5202960ba..4ebbe8ce681 100644
--- a/source/_components/input_number.markdown
+++ b/source/_components/input_number.markdown
@@ -13,6 +13,10 @@ ha_release: 0.16
redirect_from: /components/input_slider/
---
+
+Before version 0.55 this component was known as `input_slider` and did not have the `mode` configuration option.
+
+
The `input_number` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well.
To enable this input number in your installation, add the following lines to your `configuration.yaml`:
From eda442a67394fef4cfc56a87295dbe909cfb97b2 Mon Sep 17 00:00:00 2001
From: DubhAd
Date: Sun, 15 Oct 2017 20:45:33 +0100
Subject: [PATCH 45/88] Adding warning to the top
Adding warning about GHome not working for new users
---
source/_components/emulated_hue.markdown | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/_components/emulated_hue.markdown b/source/_components/emulated_hue.markdown
index a78b478dba4..b6dfa32c7e5 100644
--- a/source/_components/emulated_hue.markdown
+++ b/source/_components/emulated_hue.markdown
@@ -13,6 +13,10 @@ ha_release: 0.27
ha_iot_class: "Local Push"
---
+
+At this time `emulated_hue` doesn't appear to be working for new Google Home users.
+
+
The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant
entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no set up cost outside of configuration changes.
The virtual bridge has the ability to turn entities on or off, or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness.
From 36ce6730bfc806a3c1f957a12c01913ac65d611d Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Sun, 15 Oct 2017 22:32:45 +0200
Subject: [PATCH 46/88] Update 'now()' and 'utcnow()' (#3625)
* Update 'now()' and 'utcnow()'
* Add note
---
source/_docs/configuration/templating.markdown | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown
index 50fb0abf4ca..c02fbb7f2a2 100644
--- a/source/_docs/configuration/templating.markdown
+++ b/source/_docs/configuration/templating.markdown
@@ -69,7 +69,9 @@ Home Assistant adds extensions to allow templates to access all of the current s
- `is_state('device_tracker.paulus', 'home')` will test if the given entity is specified state.
- `is_state_attr('device_tracker.paulus', 'battery', 40)` will test if the given entity is specified state.
- `now()` will be rendered as current time in your time zone.
+ - For specific values: `now().second`, `now().minute`, `now().hour`, `now().day`, `now().month`, `now().year`, `now().weekday()` and `now().isoweekday()`
- `utcnow()` will be rendered as UTC time.
+ - For specific values: `utcnow().second`, `utcnow().minute`, `utcnow().hour`, `utcnow().day`, `utcnow().month`, `utcnow().year`, `utcnow().weekday()` and `utcnow().isoweekday()`.
- `as_timestamp()` will convert datetime object or string to UNIX timestamp
- `distance()` will measure the distance in meters between home, entity, coordinates.
- `closest()` will find the closest entity.
@@ -89,6 +91,10 @@ Home Assistant adds extensions to allow templates to access all of the current s
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']`
+
+Rendering templates with time is dangerous as updates only trigger templates in sensors based on entity state changes.
+
+
## {% linkable_title Home Assistant template extensions %}
In templates, besides the normal [state object methods and properties](/topics/state_object/), there are also some extra things available:
From 40f5aa365178a1baaf4994afdb70e2015747a8a2 Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Sun, 15 Oct 2017 22:45:48 +0200
Subject: [PATCH 47/88] Template blog post (#3626)
* Add a blog post templating and times/dates
* Update date
---
.../2017-10-14-templating-date-time.markdown | 38 ++++++++++++++++++
.../images/blog/2017-10-template/social.png | Bin 0 -> 69415 bytes
2 files changed, 38 insertions(+)
create mode 100644 source/_posts/2017-10-14-templating-date-time.markdown
create mode 100644 source/images/blog/2017-10-template/social.png
diff --git a/source/_posts/2017-10-14-templating-date-time.markdown b/source/_posts/2017-10-14-templating-date-time.markdown
new file mode 100644
index 00000000000..1af3ecff8bc
--- /dev/null
+++ b/source/_posts/2017-10-14-templating-date-time.markdown
@@ -0,0 +1,38 @@
+---
+layout: post
+title: "Templates, dates and times"
+description: "Using templates for seconds and years in Home Assistant."
+date: 2017-10-15 08:00:00 +0200
+date_formatted: "October 15, 2017"
+author: Fabian Affolter
+comments: true
+categories: Community
+og_image: /images/blog/2017-10-template/social.png
+---
+
+This [Pull Request](https://github.com/home-assistant/home-assistant/pull/9868) shows in a clear way what happens if the documentation is not as good as it should be. In short, it's about [Templating](/docs/configuration/templating/) and how people start to think about creative ways to solve it if it's not documented. Let's assume that we want the current year. There are a couple of options available to do that:
+
+- Query [JSON Test](http://date.jsontest.com/) with a [`rest` sensor](/components/sensor.rest/) and a `value_template:`.
+- Use a [`time_date` sensor ](/components/sensor.time_date/) and a template {% raw %}`{{ strptime(states('sensor.date'), '%Y-%m-%d').year }}`{% endraw %}.
+- Write a script in language X and use it with the [`command` sensor](/components/sensor.command_line/) or use `date +"%Y"` as a `command:`.
+
+
+
+We want it simpler, right? [Templating](/docs/configuration/templating/) offers `now()` and `utcnow()`. We will stick with `now()` in this blog post but it applies to `utcnow()` as well. Our documentation said:
+
+
+ `now()` will be rendered as current time in your time zone.
+