jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-08 09:56:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update calendar.google.markdown (#5653)

Browse Source 
Fixes typos and formatting
This commit is contained in:
Jeff Wilson 2018-07-04 06:33:15 -04:00 committed by Franck Nijhof
parent a771899eb0
commit 2718fa9033
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_components/calendar.google.markdown
View File

@ -46,7 +46,7 @@ client_id:
description: Use the value you generated in the Prerequisites stage. description: Use the value you generated in the Prerequisites stage.
required: true required: true
type: string type: string
minimum: client_secret:
description: Use the value you generated in the Prerequisites stage. description: Use the value you generated in the Prerequisites stage.
required: true required: true
type: string type: string
@ -95,7 +95,7 @@ Variables:
- **track**: (*Required*): Should we create a sensor `True` or ignore it `False`? - **track**: (*Required*): Should we create a sensor `True` or ignore it `False`?
- **search**: (*Optional*): If set will only trigger for matched events. - **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: `!!`) - **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`) - **ignore_availability**: (*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. 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.