From 086960a502281d2b3ddfe25574adeb610bcd81bd Mon Sep 17 00:00:00 2001 From: cgtobi Date: Fri, 6 Apr 2018 21:49:47 +0200 Subject: [PATCH] Docs for transparency feature google calendar component (#5101) * Add transparency feature to google calendar component * Set default behaviour to ignore the availability. This reflects the old behaviour and does not break current workflows. --- source/_components/calendar.google.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_components/calendar.google.markdown b/source/_components/calendar.google.markdown index d0463968357..5999dc48ac6 100644 --- a/source/_components/calendar.google.markdown +++ b/source/_components/calendar.google.markdown @@ -95,7 +95,8 @@ Variables: - **track**: (*Required*): Should we create a sensor `True` or ignore it `False`? - **search**: (*Optional*): If set will only trigger for matched events. - **offset**: (*Optional*): A set of characters that precede a number in the event title for designating a pre-trigger state change on the sensor. (Default: `!!`) - +  - **ignore_availablilty**: (*Optional*): Should we respect `free`/`busy` flags? (Defaults to `true`) +   From this we will end up with the binary sensors `calendar.test_unimportant` and `calendar.test_important` which will toggle themselves on/off based on events on the same calendar that match the search value set for each. You'll also have a sensor `calendar.test_everything` that will not filter events out and always show the next event available. But what if you only wanted it to toggle based on all events? Just leave out the *search* parameter.