From 2459f599bc6262047c9b6416734480dae2a0aeef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alexander=20Gro=C3=9F?= Date: Sun, 26 Mar 2017 19:44:39 +0200 Subject: [PATCH] Clarify hash in Google Calendar search term (#2305) Relates to https://github.com/home-assistant/home-assistant/issues/6670 --- source/_components/calendar.google.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/calendar.google.markdown b/source/_components/calendar.google.markdown index e57f182091e..658dae1f2bc 100644 --- a/source/_components/calendar.google.markdown +++ b/source/_components/calendar.google.markdown @@ -95,7 +95,7 @@ From this we will end up with the binary sensors `calendar.test_unimportant` and But what if you only wanted it to toggle based on all events? Just leave out the *search* parameter. -**Note**: If you use a `#` sign for search then wrap it up. It's better to be safe! +**Note**: If you use a `#` sign for `search` then wrap the whole search term in quotes. Otherwise everything following the hash sign would be considered a YAML comment. ### {% linkable_title Sensor attributes %}