Date: Fri, 9 Mar 2018 12:20:03 +0100
Subject: [PATCH 03/33] Update device_tracker.ubus.markdown
---
.../_components/device_tracker.ubus.markdown | 53 ++++++++++++++++++-
1 file changed, 52 insertions(+), 1 deletion(-)
diff --git a/source/_components/device_tracker.ubus.markdown b/source/_components/device_tracker.ubus.markdown
index 3df045db24b..54e25ebd9b1 100644
--- a/source/_components/device_tracker.ubus.markdown
+++ b/source/_components/device_tracker.ubus.markdown
@@ -12,7 +12,58 @@ ha_category: Presence Detection
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 one of the multiple ways we support OpenWRT. If you encounter problems, see [openwrt](---
+layout: page
+title: "OpenWRT (luci)"
+description: "Instructions how to integrate OpenWRT routers into Home Assistant."
+date: 2015-03-23 19:59
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: openwrt.png
+ha_category: Presence Detection
+ha_release: pre 0.7
+---
+
+_This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/components/device_tracker.openwrt/)._
+
+This is a presence detection scanner for OpenWRT using [luci](http://wiki.openwrt.org/doc/techref/luci).
+
+
+This component requires a [workaround](https://github.com/home-assistant/home-assistant/issues/1258#issuecomment-252469880) when using luci with HTTPS and a self-signed certificate.
+
+
+Before this scanner can be used you have to install the luci RPC package on OpenWRT:
+
+```bash
+# opkg install luci-mod-rpc
+```
+
+To use this device tracker in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+ - platform: luci
+ host: ROUTER_IP_ADDRESS
+ username: YOUR_ADMIN_USERNAME
+ password: YOUR_ADMIN_PASSWORD
+```
+
+Configuration variables:
+
+- **host** (*Required*): The IP address of your router, e.g. `192.168.1.1`.
+- **username** (*Required*): The username of an user with administrative privileges, usually `admin`.
+- **password** (*Required*): The password for your given admin account.
+
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
+
+
+Some installations have [a small bug](https://github.com/openwrt/luci/issues/576). The timeout for luci RPC calls is not set and this makes the call fail.
+
+
+)._
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.
From 7ba9794a09eb5da22e51cdca904c2b6fd180c996 Mon Sep 17 00:00:00 2001
From: mueslo
Date: Fri, 9 Mar 2018 12:21:49 +0100
Subject: [PATCH 04/33] Update device_tracker.ubus.markdown
---
source/_components/device_tracker.ubus.markdown | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/source/_components/device_tracker.ubus.markdown b/source/_components/device_tracker.ubus.markdown
index 54e25ebd9b1..5f9cb6206ba 100644
--- a/source/_components/device_tracker.ubus.markdown
+++ b/source/_components/device_tracker.ubus.markdown
@@ -12,20 +12,6 @@ ha_category: Presence Detection
ha_release: 0.7.6
---
-_This is one of the multiple ways we support OpenWRT. If you encounter problems, see [openwrt](---
-layout: page
-title: "OpenWRT (luci)"
-description: "Instructions how to integrate OpenWRT routers into Home Assistant."
-date: 2015-03-23 19:59
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: openwrt.png
-ha_category: Presence Detection
-ha_release: pre 0.7
----
-
_This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/components/device_tracker.openwrt/)._
This is a presence detection scanner for OpenWRT using [luci](http://wiki.openwrt.org/doc/techref/luci).
From c8343de48ed17c8c805819e48f6004fdb3c3b017 Mon Sep 17 00:00:00 2001
From: mueslo
Date: Fri, 9 Mar 2018 12:51:12 +0100
Subject: [PATCH 05/33] Add linkable heading
---
source/_components/device_tracker.openwrt.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/device_tracker.openwrt.markdown b/source/_components/device_tracker.openwrt.markdown
index 4c319341590..a5e0f0c349a 100644
--- a/source/_components/device_tracker.openwrt.markdown
+++ b/source/_components/device_tracker.openwrt.markdown
@@ -35,7 +35,7 @@ There are _multiple_ ways of integrating an OpenWRT router for presence detction
* [openwrt_hass_devicetracker](https://github.com/mueslo/openwrt_hass_devicetracker)
* your own custom script
-### Event-based device tracker
+### {% linkable_title Event-based device tracker %}
This can be achieved by running a simple shell script on the OpenWRT router which calls the appropriate Home Assistant service. An OpenWRT package which does this is listed above. As this method directly calls the [service API](/developers/rest_api.markdown#post-apiservicesltdomainltservice), no special configuration is necessary on the Home Assistant side, except for ensuring the device_tracker API is running, which is achieved by adding the following to your `configuration.yaml` file:
From 3ca4b48dca858298661f1ebf8b7b6b4f729ea392 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
Date: Fri, 23 Mar 2018 21:11:53 +0100
Subject: [PATCH 06/33] :pencil2: Tweak
---
source/_components/device_tracker.openwrt.markdown | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/source/_components/device_tracker.openwrt.markdown b/source/_components/device_tracker.openwrt.markdown
index a5e0f0c349a..2f4b0f5a18e 100644
--- a/source/_components/device_tracker.openwrt.markdown
+++ b/source/_components/device_tracker.openwrt.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "OpenWRT"
-description: "Instructions how to integrate OpenWRT routers into Home Assistant."
+description: "Instructions on how to integrate OpenWRT routers into Home Assistant."
date: 2018-03-09 12:00
sidebar: true
comments: false
@@ -12,7 +12,7 @@ ha_category: Presence Detection
ha_release: pre 0.7
---
-There are _multiple_ ways of integrating an OpenWRT router for presence detction. A broad distinction can be made between presence detection methods which actively scan for devices (by default every 12 seconds) and those that are notified by some external service on changes. It is essentially a problem of synchronizing states between two remote machines.
+There are _multiple_ ways of integrating an OpenWRT router for presence detection. A broad distinction can be made between presence detection methods which actively scan for devices (by default every 12 seconds) and those that are notified by some external service on changes. It is essentially a problem of synchronizing states between two remote machines.
* __active scanning__
Scan for devices regularly.
@@ -25,7 +25,7 @@ There are _multiple_ ways of integrating an OpenWRT router for presence detction
* [ubus](/components/device_tracker.ubus/)
* [luci](/components/device_tracker.luci/)
* __passive/event-based__
- External services which notify Home Assistant of devices vie the [REST API endpoint](/developers/rest_api.markdown).
+ External services which notify Home Assistant of devices via the [REST API endpoint](/developers/rest_api.markdown).
* Advantages:
* devices typically registered in under one second when they connect
* very few network requests
From 874f7fb54f6005513a20c43e2e523bff442c0c11 Mon Sep 17 00:00:00 2001
From: Jordi
Date: Thu, 5 Apr 2018 22:54:58 +0200
Subject: [PATCH 07/33] The distance is in fact measured in kilometers not
meters
---
source/_docs/configuration/templating.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown
index b8752c54ac5..e2c345df0fd 100644
--- a/source/_docs/configuration/templating.markdown
+++ b/source/_docs/configuration/templating.markdown
@@ -74,7 +74,7 @@ Home Assistant adds extensions to allow templates to access all of the current s
- `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.
+- `distance()` will measure the distance in kilometers between home, entity, coordinates.
- `closest()` will find the closest entity.
- `float` will format the output as float.
- `strptime(string, format)` will parse a string to a datetime based on a [format][strp-format].
@@ -189,7 +189,7 @@ Closest to an entity: {{ closest(states.zone.school, 'group.children') }}{% endr
Since closest returns a state, we can combine it with distance too.
```text
-{% raw %}{{ closest(states).name }} is {{ distance(closest(states)) }} meters away.{% endraw %}
+{% raw %}{{ closest(states).name }} is {{ distance(closest(states)) }} kilometers away.{% endraw %}
```
## {% linkable_title Processing incoming data %}
From e4e0e30ef540b9e5570dcb81a285d0308e677396 Mon Sep 17 00:00:00 2001
From: phispi
Date: Sat, 21 Apr 2018 23:19:55 +0200
Subject: [PATCH 08/33] Mention possibility to support a "stop" group address.
My KNX device has a "start" (down/up) and a "stop" group address. It works perfectly if I enter the "start" group address in "move_long_address" and "stop" in "move_short_address". However, I only found out because I found issue #10624.
---
source/_components/cover.knx.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_components/cover.knx.markdown b/source/_components/cover.knx.markdown
index cd620f15634..d6d3733c1e1 100644
--- a/source/_components/cover.knx.markdown
+++ b/source/_components/cover.knx.markdown
@@ -37,7 +37,7 @@ Configuration variables:
- **name** (*Optional*): A name for this device used within Home Assistant.
- **move_long_address**: KNX group address for moving the cover full up or down.
-- **move_short_address** (*Optional*): KNX group address for moving the cover short time up or down.
+- **move_short_address** (*Optional*): KNX group address for moving the cover short time up or down. If the KNX device has a stop group address you can use that here.
- **position_address** (*Optional*): KNX group address for moving the cover to the dedicated position.
- **position_state_address** (*Optional*): Separate KNX group address for requesting the current position of the cover.
- **angle_address** (*Optional*): KNX group address for moving the cover to the dedicated angle.
From b4fb6b7695470685abe7eadf0095cb0ef510cc7c Mon Sep 17 00:00:00 2001
From: Marc Forth
Date: Thu, 26 Apr 2018 00:28:19 +0100
Subject: [PATCH 09/33] Tidy Folder Watcher component page automation.
The automation on this page was obviously created by the automation editor and was super-ugly!!
---
source/_components/folder_watcher.markdown | 28 +++++++++++-----------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/source/_components/folder_watcher.markdown b/source/_components/folder_watcher.markdown
index 88b19937e0e..656c1097ea0 100644
--- a/source/_components/folder_watcher.markdown
+++ b/source/_components/folder_watcher.markdown
@@ -62,19 +62,19 @@ Automations can be triggered on filesystem event data using a `data_template`. T
{% raw %}
```yaml
-- action:
- - data_template:
- message: 'Created {{ trigger.event.data.file }} in {{ trigger.event.data.folder }}'
- title: New image captured!
- data:
- file: " {{ trigger.event.data.path }} "
- service: notify.pushbullet
- alias: New file alert
- condition: []
- id: '1520092824697'
- trigger:
- - event_data: {"event_type":"created"}
- event_type: folder_watcher
- platform: event
+#Send notification for new image (including the image itself)
+alias: New file alert
+trigger:
+ platform: event
+ event_type: folder_watcher
+ event_data:
+ event_type: created
+action:
+ service: notify.notify
+ data_template:
+ title: New image captured!
+ message: "Created {{ trigger.event.data.file }} in {{ trigger.event.data.folder }}"
+ data:
+ file: "{{ trigger.event.data.path }}"
```
{% endraw %}
From f1cc2e0edfc606db945b79113a9780cba3211ec9 Mon Sep 17 00:00:00 2001
From: Marc Forth
Date: Fri, 11 May 2018 05:04:25 +0100
Subject: [PATCH 10/33] Update folder_watcher.markdown
---
source/_components/folder_watcher.markdown | 27 +++++++++++-----------
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/source/_components/folder_watcher.markdown b/source/_components/folder_watcher.markdown
index 656c1097ea0..b590b01653a 100644
--- a/source/_components/folder_watcher.markdown
+++ b/source/_components/folder_watcher.markdown
@@ -63,18 +63,19 @@ Automations can be triggered on filesystem event data using a `data_template`. T
{% raw %}
```yaml
#Send notification for new image (including the image itself)
-alias: New file alert
-trigger:
- platform: event
- event_type: folder_watcher
- event_data:
- event_type: created
-action:
- service: notify.notify
- data_template:
- title: New image captured!
- message: "Created {{ trigger.event.data.file }} in {{ trigger.event.data.folder }}"
- data:
- file: "{{ trigger.event.data.path }}"
+automation:
+ alias: New file alert
+ trigger:
+ platform: event
+ event_type: folder_watcher
+ event_data:
+ event_type: created
+ action:
+ service: notify.notify
+ data_template:
+ title: New image captured!
+ message: "Created {{ trigger.event.data.file }} in {{ trigger.event.data.folder }}"
+ data:
+ file: "{{ trigger.event.data.path }}"
```
{% endraw %}
From 1123cf688480a8a2be9ab78646be74b06835e70c Mon Sep 17 00:00:00 2001
From: Fabian Affolter
Date: Fri, 11 May 2018 22:25:33 +0200
Subject: [PATCH 11/33] Add articles from SmartHome University
---
source/help/index.markdown | 2 ++
1 file changed, 2 insertions(+)
diff --git a/source/help/index.markdown b/source/help/index.markdown
index ab93fa10350..84b6d6b5d52 100644
--- a/source/help/index.markdown
+++ b/source/help/index.markdown
@@ -52,7 +52,9 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
- [Home Assistant lets you automate your smart home without giving up privacy](https://www.the-ambient.com/features/home-assistant-automation-privacy-582) - May 2018
- [HackSpace magazine #6](https://s3-eu-west-1.amazonaws.com/rpi-magazines/issues/full_pdfs/000/000/013/original/HS_6_Digital_Optimised.pdf?1524495009) - May 2018
+- [SmartThings vs Home Assistant](https://smarthome.university/smartthings-vs-home-assistant/) - April 2018
- [The winners of the Thomas-Krenn-Awards 2018](https://www.thomas-krenn.com/de/tkmag/allgemein/die-gewinner-des-thomas-krenn-awards-2018-stehen-fest/) - March 2018
+- [Best of Open Source Smart Home: Home Assistant vs OpenHAB](https://smarthome.university/your-smart-home-platform-home-assistant-vs-openhab/) - February 2018
- [Hausautomations-Schaltzentrale Home Assistant auf Python-Basis](https://www.heise.de/ct/ausgabe/2017-26-Hausautomations-Schaltzentrale-Home-Assistant-3909532.html) - December 2017
- [Using Home Assistant the ARTIK Cloud](https://developer.artik.io/documentation/developer-guide/wireless-iot/hass.html) - September 2017
- [Control home automation hardware with Home Assistant](http://www.linux-magazine.com/Issues/2017/203/Home-Assistant) - August 2017
From c4b17aa46764fae00893b8538707eb1d9ee5e48f Mon Sep 17 00:00:00 2001
From: Matt Schmitt
Date: Fri, 11 May 2018 20:24:50 -0400
Subject: [PATCH 12/33] Add sample config HomeKit (#5351)
---
source/_components/homekit.markdown | 20 ++++++++++++++++----
1 file changed, 16 insertions(+), 4 deletions(-)
diff --git a/source/_components/homekit.markdown b/source/_components/homekit.markdown
index 7ab434c8902..5ee71d0b971 100644
--- a/source/_components/homekit.markdown
+++ b/source/_components/homekit.markdown
@@ -23,6 +23,18 @@ The `HomeKit` component allows you to forward entities from Home Assistant to Ap
If you are upgrading Home Assistant from `0.65.x` and have used the HomeKit component, some accessories may not respond or may behave unusually. To fix these problems, you will need to remove the Home Assistant Bridge from your Home, stop Home Assistant and delete the `.homekit.state` file in your configuration folder and follow the Homekit [setup](#setup) steps again.