-All configuration entries have to be sequential. If you have automation:, automation 2: and automation 4: then the last one will not be processed.
+All configuration entries have to be sequential. If you have automation:,
+automation 2: and automation 4: then the last one will not be processed.
Triggers are what starts the processing of an automation rule. It is possible to specify multiple
triggers for the same rule. Once a trigger starts, Home Assistant will validate the conditions, if any,
@@ -218,7 +220,8 @@ being sent over the topic.
Numeric state trigger
-
On state change of a specified entity, attempts to parse the state as a number and triggers if value is above and/or below a threshold.
+
On state change of a specified entity, attempts to parse the state as a number and triggers if value
+is above and/or below a threshold.
12
@@ -261,7 +264,8 @@ being sent over the topic.
- Use quotes around your values for from and to to avoid the YAML parser interpreting some values as booleans.
+ Use quotes around your values for from and to to avoid the YAML parser
+ interpreting some values as booleans.
@@ -290,8 +294,8 @@ being sent over the topic.
Time can be triggered in many ways. The most common is to specify after and trigger at a specific
point in time each day. Alternatively, you can also match if the hour, minute or second of the current
-time has a specifc value. For example, by only setting minutes in the config to 5 it will trigger every
-hour when it is 5 minutes past whole.
+time has a specific value. For example, by only setting minutes in the config to 5 it will trigger every
+hour when it is 5 minutes past whole. You cannot use after together with hour, minute or second.
12
@@ -303,20 +307,31 @@ hour when it is 5 minutes past whole.
8910
+11
+12
+13
automation:trigger:platform:time# All following are optional.# When 'after' is used, you cannot also match on hour, minute, seconds.# Military time format.
-after:"15:32:00"
-hours:10
+# after: "15:32:00"
+hours:0minutes:5seconds:0
+weekday:
+-sat
+-sun
-
Conditions
+
You can use weekday to limit the trigger times to speific days as well (also available in conditions).
+Valid values for weekday are (sun, mon, tue, wed, thu, fri & sat)
+
+
The above example will trigger on Saturday and Sunday every hour on the 5 (2:05, 3:05, 4:05, etc).
+
+
Conditions
Conditions are an optional part of an automation rule and be used to prevent an action from happening
when triggered. Conditions look very familiar to triggers but are very different. A trigger will look
@@ -387,7 +402,7 @@ below a threshold.
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.
+certain day of the week
12
@@ -412,7 +427,9 @@ certain day of the week.
-
Actions
+
Valid values for weekday are (sun, mon, tue, wed, thu, fri & sat)
+
+
Actions
When an automation rule fires, it calls a service. For this service you can specify an entity id it
should apply to and optional service parameters (to specify for example the brightness).
@@ -461,6 +478,27 @@ should apply to and optional service parameters (to specify for example the brig
script component. If you want to describe how certain entities should look,
check out the scene component.
+
Troubleshooting
+
+
You can verify that your automation rules are being initialized correctly by watching both the realtime
+logs and also the logbook. The realtime logs will show the rules being initialized (once for each trigger):
+
+
1
+2
+3
+4
+
INFO [homeassistant.components.automation] Initialized rule Rainy Day
+INFO [homeassistant.components.automation] Initialized rule Rainy Day
+INFO [homeassistant.components.automation] Initialized rule Rainy Day
+INFO [homeassistant.components.automation] Initialized rule Rain is over
+
+
+
+
The Logbook component will show a line entry when an automation is triggered. You can look at the
+previous entry to determine which trigger in the rule triggered the event.
+
+
+
diff --git a/components/device_tracker.nmap_scanner.html b/components/device_tracker.nmap_scanner.html
index f9b9d86655..06afb8c6e4 100644
--- a/components/device_tracker.nmap_scanner.html
+++ b/components/device_tracker.nmap_scanner.html
@@ -114,12 +114,16 @@ As an alternative to the router-based device tracking, it is possible to directl
234
+5
# Example configuration.yaml entry
device_tracker:
platform: nmap_tracker
- hosts: 192.168.1.1/24
+ hosts: 192.168.1.1/24
+ home_interval: 10
+
home_interval is an optional value set in minutes. This will be the number of minutes to exclude devices from a scan while they are home. This is useful for iOS users that are experiencing issues where thier iDevices drop off the network for periods in order to save battery life.
