jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Upgrade ruby/jekyll/style

Browse source
This commit is contained in:
Paulus Schoutsen 2016-08-22 01:01:04 -07:00
parent ad565e855d
commit 5f1b5997da
33 changed files with 329 additions and 950 deletions
Download patch file Download diff file Expand all files Collapse all files

23
source/getting-started/scripts-conditions.markdown
View file

@ -11,7 +11,7 @@ footer: true
Conditions can be used within a script or automation to prevent further execution. A condition will look at the system right now. For example a condition can test if a switch is currently turned on or off.
#### {% linkable_title AND condition %}
### {% linkable_title AND condition %}
Test multiple conditions in 1 condition statement. Passes if all embedded conditions are valid.
@ -26,7 +26,7 @@ conditions:
below: '20'
```
#### {% linkable_title OR condition %}
### {% linkable_title OR condition %}
Test multiple conditions in 1 condition statement. Passes if any embedded conditions is valid.
@ -41,7 +41,7 @@ conditions:
below: '20'
```
#### {% linkable_title MIXED AND and OR conditions %}
### {% linkable_title MIXED AND and OR conditions %}
Test multiple AND and OR conditions in 1 condition statement. Passes if any embedded conditions is valid.
This allows you to mix several AND and OR conditions together.
@ -62,7 +62,7 @@ conditions:
below: '20'
```
#### {% linkable_title Numeric state condition %}
### {% linkable_title Numeric state condition %}
This type of condition attempts to parse the state of specified entity as a number and triggers if the value matches all of the above or below thresholds.
@ -76,10 +76,10 @@ entity_id: sensor.temperature
above: 17
below: 25
# If your sensor value needs to be adjusted
value_template: {{ float(state.state) + 2 }}
value_template: {% raw %}{{ float(state.state) + 2 }}{% endraw %}
```
#### {% linkable_title State condition %}
### {% linkable_title State condition %}
Tests if an entity is a specified state.
@ -94,7 +94,7 @@ for:
seconds: 5
```
#### {% linkable_title Sun condition %}
### {% linkable_title Sun condition %}
The sun condition can test if the sun has already set or risen when a trigger occurs. The `before` and `after` keys can only be set to `sunset` or `sunrise`. They have a corresponding optional offset value (`before_offset`, `after_offset`) that can be added, similar to the [sun trigger][sun_trigger].
@ -107,7 +107,7 @@ after: sunset
after_offset: "-1:00:00"
```
#### {% linkable_title Template condition %}
### {% linkable_title Template condition %}
The template condition will test if the [given template][template] renders a value equal to true. This is achieved by having the template result in a true boolean expression or by having the template render 'true'.
@ -121,7 +121,7 @@ Within an automation, template conditions also have access to the `trigger` vari
[template]: /topics/templating/
[automation-templating]: /getting-started/automation-templating/
#### {% linkable_title Time condition %}
### {% linkable_title Time condition %}
The time condition can test if it is after a specified time, before a specified time or if it is a certain day of the week
@ -138,7 +138,7 @@ weekday:
Valid values for `weekday` are `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun`.
#### {% linkable_title Zone condition %}
### {% linkable_title Zone condition %}
Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the [OwnTracks platform](/components/device_tracker.owntracks/) and the [iCloud platform](/components/device_tracker.icloud/).
@ -148,8 +148,7 @@ entity_id: device_tracker.paulus
zone: zone.home
```
#### {% linkable_title Examples %}
### {% linkable_title Examples %}
```yaml
condition: