From 88a83d782323531aea2fc35325e4f2ca12abaf4d Mon Sep 17 00:00:00 2001 From: Robin Date: Sun, 11 Mar 2018 13:46:12 +0000 Subject: [PATCH 1/3] Fix typo The extra () resulted in a 404 error --- source/_components/sensor.folder.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.folder.markdown b/source/_components/sensor.folder.markdown index dc6951c531e..2555b7a0ad4 100644 --- a/source/_components/sensor.folder.markdown +++ b/source/_components/sensor.folder.markdown @@ -13,7 +13,7 @@ ha_iot_class: "Local Polling" ha_release: 0.64 --- -Sensor for monitoring the contents of a folder. Note that folder paths must be added to [whitelist_external_dirs](https://home-assistant.io/docs/configuration/basic/). Optionally a [wildcard filter]((https://docs.python.org/3.6/library/fnmatch.html)) can be applied to the files considered within the folder. The state of the sensor is the size in MB of files within the folder that meet the filter criteria. The number of filtered files in the folder and total size in bytes of those files are exposed as attributes. +Sensor for monitoring the contents of a folder. Note that folder paths must be added to [whitelist_external_dirs](https://home-assistant.io/docs/configuration/basic/). Optionally a [wildcard filter](https://docs.python.org/3.6/library/fnmatch.html) can be applied to the files considered within the folder. The state of the sensor is the size in MB of files within the folder that meet the filter criteria. The number of filtered files in the folder and total size in bytes of those files are exposed as attributes. To enable the `folder` sensor in your installation, add the following to your `configuration.yaml` file: From ca952b41cc2f68fb64fd9f6eb18bd90b69a2bf5d Mon Sep 17 00:00:00 2001 From: IainPHay Date: Sun, 11 Mar 2018 18:08:05 +0000 Subject: [PATCH 2/3] Change upgrade homeassistant to upgrade home-assistant Line 40 Change: You can also use `hassbian-config` to automate the process by running `sudo hassbian-config upgrade homeassistant` to You can also use `hassbian-config` to automate the process by running `sudo hassbian-config upgrade home-assistant` as this was incorrect --- source/_docs/installation/hassbian/common-tasks.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/installation/hassbian/common-tasks.markdown b/source/_docs/installation/hassbian/common-tasks.markdown index 73e96a07876..6fddcd360b6 100644 --- a/source/_docs/installation/hassbian/common-tasks.markdown +++ b/source/_docs/installation/hassbian/common-tasks.markdown @@ -37,7 +37,7 @@ To get the current state of the `homeassistant.service` replace `stop` with `sta ### {% linkable_title Update Home Assistant %}

-You can also use `hassbian-config` to automate the process by running `sudo hassbian-config upgrade homeassistant` +You can also use `hassbian-config` to automate the process by running `sudo hassbian-config upgrade home-assistant`

Log in as the `pi` account and execute the following commands: From 90cf4205cc0b7420fc9a3d957604a1b5e7e542fe Mon Sep 17 00:00:00 2001 From: Max Laverse Date: Sun, 11 Mar 2018 20:06:26 +0100 Subject: [PATCH 3/3] Improve caldav documentation --- source/_components/calendar.caldav.markdown | 46 ++++++++++++++------- 1 file changed, 30 insertions(+), 16 deletions(-) diff --git a/source/_components/calendar.caldav.markdown b/source/_components/calendar.caldav.markdown index 6ae9f8c36a4..ca93537fec0 100644 --- a/source/_components/calendar.caldav.markdown +++ b/source/_components/calendar.caldav.markdown @@ -33,9 +33,38 @@ To integrate a WebDav calendar in Home Assistant, add the following section to y # Example configuration.yaml entry calendar: - platform: caldav + username: john.doe@test.com + password: !secret caldav url: https://baikal.my-server.net/cal.php/calendars/john.doe@test.com/default ``` +This example will generate default binary sensors for each calendar you have in your account. Those calendars will be `on` when there is an ongoing event and `off` if not. Events that last a whole day are ignored in those calendars. You have to setup custom calendars in order to take them into account or for advanced event filtering. + + +### {% linkable_title Custom calendars %} + +You have the possibility to create multiple binary sensors for events that match certain conditions. + +```yaml +# Example configuration.yaml entry +calendar: + - platform: caldav + username: john.doe@test.com + password: !secret caldav + url: https://baikal.my-server.net/cal.php/calendars/john.doe@test.com/default + custom_calendars: + - name: 'HomeOffice' + calendar: 'Agenda' + search: 'HomeOffice' + - name: 'WarmupFlat' + calendar: 'Agenda' + search: 'Warmup' +``` + +This will create two binary sensors for the calendar name Agenda: "HomeOffice" and "WarmupFlat". Those sensors will be `on` if there is an ongoing event matching the regular expression specified in `search`. In custom calendars, events that last a whole day are taken into account. + +Please note that when you configure custom calendars, the default ones are not created anymore. + {% configuration %} url: required: true @@ -68,7 +97,7 @@ custom_calendars: type: string search: required: true - pending_charges: Regular expression for filtering the events + pending_charges: Regular expression for filtering the events based on the content of their summary, description or location. type: string {% endconfiguration %} @@ -82,18 +111,3 @@ custom_calendars: - **location**: The event Location. - **start_time**: Start time of event. - **end_time**: End time of event. - -### {% linkable_title Sensor attributes %} - -```yaml -# Example configuration.yaml entry -calendar: - - platform: caldav - url: https://baikal.my-server.net/cal.php/calendars/john.doe@test.com/default - username: john.doe@test.com - password: !secret caldav - custom_calendars: - - name: 'HomeOffice' - calendar: 'Agenda' - search: 'HomeOffice' -```