From ae9047731a86a9ce4978e7adf42328ac85880bc2 Mon Sep 17 00:00:00 2001 From: smolz Date: Sat, 24 Dec 2016 00:12:32 -0800 Subject: [PATCH] Update group_visibility.markdown (#1649) --- source/_topics/group_visibility.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_topics/group_visibility.markdown b/source/_topics/group_visibility.markdown index 64b01be9e78..a312ced7588 100644 --- a/source/_topics/group_visibility.markdown +++ b/source/_topics/group_visibility.markdown @@ -56,7 +56,7 @@ automation 2: ## {% linkable_title Easier automations %} -One of the most common uses cases are to show groups during certain times of day, maybe commuting information durig a work day morning or light switches when it is getting dark. The complexity of automations needed to make this happen will quickly get out of hands. So, one way to make the automations easier is to create a sensor that alters its state depending on time of day. One way of doing that is using a `command_line` sensor and a script: +One of the most common uses cases are to show groups during certain times of day, maybe commuting information during a work day morning or light switches when it is getting dark. The complexity of automations needed to make this happen will quickly get out of hand. So, one way to make the automations easier is to create a sensor that alters its state depending on time of day. One way of doing that is using a `command_line` sensor and a script: ```python #!/usr/bin/env python3 @@ -103,7 +103,7 @@ sensor: command: "python3 occasion.py" ``` -To simplify things, we create a Home Assistant script that change visibility of a group but also verifies that an entity is in a specific state: +To simplify things, we create a Home Assistant script that changes the visibility of a group, but also verifies that an entity is in a specific state: ```yaml script: @@ -176,4 +176,4 @@ automation: entity_id: group.work_sensors cond: sensor.occasion visible_state: 'work_morning' -``` \ No newline at end of file +```