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-13 12:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add detail about hiding rules (fixes #1002)

Browse Source
This commit is contained in:
Fabian Affolter 2016-09-30 08:26:18 +02:00
parent 1d43a195f0
commit 4adaa72d8c
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
3 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
source/_components/automation.markdown
View File

@ -19,4 +19,13 @@ Starting with 0.28 your automation rules can be controlled with the frontend.
<img src='{{site_root}}/images/screenshots/automation-switches.png' />
</p>
This allows one to reload the automation without restarting Home Assistant itself.
This allows one to reload the automation without restarting Home Assistant itself. If you don't want to see the automation rule in your frontend use `hide_entity: True` to hide it.
```yaml
automation:
- alias: Door alarm
hide_entity: True
trigger:
- platform: state
...
```

4
source/_posts/2016-09-29-async-sleepiq-emoncms-stocks.markdown
View File

@ -28,6 +28,10 @@ On the voluptuous front we have also made great progress. We were able to fully
As you might have noticed, this release has been delayed by 5 days. This was due to a rare, difficult to reproduce problem with the Python interpreter. A huuuuge thanks to all the people that have helped countless hours in researching, debugging and fixing this issue: [@bbangert], [@turbokongen], [@lwis], [@kellerza], [@technicalpickles], [@pvizeli], [@persandstrom] and [@joyrider3774]. I am grateful to have all of you as part of the Home Assistant community.
### {% linkable_title Hide automation rules %}
Since 0.28 [automation rules](/blog/2016/09/10/notify-group-reload-api-pihole/#reload-automation-rules) can be reloaded directly from the frontend. By default all automation rules are shown. If you want to [hide an automation rule](/getting-started/automation-create-first/), use `hide_entity: True`.
### {% linkable_title All changes %}
<img src='/images/supported_brands/emoncms.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/sleepiq.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/openalpr.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />

4
source/getting-started/automation-create-first.markdown
View File

@ -17,6 +17,7 @@ In this example, we are defining a trigger to track the sunset and tell it to fi
# Example configuration.yaml entry
automation:
alias: Turn on light when sun sets
hide_entity: False
trigger:
platform: sun
event: sunset
@ -24,6 +25,8 @@ automation:
service: light.turn_on
```
Starting with 0.28 automation rules can be reloaded from the [frontend](/components/automation/) and are shown by default. With [`hide_entity:`](/components/automation/) you can control this behaviour. It's is very handy if you are working on your rules but when a rule is finished and you don't want to see that rule in your frontend, you can set `hide_entity:` to `True`.
After a few days of running this automation rule you come to realize that this automation rule is not good enough. It was already dark when the lights went on and the one day you weren't home, the lights turned on anyway. Time for some tweaking. Let's add an offset to the sunset trigger and a condition to only turn on the lights if anyone is home.
```yaml
@ -86,6 +89,7 @@ group:
automation:
alias: Turn on light when sun sets
hide_entity: True
trigger:
platform: sun
event: sunset