diff --git a/atom.xml b/atom.xml index 8e1a366bb0..2b9dae1ce6 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
# 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.
You have the possibility to create multiple binary sensors for events that match certain conditions.
+# 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.
# 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'
-
-